Skip to content

[All hosts] Get latest #2421

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 7, 2025
Merged

[All hosts] Get latest #2421

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
158 changes: 73 additions & 85 deletions docs/docs-ref-autogen/outlook/outlook/office.mailbox.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -659,20 +659,17 @@ methods:
**Important**:


- Legacy Exchange tokens are deprecated. Legacy Exchange [user
identity](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and
[callback](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
tokens have been turned off by default for most Exchange Online tenants.
Administrators can reenable legacy tokens for tenants and add-ins until
June 2025. In October 2025, legacy tokens will be completely turned off
for all tenants. This is part of [Microsoft's Secure Future
Initiative](https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/)<!--
-->, which gives organizations the tools needed to respond to the current
threat landscape. Exchange user identity tokens will still work for
Exchange on-premises. Nested app authentication (NAA) is the recommended
approach for tokens going forward. For more information, see the [FAQ
page](https://aka.ms/naafaq)<!-- -->.
- Legacy Exchange Online [user identity
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and [callback
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
are no longer supported and are turned off across all Microsoft 365
tenants. If an Outlook add-in requires delegated user access or user
identity, we recommend using [MSAL (Microsoft Authentication Library) and
nested app authentication
(NAA)](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)<!--
-->. Exchange user identity tokens are still supported for Exchange
on-premises.


- This method isn't supported in Outlook on Android or on iOS. For more
Expand Down Expand Up @@ -2196,20 +2193,17 @@ methods:
**Important**:


- Legacy Exchange tokens are deprecated. Legacy Exchange [user
identity](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and
[callback](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
tokens have been turned off by default for most Exchange Online tenants.
Administrators can reenable legacy tokens for tenants and add-ins until
June 2025. In October 2025, legacy tokens will be completely turned off
for all tenants. This is part of [Microsoft's Secure Future
Initiative](https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/)<!--
-->, which gives organizations the tools needed to respond to the current
threat landscape. Exchange user identity tokens will still work for
Exchange on-premises. Nested app authentication (NAA) is the recommended
approach for tokens going forward. For more information, see the [FAQ
page](https://aka.ms/naafaq)<!-- -->.
- Legacy Exchange Online [user identity
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and [callback
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
are no longer supported and are turned off across all Microsoft 365
tenants. If an Outlook add-in requires delegated user access or user
identity, we recommend using [MSAL (Microsoft Authentication Library) and
nested app authentication
(NAA)](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)<!--
-->. Exchange user identity tokens are still supported for Exchange
on-premises.


- The Outlook REST v2.0 and beta endpoints are now deprecated. However,
Expand Down Expand Up @@ -2322,9 +2316,9 @@ methods:
- `GenericTokenError: An internal error has occurred.` - In Exchange
Online environments, this error occurs when the token can't be retrieved
because legacy Exchange tokens for Outlook add-ins are turned off. We
recommend using NAA as a single sign-on solution for your add-in. For
guidance on how to implement NAA, see the [FAQ
page](https://aka.ms/naafaq)<!-- -->.
recommend using
[NAA](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)
as a single sign-on solution for your add-in.


- `HTTPRequestFailure: The request has failed. Please look at the
Expand All @@ -2335,8 +2329,9 @@ methods:
at the diagnostics object for more information.` - In Exchange Online
environments, this error occurs when the token can't be retrieved because
legacy Exchange tokens for Outlook add-ins are turned off. We recommend
using NAA as a single sign-on solution for your add-in. For guidance on
how to implement NAA, see the [FAQ page](https://aka.ms/naafaq)<!-- -->.
using
[NAA](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)
as a single sign-on solution for your add-in.


- `NetworkError: The user is no longer connected to the network. Please
Expand Down Expand Up @@ -2408,20 +2403,17 @@ methods:
**Important**:


- Legacy Exchange tokens are deprecated. Legacy Exchange [user
identity](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and
[callback](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
tokens have been turned off by default for most Exchange Online tenants.
Administrators can reenable legacy tokens for tenants and add-ins until
June 2025. In October 2025, legacy tokens will be completely turned off
for all tenants. This is part of [Microsoft's Secure Future
Initiative](https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/)<!--
-->, which gives organizations the tools needed to respond to the current
threat landscape. Exchange user identity tokens will still work for
Exchange on-premises. Nested app authentication (NAA) is the recommended
approach for tokens going forward. For more information, see the [FAQ
page](https://aka.ms/naafaq)<!-- -->.
- Legacy Exchange Online [user identity
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and [callback
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
are no longer supported and are turned off across all Microsoft 365
tenants. If an Outlook add-in requires delegated user access or user
identity, we recommend using [MSAL (Microsoft Authentication Library) and
nested app authentication
(NAA)](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)<!--
-->. Exchange user identity tokens are still supported for Exchange
on-premises.


- You can pass both the token and either an attachment identifier or item
Expand Down Expand Up @@ -2474,9 +2466,9 @@ methods:
- `GenericTokenError: An internal error has occurred.` - In Exchange
Online environments, this error occurs when the token can't be retrieved
because legacy Exchange tokens for Outlook add-ins are turned off. We
recommend using NAA as a single sign-on solution for your add-in. For
guidance on how to implement NAA, see the [FAQ
page](https://aka.ms/naafaq)<!-- -->.
recommend using
[NAA](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)
as a single sign-on solution for your add-in.


- `HTTPRequestFailure: The request has failed. Please look at the
Expand All @@ -2487,8 +2479,9 @@ methods:
at the diagnostics object for more information.` - In Exchange Online
environments, this error occurs when the token can't be retrieved because
legacy Exchange tokens for Outlook add-ins are turned off. We recommend
using NAA as a single sign-on solution for your add-in. For guidance on
how to implement NAA, see the [FAQ page](https://aka.ms/naafaq)<!-- -->.
using
[NAA](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)
as a single sign-on solution for your add-in.


- `NetworkError: The user is no longer connected to the network. Please
Expand Down Expand Up @@ -2903,20 +2896,17 @@ methods:
**Important**:


- Legacy Exchange tokens are deprecated. Legacy Exchange [user
identity](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and
[callback](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
tokens have been turned off by default for most Exchange Online tenants.
Administrators can reenable legacy tokens for tenants and add-ins until
June 2025. In October 2025, legacy tokens will be completely turned off
for all tenants. This is part of [Microsoft's Secure Future
Initiative](https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/)<!--
-->, which gives organizations the tools needed to respond to the current
threat landscape. Exchange user identity tokens will still work for
Exchange on-premises. Nested app authentication (NAA) is the recommended
approach for tokens going forward. For more information, see the [FAQ
page](https://aka.ms/naafaq)<!-- -->.
- Legacy Exchange Online [user identity
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and [callback
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
are no longer supported and are turned off across all Microsoft 365
tenants. If an Outlook add-in requires delegated user access or user
identity, we recommend using [MSAL (Microsoft Authentication Library) and
nested app authentication
(NAA)](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)<!--
-->. Exchange user identity tokens are still supported for Exchange
on-premises.


- The `getUserIdentityTokenAsync` method returns a token that you can use
Expand All @@ -2940,9 +2930,9 @@ methods:
- `GenericTokenError: An internal error has occurred.` - In Exchange
Online environments, this error occurs when the token can't be retrieved
because legacy Exchange tokens for Outlook add-ins are turned off. We
recommend using NAA as a single sign-on solution for your add-in. For
guidance on how to implement NAA, see the [FAQ
page](https://aka.ms/naafaq)<!-- -->.
recommend using
[NAA](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)
as a single sign-on solution for your add-in.


- `HTTPRequestFailure: The request has failed. Please look at the
Expand All @@ -2953,8 +2943,9 @@ methods:
at the diagnostics object for more information.` - In Exchange Online
environments, this error occurs when the token can't be retrieved because
legacy Exchange tokens for Outlook add-ins are turned off. We recommend
using NAA as a single sign-on solution for your add-in. For guidance on
how to implement NAA, see the [FAQ page](https://aka.ms/naafaq)<!-- -->.
using
[NAA](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)
as a single sign-on solution for your add-in.


- `NetworkError: The user is no longer connected to the network. Please
Expand Down Expand Up @@ -3235,20 +3226,17 @@ methods:
**Important**:


- Legacy Exchange tokens are deprecated. Legacy Exchange [user
identity](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and
[callback](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
tokens have been turned off by default for most Exchange Online tenants.
Administrators can reenable legacy tokens for tenants and add-ins until
June 2025. In October 2025, legacy tokens will be completely turned off
for all tenants. This is part of [Microsoft's Secure Future
Initiative](https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/)<!--
-->, which gives organizations the tools needed to respond to the current
threat landscape. Exchange user identity tokens will still work for
Exchange on-premises. Nested app authentication (NAA) is the recommended
approach for tokens going forward. For more information, see the [FAQ
page](https://aka.ms/naafaq)<!-- -->.
- Legacy Exchange Online [user identity
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token)
and [callback
tokens](https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens)
are no longer supported and are turned off across all Microsoft 365
tenants. If an Outlook add-in requires delegated user access or user
identity, we recommend using [MSAL (Microsoft Authentication Library) and
nested app authentication
(NAA)](https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in)<!--
-->. Exchange user identity tokens are still supported for Exchange
on-premises.


- To enable the `makeEwsRequestAsync` method to make EWS requests, the
Expand Down
Loading