From 847593a79c1706c1a33caaf3813db080740dd66d Mon Sep 17 00:00:00 2001 From: hfukumotoms <100330338+hfukumotoms@users.noreply.github.com> Date: Mon, 7 Jul 2025 09:55:42 +0900 Subject: [PATCH 01/14] Update SamAccountName description The explanation "The maximum length is 20 characters." has been removed. This explanation applies to user objects (Set-Mailbox), and it is possible to set a SamAccountName longer than 20 characters for group objects. In fact, in Exchange Server 2016 and 2019, you can create groups with a SamAccountName longer than 20 characters using the Set-DistributionGroup. (Set-Mailbox will fail with an error.) --- exchange/exchange-ps/exchange/Set-DistributionGroup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Set-DistributionGroup.md b/exchange/exchange-ps/exchange/Set-DistributionGroup.md index 7d84dcf397..918556255a 100644 --- a/exchange/exchange-ps/exchange/Set-DistributionGroup.md +++ b/exchange/exchange-ps/exchange/Set-DistributionGroup.md @@ -1547,7 +1547,7 @@ Accept wildcard characters: False ### -SamAccountName This parameter is available only in on-premises Exchange. -The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). The maximum length is 20 characters. +The SamAccountName parameter (also known as the pre-Windows 2000 user account or group name) specifies an object identifier that's compatible with older versions of Microsoft Windows client and server operating systems. The value can contain letters, numbers, spaces, periods (.), and the following characters: !, #, $, %, ^, &, -, \_, {, }, and ~. The last character can't be a period. Unicode characters are allowed, but accented characters may generate collisions (for example, o and ö match). ```yaml Type: String From 36481310cf349a22e0fb7c6ceaf396a1b57a61d1 Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Tue, 29 Jul 2025 18:22:26 -0700 Subject: [PATCH 02/14] Update remarks --- .../ExchangePowerShell/Get-AuthenticationPolicy.md | 2 +- .../ExchangePowerShell/Remove-AuthenticationPolicy.md | 2 +- .../ExchangePowerShell/Set-AuthenticationPolicy.md | 10 ++-------- 3 files changed, 4 insertions(+), 10 deletions(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md index bd25769376..2dcc1d6a9f 100644 --- 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 index 9e29dc960a..fe1c9a4745 100644 --- 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 index dfbc58bcc8..680f7284de 100644 --- 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 From 1420b4be78d53ed8c1d080fa2fcbae325015721e Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Tue, 29 Jul 2025 18:24:32 -0700 Subject: [PATCH 03/14] Fix link --- .../ExchangePowerShell/Get-AuthenticationPolicy.md | 2 +- .../ExchangePowerShell/Remove-AuthenticationPolicy.md | 2 +- .../ExchangePowerShell/Set-AuthenticationPolicy.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md index 2dcc1d6a9f..e884da99ad 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md @@ -89,7 +89,7 @@ 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). +- 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). - 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). ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md index fe1c9a4745..5039b89140 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md @@ -87,7 +87,7 @@ 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). +- 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). - 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. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md index 680f7284de..6a05ec9517 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md +++ b/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**: 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). +**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). ```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#what-is-the-timeline-for-shutting-down-legacy-exchange-online-tokens). +- 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 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. From 0a48a28ed21d2cae1b48bf7b79907b7c81449a0e Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 29 Jul 2025 22:51:26 -0700 Subject: [PATCH 04/14] Update Get-AuthenticationPolicy.md --- .../exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md index e884da99ad..81612d27bc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md @@ -89,7 +89,7 @@ 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). +- 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). - 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). ```yaml From 6640475b7b80dc7c328cd13d3ca9a9e4c9466fd9 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 29 Jul 2025 22:51:52 -0700 Subject: [PATCH 05/14] Update Remove-AuthenticationPolicy.md --- .../ExchangePowerShell/Remove-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md index 5039b89140..563b4a66cb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md @@ -87,7 +87,7 @@ 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). +- 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). - 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. From 96db926a32be9847fd2817928224d9024ddc0d71 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 29 Jul 2025 22:52:28 -0700 Subject: [PATCH 06/14] Update Set-AuthenticationPolicy.md --- .../exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md index 6a05ec9517..5647c0e8e1 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md +++ b/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**: 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). +**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). ```yaml Type: SwitchParameter From 07d9060c8f7f21c25dfb6dace9319a6ab3d6b91d Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 29 Jul 2025 22:55:45 -0700 Subject: [PATCH 07/14] Update Set-AuthenticationPolicy.md --- .../ExchangePowerShell/Set-AuthenticationPolicy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md index 5647c0e8e1..ae29e2ea8c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md +++ b/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. From 1db7e5f485e0eb79cdb0958fffb3748bac9775ac Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 29 Jul 2025 22:56:11 -0700 Subject: [PATCH 08/14] Update Get-AuthenticationPolicy.md --- .../exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md index 81612d27bc..e1849983c9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md @@ -89,7 +89,7 @@ Legacy Exchange tokens include Exchange user identity and callback 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 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). +- 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). - 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). ```yaml From d921def8692ffb4d57dd21bae5361cabd5dc974c Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 29 Jul 2025 22:56:54 -0700 Subject: [PATCH 09/14] Update Remove-AuthenticationPolicy.md --- .../ExchangePowerShell/Remove-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md index 563b4a66cb..f63ce1e750 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md @@ -87,7 +87,7 @@ This switch applies to the entire organization. The Identity parameter is requir **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). +- 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). - 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. From e5c640ef0cb66e2f34724c55ae44a5f716e62e49 Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Thu, 31 Jul 2025 13:27:48 -0700 Subject: [PATCH 10/14] Fix merge conflicts and apply suggestions from review --- .../ExchangePowerShell/Get-AuthenticationPolicy.md | 2 +- .../ExchangePowerShell/Remove-AuthenticationPolicy.md | 2 +- .../ExchangePowerShell/Set-AuthenticationPolicy.md | 10 ++++++++-- 3 files changed, 10 insertions(+), 4 deletions(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md index e1849983c9..45f5dbff7f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md @@ -89,7 +89,7 @@ Legacy Exchange tokens include Exchange user identity and callback 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). +- 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. You'll receive the warning "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). - 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). ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md index f63ce1e750..e382cc030a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md @@ -87,7 +87,7 @@ This switch applies to the entire organization. The Identity parameter is requir **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). +- 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. You'll receive the warning "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). - 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. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md index ae29e2ea8c..3d7881c18a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md @@ -397,7 +397,11 @@ 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 [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). +**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. You'll receive the warning "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). +- 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. ```yaml Type: SwitchParameter @@ -609,7 +613,9 @@ The switch applies to the entire organization. The Identity parameter is require **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). +- 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. You'll receive the warning "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). +- 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. - 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. From 37f3196720d90dfa001f4327fc288216bd30e702 Mon Sep 17 00:00:00 2001 From: Mandar <83323280+mshahane@users.noreply.github.com> Date: Fri, 1 Aug 2025 09:22:10 +0900 Subject: [PATCH 11/14] Update Disable-App.md Confirmed with the PG in below ADO issue that even if admin disabled default app by Disable-App cmdlet, it gets enabled automatically once user access the app thereafter. https://o365exchange.visualstudio.com/DefaultCollection/O365%20Core/_workitems/edit/5593477 Therefore, mentioning the same to avoid confusion at customer side (There are already similar SRs in the past from time to time). --- exchange/exchange-ps/ExchangePowerShell/Disable-App.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md index e2b6811c5f..ace0db7319 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Disable-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Disable-App.md @@ -60,6 +60,8 @@ Disable-App -Identity 545d8236-721a-468f-85d8-254eca7cb0da -Mailbox Tony This example disables the Share to Teams app for user Tony. +**Note**: Even if you disable default app by this cmdlet, it will be enabled automatically when user access respective app. This is by design behavior. + ## PARAMETERS ### -Identity From e08b28cfde4f34714c6c8e181ace38388ad35ceb Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Fri, 1 Aug 2025 15:59:31 -0700 Subject: [PATCH 12/14] Fixed unnecessary future tense --- .../ExchangePowerShell/Get-AuthenticationPolicy.md | 2 +- .../ExchangePowerShell/Remove-AuthenticationPolicy.md | 2 +- .../ExchangePowerShell/Set-AuthenticationPolicy.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md index 848e4d890e..5c142396b0 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-AuthenticationPolicy.md @@ -89,7 +89,7 @@ Legacy Exchange tokens include Exchange user identity and callback 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. You'll receive the warning "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 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. You get the warning "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). - 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). ```yaml diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md index 7b2984dfae..1d83ba7551 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-AuthenticationPolicy.md @@ -87,7 +87,7 @@ This switch applies to the entire organization. The Identity parameter is requir **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. You'll receive the warning "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 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. You get the warning "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). - 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. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md index 37decd71a4..480c57c088 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md @@ -399,7 +399,7 @@ The switch applies to the entire organization. The Identity parameter is require **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. You'll receive the warning "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 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. You get the warning "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). - 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. @@ -613,7 +613,7 @@ The switch applies to the entire organization. The Identity parameter is require **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. You'll receive the warning "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 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. You get the warning "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). - 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. From abec9004a078d3d2ad15eb91be8e2274b94b16ce Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Fri, 1 Aug 2025 16:06:13 -0700 Subject: [PATCH 13/14] Update Disable-App.md --- exchange/exchange-ps/exchange/Disable-App.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Disable-App.md b/exchange/exchange-ps/exchange/Disable-App.md index b1f452e4db..4d6464e2df 100644 --- a/exchange/exchange-ps/exchange/Disable-App.md +++ b/exchange/exchange-ps/exchange/Disable-App.md @@ -59,7 +59,7 @@ Disable-App -Identity 545d8236-721a-468f-85d8-254eca7cb0da -Mailbox Tony This example disables the Share to Teams app for user Tony. -**Note**: Even if you disable default app by this cmdlet, it will be enabled automatically when user access respective app. This is by design behavior. +**Note**: Even if you disable the default app with this cmdlet, that app is automatically enabled automatically the user accesses the respective app. This behavior is by design. ## PARAMETERS From fccba342a4e659835d2c2b7900b86e39472f4432 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Fri, 1 Aug 2025 16:07:23 -0700 Subject: [PATCH 14/14] Update Disable-App.md --- exchange/exchange-ps/exchange/Disable-App.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Disable-App.md b/exchange/exchange-ps/exchange/Disable-App.md index 4d6464e2df..2794396fd6 100644 --- a/exchange/exchange-ps/exchange/Disable-App.md +++ b/exchange/exchange-ps/exchange/Disable-App.md @@ -59,7 +59,7 @@ Disable-App -Identity 545d8236-721a-468f-85d8-254eca7cb0da -Mailbox Tony This example disables the Share to Teams app for user Tony. -**Note**: Even if you disable the default app with this cmdlet, that app is automatically enabled automatically the user accesses the respective app. This behavior is by design. +**Note**: Even if you disable the default app with this cmdlet, that app is automatically enabled when the user accesses the app. This behavior is by design. ## PARAMETERS