diff --git a/docs/docs-ref-autogen/outlook/outlook/office.mailbox.yml b/docs/docs-ref-autogen/outlook/outlook/office.mailbox.yml index 75817a7eb..0ccf29c74 100644 --- a/docs/docs-ref-autogen/outlook/outlook/office.mailbox.yml +++ b/docs/docs-ref-autogen/outlook/outlook/office.mailbox.yml @@ -586,15 +586,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1884,15 +1883,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1979,16 +1977,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -2043,15 +2053,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -2087,16 +2096,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2450,15 +2471,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -2471,16 +2491,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2688,15 +2720,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 eaf007047..24672b88f 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 @@ -642,15 +642,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -686,16 +685,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -908,15 +919,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -929,16 +939,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1007,15 +1029,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 ca5d3f426..8c6b7676e 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 @@ -586,15 +586,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1884,15 +1883,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1979,16 +1977,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -2043,15 +2053,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -2087,16 +2096,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2330,15 +2351,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -2351,16 +2371,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2429,15 +2461,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 5e7b433a0..b24fc49c2 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 @@ -586,15 +586,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1884,15 +1883,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1979,16 +1977,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -2043,15 +2053,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -2087,16 +2096,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2330,15 +2351,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -2351,16 +2371,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2429,15 +2461,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 4534da825..647b00291 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 @@ -586,15 +586,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1884,15 +1883,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1979,16 +1977,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -2043,15 +2053,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -2087,16 +2096,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2330,15 +2351,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -2351,16 +2371,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2429,15 +2461,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 fb522b064..869993d2f 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 @@ -586,15 +586,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1884,15 +1883,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1979,16 +1977,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -2043,15 +2053,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -2087,16 +2096,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2450,15 +2471,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -2471,16 +2491,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2549,15 +2581,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 9103dfdf8..85ebe50ff 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 @@ -586,15 +586,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1884,15 +1883,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1979,16 +1977,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -2043,15 +2053,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -2087,16 +2096,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2450,15 +2471,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -2471,16 +2491,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2549,15 +2581,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 eaf007047..24672b88f 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 @@ -642,15 +642,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -686,16 +685,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -908,15 +919,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -929,16 +939,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1007,15 +1029,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 d9ef61674..b34fab21b 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 @@ -309,15 +309,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -815,15 +814,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -859,16 +857,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -1081,15 +1091,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -1102,16 +1111,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1180,15 +1201,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 d9ef61674..b34fab21b 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 @@ -309,15 +309,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -815,15 +814,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -859,16 +857,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -1081,15 +1091,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -1102,16 +1111,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1180,15 +1201,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 0a10ecfea..517d8a222 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 @@ -502,15 +502,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1007,15 +1006,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1102,16 +1100,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -1166,15 +1176,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -1210,16 +1219,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1453,15 +1474,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -1474,16 +1494,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1552,15 +1584,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 cbc0a3c48..5fce8932b 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 @@ -502,15 +502,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1121,15 +1120,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1216,16 +1214,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -1280,15 +1290,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -1324,16 +1333,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1567,15 +1588,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -1588,16 +1608,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1666,15 +1698,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 ed18261a4..d37ef0fd3 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 @@ -502,15 +502,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1121,15 +1120,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1216,16 +1214,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -1280,15 +1290,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -1324,16 +1333,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1567,15 +1588,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -1588,16 +1608,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1666,15 +1698,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 3c20844df..08517ba6a 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 @@ -586,15 +586,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1205,15 +1204,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1300,16 +1298,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -1364,15 +1374,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -1408,16 +1417,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1651,15 +1672,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -1672,16 +1692,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -1750,15 +1782,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 904cfd430..48b7fe46c 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 @@ -586,15 +586,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - This method isn't supported in Outlook on Android or on iOS. For more information on supported APIs in Outlook @@ -1884,15 +1883,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The Outlook REST v2.0 and beta endpoints are now deprecated. However, privately released and AppSource-hosted @@ -1979,16 +1977,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + property to view details about the error. - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `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). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` isPreview: false isDeprecated: false syntax: @@ -2043,15 +2053,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - You can pass both the token and either an attachment identifier or item identifier to an external system. That @@ -2087,16 +2096,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). - - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for - more information. + - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `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 [FAQ page](https://aka.ms/naafaq). + + + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2330,15 +2351,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - The `getUserIdentityTokenAsync` method returns a token that you can use to identify and [authenticate the add-in @@ -2351,16 +2371,28 @@ methods: **Errors**: - - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error - code. + If your call fails, use the + [asyncResult.diagnostics](https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member) + 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 [FAQ + page](https://aka.ms/naafaq). + + + - `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. + - `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 [FAQ page](https://aka.ms/naafaq). - - `NetworkError`: The user is no longer connected to the network. Please check your network connection and - try again. + - `NetworkError: The user is no longer connected to the network. Please check your network connection and try + again.` #### Examples @@ -2429,15 +2461,14 @@ methods: **Important**: - - In October 2024, legacy Exchange [user + - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens - going forward. For more information, see our [blog post](https://aka.ms/NAApreviewblog) and [FAQ - page](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens). + 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). - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set 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 169585f62..95d0ed773 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 @@ -2613,12 +2613,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -2643,11 +2642,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -2737,12 +2745,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -2751,11 +2758,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -2778,12 +2794,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 68fc740cd..7e2092ca6 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 @@ -5964,12 +5964,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6481,12 +6480,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -6546,11 +6544,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -6577,12 +6584,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -6607,11 +6613,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -6701,12 +6716,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6715,11 +6729,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -6742,12 +6765,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 2d5b60741..e813d3d09 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 @@ -5976,12 +5976,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6493,12 +6492,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -6558,11 +6556,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -6589,12 +6596,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -6619,11 +6625,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -6713,12 +6728,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6727,11 +6741,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -6754,12 +6777,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 5d9294490..4b936fd6c 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 @@ -5976,12 +5976,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6493,12 +6492,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -6558,11 +6556,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -6589,12 +6596,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -6619,11 +6625,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -6713,12 +6728,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6727,11 +6741,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -6754,12 +6777,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 4225c2788..76de6e60f 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 @@ -6175,12 +6175,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6692,12 +6691,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -6757,11 +6755,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -6788,12 +6795,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -6818,11 +6824,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -6954,12 +6969,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6968,11 +6982,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -6995,12 +7018,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 b762982a8..b4f386dcc 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 @@ -6286,12 +6286,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6803,12 +6802,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -6868,11 +6866,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -6899,12 +6906,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -6929,11 +6935,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -7065,12 +7080,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -7079,11 +7093,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -7106,12 +7129,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 14c9a8a66..614490bab 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 @@ -2736,12 +2736,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -2766,11 +2765,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -2860,12 +2868,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -2874,11 +2881,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -2901,12 +2917,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 b8fa889c1..4633836f2 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 @@ -2920,12 +2920,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -3114,12 +3113,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -3144,11 +3142,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -3238,12 +3245,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -3252,11 +3258,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -3279,12 +3294,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 6b63f77c4..b31409a29 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 @@ -2920,12 +2920,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -3114,12 +3113,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -3144,11 +3142,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -3238,12 +3245,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -3252,11 +3258,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -3279,12 +3294,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 96bbfe3cc..b1b15ccd0 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 @@ -2986,12 +2986,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -3179,12 +3178,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -3244,11 +3242,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -3275,12 +3282,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -3305,11 +3311,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -3399,12 +3414,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -3413,11 +3427,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -3440,12 +3463,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 895ab9c4d..1870f4f38 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 @@ -3039,12 +3039,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -3278,12 +3277,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -3343,11 +3341,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -3374,12 +3381,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -3404,11 +3410,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -3498,12 +3513,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -3512,11 +3526,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -3539,12 +3562,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 60a39f217..9ef73d10c 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 @@ -4102,12 +4102,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -4341,12 +4340,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -4406,11 +4404,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -4437,12 +4444,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -4467,11 +4473,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -4561,12 +4576,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -4575,11 +4589,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -4602,12 +4625,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 4c9e3d6e7..3219010a0 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 @@ -5465,12 +5465,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -5704,12 +5703,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -5769,11 +5767,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -5800,12 +5807,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -5830,11 +5836,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -5924,12 +5939,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -5938,11 +5952,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -5965,12 +5988,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 f638ff3b4..1e81ef680 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 @@ -5672,12 +5672,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6189,12 +6188,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -6254,11 +6252,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -6285,12 +6292,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -6315,11 +6321,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -6409,12 +6424,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -6423,11 +6437,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -6450,12 +6473,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 73d879840..c0709a11d 100644 --- a/generate-docs/api-extractor-inputs-outlook/outlook.d.ts +++ b/generate-docs/api-extractor-inputs-outlook/outlook.d.ts @@ -8374,12 +8374,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -8891,12 +8890,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -8956,11 +8954,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -8987,12 +8994,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -9017,11 +9023,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -9153,12 +9168,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -9167,11 +9181,20 @@ export declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -9264,12 +9287,11 @@ export declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 9d0de9db8..f62276b33 100644 --- a/generate-docs/script-inputs/office.d.ts +++ b/generate-docs/script-inputs/office.d.ts @@ -15024,12 +15024,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -15541,12 +15540,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -15606,11 +15604,20 @@ declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -15637,12 +15644,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -15667,11 +15673,20 @@ declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -15803,12 +15818,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -15817,11 +15831,20 @@ declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -15844,12 +15867,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 26765f3e5..af4339b36 100644 --- a/generate-docs/script-inputs/office_preview.d.ts +++ b/generate-docs/script-inputs/office_preview.d.ts @@ -17164,12 +17164,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -17681,12 +17680,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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 @@ -17746,11 +17744,20 @@ declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * property to view details about the error. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param options - An object literal that contains one or more of the following properties:- * `isRest`: Determines if the token provided will be used for the Outlook REST APIs or Exchange Web Services. Default value is `false`. @@ -17777,12 +17784,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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) @@ -17807,11 +17813,20 @@ declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. * - * - `InternalServerError`: The Exchange server returned an error. Please look at the diagnostics object for more information. + * - `HTTPRequestFailure: The request has failed. Please look at the diagnostics object for the HTTP error code.` * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `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}. + * + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. The token is returned as a string in the `asyncResult.value` property. @@ -17943,12 +17958,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - 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}. @@ -17957,11 +17971,20 @@ declare namespace Office { * * **Errors**: * - * - `HTTPRequestFailure`: The request has failed. Please look at the diagnostics object for the HTTP error code. + * If your call fails, use the {@link https://learn.microsoft.com/javascript/api/office/office.asyncresult#office-office-asyncresult-diagnostics-member | asyncResult.diagnostics} + * 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}. + * + * - `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. + * - `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}. * - * - `NetworkError`: The user is no longer connected to the network. Please check your network connection and try again. + * - `NetworkError: The user is no longer connected to the network. Please check your network connection and try again.` * * @param callback - When the method completes, the function passed in the callback parameter is called with a single parameter of * type `Office.AsyncResult`. @@ -18054,12 +18077,11 @@ declare namespace Office { * * **Important**: * - * - In October 2024, legacy Exchange {@link https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token | user identity} and + * - In February 2025, 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 will be turned off by default for all Exchange Online 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 is the recommended approach for tokens going forward. For more information, see our {@link https://aka.ms/NAApreviewblog | blog post} and - * {@link https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens | FAQ page}. + * Nested app authentication (NAA) is the recommended approach for tokens going forward. For more information, see the {@link https://aka.ms/naafaq | FAQ page}. * * - To enable the `makeEwsRequestAsync` method to make EWS requests, the server administrator must set `OAuthAuthentication` to `true` on the * Client Access Server EWS directory .