Merge pull request MicrosoftDocs#2184 from MicrosoftDocs/chrisda

Chrisda to Master

Author: chrisda

exchange/exchange-ps/exchange/federation-and-hybrid/Set-RemoteMailbox.md

@@ -27,6 +27,8 @@ Get-MessageTrace [-EndDate <DateTime>] [-Expression <Expression>] [-FromIP <Stri
 ## DESCRIPTION
 You can use this cmdlet to search message data for the last 10 days. If you run this cmdlet without any parameters, only data from the last 48 hours is returned.
 
+ If you enter a time period that's older than 10 days, you won't receive an error, but the command will return no results. To search for message data that's between 10 and 90 days old, use the Start-HistoricalSearch and Get-HistoricalSearch cmdlets.
+
 This cmdlet returns a maximum of 1000000 results, and will timeout on very large queries. If your query returns too many results, consider splitting it up using smaller StartDate and EndDate intervals.
 
 You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not included in the permissions assigned to you. To find the permissions required to run any cmdlet or parameter in your organization, see Find the permissions required to run any Exchange cmdlet (https://technet.microsoft.com/library/mt432940.aspx).

exchange/exchange-ps/exchange/mail-flow/Get-MessageTrace.md

@@ -18,8 +18,7 @@ For information about the parameter sets in the Syntax section below, see Exchan
 ## SYNTAX
 
 ```
-Remove-MigrationUser [-Identity] <MigrationUserIdParameter> [-Confirm] [-DomainController <Fqdn>] [-Force]
- [-WhatIf] [-Partition <MailboxIdParameter>] [<CommonParameters>]
+Remove-MigrationUser [-Identity] <MigrationUserIdParameter> [-Confirm] [-DomainController <Fqdn>] [-Force] [-Partition <MailboxIdParameter>] [-WhatIf] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
@@ -88,43 +87,47 @@ Accept wildcard characters: False
 ```
 
 ### -Force
-The Force switch specifies that some specific checks and removal steps should be skipped and that the migration user should be forcibly removed. This parameter is used to work around issues where the migration user needs to be removed to fix issues when the user or data is corrupted, or to prevent such issues from occurring
+This parameter is available only in on-premises Exchange.
+
+The Force switch specifies that some specific checks and removal steps should be skipped and that the migration user should be forcibly removed. This parameter is used to work around issues where the migration user needs to be removed to fix issues when the user or data is corrupted, or to prevent such issues from occurring.
 
 ```yaml
 Type: SwitchParameter
 Parameter Sets: (All)
 Aliases:
-Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 Required: False
 Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -WhatIf
-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.
+### -Partition
+This parameter is available only in the cloud-based service.
+
+This parameter is reserved for internal Microsoft use.
 
 ```yaml
-Type: SwitchParameter
+Type: MailboxIdParameter
 Parameter Sets: (All)
-Aliases: wi
-Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Aliases:
+Applicable: Exchange Online
 Required: False
 Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Partition
-This parameter is reserved for internal Microsoft use.
+### -WhatIf
+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.
 
 ```yaml
-Type: MailboxIdParameter
+Type: SwitchParameter
 Parameter Sets: (All)
-Aliases:
-Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False
 Position: Named
 Default value: None

exchange/exchange-ps/exchange/mailboxes/Set-MailboxAutoReplyConfiguration.md

@@ -154,29 +154,29 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -WhatIf
-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.
+### -Force
+The Force switch specifies whether to suppress warning or confirmation messages. You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
-Parameter Sets: (All)
-Aliases: wi
-Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
+Parameter Sets: Identity
+Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False
 Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Force
-The Force switch specifies whether to suppress warning or confirmation messages. You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. You don't need to specify a value with this switch.
+### -WhatIf
+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.
 
 ```yaml
 Type: SwitchParameter
-Parameter Sets: Identity
-Aliases:
-Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Online
+Parameter Sets: (All)
+Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Online
 Required: False
 Position: Named
 Default value: None

exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationUser.md

@@ -22,7 +22,8 @@ For information about the parameter sets in the Syntax section below, see Exchan
 Remove-PublicFolderMoveRequest [-Identity] <PublicFolderMoveRequestIdParameter>
  [-Confirm]
  [-DomainController <Fqdn>]
- [-WhatIf] [-Force] [<CommonParameters>]
+ [-Force]
+ [-WhatIf] [<CommonParameters>]
 ```
 
 ### MigrationRequestQueue
@@ -147,29 +148,29 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -WhatIf
-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.
+### -Force
+The Force switch specifies whether to suppress warning or confirmation messages. You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. You don't need to specify a value with this switch.
 
 ```yaml
 Type: SwitchParameter
-Parameter Sets: (All)
-Aliases: wi
-Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
+Parameter Sets: Identity
+Aliases:
+Applicable: Exchange Server 2016, Exchange Server 2019
 Required: False
 Position: Named
 Default value: None
 Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Force
-The Force switch specifies whether to suppress warning or confirmation messages. You can use this switch to run tasks programmatically where prompting for administrative input is inappropriate. You don't need to specify a value with this switch.
+### -WhatIf
+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.
 
 ```yaml
 Type: SwitchParameter
-Parameter Sets: Identity
-Aliases:
-Applicable: Exchange Server 2016, Exchange Server 2019
+Parameter Sets: (All)
+Aliases: wi
+Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019
 Required: False
 Position: Named
 Default value: None

exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMigrationRequest.md

@@ -29,7 +29,7 @@ You need to be assigned permissions in the Office 365 Security & Compliance Cent
 
 ### -------------------------- Example 1 --------------------------
 ```
-New-SupervisoryReviewRule -Name "EU Brokers Rule" -Policy "EU Brokers Policy" -SamplingRate 100 -Conditions ((NOT(Reviewee:US Compliance)) -AND (Reviewee:EU Brokers) -AND ((trade) -OR (insider trading)) -AND (NOT(approved by the Contoso financial team)))
+New-SupervisoryReviewRule -Name "EU Brokers Rule" -Policy "EU Brokers Policy" -SamplingRate 100 -Conditions "((NOT(Reviewee:US Compliance)) -AND (Reviewee:EU Brokers) -AND ((trade) -OR (insider trading)) -AND (NOT(approved by the Contoso financial team)))"
 ```
 
 This example creates a new supervisory review rule named EU Brokers Rule with the following settings:
@@ -83,23 +83,23 @@ Accept wildcard characters: False
 ### -Condition
 The Condition parameter specifies the conditions and exceptions for the rule. This parameter uses the following syntax:
 
-- User or group communications to supervise: ((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...). Exceptions use the syntax (NOT((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...)).
+- User or group communications to supervise: "((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...)". Exceptions use the syntax "(NOT((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...))".
 
-- Direction: ((Direction:Inbound) -OR (Direction:Outbound) -OR (Direction:Internal)).
+- Direction: "((Direction:Inbound) -OR (Direction:Outbound) -OR (Direction:Internal))".
 
-- Message contains words: ((\<Word1orPhrase1\>) -OR (\<Word2orPhrase2\>)...). Exceptions use the syntax (NOT((\<Word1orPhrase1\>)-OR (\<Word2orPhrase2\>)...)).
+- Message contains words: "((\<Word1orPhrase1\>) -OR (\<Word2orPhrase2\>)...)". Exceptions use the syntax "(NOT((\<Word1orPhrase1\>)-OR (\<Word2orPhrase2\>)...))".
 
-- Any attachment contains words: ((Attachment:\<word1\>) -OR (Attachment:\<word2\>)...). Exceptions use the syntax (NOT((Attachment:\<word1\>)-OR (Attachment:\<word2\>)...)).
+- Any attachment contains words: "((Attachment:\<word1\>) -OR (Attachment:\<word2\>)...)". Exceptions use the syntax "(NOT((Attachment:\<word1\>)-OR (Attachment:\<word2\>)...))".
 
-- Any attachment has the extension: ((AttachmentName:.\<extension1\>) -OR (AttachmentName:.\<extension2\>)...). Exceptions use the syntax (NOT((AttachmentName:.\<extension1\>)-OR (AttachmentName:.\<extension2\>)...)).
+- Any attachment has the extension: "((AttachmentName:.\<extension1\>) -OR (AttachmentName:.\<extension2\>)...)". Exceptions use the syntax "(NOT((AttachmentName:.\<extension1\>)-OR (AttachmentName:.\<extension2\>)...))".
 
-- Message size is larger than: (MessageSize:\<size in B, KB, MB or GB\>). For example (MessageSize:300KB). Exceptions use the syntax (NOT(MessageSize:\<size in B, KB, MB or GB\>))
+- Message size is larger than: "(MessageSize:\<size in B, KB, MB or GB\>)". For example "(MessageSize:300KB)". Exceptions use the syntax "(NOT(MessageSize:\<size in B, KB, MB or GB\>))".
 
-- Any attachment is larger than: (AttachmentSize:\<size in B, KB, MB or GB\>). For example (AttachmentSize:3MB). Exceptions use the syntax (NOT(AttachmentSize:\<size in B, KB, MB or GB\>))
+- Any attachment is larger than: "(AttachmentSize:\<size in B, KB, MB or GB\>)". For example "(AttachmentSize:3MB)". Exceptions use the syntax "(NOT(AttachmentSize:\<size in B, KB, MB or GB\>))".
 
 - Parentheses ( ) are required around the whole filter.
 
-- Separate multiple conditions or exception types with the -AND operator. For example, ((Reviewee:[email protected]) -AND (AttachmentSize:3MB)).
+- Separate multiple conditions or exception types with the -AND operator. For example, "((Reviewee:[email protected]) -AND (AttachmentSize:3MB))".
 
 ```yaml
 Type: String

exchange/exchange-ps/exchange/move-and-migration/Remove-PublicFolderMoveRequest.md

@@ -29,10 +29,14 @@ You need to be assigned permissions in the Office 365 Security & Compliance Cent
 
 ### -------------------------- Example 1 --------------------------
 ```
-Set-SupervisoryReviewRule -Identity "EU Brokers Rule" -AddReviewers [email protected]
+Set-SupervisoryReviewRule -Identity "EU Brokers Rule" -Conditions "((NOT(Reviewee:US Compliance)) -AND (Reviewee:EU Brokers) -AND ((trade) -OR (insider trading)) -AND (NOT(approved by the Contoso financial team)))"
 ```
 
-This example adds the reviewer [email protected] to the rule named EU Brokers Rule.
+This example modifies the existing rule named EU Brokers Rule with the following settings:
+
+- Conditions: Supervise inbound and outbound communications for members of the EU Brokers group that contain the words trade or insider trading.
+
+- Exceptions: Exclude supervision for members of the EU Compliance group, or messages that contain the phrase "approved by the Contoso financial team".
 
 ## PARAMETERS
 
@@ -60,23 +64,23 @@ Accept wildcard characters: False
 ### -Condition
 The Condition parameter specifies the conditions and exceptions for the rule. This parameter uses the following syntax:
 
-- User or group communications to supervise: ((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...). Exceptions use the syntax (NOT((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...)).
+- User or group communications to supervise: "((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...)". Exceptions use the syntax "(NOT((Reviewee:\<emailaddress1\>) -OR (Reviewee:\<emailaddress2\>)...))".
 
-- Direction :((Direction:Inbound) -OR (Direction:Outbound) -OR (Direction:Internal)).
+- Direction: "((Direction:Inbound) -OR (Direction:Outbound) -OR (Direction:Internal))".
 
-- Message contains words: ((\<Word1orPhrase1\>)-OR (\<Word2orPhrase2\>)...). Exceptions use the syntax (NOT((\<Word1orPhrase1\>)-OR (\<Word2orPhrase2\>)...)).
+- Message contains words: "((\<Word1orPhrase1\>) -OR (\<Word2orPhrase2\>)...)". Exceptions use the syntax "(NOT((\<Word1orPhrase1\>) -OR (\<Word2orPhrase2\>)...))".
 
-- Any attachment contains words: ((Attachment:\<word1\>)-OR (Attachment:\<word2\>)...). Exceptions use the syntax (NOT((Attachment:\<word1\>)-OR (Attachment:\<word2\>)...)).
+- Any attachment contains words: "((Attachment:\<word1\>) -OR (Attachment:\<word2\>)...)". Exceptions use the syntax "(NOT((Attachment:\<word1\>) -OR (Attachment:\<word2\>)...))".
 
-- Any attachment has the extension: ((AttachmentName:.\<extension1\>)-OR (AttachmentName:.\<extension2\>)...). Exceptions use the syntax (NOT((AttachmentName:.\<extension1\>)-OR (AttachmentName:.\<extension2\>)...)).
+- Any attachment has the extension: "((AttachmentName:.\<extension1\>) -OR (AttachmentName:.\<extension2\>)...)". Exceptions use the syntax "(NOT((AttachmentName:.\<extension1\>) -OR (AttachmentName:.\<extension2\>)...))".
 
-- Message size is larger than: (MessageSize:\<size in B, KB, MB or GB\>). For example (MessageSize:300KB). Exceptions use the syntax (NOT(MessageSize:\<size in B, KB, MB or GB\>))
+- Message size is larger than: "(MessageSize:\<size in B, KB, MB or GB\>)". For example "(MessageSize:300KB)". Exceptions use the syntax "(NOT(MessageSize:\<size in B, KB, MB or GB\>))".
 
-- Any attachment is larger than: (AttachmentSize:\<size in B, KB, MB or GB\>). For example (AttachmentSize:3MB). Exceptions use the syntax (NOT(AttachmentSize:\<size in B, KB, MB or GB\>))
+- Any attachment is larger than: "(AttachmentSize:\<size in B, KB, MB or GB\>)". For example "(AttachmentSize:3MB)". Exceptions use the syntax "(NOT(AttachmentSize:\<size in B, KB, MB or GB\>))".
 
 - Parentheses ( ) are required around the whole filter.
 
-- Separate multiple conditions or exception types with the -AND operator. For example, ((Reviewee:[email protected]) -AND (AttachmentSize:3MB)).
+- Separate multiple conditions or exception types with the -AND operator. For example, "((Reviewee:[email protected]) -AND (AttachmentSize:3MB))".
 
 ```yaml
 Type: String