Update remarks

samantharamon · samantharamon · commit 36481310cf34 · 2025-07-31T13:16:08.000-07:00
diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md
@@ -89,8 +89,8 @@ Legacy Exchange tokens include Exchange user identity and callback tokens.
 
 **Important**:
 
+- Beginning August 1 2025 through September 2025, legacy Exchange Online tokens will be turned off for all organizations. Once turned off, you can no longer use the _AllowLegacyExchangeTokens_ parameter on the **Set-AuthenticationPolicy** cmdlet to turn on these tokens. To determine if legacy tokens have been turned off for your organization, run `Get-AuthenticationPolicy -AllowLegacyExchangeTokens`. If legacy tokens have been turned off, the "Legacy Exchange Online tokens are disabled" warning is shown. To request an exception, [create a request through Microsoft Support](https://aka.ms/LegacyTokensByOctober). For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens).
 - The AllowLegacyExchangeTokens switch returns `Not Set` if tokens haven't been explicitly allowed or blocked in your organization using the _AllowLegacyExchangeTokens_ or _BlockLegacyExchangeTokens_ parameters on the **Set-AuthenticationPolicy** cmdlet. For more information, see [Get the status of legacy Exchange Online tokens and add-ins that use them](https://learn.microsoft.com/office/dev/add-ins/outlook/turn-exchange-tokens-on-off#get-the-status-of-legacy-exchange-online-tokens-and-add-ins-that-use-them).
-- As of February 17 2025, legacy Exchange tokens are blocked by default in all cloud-based organizations. Although tokens are blocked by default, the AllowLegacyExchangeTokens switch still returns `Not Set` if you haven't used the _AllowLegacyExchangeTokens_ or _BlockLegacyExchangeTokens_ parameters on the **Set-AuthenticationPolicy** cmdlet. For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens).
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md
@@ -87,10 +87,10 @@ This switch applies to the entire organization. The Identity parameter is requir
 
 **Important**:
 
+- Beginning August 1 2025 through September 2025, legacy Exchange Online tokens will be turned off for all organizations. Once turned off, you can no longer use the _AllowLegacyExchangeTokens_ parameter on the **Set-AuthenticationPolicy** cmdlet to turn on these tokens. To determine if legacy tokens have been turned off for your organization, run `Get-AuthenticationPolicy -AllowLegacyExchangeTokens`. If legacy tokens have been turned off, the "Legacy Exchange Online tokens are disabled" warning is shown. To request an exception, [create a request through Microsoft Support](https://aka.ms/LegacyTokensByOctober). For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens).
 - Apart from the Identity parameter, this switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes.
 - It might take up to 24 hours for the change to take effect across your entire organization.
 - Legacy Exchange tokens issued to Outlook add-ins before token blocking was implemented in your organization will remain valid until they expire.
-- As of February 17 2025, legacy Exchange tokens are blocked by default in all cloud-based organizations. For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens).
 
 ```yaml
 Type: SwitchParameter
diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md
@@ -397,11 +397,7 @@ Legacy Exchange tokens include Exchange user identity and callback tokens.
 
 The switch applies to the entire organization. The Identity parameter is required and must be set to the value "LegacyExchangeTokens". Specific authentication policies can't be applied.
 
-**Important**:
-
-- Apart from the Identity parameter, this switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes.
-- It might take up to 24 hours for the change to take effect across your entire organization.
-- As of February 17 2025, legacy Exchange tokens are blocked by default in all cloud-based organizations. For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens).
+**Important**: Beginning August 1 2025 through September 2025, legacy Exchange Online tokens will be turned off for all organizations. Once turned off, you can no longer use the _AllowLegacyExchangeTokens_ parameter on the **Set-AuthenticationPolicy** cmdlet to turn on these tokens. To determine if legacy tokens have been turned off for your organization, run `Get-AuthenticationPolicy -AllowLegacyExchangeTokens`. If legacy tokens have been turned off, the "Legacy Exchange Online tokens are disabled" warning is shown. To request an exception, [create a request through Microsoft Support](https://aka.ms/LegacyTokensByOctober). For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens).
 
 ```yaml
 Type: SwitchParameter
@@ -613,11 +609,9 @@ The switch applies to the entire organization. The Identity parameter is require
 
 **Important**:
 
-- Apart from the Identity parameter, this switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes.
-- It might take up to 24 hours for the change to take effect across your entire organization.
+- Beginning August 1 2025 through September 2025, legacy Exchange Online tokens will be turned off for all organizations. Once turned off, you can no longer use the _AllowLegacyExchangeTokens_ parameter on the **Set-AuthenticationPolicy** cmdlet to turn on these tokens. To determine if legacy tokens have been turned off for your organization, run `Get-AuthenticationPolicy -AllowLegacyExchangeTokens`. If legacy tokens have been turned off, the "Legacy Exchange Online tokens are disabled" warning is shown. To request an exception, [create a request through Microsoft Support](https://aka.ms/LegacyTokensByOctober). For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens).
 - Legacy Exchange tokens issued to Outlook add-ins before token blocking was implemented in your organization will remain valid until they expire.
 - Blocking legacy Exchange tokens might cause some Microsoft add-ins to stop working. These add-ins are being updated to no longer use legacy tokens.
-- As of February 17 2025, legacy Exchange tokens are blocked by default in all cloud-based organizations. For more information, see [Nested app authentication and Outlook legacy tokens deprecation FAQ](https://learn.microsoft.com/office/dev/add-ins/outlook/faq-nested-app-auth-outlook-legacy-tokens#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens).
 
 ```yaml
 Type: SwitchParameter
