diff --git a/docs/docs-ref-autogen/outlook/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook/outlook/office.mailbox.yml index 406d3419be..97c7ea04fa 100644 --- a/docs/docs-ref-autogen/outlook/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook/outlook/office.mailbox.yml @@ -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 @@ -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, @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 diff --git a/docs/docs-ref-autogen/outlook_1_1/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_1/outlook/office.mailbox.yml index 161fbe5e28..c25995c01b 100644 --- a/docs/docs-ref-autogen/outlook_1_1/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_1/outlook/office.mailbox.yml @@ -742,20 +742,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 @@ -808,9 +805,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 @@ -821,8 +818,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 @@ -1072,20 +1070,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 @@ -1109,9 +1104,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 @@ -1122,8 +1117,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 @@ -1204,20 +1200,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 diff --git a/docs/docs-ref-autogen/outlook_1_10/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_10/outlook/office.mailbox.yml index a560c6869a..b3968398e4 100644 --- a/docs/docs-ref-autogen/outlook_1_10/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_10/outlook/office.mailbox.yml @@ -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](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 @@ -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, @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -2759,20 +2752,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 @@ -2796,9 +2786,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 @@ -2809,8 +2799,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 @@ -2891,20 +2882,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 diff --git a/docs/docs-ref-autogen/outlook_1_11/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_11/outlook/office.mailbox.yml index a59b29f889..0e66a24d75 100644 --- a/docs/docs-ref-autogen/outlook_1_11/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_11/outlook/office.mailbox.yml @@ -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](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 @@ -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, @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -2759,20 +2752,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 @@ -2796,9 +2786,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 @@ -2809,8 +2799,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 @@ -2891,20 +2882,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 diff --git a/docs/docs-ref-autogen/outlook_1_12/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_12/outlook/office.mailbox.yml index 991603f526..f573789bbd 100644 --- a/docs/docs-ref-autogen/outlook_1_12/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_12/outlook/office.mailbox.yml @@ -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](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 @@ -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, @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -2759,20 +2752,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 @@ -2796,9 +2786,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 @@ -2809,8 +2799,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 @@ -2891,20 +2882,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 diff --git a/docs/docs-ref-autogen/outlook_1_13/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_13/outlook/office.mailbox.yml index 5a4bc31367..980ef4b67e 100644 --- a/docs/docs-ref-autogen/outlook_1_13/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_13/outlook/office.mailbox.yml @@ -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](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 @@ -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, @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -3035,20 +3026,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 diff --git a/docs/docs-ref-autogen/outlook_1_14/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_14/outlook/office.mailbox.yml index dbb36b06d0..6af1dbcd38 100644 --- a/docs/docs-ref-autogen/outlook_1_14/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_14/outlook/office.mailbox.yml @@ -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](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 @@ -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, @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -3035,20 +3026,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 diff --git a/docs/docs-ref-autogen/outlook_1_15/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_15/outlook/office.mailbox.yml index 0c084c8061..a5a449b67b 100644 --- a/docs/docs-ref-autogen/outlook_1_15/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_15/outlook/office.mailbox.yml @@ -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](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 @@ -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, @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 diff --git a/docs/docs-ref-autogen/outlook_1_2/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_2/outlook/office.mailbox.yml index 161fbe5e28..c25995c01b 100644 --- a/docs/docs-ref-autogen/outlook_1_2/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_2/outlook/office.mailbox.yml @@ -742,20 +742,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 @@ -808,9 +805,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 @@ -821,8 +818,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 @@ -1072,20 +1070,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 @@ -1109,9 +1104,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 @@ -1122,8 +1117,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 @@ -1204,20 +1200,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 diff --git a/docs/docs-ref-autogen/outlook_1_3/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_3/outlook/office.mailbox.yml index eddeff19d8..6cc36ba554 100644 --- a/docs/docs-ref-autogen/outlook_1_3/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_3/outlook/office.mailbox.yml @@ -349,20 +349,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](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 @@ -948,20 +945,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 @@ -1014,9 +1008,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 @@ -1027,8 +1021,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 @@ -1278,20 +1273,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 @@ -1315,9 +1307,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 @@ -1328,8 +1320,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 @@ -1410,20 +1403,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 diff --git a/docs/docs-ref-autogen/outlook_1_4/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_4/outlook/office.mailbox.yml index eddeff19d8..6cc36ba554 100644 --- a/docs/docs-ref-autogen/outlook_1_4/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_4/outlook/office.mailbox.yml @@ -349,20 +349,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](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 @@ -948,20 +945,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 @@ -1014,9 +1008,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 @@ -1027,8 +1021,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 @@ -1278,20 +1273,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 @@ -1315,9 +1307,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 @@ -1328,8 +1320,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 @@ -1410,20 +1403,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 diff --git a/docs/docs-ref-autogen/outlook_1_5/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_5/outlook/office.mailbox.yml index 8fff2cf8be..cff0a6d5da 100644 --- a/docs/docs-ref-autogen/outlook_1_5/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_5/outlook/office.mailbox.yml @@ -568,20 +568,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](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 @@ -1167,20 +1164,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, @@ -1293,9 +1287,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 @@ -1306,8 +1300,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 @@ -1379,20 +1374,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 @@ -1445,9 +1437,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 @@ -1458,8 +1450,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 @@ -1730,20 +1723,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 @@ -1767,9 +1757,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 @@ -1780,8 +1770,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 @@ -1862,20 +1853,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 diff --git a/docs/docs-ref-autogen/outlook_1_6/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_6/outlook/office.mailbox.yml index ade667996e..687e0d62dc 100644 --- a/docs/docs-ref-autogen/outlook_1_6/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_6/outlook/office.mailbox.yml @@ -568,20 +568,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](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 @@ -1300,20 +1297,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, @@ -1426,9 +1420,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 @@ -1439,8 +1433,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 @@ -1512,20 +1507,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 @@ -1578,9 +1570,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 @@ -1591,8 +1583,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 @@ -1863,20 +1856,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 @@ -1900,9 +1890,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 @@ -1913,8 +1903,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 @@ -1995,20 +1986,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 diff --git a/docs/docs-ref-autogen/outlook_1_7/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_7/outlook/office.mailbox.yml index f983a0e469..445d3c0832 100644 --- a/docs/docs-ref-autogen/outlook_1_7/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_7/outlook/office.mailbox.yml @@ -568,20 +568,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](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 @@ -1300,20 +1297,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, @@ -1426,9 +1420,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 @@ -1439,8 +1433,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 @@ -1512,20 +1507,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 @@ -1578,9 +1570,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 @@ -1591,8 +1583,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 @@ -1863,20 +1856,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 @@ -1900,9 +1890,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 @@ -1913,8 +1903,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 @@ -1995,20 +1986,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 diff --git a/docs/docs-ref-autogen/outlook_1_8/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_8/outlook/office.mailbox.yml index de580022e6..77e4cbf2c4 100644 --- a/docs/docs-ref-autogen/outlook_1_8/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_8/outlook/office.mailbox.yml @@ -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](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 @@ -1391,20 +1388,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, @@ -1517,9 +1511,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 @@ -1530,8 +1524,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 @@ -1603,20 +1598,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 @@ -1669,9 +1661,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 @@ -1682,8 +1674,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 @@ -1954,20 +1947,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 @@ -1991,9 +1981,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 @@ -2004,8 +1994,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 @@ -2086,20 +2077,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 diff --git a/docs/docs-ref-autogen/outlook_1_9/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook_1_9/outlook/office.mailbox.yml index 4f1265c5f5..63440c8749 100644 --- a/docs/docs-ref-autogen/outlook_1_9/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook_1_9/outlook/office.mailbox.yml @@ -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](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 @@ -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, @@ -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 @@ -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 @@ -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 @@ -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 @@ -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 @@ -2759,20 +2752,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 @@ -2796,9 +2786,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 @@ -2809,8 +2799,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 @@ -2891,20 +2882,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 diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_1/Outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_1/Outlook.d.ts index a32153fa66..5c682e5f32 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_1/Outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_1/Outlook.d.ts @@ -2714,12 +2714,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -2748,14 +2747,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -2847,12 +2845,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -2865,14 +2862,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -2899,12 +2895,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_10/outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_10/outlook.d.ts index 6fd1fe1f64..ca920f0db9 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_10/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_10/outlook.d.ts @@ -6445,12 +6445,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -6965,12 +6964,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -7034,14 +7032,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7070,12 +7067,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -7104,14 +7100,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7203,12 +7198,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -7221,14 +7215,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7255,12 +7248,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_11/outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_11/outlook.d.ts index bcbf3a4d0f..4ee519b6a5 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_11/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_11/outlook.d.ts @@ -6457,12 +6457,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -6977,12 +6976,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -7046,14 +7044,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7082,12 +7079,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -7116,14 +7112,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7215,12 +7210,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -7233,14 +7227,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7267,12 +7260,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_12/outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_12/outlook.d.ts index 3df835321a..32d269f340 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_12/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_12/outlook.d.ts @@ -6457,12 +6457,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -6977,12 +6976,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -7046,14 +7044,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7082,12 +7079,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -7116,14 +7112,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7215,12 +7210,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -7233,14 +7227,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7267,12 +7260,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_13/outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_13/outlook.d.ts index 348345f1b8..a77b099918 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_13/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_13/outlook.d.ts @@ -6672,12 +6672,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -7192,12 +7191,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -7261,14 +7259,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7297,12 +7294,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -7331,14 +7327,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7472,12 +7467,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -7490,14 +7484,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7524,12 +7517,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_14/outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_14/outlook.d.ts index e2df22b691..da7f573a6f 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_14/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_14/outlook.d.ts @@ -6783,12 +6783,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -7303,12 +7302,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -7372,14 +7370,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7408,12 +7405,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -7442,14 +7438,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7583,12 +7578,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -7601,14 +7595,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -7635,12 +7628,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_15/outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_15/outlook.d.ts index 82bd9f3a03..48848f30d9 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_15/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_15/outlook.d.ts @@ -8676,12 +8676,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -9196,12 +9195,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -9265,14 +9263,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -9301,12 +9298,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -9335,14 +9331,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -9476,12 +9471,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -9494,14 +9488,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -9592,12 +9585,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_2/Outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_2/Outlook.d.ts index 3ba6e7c9bc..009ec78603 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_2/Outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_2/Outlook.d.ts @@ -2837,12 +2837,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -2871,14 +2870,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -2970,12 +2968,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -2988,14 +2985,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3022,12 +3018,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_3/Outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_3/Outlook.d.ts index 41af10a444..542a1cc561 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_3/Outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_3/Outlook.d.ts @@ -3100,12 +3100,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -3294,12 +3293,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -3328,14 +3326,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3427,12 +3424,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -3445,14 +3441,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3479,12 +3474,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_4/Outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_4/Outlook.d.ts index b819ea6ec1..ec27a7f481 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_4/Outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_4/Outlook.d.ts @@ -3100,12 +3100,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -3294,12 +3293,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -3328,14 +3326,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3427,12 +3424,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -3445,14 +3441,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3479,12 +3474,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_5/Outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_5/Outlook.d.ts index 27e867a50c..c2e3819400 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_5/Outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_5/Outlook.d.ts @@ -3331,12 +3331,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -3524,12 +3523,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -3593,14 +3591,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3629,12 +3626,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -3663,14 +3659,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3762,12 +3757,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -3780,14 +3774,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3814,12 +3807,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_6/Outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_6/Outlook.d.ts index 732707ba4d..ab279337c2 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_6/Outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_6/Outlook.d.ts @@ -3384,12 +3384,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -3624,12 +3623,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -3693,14 +3691,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3729,12 +3726,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -3763,14 +3759,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3862,12 +3857,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -3880,14 +3874,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -3914,12 +3907,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_7/Outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_7/Outlook.d.ts index 610c009ef4..a969a9a207 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_7/Outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_7/Outlook.d.ts @@ -4447,12 +4447,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -4687,12 +4686,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -4756,14 +4754,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -4792,12 +4789,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -4826,14 +4822,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -4925,12 +4920,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -4943,14 +4937,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -4977,12 +4970,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_8/outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_8/outlook.d.ts index c80656d1af..c6deae83d3 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_8/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_8/outlook.d.ts @@ -5934,12 +5934,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -6174,12 +6173,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -6243,14 +6241,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -6279,12 +6276,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -6313,14 +6309,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -6412,12 +6407,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -6430,14 +6424,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -6464,12 +6457,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_9/outlook.d.ts b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_9/outlook.d.ts index d02dee93eb..635ebc7a1d 100644 --- a/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_9/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook-release/Outlook_1_9/outlook.d.ts @@ -6147,12 +6147,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -6667,12 +6666,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -6736,14 +6734,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -6772,12 +6769,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -6806,14 +6802,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -6905,12 +6900,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -6923,14 +6917,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -6957,12 +6950,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/api-extractor-inputs-outlook/outlook.d.ts b/generate-docs/api-extractor-inputs-outlook/outlook.d.ts index d826474c96..0af6bd13fc 100644 --- a/generate-docs/api-extractor-inputs-outlook/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook/outlook.d.ts @@ -9080,12 +9080,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -9600,12 +9599,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -9669,14 +9667,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -9705,12 +9702,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -9739,14 +9735,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -9880,12 +9875,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -9898,14 +9892,13 @@ export declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -9996,12 +9989,11 @@ export declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/script-inputs/office.d.ts b/generate-docs/script-inputs/office.d.ts index 689b1e899c..5960cf2159 100644 --- a/generate-docs/script-inputs/office.d.ts +++ b/generate-docs/script-inputs/office.d.ts @@ -17577,12 +17577,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -18097,12 +18096,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -18166,14 +18164,13 @@ declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -18202,12 +18199,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -18236,14 +18232,13 @@ declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -18377,12 +18372,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -18395,14 +18389,13 @@ declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -18493,12 +18486,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory . diff --git a/generate-docs/script-inputs/office_preview.d.ts b/generate-docs/script-inputs/office_preview.d.ts index 1cfd55553d..5e33bab6d0 100644 --- a/generate-docs/script-inputs/office_preview.d.ts +++ b/generate-docs/script-inputs/office_preview.d.ts @@ -17991,12 +17991,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * 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 information on supported APIs in Outlook mobile, see * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/outlook-mobile-apis | Outlook JavaScript APIs supported in Outlook on mobile devices}. @@ -18511,12 +18510,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted add-ins are able to use the REST service * until extended support ends for Outlook 2019 on October 14, 2025. Traffic from these add-ins is automatically identified for exemption. This exemption also @@ -18580,14 +18578,13 @@ declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -18616,12 +18613,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - You can pass both the token and either an attachment identifier or item identifier to an external system. That system uses * the token as a bearer authorization token to call the Exchange Web Services (EWS) @@ -18650,14 +18646,13 @@ declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -18791,12 +18786,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication | authenticate the add-in and user with an external system}. @@ -18809,14 +18803,13 @@ declare namespace Office { * property to view details about the error. * * - `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 - * {@link https://aka.ms/naafaq | FAQ page}. + * for Outlook add-ins are turned off. We recommend using {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * * - `InternalServerError: The Exchange server returned an error. Please look 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 {@link https://aka.ms/naafaq | FAQ page}. + * this error occurs when the token can't be retrieved because legacy Exchange tokens for Outlook add-ins are turned off. We recommend using + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | NAA} as a single sign-on solution for your add-in. * * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * @@ -18907,12 +18900,11 @@ declare namespace Office { * * **Important**: * - * - Legacy Exchange tokens are deprecated. Legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | callback} 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 {@link https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/ | Microsoft's Secure Future Initiative}, - * 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 {@link https://aka.ms/naafaq | FAQ page}. + * - Legacy Exchange Online {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity tokens} and + * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens | 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 + * {@link https://learn.microsoft.com/office/dev/add-ins/develop/enable-nested-app-authentication-in-your-add-in | MSAL (Microsoft Authentication Library) and nested app authentication (NAA)}. + * Exchange user identity tokens are still supported for Exchange on-premises. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory .