Update Set-AuthenticationPolicy.md

Author: chrisda

exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md

@@ -397,7 +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**: Legacy Exchange Online tokens will be turned off for all organizations from August 2025 through September 2025. Once turned off, you can't use the _AllowLegacyExchangeTokens_ switch on the **Set-AuthenticationPolicy** cmdlet to turn on these tokens. If you receive the error "Legacy Exchange Online tokens are disabled" when you run the command `Get-AuthenticationPolicy -AllowLegacyExchangeTokens`, you can request an exception by [creatin 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).
+**Important**: Legacy Exchange Online tokens will be turned off for all organizations from August 2025 through September 2025. Once turned off, you can't use the _AllowLegacyExchangeTokens_ switch on the **Set-AuthenticationPolicy** cmdlet to turn on these tokens. If you receive the error "Legacy Exchange Online tokens are disabled" when you run the command `Get-AuthenticationPolicy -AllowLegacyExchangeTokens`, you can [contact Microsoft Support to request an exception](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).
 
 ```yaml
 Type: SwitchParameter
@@ -609,7 +609,7 @@ The switch applies to the entire organization. The Identity parameter is require
 
 **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).
+- Legacy Exchange Online tokens will be turned off for all organizations from August 2025 through September 2025. Once turned off, you can't use the _AllowLegacyExchangeTokens_ switch on the **Set-AuthenticationPolicy** cmdlet to turn on these tokens. If you receive the error "Legacy Exchange Online tokens are disabled" when you run the command `Get-AuthenticationPolicy -AllowLegacyExchangeTokens`, you can [contact Microsoft Support to request an exception](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).
 - 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.