diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md index 0c2423156e..45d39b8a55 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressList.md @@ -545,10 +545,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -723,7 +723,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md b/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md index 8400b4963e..72a02151ea 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AddressRewriteEntry.md @@ -79,10 +79,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -220,7 +220,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md index 483f18b777..d28efe084b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AdminAuditLogConfig.md @@ -216,10 +216,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -367,7 +367,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md index 357ad0acdd..1fd98b932b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishPolicy.md @@ -155,10 +155,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -1008,7 +1008,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md index 9eaee6f351..79f8149312 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AntiPhishRule.md @@ -119,10 +119,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -330,7 +330,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-App.md b/exchange/exchange-ps/ExchangePowerShell/Set-App.md index e8479f8ba7..40a4be577f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-App.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-App.md @@ -84,10 +84,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -266,7 +266,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md index 27fc6cbe35..7571c9a1a9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionCompliancePolicy.md @@ -402,10 +402,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md index bc57f36a22..f2cae5b3ab 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AppRetentionComplianceRule.md @@ -94,10 +94,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md index 3ec1523491..4002fd7d78 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ApplicationAccessPolicy.md @@ -83,10 +83,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -104,7 +104,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch doesn't work on this cmdlet. +This parameter is reserved for internal Microsoft use. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md index 186ccedfc6..762a14cb65 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ArcConfig.md @@ -146,10 +146,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -167,7 +167,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md b/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md index 1ab845faa7..89649d068f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AtpPolicyForO365.md @@ -98,10 +98,10 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -163,7 +163,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md index 44cfb9288e..6b7910e6b4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AttachmentFilterListConfig.md @@ -91,10 +91,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -168,7 +168,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md index 11bda9fb86..49225e41fc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthConfig.md @@ -128,10 +128,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -319,7 +319,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md index f7f6d20f7d..b632832b0c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthRedirect.md @@ -71,17 +71,17 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter Parameter Sets: (All) Aliases: cf -Required: True +Required: False Position: Named Default value: None Accept pipeline input: False @@ -128,7 +128,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md index 34c75d5f97..c3fdd47bc4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthServer.md @@ -156,10 +156,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -318,7 +318,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md index 3f08006d9c..224d210531 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AuthenticationPolicy.md @@ -776,10 +776,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -817,7 +817,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md index 4ebbe9dacf..e2dd60a56e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelPolicy.md @@ -301,10 +301,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md index 9ae88fcfc1..698be48c4d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutoSensitivityLabelRule.md @@ -248,10 +248,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md index 744222c1d0..e27ebf3bd5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AutodiscoverVirtualDirectory.md @@ -114,10 +114,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -243,8 +243,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The ExternalURL parameter specifies the URL that connects to the virtual directory from outside the firewall. ```yaml @@ -263,8 +261,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The InternalURL parameter specifies the URL that connects to the virtual directory from inside the firewall. ```yaml @@ -304,7 +300,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md index 9ab4cea775..3f00581f3c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityConfig.md @@ -92,10 +92,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -203,7 +203,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md index f389e38d22..30cba6f578 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-AvailabilityReportOutage.md @@ -133,10 +133,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -228,7 +228,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md index 51c3da14fd..e565bff1a5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailbox.md @@ -276,10 +276,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -560,8 +560,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The HasActiveSyncDevicePartnership parameter specifies whether the mailbox has an Exchange ActiveSync device partnership established. Valid values are: - $true: The mailbox has an ActiveSync device partnership. @@ -1391,7 +1389,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md index 1decd4223a..e8d06ad845 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CASMailboxPlan.md @@ -99,10 +99,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -260,7 +260,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md index 091fb0cdf5..7cec8f7e0d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarNotification.md @@ -132,10 +132,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -292,7 +292,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md index 775ad6b35a..966cb2f90d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CalendarProcessing.md @@ -485,10 +485,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -1107,7 +1107,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md index bc70dd1d53..a95942c24d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldPolicy.md @@ -203,10 +203,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md index 4d708d298c..63a9f6bf03 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CaseHoldRule.md @@ -87,10 +87,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md index f5cef86ed3..8a7a3c5897 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClassificationRuleCollection.md @@ -67,10 +67,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. @@ -110,7 +110,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md index 4d53955d58..5631e78689 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessArray.md @@ -86,10 +86,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -185,7 +185,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md index cb504abd42..6a78963d3c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md @@ -231,10 +231,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -556,7 +556,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md index 536a73cd14..b9d1da6d9d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessServer.md @@ -194,10 +194,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -233,8 +233,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The IrmLogEnabled parameter specifies whether logging is enabled for Information Rights Management (IRM). Valid values are $true or $false. The default value is $true. ```yaml @@ -253,8 +251,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The IrmLogMaxAge parameter specifies the max age for IRM logs. Logs older than the specified value are deleted. To specify a value, enter it as a time span: dd.hh:mm:ss where d = days, h = hours, m = minutes, and s = seconds. @@ -277,8 +273,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The IrmLogMaxDirectorySize parameter specifies the maximum directory size for IRM logs. When the maximum directory size is reached, the server deletes the old log files first. A valid value is a number up to 909.5 terabytes (999999999999999 bytes) or the value unlimited. The default value is 250 megabytes (262144000 bytes). @@ -309,8 +303,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The IrmLogMaxFileSize parameter specifies the maximum size of the IRM log. This value can't be larger than the IrmLogMaxDirectorySize parameter value. A valid value is a number up to 4 gigabytes (4294967296 bytes). The default value is 10 megabytes (10485760 bytes). @@ -342,8 +334,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The IrmLogPath parameter specifies the location of the IRM log files. The default location is %ExchangeInstallPath%Logging\\IRMLogs. If you set the value of this parameter to $null, you effectively disable IRM logging. However, if the value of the IrmLogEnabled parameter is $true, Exchange adds errors to the Application event log. The preferred way to disable IRM logging is to set the IrmLogEnabled parameter to $false. @@ -364,8 +354,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - This parameter is reserved for internal Microsoft use. ```yaml @@ -402,7 +390,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md index 3bac4bc435..78e3925a05 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessService.md @@ -180,10 +180,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -237,7 +237,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md index ab5d7587a4..d4cd790327 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-CmdletExtensionAgent.md @@ -73,10 +73,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -148,7 +148,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceCase.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceCase.md index 0c963c7373..308a9e7389 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceCase.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceCase.md @@ -113,10 +113,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md index fa99a6d365..2f3a2eec45 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceRetentionEventType.md @@ -85,10 +85,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md index 53c13e57ad..375c319e29 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearch.md @@ -236,10 +236,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -663,7 +663,7 @@ Accept wildcard characters: False The WhatIf switch doesn't work in Security & Compliance PowerShell. -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md index 804dd4d09c..2114e32706 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSearchAction.md @@ -89,10 +89,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -126,10 +126,11 @@ Accept wildcard characters: False ### -WhatIf -> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance +The WhatIf switch doesn't work in Security & Compliance PowerShell. -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance ```yaml Type: SwitchParameter Parameter Sets: (All) diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md index 9cdefd0084..a06bbd2e81 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceSecurityFilter.md @@ -106,10 +106,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -224,10 +224,11 @@ Accept wildcard characters: False ### -WhatIf -> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance - The WhatIf switch doesn't work in Security & Compliance PowerShell. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Security & Compliance ```yaml Type: SwitchParameter Parameter Sets: (All) diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceTag.md b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceTag.md index ce7ef0ef05..2d1ea81abf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceTag.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ComplianceTag.md @@ -145,10 +145,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md index f0f4dbd5eb..1353e68c0c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Contact.md @@ -184,10 +184,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -866,7 +866,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md index 65aa1d670d..704a69fb77 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ContentFilterConfig.md @@ -132,10 +132,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -415,7 +415,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md index c2f844c7ab..053c18962b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DataClassification.md @@ -117,10 +117,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -258,7 +258,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md index 7cedcb2028..1ee1fa15b9 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DataEncryptionPolicy.md @@ -186,10 +186,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. @@ -304,7 +304,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md index 4506ab28c9..c42d85ec34 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroup.md @@ -423,10 +423,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -720,7 +720,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md index 797439c677..dc051c501e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DatabaseAvailabilityGroupNetwork.md @@ -77,10 +77,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -206,7 +206,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md index 0770a16271..eb79899a1c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeliveryAgentConnector.md @@ -129,10 +129,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -353,7 +353,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md index 694d1e14d3..87177d64da 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DetailsTemplate.md @@ -71,10 +71,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -128,7 +128,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md index de4b56a636..dbc27bea81 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessPolicy.md @@ -124,10 +124,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md index e15f54a9c1..888dc68305 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConditionalAccessRule.md @@ -696,10 +696,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md index 4a8c73f657..4340b02a2a 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationPolicy.md @@ -124,10 +124,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md index cb3738c26e..97948ca317 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceConfigurationRule.md @@ -668,10 +668,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md index da82206dbc..f7caab91fb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantPolicy.md @@ -102,10 +102,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantRule.md index eab06f7701..023dbe7715 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DeviceTenantRule.md @@ -118,10 +118,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md index 5ffb1af400..5b98cd6876 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DistributionGroup.md @@ -427,10 +427,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -1814,7 +1814,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md index 849727e1fd..24e5654ec6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DkimSigningConfig.md @@ -110,10 +110,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -193,7 +193,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md index 7132bead2c..c3b87529d6 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpCompliancePolicy.md @@ -541,10 +541,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md index b6ad40f86a..4c4a90a2c2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpComplianceRule.md @@ -553,10 +553,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpEdmSchema.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpEdmSchema.md index 33ba5f5c87..371d7684c4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpEdmSchema.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpEdmSchema.md @@ -66,10 +66,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpKeywordDictionary.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpKeywordDictionary.md index 79c6e3fc03..7bff27b169 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpKeywordDictionary.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpKeywordDictionary.md @@ -128,10 +128,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md index 487a682cf5..5fdccce2fc 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpPolicy.md @@ -73,10 +73,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -190,7 +190,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md index f8cef885f8..b1ba78bdad 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationType.md @@ -117,10 +117,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationTypeRulePackage.md b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationTypeRulePackage.md index f28f8ac9b9..f736ec5759 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationTypeRulePackage.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DlpSensitiveInformationTypeRulePackage.md @@ -66,10 +66,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md b/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md index 631d913d2e..7bc6f05d5e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-DynamicDistributionGroup.md @@ -817,10 +817,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -2175,7 +2175,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md index e4c9c32aac..64176d22b5 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EOPProtectionPolicyRule.md @@ -107,10 +107,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -318,7 +318,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md index b0e7e83f48..ade1df2467 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EcpVirtualDirectory.md @@ -156,10 +156,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -422,7 +422,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md index 920bf426f6..10d44b69ac 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EdgeSyncServiceConfig.md @@ -105,10 +105,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -421,7 +421,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md index e76f3faaef..8d614e08ee 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EmailAddressPolicy.md @@ -588,10 +588,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -855,7 +855,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md index cc9f05b22b..22180633af 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EmailTenantSettings.md @@ -65,10 +65,10 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -143,7 +143,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md index 730b3b7b3a..adbc955ba2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-EventLogLevel.md @@ -88,10 +88,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -109,7 +109,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md index 8edb5ada29..dc875bb96d 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeAssistanceConfig.md @@ -116,10 +116,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -430,7 +430,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md index a2e2cc0c75..5d027ea37e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeFeature.md @@ -125,10 +125,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -164,7 +164,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md index 272dc46423..a1d1b6a523 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeServer.md @@ -99,10 +99,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -426,7 +426,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md index c96b1f21ce..cd7e738cea 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExchangeSettings.md @@ -489,10 +489,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. @@ -815,7 +815,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md index c35d90b225..a8b60e9530 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExoPhishSimOverrideRule.md @@ -148,10 +148,10 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -231,7 +231,7 @@ Accept wildcard characters: False > Applicable: Exchange Online -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md index cd2728c85c..0e7449d8fa 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ExoSecOpsOverrideRule.md @@ -98,10 +98,10 @@ Accept wildcard characters: False > Applicable: Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FeatureConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-FeatureConfiguration.md index 70bc6decf7..2e3ab9ca16 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FeatureConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FeatureConfiguration.md @@ -107,10 +107,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -185,7 +185,7 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md index dc2a85e8bc..1b16248aad 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederatedOrganizationIdentifier.md @@ -106,10 +106,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -221,7 +221,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md index 819498437b..8932ba0100 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FederationTrust.md @@ -150,10 +150,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -261,7 +261,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyAuthority.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyAuthority.md index 2f500c9bff..bff0252493 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyAuthority.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyAuthority.md @@ -66,10 +66,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCategory.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCategory.md index 7643afcc0f..81ecc3b7e4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCategory.md @@ -64,10 +64,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCitation.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCitation.md index fe10f51f45..b4cb6920fb 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCitation.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyCitation.md @@ -105,10 +105,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyDepartment.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyDepartment.md index aa1f144242..f655fdde1b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyDepartment.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyDepartment.md @@ -71,10 +71,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyReferenceId.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyReferenceId.md index 9f9b2aa030..0dabd3630e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyReferenceId.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertyReferenceId.md @@ -67,10 +67,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertySubCategory.md b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertySubCategory.md index d5177695be..3fb2e5b1a2 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertySubCategory.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FilePlanPropertySubCategory.md @@ -67,10 +67,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. -- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: -Confirm:$false. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md index 1bd8e67f1f..375d5cf26e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ForeignConnector.md @@ -131,10 +131,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -379,7 +379,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md index 80858cd2a6..ab398f696f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-FrontendTransportService.md @@ -250,10 +250,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -1073,7 +1073,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md index 306df6f224..5a63a58b24 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-GlobalAddressList.md @@ -534,10 +534,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -694,7 +694,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-Group.md b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md index 9ed78dad09..b500dcca17 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-Group.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-Group.md @@ -117,10 +117,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -404,7 +404,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md index a4a3c22e5e..854f8af548 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HoldCompliancePolicy.md @@ -204,10 +204,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md index 2e2d383903..1855a7cdcf 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HoldComplianceRule.md @@ -93,10 +93,10 @@ Accept wildcard characters: False > Applicable: Security & Compliance -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md index d42be66013..db471c3120 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedConnectionFilterPolicy.md @@ -123,10 +123,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -231,7 +231,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md index a5a8042bce..5abe45c8a7 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterPolicy.md @@ -345,10 +345,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -1398,7 +1398,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md index a0af58485a..aed7ebc494 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedContentFilterRule.md @@ -97,10 +97,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -334,7 +334,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md index 878a28ee60..01824a7a4c 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterPolicy.md @@ -186,10 +186,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -306,7 +306,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md index 1e13c1a609..8f190c547f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HostedOutboundSpamFilterRule.md @@ -94,10 +94,10 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -331,7 +331,7 @@ Accept wildcard characters: False > Applicable: Exchange Online, Built-in security add-on for on-premises mailboxes -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md index a14551aa67..d8b468f0ac 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-HybridConfiguration.md @@ -100,10 +100,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -273,8 +273,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.509 certificate to be used as the certificate for hybrid deployment secure message transport. This certificate can't be self-signed, must be obtained from a trusted certificate authority (CA), and must be installed on all Hub Transport servers defined in the TransportServers parameter. ```yaml @@ -367,8 +365,6 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010 -This parameter is available only in Exchange Server 2010. - The TransportServers parameter specifies the Hub Transport servers in Exchange Server 2010 SP2 or later that are configured to support hybrid deployment features. You need to specify at least one Hub Transport server that's accessible from the internet for secure mail between on-premises Exchange and Exchange Online. @@ -391,7 +387,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md index d477fe5dd9..f69e9144c3 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListConfig.md @@ -49,10 +49,10 @@ This example configures connection filtering to use the IP Allow list on message > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -144,7 +144,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md index 14d6c09bd6..a04336e5f4 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-IPAllowListProvider.md @@ -117,10 +117,10 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on if the cmdlet requires confirmation before proceeding. +The Confirm switch specifies whether to show or hide the confirmation prompt. How this switch affects the cmdlet depends on whether the cmdlet requires confirmation before proceeding. - Destructive cmdlets (for example, Remove-\* cmdlets) have a built-in pause that forces you to acknowledge the command before proceeding. For these cmdlets, you can skip the confirmation prompt by using this exact syntax: `-Confirm:$false`. -- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you acknowledge the command before proceeding. +- Most other cmdlets (for example, New-\* and Set-\* cmdlets) don't have a built-in pause. For these cmdlets, specifying the Confirm switch without a value introduces a pause that forces you to acknowledge the command before proceeding. ```yaml Type: SwitchParameter @@ -254,7 +254,7 @@ Accept wildcard characters: False > Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE -The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. +The WhatIf switch shows what the command does without making any changes. You don't need to specify a value with this switch. ```yaml Type: SwitchParameter