From a6306b400fc57befc37ea071d7ad67eef8b20616 Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Mon, 11 Nov 2024 16:57:16 -0800 Subject: [PATCH 01/24] Update switches for legacy Exchange tokens --- .../exchange/Get-AuthenticationPolicy.md | 26 +++++++++++++++++++ .../exchange/Remove-AuthenticationPolicy.md | 9 ++++++- .../exchange/Set-AuthenticationPolicy.md | 21 ++++++++++++--- 3 files changed, 52 insertions(+), 4 deletions(-) diff --git a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md index 18c427840c..56638493cd 100644 --- a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md @@ -21,6 +21,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-AuthenticationPolicy [[-Identity] ] + [-AllowLegacyExchangeTokens] [-TenantId ] [] ``` @@ -46,6 +47,31 @@ This example returns detailed information for the authentication policy named En ## PARAMETERS +### -AllowLegacyExchangeTokens +This parameter is available only in the cloud-based service. + +The AllowLegacyExchangeTokens switch specifies whether legacy Exchange tokens for Outlook add-ins are allowed in the tenant. It also identifies the IDs of the Outlook add-ins that have been allowed or blocked from using legacy tokens. You don't need to specify a value with this switch. + +Legacy Exchange tokens include Exchange user identity and callback tokens. + +**Important**: + +- Blocking legacy Exchange tokens may cause some Microsoft add-ins to stop working in your tenant. These add-ins are being updated to no longer use legacy tokens. +- Legacy Exchange tokens will eventually be 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 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Identity The Identity parameter specifies the authentication policy you want to view. You can use any value that uniquely identifies the policy. For example: diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index 4a09e10325..d9094d1782 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -66,7 +66,14 @@ Accept wildcard characters: False ### -AllowLegacyExchangeTokens This parameter is available only in the cloud-based service. -This parameter is reserved for internal Microsoft use. +The AllowLegacyExchangeTokens switch returns your tenant to its previous state before changes were made to allow or block legacy Exchange tokens for Outlook add-ins. Legacy Exchange tokens include Exchange user identity and callback tokens. + +This switch applies to your entire tenant even if you specify an authentication policy in the Identity parameter. You don't need to specify a value with this switch. + +**Important**: + +- The AllowLegacyExchangeTokens switch disregards other authentication policy parameters used in the same cmdlet. We recommend making separate calls for other authentication policy changes. +- Legacy Exchange tokens will eventually be 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/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index f1e832790a..cd7a797180 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -354,7 +354,14 @@ Accept wildcard characters: False ### -AllowLegacyExchangeTokens This parameter is available only in the cloud-based service. -This parameter is reserved for internal Microsoft use. +The AllowLegacyExchangeTokens switch specifies whether to allow legacy Exchange tokens for Outlook add-ins. Legacy Exchange tokens include Exchange user identity and callback tokens. + +This switch applies to your entire tenant even if you specify an authentication policy in the Identity parameter. You don't need to specify a value with this switch. + +**Important**: + +- The AllowLegacyExchangeTokens switch disregards other authentication policy parameters used in the same cmdlet. We recommend making separate calls for other authentication policy changes. +- Legacy Exchange tokens will eventually be 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 @@ -540,7 +547,15 @@ Accept wildcard characters: False ### -BlockLegacyExchangeTokens This parameter is available only in the cloud-based service. -This parameter is reserved for internal Microsoft use. +The BlockLegacyExchangeTokens switch specifies whether to block legacy Exchange tokens for Outlook add-ins. Legacy Exchange tokens include Exchange user identity and callback tokens. + +This switch applies to your entire tenant even if you specify an authentication policy in the Identity parameter. You don't need to specify a value with this switch. + +**Important**: + +- The BlockLegacyExchangeTokens switch disregards other authentication policy parameters used in the same cmdlet. We recommend making separate calls for other authentication policy changes. +- Blocking legacy Exchange tokens may cause some Microsoft add-ins to stop working in your tenant. These add-ins are being updated to no longer use legacy tokens. +- Legacy Exchange tokens will eventually be 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 @@ -550,7 +565,7 @@ Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named -Default value: True +Default value: False Accept pipeline input: False Accept wildcard characters: False ``` From 408fb73495d14607b179237b69d88395d60e12da Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 19 Nov 2024 08:51:36 -0800 Subject: [PATCH 02/24] Update Remove-AuthenticationPolicy.md --- exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index d9094d1782..40ed8899a9 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -72,7 +72,7 @@ This switch applies to your entire tenant even if you specify an authentication **Important**: -- The AllowLegacyExchangeTokens switch disregards other authentication policy parameters used in the same cmdlet. We recommend making separate calls for other authentication policy changes. +- The AllowLegacyExchangeTokens switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. - Legacy Exchange tokens will eventually be 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 From 9dea352a8af406ade4321a15e8b31fe8d9ef6c1d Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 19 Nov 2024 08:52:52 -0800 Subject: [PATCH 03/24] Update Remove-AuthenticationPolicy.md --- .../exchange-ps/exchange/Remove-AuthenticationPolicy.md | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index 40ed8899a9..4a09e10325 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -66,14 +66,7 @@ Accept wildcard characters: False ### -AllowLegacyExchangeTokens This parameter is available only in the cloud-based service. -The AllowLegacyExchangeTokens switch returns your tenant to its previous state before changes were made to allow or block legacy Exchange tokens for Outlook add-ins. Legacy Exchange tokens include Exchange user identity and callback tokens. - -This switch applies to your entire tenant even if you specify an authentication policy in the Identity parameter. You don't need to specify a value with this switch. - -**Important**: - -- The AllowLegacyExchangeTokens switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. -- Legacy Exchange tokens will eventually be 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). +This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter From 1ab3aad68179ec41becba15e5e91bdced55a7480 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Tue, 19 Nov 2024 09:17:15 -0800 Subject: [PATCH 04/24] Minor consistency updates --- .../exchange/Get-AuthenticationPolicy.md | 4 ++-- .../exchange/Remove-AuthenticationPolicy.md | 11 ++++++++++- .../exchange/Set-AuthenticationPolicy.md | 18 +++++++++++------- 3 files changed, 23 insertions(+), 10 deletions(-) diff --git a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md index 56638493cd..f5a68e8937 100644 --- a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md @@ -50,13 +50,13 @@ This example returns detailed information for the authentication policy named En ### -AllowLegacyExchangeTokens This parameter is available only in the cloud-based service. -The AllowLegacyExchangeTokens switch specifies whether legacy Exchange tokens for Outlook add-ins are allowed in the tenant. It also identifies the IDs of the Outlook add-ins that have been allowed or blocked from using legacy tokens. You don't need to specify a value with this switch. +The AllowLegacyExchangeTokens switch specifies whether legacy Exchange tokens for Outlook add-ins are allowed in the organization. It also identifies the IDs of the Outlook add-ins that have been allowed or blocked from using legacy tokens. You don't need to specify a value with this switch. Legacy Exchange tokens include Exchange user identity and callback tokens. **Important**: -- Blocking legacy Exchange tokens may cause some Microsoft add-ins to stop working in your tenant. These add-ins are being updated to no longer use legacy tokens. +- 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. - Legacy Exchange tokens will eventually be 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 diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index 4a09e10325..9c17c288e5 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -66,7 +66,16 @@ Accept wildcard characters: False ### -AllowLegacyExchangeTokens This parameter is available only in the cloud-based service. -This parameter is reserved for internal Microsoft use. +The AllowLegacyExchangeTokens switch returns your organization to its previous state before changes were made to allow or block legacy Exchange tokens for Outlook add-ins. You don't need to specify a value with this switch. + +Legacy Exchange tokens include Exchange user identity and callback tokens. + +This switch applies to the entire organization, even if you specify an authentication policy using the Identity parameter. + +**Important**: + +- This switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. +- Legacy Exchange tokens will eventually be 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/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index cd7a797180..d0616b33dc 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -354,13 +354,15 @@ Accept wildcard characters: False ### -AllowLegacyExchangeTokens This parameter is available only in the cloud-based service. -The AllowLegacyExchangeTokens switch specifies whether to allow legacy Exchange tokens for Outlook add-ins. Legacy Exchange tokens include Exchange user identity and callback tokens. +The AllowLegacyExchangeTokens switch specifies whether to allow legacy Exchange tokens for Outlook add-ins. You don't need to specify a value with this switch. -This switch applies to your entire tenant even if you specify an authentication policy in the Identity parameter. You don't need to specify a value with this switch. +Legacy Exchange tokens include Exchange user identity and callback tokens. + +This switch applies to the entire organization, even if you specify an authentication policy using the Identity parameter. **Important**: -- The AllowLegacyExchangeTokens switch disregards other authentication policy parameters used in the same cmdlet. We recommend making separate calls for other authentication policy changes. +- This switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. - Legacy Exchange tokens will eventually be 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 @@ -547,14 +549,16 @@ Accept wildcard characters: False ### -BlockLegacyExchangeTokens This parameter is available only in the cloud-based service. -The BlockLegacyExchangeTokens switch specifies whether to block legacy Exchange tokens for Outlook add-ins. Legacy Exchange tokens include Exchange user identity and callback tokens. +The BlockLegacyExchangeTokens switch specifies whether to block legacy Exchange tokens for Outlook add-ins. You don't need to specify a value with this switch. + +Legacy Exchange tokens include Exchange user identity and callback tokens. -This switch applies to your entire tenant even if you specify an authentication policy in the Identity parameter. You don't need to specify a value with this switch. +This switch applies to the entire organization, even if you specify an authentication policy using the Identity parameter. **Important**: -- The BlockLegacyExchangeTokens switch disregards other authentication policy parameters used in the same cmdlet. We recommend making separate calls for other authentication policy changes. -- Blocking legacy Exchange tokens may cause some Microsoft add-ins to stop working in your tenant. These add-ins are being updated to no longer use legacy tokens. +- This switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. +- 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. - Legacy Exchange tokens will eventually be 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 From c2774ef8938ca932b74360d417b52d647bcd80d4 Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Tue, 19 Nov 2024 16:17:56 -0800 Subject: [PATCH 05/24] Remove Get-AuthenticationPolicy changes --- .../exchange/Get-AuthenticationPolicy.md | 26 ------------------- 1 file changed, 26 deletions(-) diff --git a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md index f5a68e8937..18c427840c 100644 --- a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md @@ -21,7 +21,6 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-AuthenticationPolicy [[-Identity] ] - [-AllowLegacyExchangeTokens] [-TenantId ] [] ``` @@ -47,31 +46,6 @@ This example returns detailed information for the authentication policy named En ## PARAMETERS -### -AllowLegacyExchangeTokens -This parameter is available only in the cloud-based service. - -The AllowLegacyExchangeTokens switch specifies whether legacy Exchange tokens for Outlook add-ins are allowed in the organization. It also identifies the IDs of the Outlook add-ins that have been allowed or blocked from using legacy tokens. You don't need to specify a value with this switch. - -Legacy Exchange tokens include Exchange user identity and callback tokens. - -**Important**: - -- 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. -- Legacy Exchange tokens will eventually be 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 -Parameter Sets: (All) -Aliases: -Applicable: Exchange Online, Exchange Online Protection - -Required: False -Position: Named -Default value: True -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -Identity The Identity parameter specifies the authentication policy you want to view. You can use any value that uniquely identifies the policy. For example: From 57a8aa5f3e03d372821619454054bd89479ec63c Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Tue, 19 Nov 2024 16:55:06 -0800 Subject: [PATCH 06/24] Add note about token issuance --- exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md | 1 + exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md | 1 + 2 files changed, 2 insertions(+) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index 9c17c288e5..66e962003c 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -75,6 +75,7 @@ This switch applies to the entire organization, even if you specify an authentic **Important**: - This switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. +- Legacy Exchange tokens issued to Outlook add-ins before token blocking was implemented in your organization will remain valid until they expire. - Legacy Exchange tokens will eventually be 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 diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index d0616b33dc..db431bdb73 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -558,6 +558,7 @@ This switch applies to the entire organization, even if you specify an authentic **Important**: - This switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. +- 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. - Legacy Exchange tokens will eventually be 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). From 2e0cf6fff9623944f72f08630d0b06d33c58fbe1 Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Wed, 20 Nov 2024 16:43:19 -0800 Subject: [PATCH 07/24] Add examples for Exchange token switches --- .../exchange-ps/exchange/Remove-AuthenticationPolicy.md | 7 +++++++ exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md | 7 +++++++ 2 files changed, 14 insertions(+) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index 66e962003c..aec7b72395 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -41,6 +41,13 @@ Remove-AuthenticationPolicy -Identity "Engineering Group" This example removes the authentication policy named "Engineering Group". +### Example 2 +```powershell +Remove-AuthenticationPolicy -Identity "Legacy Exchange Tokens" -AllowLegacyExchangeTokens +``` + +In Exchange Online, this example returns your organization to its previous state before legacy Exchange token issuance was allowed or blocked for Outlook add-ins. Since this switch applies to the entire organization, the authentication policy specified with the Identity parameter is ignored. + ## PARAMETERS ### -Identity diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index db431bdb73..8d78d0614c 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -77,6 +77,13 @@ Set-AuthenticationPolicy -Identity "Research and Development Group" -BlockLegacy In Exchange 2019, this example re-enables Basic authentication for Exchange Reporting Web Services in the authentication policy named Research and Development Group. +### Example 3 +```powershell +Set-AuthenticationPolicy -Identity "Legacy Exchange Tokens" -BlockLegacyExchangeTokens +``` + +In Exchange Online, this example blocks legacy Exchange tokens from being issued to Outlook add-ins. Since this switch applies to the entire organization, the authentication policy specified with the Identity parameter is ignored. + ## PARAMETERS ### -Identity From c4212ad76243ec8c211d5a49110149f24103bd35 Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Thu, 21 Nov 2024 11:43:04 -0800 Subject: [PATCH 08/24] Add note --- exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md | 1 + exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md | 2 ++ 2 files changed, 3 insertions(+) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index aec7b72395..303151ccdf 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -82,6 +82,7 @@ This switch applies to the entire organization, even if you specify an authentic **Important**: - 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. - Legacy Exchange tokens will eventually be 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). diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index 8d78d0614c..575266fc02 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -370,6 +370,7 @@ This switch applies to the entire organization, even if you specify an authentic **Important**: - 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 will eventually be 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 @@ -565,6 +566,7 @@ This switch applies to the entire organization, even if you specify an authentic **Important**: - 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. - Legacy Exchange tokens will eventually be 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). From 44f2354e2f347c8b51df4300fb444833a76ccf2a Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Fri, 22 Nov 2024 09:35:01 -0800 Subject: [PATCH 09/24] Apply suggestions from review --- .../exchange-ps/exchange/Remove-AuthenticationPolicy.md | 4 ++-- .../exchange-ps/exchange/Set-AuthenticationPolicy.md | 9 ++++----- 2 files changed, 6 insertions(+), 7 deletions(-) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index 303151ccdf..3eb387bfb3 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -77,11 +77,11 @@ The AllowLegacyExchangeTokens switch returns your organization to its previous s Legacy Exchange tokens include Exchange user identity and callback tokens. -This switch applies to the entire organization, even if you specify an authentication policy using the Identity parameter. +This switch applies to the entire organization. Although the Identity parameter is required, its value is ignored. You can pass any non-empty value as the Identity parameter. **Important**: -- This switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. +- 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. - Legacy Exchange tokens will eventually be 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). diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index 575266fc02..be4a9b5c73 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -365,12 +365,11 @@ The AllowLegacyExchangeTokens switch specifies whether to allow legacy Exchange Legacy Exchange tokens include Exchange user identity and callback tokens. -This switch applies to the entire organization, even if you specify an authentication policy using the Identity parameter. +This switch applies to the entire organization. Although the Identity parameter is required, its value is ignored. You can pass any non-empty value as the Identity parameter. **Important**: -- 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. +- 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. - Legacy Exchange tokens will eventually be 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 @@ -561,11 +560,11 @@ The BlockLegacyExchangeTokens switch specifies whether to block legacy Exchange Legacy Exchange tokens include Exchange user identity and callback tokens. -This switch applies to the entire organization, even if you specify an authentication policy using the Identity parameter. +This switch applies to the entire organization. Although the Identity parameter is required, its value is ignored. You can pass any non-empty value as the Identity parameter. **Important**: -- This switch disregards other authentication policy parameters used in the same command. We recommend running separate commands for other authentication policy changes. +- 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 511a8d4296ddd9f336a9af493b2bbed8ab2abb9b Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Wed, 11 Dec 2024 02:05:16 -0800 Subject: [PATCH 10/24] Add Get-AuthenticationPolicy switch --- .../exchange/Get-AuthenticationPolicy.md | 30 +++++++++++++++++++ .../exchange/Set-AuthenticationPolicy.md | 1 + 2 files changed, 31 insertions(+) diff --git a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md index 18c427840c..72f244e01c 100644 --- a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md @@ -21,6 +21,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-AuthenticationPolicy [[-Identity] ] + [-AllowLegacyExchangeTokens] [-TenantId ] [] ``` @@ -44,6 +45,13 @@ Get-AuthenticationPolicy -Identity "Engineering Group" This example returns detailed information for the authentication policy named Engineering Group. +### Example 3 +```powershell +Get-AuthenticationPolicy -AllowLegacyExchangeTokens +``` + +In Exchange Online, this example specifies whether legacy Exchange tokens for Outlook add-ins are allowed in the organization. + ## PARAMETERS ### -Identity @@ -66,6 +74,28 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -AllowLegacyExchangeTokens +This parameter is available only in the cloud-based service. + +The AllowLegacyExchangeTokens switch specifies whether legacy Exchange tokens are allowed for Outlook add-ins in your organization. You don't need to specify a value with this switch. + +Legacy Exchange tokens include Exchange user identity and callback tokens. + +**Important**: Legacy Exchange tokens will eventually be 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 +Parameter Sets: (All) +Aliases: +Applicable: Exchange Online, Exchange Online Protection + +Required: False +Position: Named +Default value: True +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -TenantId This parameter is available only in the cloud-based service. diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index be4a9b5c73..83d3e93696 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -370,6 +370,7 @@ This switch applies to the entire organization. Although the Identity parameter **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. - Legacy Exchange tokens will eventually be 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 From c659d1563ded2b57727ea7baf015fc0bc1248836 Mon Sep 17 00:00:00 2001 From: Sam Ramon <15154970+samantharamon@users.noreply.github.com> Date: Wed, 11 Dec 2024 17:05:30 -0800 Subject: [PATCH 11/24] Add note to Get-AuthenticationPolicy switch --- exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md index 72f244e01c..2a91335ad9 100644 --- a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md @@ -81,7 +81,10 @@ The AllowLegacyExchangeTokens switch specifies whether legacy Exchange tokens ar Legacy Exchange tokens include Exchange user identity and callback tokens. -**Important**: Legacy Exchange tokens will eventually be 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**: + +- Currently, the AllowLegacyExchangeTokens switch only specifies whether legacy Exchange tokens are allowed in your organization. For now, disregard the empty Allowed and Blocked arrays returned by the switch. Improvements are underway to populate these arrays with Outlook add-ins that were allowed or blocked from getting legacy tokens. +- Legacy Exchange tokens will eventually be 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 acfc6d5988739a5a7f257bc061e0ef2a4ff67d41 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Wed, 11 Dec 2024 17:09:46 -0800 Subject: [PATCH 12/24] Update Get-AuthenticationPolicy.md --- exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md index 2a91335ad9..7c9cce1ad9 100644 --- a/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Get-AuthenticationPolicy.md @@ -83,7 +83,7 @@ Legacy Exchange tokens include Exchange user identity and callback tokens. **Important**: -- Currently, the AllowLegacyExchangeTokens switch only specifies whether legacy Exchange tokens are allowed in your organization. For now, disregard the empty Allowed and Blocked arrays returned by the switch. Improvements are underway to populate these arrays with Outlook add-ins that were allowed or blocked from getting legacy tokens. +- Currently, the AllowLegacyExchangeTokens switch only specifies whether legacy Exchange tokens are allowed in your organization. For now, disregard the empty Allowed and Blocked arrays returned by the switch. - Legacy Exchange tokens will eventually be 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 From da99bf6497866a574900a3129e1f8c6a3c1871e6 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:27:37 -0800 Subject: [PATCH 13/24] Update exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index 3eb387bfb3..b81626167c 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -43,7 +43,7 @@ This example removes the authentication policy named "Engineering Group". ### Example 2 ```powershell -Remove-AuthenticationPolicy -Identity "Legacy Exchange Tokens" -AllowLegacyExchangeTokens +Remove-AuthenticationPolicy -Identity "LegacyExchangeTokens" -AllowLegacyExchangeTokens ``` In Exchange Online, this example returns your organization to its previous state before legacy Exchange token issuance was allowed or blocked for Outlook add-ins. Since this switch applies to the entire organization, the authentication policy specified with the Identity parameter is ignored. From 215d96989b5f87114aa549869bbc89e6c2bb45ec Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:27:56 -0800 Subject: [PATCH 14/24] Update exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index b81626167c..66a4dca7d4 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -46,7 +46,7 @@ This example removes the authentication policy named "Engineering Group". Remove-AuthenticationPolicy -Identity "LegacyExchangeTokens" -AllowLegacyExchangeTokens ``` -In Exchange Online, this example returns your organization to its previous state before legacy Exchange token issuance was allowed or blocked for Outlook add-ins. Since this switch applies to the entire organization, the authentication policy specified with the Identity parameter is ignored. +In Exchange Online, this example enables legacy Exchange tokens to be issued to Outlook add-ins. This switch applies to the entire organization. The Identity parameter is required, and its value must be set to "LegacyExchangeTokens". Specific authentication polices can't be applied. ## PARAMETERS From 612fc39132fbe7049f5dc1a40fb9ecdf03f83a7e Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:28:06 -0800 Subject: [PATCH 15/24] Update exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index 66a4dca7d4..32cd62d21c 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -73,7 +73,7 @@ Accept wildcard characters: False ### -AllowLegacyExchangeTokens This parameter is available only in the cloud-based service. -The AllowLegacyExchangeTokens switch returns your organization to its previous state before changes were made to allow or block legacy Exchange tokens for Outlook add-ins. You don't need to specify a value with this switch. +The AllowLegacyExchangeTokens switch enables legacy Exchange tokens to be issued to Outlook add-ins for your organization. You don't need to specify a value with this switch. Legacy Exchange tokens include Exchange user identity and callback tokens. From 6ed65f91c94f7853bd48841e75a4a36e3b16f154 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:28:19 -0800 Subject: [PATCH 16/24] Update exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md index 32cd62d21c..ee48f9b65e 100644 --- a/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Remove-AuthenticationPolicy.md @@ -77,7 +77,7 @@ The AllowLegacyExchangeTokens switch enables legacy Exchange tokens to be issued Legacy Exchange tokens include Exchange user identity and callback tokens. -This switch applies to the entire organization. Although the Identity parameter is required, its value is ignored. You can pass any non-empty value as the Identity parameter. +This switch applies to the entire organization. The Identity parameter is required, and its value must be set to "LegacyExchangeTokens". Specific authentication polices can't be applied. **Important**: From 7f7a470aac4cafe0a1f2320711aaa9a633966cfe Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:28:26 -0800 Subject: [PATCH 17/24] Update exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index 83d3e93696..419edc8f09 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -79,7 +79,7 @@ In Exchange 2019, this example re-enables Basic authentication for Exchange Repo ### Example 3 ```powershell -Set-AuthenticationPolicy -Identity "Legacy Exchange Tokens" -BlockLegacyExchangeTokens +Set-AuthenticationPolicy -Identity "LegacyExchangeTokens" -BlockLegacyExchangeTokens ``` In Exchange Online, this example blocks legacy Exchange tokens from being issued to Outlook add-ins. Since this switch applies to the entire organization, the authentication policy specified with the Identity parameter is ignored. From 184b7290cc63b60bc2429aca4c6b81701b146597 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:28:35 -0800 Subject: [PATCH 18/24] Update exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index 419edc8f09..0ed013e199 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -82,7 +82,7 @@ In Exchange 2019, this example re-enables Basic authentication for Exchange Repo Set-AuthenticationPolicy -Identity "LegacyExchangeTokens" -BlockLegacyExchangeTokens ``` -In Exchange Online, this example blocks legacy Exchange tokens from being issued to Outlook add-ins. Since this switch applies to the entire organization, the authentication policy specified with the Identity parameter is ignored. +In Exchange Online, this example blocks legacy Exchange tokens from being issued to Outlook add-ins. The switch applies to the entire organization, and the Identity parameter must be set to the value "LegacyExchangeTokens". Specific authentication polices can't be applied. ## PARAMETERS From ccffc5a4d5771ecdc1c8f14a450cf39a53a3a2d9 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:29:25 -0800 Subject: [PATCH 19/24] Update exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index 0ed013e199..79fd7fa901 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -557,7 +557,7 @@ Accept wildcard characters: False ### -BlockLegacyExchangeTokens This parameter is available only in the cloud-based service. -The BlockLegacyExchangeTokens switch specifies whether to block legacy Exchange tokens for Outlook add-ins. You don't need to specify a value with this switch. +The BlockLegacyExchangeTokens switch specifies to block legacy Exchange tokens being issued to Outlook add-ins. You don't need to specify a value with this switch. Legacy Exchange tokens include Exchange user identity and callback tokens. From edf657f0903c859b44663e7fdf430aa558fd56a6 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:29:32 -0800 Subject: [PATCH 20/24] Update exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index 79fd7fa901..0f5e244ae0 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -561,7 +561,7 @@ The BlockLegacyExchangeTokens switch specifies to block legacy Exchange tokens b Legacy Exchange tokens include Exchange user identity and callback tokens. -This switch applies to the entire organization. Although the Identity parameter is required, its value is ignored. You can pass any non-empty value as the Identity parameter. +The switch applies to the entire organization. The Identity parameter is required and must be set to the value "LegacyExchangeTokens". Specific authentication polices can't be applied. **Important**: From 3d2a9f156b91c53c3ff4de1c7a284a8cbf2f926d Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:29:38 -0800 Subject: [PATCH 21/24] Update exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index 0f5e244ae0..a1475c0ee7 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -361,7 +361,7 @@ Accept wildcard characters: False ### -AllowLegacyExchangeTokens This parameter is available only in the cloud-based service. -The AllowLegacyExchangeTokens switch specifies whether to allow legacy Exchange tokens for Outlook add-ins. You don't need to specify a value with this switch. +The AllowLegacyExchangeTokens switch specifies to allow legacy Exchange tokens to be issued to Outlook add-ins. You don't need to specify a value with this switch. Legacy Exchange tokens include Exchange user identity and callback tokens. From 09a95ae3e73e5e17638aced52be92fbd9938c708 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:29:48 -0800 Subject: [PATCH 22/24] Update exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md Co-authored-by: David Chesnut --- exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md index a1475c0ee7..5badd29be6 100644 --- a/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AuthenticationPolicy.md @@ -365,7 +365,7 @@ The AllowLegacyExchangeTokens switch specifies to allow legacy Exchange tokens t Legacy Exchange tokens include Exchange user identity and callback tokens. -This switch applies to the entire organization. Although the Identity parameter is required, its value is ignored. You can pass any non-empty value as the Identity parameter. +The switch applies to the entire organization. The Identity parameter is required and must be set to the value "LegacyExchangeTokens". Specific authentication polices can't be applied. **Important**: From c471a304f5b0cb7717d5911c3a6c1a5fc80f34bc Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 10:47:53 -0800 Subject: [PATCH 23/24] Blind cmdlet sweep EOP --- .../exchange/Get-PendingDelicenseUser.md | 8 ++++---- .../exchange/Import-TransportRuleCollection.md | 16 +++++++++------- .../exchange/Set-OrganizationConfig.md | 6 +++--- 3 files changed, 16 insertions(+), 14 deletions(-) diff --git a/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md b/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md index 89b0f4c17e..43ecd543dd 100644 --- a/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md +++ b/exchange/exchange-ps/exchange/Get-PendingDelicenseUser.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Exchange.RolesAndAccess-Help.xml online version: https://learn.microsoft.com/powershell/module/exchange/get-pendingdelicenseuser -applicable: Exchange Online +applicable: Exchange Online, Exchange Online Protection title: Get-PendingDelicenseUser schema: 2.0.0 author: chrisda @@ -80,7 +80,7 @@ You can't use this parameter with the ShowDueObjectsOnly switch. Type: RecipientIdParameter Parameter Sets: Identity Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: 1 @@ -96,7 +96,7 @@ The ResultSize parameter specifies the maximum number of results to return. If y Type: Unlimited Parameter Sets: TenantLevelParameterSet Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -114,7 +114,7 @@ You can't use this switch with the Identity parameter. Type: SwitchParameter Parameter Sets: TenantLevelParameterSet Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Import-TransportRuleCollection.md b/exchange/exchange-ps/exchange/Import-TransportRuleCollection.md index 3273303524..30fae12016 100644 --- a/exchange/exchange-ps/exchange/Import-TransportRuleCollection.md +++ b/exchange/exchange-ps/exchange/Import-TransportRuleCollection.md @@ -1,7 +1,7 @@ --- external help file: Microsoft.Exchange.TransportMailflow-Help.xml online version: https://learn.microsoft.com/powershell/module/exchange/import-transportrulecollection -applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection title: Import-TransportRuleCollection schema: 2.0.0 author: chrisda @@ -12,7 +12,7 @@ ms.reviewer: # Import-TransportRuleCollection ## SYNOPSIS -This cmdlet is available only in on-premises Exchange. +This cmdlet is functional only in on-premises Exchange. Use the Import-TransportRuleCollection cmdlet to import a transport rule collection. You can import a rule collection you previously exported as a backup, or import rules that you've exported from an older version of Exchange. @@ -62,7 +62,7 @@ The Identity parameter specifies the transport rule that you want to import. You Type: RuleIdParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: 1 @@ -80,7 +80,7 @@ A valid value for this parameter requires you to read the file to a byte-encoded Type: Byte[] Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: True Position: 1 @@ -99,7 +99,7 @@ The Confirm switch specifies whether to show or hide the confirmation prompt. Ho Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -109,6 +109,8 @@ Accept wildcard characters: False ``` ### -DomainController +This parameter is available only in on-premises Exchange. + The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. The DomainController parameter isn't supported on Edge Transport servers. An Edge Transport server uses the local instance of Active Directory Lightweight Directory Services (AD LDS) to read and write data. @@ -135,7 +137,7 @@ You can use this switch to run tasks programmatically where prompting for admini Type: SwitchParameter Parameter Sets: (All) Aliases: -Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named @@ -151,7 +153,7 @@ The WhatIf switch simulates the actions of the command. You can use this switch Type: SwitchParameter Parameter Sets: (All) Aliases: wi -Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 +Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online, Exchange Online Protection Required: False Position: Named diff --git a/exchange/exchange-ps/exchange/Set-OrganizationConfig.md b/exchange/exchange-ps/exchange/Set-OrganizationConfig.md index fe6238ab03..e4e00f9576 100644 --- a/exchange/exchange-ps/exchange/Set-OrganizationConfig.md +++ b/exchange/exchange-ps/exchange/Set-OrganizationConfig.md @@ -1808,7 +1808,7 @@ When you set the value of the DelayedDelicensingEnabled parameter to $false, the Type: Boolean Parameter Sets: DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -2120,7 +2120,7 @@ Use the TenantAdminNotificationForDelayedDelicensingEnabled parameter to turn on Type: Boolean Parameter Sets: DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named @@ -3804,7 +3804,7 @@ Use the EndUserMailNotificationForDelayedDelicensingEnabled to send affected use Type: Boolean Parameter Sets: DelayedDelicensingParameterSet Aliases: -Applicable: Exchange Online +Applicable: Exchange Online, Exchange Online Protection Required: False Position: Named From 1f71ed657e4b414bd6451218a890037b82ff08d1 Mon Sep 17 00:00:00 2001 From: Chris Davis Date: Thu, 12 Dec 2024 14:09:26 -0800 Subject: [PATCH 24/24] Blind cmdlet sweep SCC --- .../exchange/Export-ContentExplorerData.md | 65 +++--- .../exchange-ps/exchange/Get-ComplianceTag.md | 17 ++ .../exchange/Get-DlpCompliancePolicy.md | 17 ++ .../exchange/Get-DlpComplianceRule.md | 17 ++ .../exchange/Get-RetentionCompliancePolicy.md | 17 ++ .../exchange/Get-RetentionComplianceRule.md | 17 ++ .../New-AutoSensitivityLabelPolicy.md | 17 ++ .../exchange/New-AutoSensitivityLabelRule.md | 17 ++ .../exchange-ps/exchange/New-ComplianceTag.md | 188 ++++++++++++------ .../exchange/New-DlpCompliancePolicy.md | 34 ++++ .../exchange/New-DlpComplianceRule.md | 51 +++++ .../exchange/New-RetentionCompliancePolicy.md | 38 ++++ .../exchange/New-RetentionComplianceRule.md | 36 ++++ .../exchange/Remove-ComplianceTag.md | 17 ++ .../Remove-RetentionCompliancePolicy.md | 17 ++ .../Remove-RetentionComplianceRule.md | 17 ++ .../Set-AppRetentionCompliancePolicy.md | 36 +++- .../Set-AutoSensitivityLabelPolicy.md | 17 ++ .../exchange/Set-AutoSensitivityLabelRule.md | 34 ++++ .../exchange-ps/exchange/Set-ComplianceTag.md | 30 +++ .../exchange/Set-DlpCompliancePolicy.md | 17 ++ .../exchange/Set-DlpComplianceRule.md | 34 ++++ .../exchange/Set-RetentionCompliancePolicy.md | 20 ++ .../exchange/Set-RetentionComplianceRule.md | 34 ++++ 24 files changed, 713 insertions(+), 91 deletions(-) diff --git a/exchange/exchange-ps/exchange/Export-ContentExplorerData.md b/exchange/exchange-ps/exchange/Export-ContentExplorerData.md index 64f9fa6b76..c1bd868260 100644 --- a/exchange/exchange-ps/exchange/Export-ContentExplorerData.md +++ b/exchange/exchange-ps/exchange/Export-ContentExplorerData.md @@ -23,13 +23,12 @@ For information about the parameter sets in the Syntax section below, see [Excha ## SYNTAX ``` -Export-ContentExplorerData +Export-ContentExplorerData [-TagName] [-TagType] + [-Aggregate] [[-PageCookie] ] [[-PageSize] ] [[-SiteUrl] ] [[-UserPrincipalName] ] - [-TagName] - [-TagType] [[-Workload] ] [] ``` @@ -69,6 +68,43 @@ This example exports records for the specified sensitive info type for all workl ## PARAMETERS +### -TagType +The TagType parameter specifies the type of label to export file details from. Valid values are: + +- Retention +- SensitiveInformationType +- Sensitivity +- TrainableClassifier + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: True +Position: 5 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Aggregate +{{ Fill Aggregate Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: False +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -PageCookie The PageCookie parameter specifies whether to get more data when the value of the MorePagesAvailable property in the command output is True. If you don't use the PageSize parameter, a maximum of 100 records are returned. If you use the PageSize parameter, a maximum of 10000 records can be returned. @@ -135,27 +171,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -TagType -The TagType parameter specifies the type of label to export file details from. Valid values are: - -- Retention -- SensitiveInformationType -- Sensitivity -- TrainableClassifier - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Security & Compliance - -Required: True -Position: 5 -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -UserPrincipalName The UserPrincipalName parameter specifies the user account in UPN format to export message details from. An example UPN value is erika@contoso.onmicrosoft.com. @@ -195,6 +210,8 @@ Accept pipeline input: False Accept wildcard characters: False ``` + + ### CommonParameters This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216). diff --git a/exchange/exchange-ps/exchange/Get-ComplianceTag.md b/exchange/exchange-ps/exchange/Get-ComplianceTag.md index 982e576f4b..2c704b8488 100644 --- a/exchange/exchange-ps/exchange/Get-ComplianceTag.md +++ b/exchange/exchange-ps/exchange/Get-ComplianceTag.md @@ -23,6 +23,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-ComplianceTag [[-Identity] ] [-IncludingLabelState] + [-PriorityCleanup] [] ``` @@ -83,6 +84,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### CommonParameters This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216). diff --git a/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md index 709d6f2a62..c8dcdf14d5 100644 --- a/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md +++ b/exchange/exchange-ps/exchange/Get-DlpCompliancePolicy.md @@ -22,6 +22,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-DlpCompliancePolicy [[-Identity] ] + [-DisplayName ] [-DistributionDetail] [-ForceValidate ] [-IncludeExtendedProperties ] @@ -88,6 +89,22 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DisplayName +{{ Fill DisplayName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -DistributionDetail The DistributionDetail switch returns detailed policy distribution information in the DistributionResults property. You don't need to specify a value with this switch. diff --git a/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md b/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md index 954bc3ec75..3ec06ed550 100644 --- a/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md +++ b/exchange/exchange-ps/exchange/Get-DlpComplianceRule.md @@ -22,6 +22,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-DlpComplianceRule [[-Identity] ] + [-DisplayName ] [-IncludeExecutionRuleGuids ] [-Policy ] [] @@ -76,6 +77,22 @@ Accept pipeline input: True Accept wildcard characters: False ``` +### -DisplayName +{{ Fill DisplayName Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -IncludeExecutionRuleGuids {{ Fill IncludeExecutionRuleGuids Description }} diff --git a/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md index 1dd04224b0..ec901b1b6b 100644 --- a/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/exchange/Get-RetentionCompliancePolicy.md @@ -26,6 +26,7 @@ Get-RetentionCompliancePolicy [[-Identity] ] [-ErrorPolicyOnly] [-ExcludeTeamsPolicy] [-IncludeTestModeResults] + [-PriorityCleanup] [-RetentionRuleTypes] [-TeamsPolicyOnly] [] @@ -147,6 +148,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RetentionRuleTypes The RetentionRuleTypes switch specifies whether to return the value of the RetentionRuleTypes property in the results. You don't need to specify a value with this switch. diff --git a/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md index a5b8eb2814..9c1279ce96 100644 --- a/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md +++ b/exchange/exchange-ps/exchange/Get-RetentionComplianceRule.md @@ -23,6 +23,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ``` Get-RetentionComplianceRule [[-Identity] ] [-Policy ] + [-PriorityCleanup] [] ``` @@ -96,6 +97,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### CommonParameters This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216). diff --git a/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md index 59702e5c92..3cf6734ddf 100644 --- a/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelPolicy.md @@ -35,6 +35,7 @@ New-AutoSensitivityLabelPolicy [-Name] -ApplySensitivityLabel [-ExchangeSenderMemberOfException ] [-ExternalMailRightsManagementOwner ] [-Force] + [-Locations ] [-Mode ] [-OneDriveAdaptiveScopes ] [-OneDriveAdaptiveScopesException ] @@ -364,6 +365,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Locations +{{ Fill Locations Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Mode The Mode parameter specifies the action and notification level of the auto-labeling policy. Valid values are: diff --git a/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md index b5200f9dda..5b058fa5c7 100644 --- a/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/exchange/New-AutoSensitivityLabelRule.md @@ -76,6 +76,7 @@ New-AutoSensitivityLabelRule [-Name] -Policy -Workl [-SenderIPRanges ] [-SentTo ] [-SentToMemberOf ] + [-SourceType ] [-SubjectMatchesPatterns ] [-WhatIf] [] @@ -1212,6 +1213,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SourceType +{{ Fill SourceType Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -SubjectMatchesPatterns The SubjectMatchesPatterns parameter specifies a condition for the auto-labeling policy rule that looks for text patterns in the Subject field of messages by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`. diff --git a/exchange/exchange-ps/exchange/New-ComplianceTag.md b/exchange/exchange-ps/exchange/New-ComplianceTag.md index 0d582e8ff3..9de8c0fca4 100644 --- a/exchange/exchange-ps/exchange/New-ComplianceTag.md +++ b/exchange/exchange-ps/exchange/New-ComplianceTag.md @@ -20,6 +20,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ## SYNTAX +### Default ``` New-ComplianceTag [-Name] [-AutoApprovalPeriod ] @@ -43,6 +44,18 @@ New-ComplianceTag [-Name] [] ``` +### PriorityCleanup +``` +New-ComplianceTag [-Name] -RetentionAction -RetentionDuration -RetentionType + -MultiStageReviewProperty [-PriorityCleanup] + [-Comment ] + [-Confirm] + [-Force] + [-Notes ] + [-WhatIf] + [] +``` + ## DESCRIPTION To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). @@ -77,6 +90,121 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionAction +The RetentionAction parameter specifies the action for the label. Valid values are: + +- Delete +- Keep +- KeepAndDelete + +```yaml +Type: String +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionDuration +The RetentionDuration parameter specifies the number of days to retain the content. Valid values are: + +- A positive integer. +- The value unlimited. + +```yaml +Type: Unlimited +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: Unlimited +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -RetentionType +The RetentionType parameter specifies whether the retention duration is calculated from the content creation date, tagged date, or last modification date. Valid values are: + +- CreationAgeInDays +- EventAgeInDays +- ModificationAgeInDays +- TaggedAgeInDays + +```yaml +Type: String +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +```yaml +Type: String +Parameter Sets: Default +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -AutoApprovalPeriod {{ Fill AutoApprovalPeriod Description }} @@ -341,66 +469,6 @@ Accept pipeline input: False Accept wildcard characters: False ``` -### -RetentionAction -The RetentionAction parameter specifies the action for the label. Valid values are: - -- Delete -- Keep -- KeepAndDelete - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Security & Compliance - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionDuration -The RetentionDuration parameter specifies the number of days to retain the content. Valid values are: - -- A positive integer. -- The value unlimited. - -```yaml -Type: Unlimited -Parameter Sets: (All) -Aliases: -Applicable: Security & Compliance - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - -### -RetentionType -The RetentionType parameter specifies whether the retention duration is calculated from the content creation date, tagged date, or last modification date. Valid values are: - -- CreationAgeInDays -- EventAgeInDays -- ModificationAgeInDays -- TaggedAgeInDays - -```yaml -Type: String -Parameter Sets: (All) -Aliases: -Applicable: Security & Compliance - -Required: False -Position: Named -Default value: None -Accept pipeline input: False -Accept wildcard characters: False -``` - ### -ReviewerEmail The ReviewerEmail parameter specifies the email address of a reviewer for Delete and KeepAndDelete retention actions. You can specify multiple email addresses separated by commas. diff --git a/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md index 2536cb70ab..e53212ec9d 100644 --- a/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md +++ b/exchange/exchange-ps/exchange/New-DlpCompliancePolicy.md @@ -38,6 +38,7 @@ New-DlpCompliancePolicy [-Name] [-ExchangeSenderMemberOfException ] [-Force] [-IsFromSmartInsights ] + [-Locations ] [-Mode ] [-OneDriveAdaptiveScopes ] [-OneDriveAdaptiveScopesException ] @@ -62,6 +63,7 @@ New-DlpCompliancePolicy [-Name] [-TeamsLocationException ] [-ThirdPartyAppDlpLocation ] [-ThirdPartyAppDlpLocationException ] + [-ValidatePolicy] [-WhatIf] [] ``` @@ -424,6 +426,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Locations +{{ Fill Locations Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Mode The Mode parameter specifies the action and notification level of the DLP policy. Valid values are: @@ -903,6 +921,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ValidatePolicy +{{ Fill ValidatePolicy Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch doesn't work in Security & Compliance PowerShell. diff --git a/exchange/exchange-ps/exchange/New-DlpComplianceRule.md b/exchange/exchange-ps/exchange/New-DlpComplianceRule.md index 67c63d9a83..91e358ea91 100644 --- a/exchange/exchange-ps/exchange/New-DlpComplianceRule.md +++ b/exchange/exchange-ps/exchange/New-DlpComplianceRule.md @@ -148,6 +148,7 @@ New-DlpComplianceRule [-Name] -Policy [-RemoveHeader ] [-RemoveRMSTemplate ] [-ReportSeverityLevel ] + [-RestrictAccess ] [-RestrictBrowserAccess ] [-RuleErrorAction ] [-SenderADAttributeContainsWords ] @@ -165,7 +166,9 @@ New-DlpComplianceRule [-Name] -Policy [-SubjectOrBodyContainsWords ] [-SubjectOrBodyMatchesPatterns ] [-ThirdPartyAppDlpRestrictions ] + [-TriggerPowerAutomateFlow ] [-UnscannableDocumentExtensionIs ] + [-ValidateRule] [-WhatIf] [-WithImportance ] [] @@ -3047,6 +3050,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RestrictAccess +{{ Fill RestrictAccess Description }} + +```yaml +Type: System.Collections.Hashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RestrictBrowserAccess {{ Fill RestrictBrowserAccess Description }} @@ -3446,6 +3465,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -TriggerPowerAutomateFlow +{{ Fill TriggerPowerAutomateFlow Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -UnscannableDocumentExtensionIs The UnscannableDocumentExtensionIs parameter specifies a condition for the rule that looks for the specified true file extension when the files aren't scannable. Irrespective of the original file type, this predicate matches based on the extension that is present in the name of the file. @@ -3464,6 +3499,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -ValidateRule +{{ Fill ValidateRule Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch doesn't work in Security & Compliance PowerShell. diff --git a/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md index 35ea5fc749..8258bfaf6b 100644 --- a/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/exchange/New-RetentionCompliancePolicy.md @@ -37,11 +37,13 @@ New-RetentionCompliancePolicy [-Name] [-OneDriveLocationException ] [-PolicyRBACScopes ] [-PolicyTemplateInfo ] + [-PriorityCleanup] [-PublicFolderLocation ] [-RestrictiveRetention ] [-RetainCloudAttachment ] [-SharePointLocation ] [-SharePointLocationException ] + [-SkipPriorityCleanupConfirmation] [-SkypeLocation ] [-SkypeLocationException ] [-WhatIf] @@ -56,8 +58,10 @@ New-RetentionCompliancePolicy [-Name] [-Enabled ] [-Force] [-IsSimulation] + [-PriorityCleanup] [-RestrictiveRetention ] [-RetainCloudAttachment ] + [-SkipPriorityCleanupConfirmation] [-TeamsChannelLocation ] [-TeamsChannelLocationException ] [-TeamsChatLocation ] @@ -75,8 +79,10 @@ New-RetentionCompliancePolicy [-Name] -AdaptiveScopeLocation ] [-Force] [-IsSimulation] + [-PriorityCleanup] [-RestrictiveRetention ] [-RetainCloudAttachment ] + [-SkipPriorityCleanupConfirmation] [-WhatIf] [] ``` @@ -437,6 +443,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -PublicFolderLocation The PublicFolderLocation parameter specifies that you want to include all public folders in the retention policy. You use the value All for this parameter. @@ -545,6 +567,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SkipPriorityCleanupConfirmation +{{ Fill SkipPriorityCleanupConfirmation Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -SkypeLocation The SkypeLocation parameter specifies the Skype for Business Online users to include in the policy. diff --git a/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md index d8b3c9c2f6..c7471abe72 100644 --- a/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md +++ b/exchange/exchange-ps/exchange/New-RetentionComplianceRule.md @@ -27,7 +27,9 @@ New-RetentionComplianceRule -ApplyComplianceTag -Policy ] [-ExpirationDateOption ] + [-IRMRiskyUserProfiles ] [-MachineLearningModelIDs ] + [-PriorityCleanup] [-RetentionComplianceAction ] [-WhatIf] [] @@ -43,6 +45,7 @@ New-RetentionComplianceRule [-Name] -Policy [-Confirm] [-ContentMatchQuery ] [-ExpirationDateOption ] + [-PriorityCleanup] [-RetentionComplianceAction ] [-WhatIf] [] @@ -53,6 +56,7 @@ New-RetentionComplianceRule [-Name] -Policy New-RetentionComplianceRule -Policy -PublishComplianceTag [-Confirm] [-ExpirationDateOption ] + [-PriorityCleanup] [-RetentionComplianceAction ] [-WhatIf] [] @@ -137,6 +141,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -PublishComplianceTag The PublishComplianceTag parameter specifies the label that's published for the rule, which makes the label visible to users in apps (for example, Outlook, SharePoint, and OneDrive). A valid value for this parameter is the name of an existing label. If the value contains spaces, enclose the value in quotation marks. @@ -292,6 +312,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IRMRiskyUserProfiles +{{ Fill IRMRiskyUserProfiles Description }} + +```yaml +Type: String +Parameter Sets: ComplianceTag +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -MachineLearningModelIDs This parameter is reserved for internal Microsoft use. diff --git a/exchange/exchange-ps/exchange/Remove-ComplianceTag.md b/exchange/exchange-ps/exchange/Remove-ComplianceTag.md index 0f7a5dbcf9..46c293ddf7 100644 --- a/exchange/exchange-ps/exchange/Remove-ComplianceTag.md +++ b/exchange/exchange-ps/exchange/Remove-ComplianceTag.md @@ -24,6 +24,7 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-ComplianceTag [-Identity] [-Confirm] [-ForceDeletion] + [-PriorityCleanup] [-WhatIf] [] ``` @@ -97,6 +98,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch causes the command to simulate its results. By using this switch, you can view what changes would occur without having to commit those changes. diff --git a/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md index 750e4c23ff..586520eb81 100644 --- a/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/exchange/Remove-RetentionCompliancePolicy.md @@ -24,6 +24,7 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-RetentionCompliancePolicy [-Identity] [-Confirm] [-ForceDeletion] + [-PriorityCleanup] [-WhatIf] [] ``` @@ -97,6 +98,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch doesn't work in Security & Compliance PowerShell. diff --git a/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md index e800da5160..fd33677240 100644 --- a/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md +++ b/exchange/exchange-ps/exchange/Remove-RetentionComplianceRule.md @@ -24,6 +24,7 @@ For information about the parameter sets in the Syntax section below, see [Excha Remove-RetentionComplianceRule [-Identity] [-Confirm] [-ForceDeletion] + [-PriorityCleanup] [-WhatIf] [] ``` @@ -99,6 +100,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -WhatIf The WhatIf switch doesn't work in Security & Compliance PowerShell. diff --git a/exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md index 8138ebd112..f3e8af0e26 100644 --- a/exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/exchange/Set-AppRetentionCompliancePolicy.md @@ -30,6 +30,7 @@ Set-AppRetentionCompliancePolicy [-Identity] [-Applications ] [-Comment ] [-Confirm] + [-DeletedResources ] [-Enabled ] [-Force] [-PolicyRBACScopes ] @@ -49,6 +50,7 @@ Set-AppRetentionCompliancePolicy [-Identity] [-Applications ] [-Comment ] [-Confirm] + [-DeletedResources ] [-Enabled ] [-Force] [-RemoveAdaptiveScopeLocation ] @@ -56,13 +58,11 @@ Set-AppRetentionCompliancePolicy [-Identity] [] ``` -### TeamLocation +### DisableRestrictiveRetentionParameterSet ``` Set-AppRetentionCompliancePolicy [-Identity] - [-Comment ] [-Confirm] - [-Enabled ] - [-Force] + [-DeletedResources ] [-WhatIf] [] ``` @@ -71,6 +71,7 @@ Set-AppRetentionCompliancePolicy [-Identity] ``` Set-AppRetentionCompliancePolicy [-Identity] [-Confirm] + [-DeletedResources ] [-Force] [-WhatIf] [] @@ -80,23 +81,28 @@ Set-AppRetentionCompliancePolicy [-Identity] ``` Set-AppRetentionCompliancePolicy [-Identity] [-Confirm] + [-DeletedResources ] [-WhatIf] [] ``` -### DisableRestrictiveRetentionParameterSet +### RetryDistributionParameterSet ``` Set-AppRetentionCompliancePolicy [-Identity] [-Confirm] + [-RetryDistribution] [-WhatIf] [] ``` -### RetryDistributionParameterSet +### TeamLocation ``` Set-AppRetentionCompliancePolicy [-Identity] + [-Comment ] [-Confirm] - [-RetryDistribution] + [-DeletedResources ] + [-Enabled ] + [-Force] [-WhatIf] [] ``` @@ -340,6 +346,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DeletedResources +{{ Fill DeletedResources Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Enabled The Enabled parameter enables or disables the policy. Valid values are: diff --git a/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md index b3211d3c6e..0bfb1b4949 100644 --- a/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelPolicy.md @@ -43,6 +43,7 @@ Set-AutoSensitivityLabelPolicy [-Identity] [-ExchangeSenderMemberOfException ] [-ExternalMailRightsManagementOwner ] [-Force] + [-Locations ] [-Mode ] [-OneDriveAdaptiveScopes ] [-OneDriveAdaptiveScopesException ] @@ -532,6 +533,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Locations +{{ Fill Locations Description }} + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Mode The Mode parameter specifies the action and notification level of the auto-labeling policy. Valid values are: diff --git a/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md b/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md index 6917526560..f573b3a19e 100644 --- a/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/exchange/Set-AutoSensitivityLabelRule.md @@ -31,6 +31,7 @@ Set-AutoSensitivityLabelRule [-Identity] [-ContentContainsSensitiveInformation ] [-ContentExtensionMatchesWords ] [-ContentPropertyContainsWords ] + [-DefaultSpoDocLibraryHasLabel ] [-Disabled ] [-DocumentCreatedBy ] [-DocumentIsPasswordProtected ] @@ -75,6 +76,7 @@ Set-AutoSensitivityLabelRule [-Identity] [-SenderIPRanges ] [-SentTo ] [-SentToMemberOf ] + [-SourceType ] [-SubjectMatchesPatterns ] [-WhatIf] [-Workload ] @@ -283,6 +285,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -DefaultSpoDocLibraryHasLabel +{{ Fill DefaultSpoDocLibraryHasLabel Description }} + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Disabled The Disabled parameter specifies whether the case hold rule is enabled or disabled. Valid values are: @@ -1159,6 +1177,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -SourceType +{{ Fill SourceType Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -SubjectMatchesPatterns The SubjectMatchesPatterns parameter specifies a condition for the auto-labeling policy rule that looks for text patterns in the Subject field of messages by using regular expressions. You can specify multiple text patterns by using the following syntax: `"regular expression1"|"regular expression2"|..."regular expressionN"`. diff --git a/exchange/exchange-ps/exchange/Set-ComplianceTag.md b/exchange/exchange-ps/exchange/Set-ComplianceTag.md index 732494af3a..ef1e0e1fd7 100644 --- a/exchange/exchange-ps/exchange/Set-ComplianceTag.md +++ b/exchange/exchange-ps/exchange/Set-ComplianceTag.md @@ -20,6 +20,7 @@ For information about the parameter sets in the Syntax section below, see [Excha ## SYNTAX +### Default ``` Set-ComplianceTag [-Identity] [-AutoApprovalPeriod ] @@ -38,6 +39,19 @@ Set-ComplianceTag [-Identity] [] ``` +### PriorityCleanup +``` +Set-ComplianceTag [-Identity] [-PriorityCleanup] + [-Comment ] + [-Confirm] + [-Force] + [-MultiStageReviewProperty ] + [-Notes ] + [-RetentionDuration ] + [-WhatIf] + [] +``` + ## DESCRIPTION To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions). @@ -285,6 +299,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: PriorityCleanup +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RetentionDuration The RetentionDuration parameter specifies the number of days to retain the content. Valid values are: diff --git a/exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md b/exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md index 242d848760..efcec3c2b6 100644 --- a/exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md +++ b/exchange/exchange-ps/exchange/Set-DlpCompliancePolicy.md @@ -51,6 +51,7 @@ Set-DlpCompliancePolicy [-Identity] [-ExchangeSenderMemberOfException ] [-Force] [-IsFromSmartInsights ] + [-Locations ] [-Mode ] [-OneDriveAdaptiveScopes ] [-OneDriveAdaptiveScopesException ] @@ -741,6 +742,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -Locations +{{ Fill Locations Description }} + +```yaml +Type: String +Parameter Sets: Identity +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -Mode The Mode parameter specifies the action and notification level of the DLP policy. Valid values are: diff --git a/exchange/exchange-ps/exchange/Set-DlpComplianceRule.md b/exchange/exchange-ps/exchange/Set-DlpComplianceRule.md index 9a4af91eaf..2db025a422 100644 --- a/exchange/exchange-ps/exchange/Set-DlpComplianceRule.md +++ b/exchange/exchange-ps/exchange/Set-DlpComplianceRule.md @@ -147,6 +147,7 @@ Set-DlpComplianceRule [-Identity] [-RemoveHeader ] [-RemoveRMSTemplate ] [-ReportSeverityLevel ] + [-RestrictAccess ] [-RestrictBrowserAccess ] [-RuleErrorAction ] [-SenderADAttributeContainsWords ] @@ -164,6 +165,7 @@ Set-DlpComplianceRule [-Identity] [-SubjectOrBodyContainsWords ] [-SubjectOrBodyMatchesPatterns ] [-ThirdPartyAppDlpRestrictions ] + [-TriggerPowerAutomateFlow ] [-UnscannableDocumentExtensionIs ] [-WhatIf] [-WithImportance ] @@ -2941,6 +2943,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -RestrictAccess +{{ Fill RestrictAccess Description }} + +```yaml +Type: System.Collections.Hashtable[] +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RestrictBrowserAccess {{ Fill RestrictBrowserAccess Description }} @@ -3334,6 +3352,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -TriggerPowerAutomateFlow +{{ Fill TriggerPowerAutomateFlow Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -UnscannableDocumentExtensionIs The UnscannableDocumentExtensionIs parameter specifies a condition for the rule that looks for the specified true file extension when the files are unscannable. Irrespective of what the original file type is, this predicate matches based on the extension that is present in the name of the file. diff --git a/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md b/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md index 6339482ae2..177b8f650c 100644 --- a/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md +++ b/exchange/exchange-ps/exchange/Set-RetentionCompliancePolicy.md @@ -45,6 +45,7 @@ Set-RetentionCompliancePolicy [-Identity] [-Force] [-PolicyTemplateInfo ] [-PolicyRBACScopes ] + [-PriorityCleanup] [-RemoveExchangeLocation ] [-RemoveExchangeLocationException ] [-RemoveModernGroupLocation ] @@ -72,6 +73,7 @@ Set-RetentionCompliancePolicy [-Identity] [-AddAdaptiveScope [-Enabled ] [-EnforceSimulationPolicy ] [-Force] + [-PriorityCleanup] [-RemoveAdaptiveScopeLocation ] [-StartSimulation ] [-WhatIf] @@ -84,6 +86,7 @@ Set-RetentionCompliancePolicy [-Identity] [-RetryDistributio [-Confirm] [-DeletedResources ] [-EnforceSimulationPolicy ] + [-PriorityCleanup] [-StartSimulation ] [-WhatIf] [] @@ -102,6 +105,7 @@ Set-RetentionCompliancePolicy [-Identity] [-Enabled ] [-EnforceSimulationPolicy ] [-Force] + [-PriorityCleanup] [-RemoveTeamsChannelLocation ] [-RemoveTeamsChannelLocationException ] [-RemoveTeamsChatLocation ] @@ -736,6 +740,22 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RemoveAdaptiveScopeLocation The RemoveAdaptiveScopeLocation parameter specifies the adaptive scope location to remove from the policy. You create adaptive scopes by using the New-AdaptiveScope cmdlet. You can use any value that uniquely identifies the adaptive scope. For example: diff --git a/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md b/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md index b79cf9ce5e..3a544e128a 100644 --- a/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md +++ b/exchange/exchange-ps/exchange/Set-RetentionComplianceRule.md @@ -31,6 +31,8 @@ Set-RetentionComplianceRule [-Identity] [-ContentMatchQuery ] [-ExcludedItemClasses ] [-ExpirationDateOption ] + [-IRMRiskyUserProfiles ] + [-PriorityCleanup] [-RetentionComplianceAction ] [-RetentionDuration ] [-RetentionDurationDisplayHint ] @@ -259,6 +261,38 @@ Accept pipeline input: False Accept wildcard characters: False ``` +### -IRMRiskyUserProfiles +{{ Fill IRMRiskyUserProfiles Description }} + +```yaml +Type: String +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -PriorityCleanup +{{ Fill PriorityCleanup Description }} + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: +Applicable: Security & Compliance + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + ### -RetentionComplianceAction The RetentionComplianceAction parameter specifies the retention action for the rule. Valid values are: