Set-InboxRule (ExchangePowerShell) By chrisda Archived: 2026-04-05 22:44:38 UTC In this article 1. Syntax 2. Description 3. Examples 4. Parameters 5. Inputs 6. Outputs This cmdlet is available in on-premises Exchange and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. Use the Set-InboxRule cmdlet to modify existing Inbox rules in mailboxes. Inbox rules process messages in the Inbox based on conditions specified and take actions such as moving a message to a specified folder or deleting a message. For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax. Set-InboxRule [-Identity] [-AlwaysDeleteOutlookRulesBlob] [-ApplyCategory ] [-ApplySystemCategory ] [-BodyContainsWords ] [-Confirm] [-CopyToFolder ] [-DeleteMessage ] [-DeleteSystemCategory ] [-DomainController ] [-ExceptIfBodyContainsWords ] [-ExceptIfFlaggedForAction ] [-ExceptIfFrom ] [-ExceptIfFromAddressContainsWords ] [-ExceptIfHasAttachment ] [-ExceptIfHasClassification ] [-ExceptIfHeaderContainsWords ] [-ExceptIfMessageTypeMatches ] [-ExceptIfMyNameInCcBox ] https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 1 of 51 [-ExceptIfMyNameInToBox ] [-ExceptIfMyNameInToOrCcBox ] [-ExceptIfMyNameNotInToBox ] [-ExceptIfReceivedAfterDate ] [-ExceptIfReceivedBeforeDate ] [-ExceptIfRecipientAddressContainsWords ] [-ExceptIfSentOnlyToMe ] [-ExceptIfSentTo ] [-ExceptIfSubjectContainsWords ] [-ExceptIfSubjectOrBodyContainsWords ] [-ExceptIfWithImportance ] [-ExceptIfWithinSizeRangeMaximum ] [-ExceptIfWithinSizeRangeMinimum ] [-ExceptIfWithSensitivity ] [-FlaggedForAction ] [-Force] [-ForwardAsAttachmentTo ] [-ForwardTo ] [-From ] [-FromAddressContainsWords ] [-HasAttachment ] [-HasClassification ] [-HeaderContainsWords ] [-Mailbox ] [-MarkAsRead ] [-MarkImportance ] [-MessageTypeMatches ] [-MoveToFolder ] [-MyNameInCcBox ] [-MyNameInToBox ] [-MyNameInToOrCcBox ] [-MyNameNotInToBox ] [-Name ] [-PinMessage ] [-Priority ] [-ReceivedAfterDate ] [-ReceivedBeforeDate ] [-RecipientAddressContainsWords ] [-RedirectTo ] [-SendTextMessageNotificationTo ] [-SentOnlyToMe ] [-SentTo ] [-SoftDeleteMessage ] [-StopProcessingRules ] [-SubjectContainsWords ] [-SubjectOrBodyContainsWords ] [-WhatIf] https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 2 of 51 [-WithImportance ] [-WithinSizeRangeMaximum ] [-WithinSizeRangeMinimum ] [-WithSensitivity ] [] The Set-InboxRule cmdlet allows you to modify the rule conditions, exceptions, and actions. When you create, modify, remove, enable, or disable an Inbox rule in Exchange PowerShell, any client-side rules created by Microsoft Outlook are removed. You need to be assigned permissions before you can run this cmdlet. Although this article lists all parameters for the cmdlet, you might not have access to some parameters if they aren't 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. Set-InboxRule -Mailbox chris@contoso.com -Name ProjectContoso -MarkImportance "High" This example modifies the action of the existing Inbox rule ProjectContoso. The MarkImportance parameter is used to mark the message with high importance. Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The AlwaysDeleteOutlookRulesBlob switch hides a warning message when you use Outlook on the web (formerly known as Outlook Web App) or Exchange PowerShell to modify Inbox rules. You don't need to specify a value with this switch. Type: SwitchParameter Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 3 of 51 Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ApplyCategory parameter specifies an action for the Inbox rule that applies the specified category to messages. A valid value is any text value that you want to define as a category. You can specify multiple categories separated by commas. If the value contains spaces, enclose the value in quotation marks ("). The categories that you specify for this parameter are defined in the mailbox (they aren't shared between mailboxes). Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ApplySystemCategory parameter specifies an action for the Inbox rule that applies the specified system category to messages. System categories are available to all mailboxes in the organization. Valid values are: NotDefined Bills Document DocumentPlus Event Family File Flight FromContact Important LiveView Lodging MailingList https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 4 of 51 Newsletter Photo Purchase RentalCar RestaurantReservation RetiredPromotion ShippingNotification Shopping SocialUpdate Travel Video To enter multiple values and overwrite any existing entries, use the following syntax: Value1,Value2,...ValueN . To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The BodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the body of messages. To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 5 of 51 The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfBodyContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: 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. 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. Type: SwitchParameter Default value: None Supports wildcards: False DontShow: False Aliases: cf (All) Position: Named https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 6 of 51 Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The CopyToFolder parameter specifies an action for the Inbox rule that copies messages to the specified mailbox folder. The syntax is MailboxID:\ParentFolder[\SubFolder] . For the value of MailboxID , you can use any value that uniquely identifies the mailbox. For example: Name Alias Distinguished name (DN) Canonical DN Domain\Username Email address GUID LegacyExchangeDN SamAccountName User ID or user principal name (UPN) Example values for this parameter are john@contoso.com:\Marketing or John:\Inbox\Reports . Type: MailboxFolderIdParameter Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 7 of 51 Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The DeleteMessage parameter specifies an action for the Inbox rule that sends messages to the Deleted Items folder. Valid values are: $true: Messages that match the conditions of the rule are moved to the Deleted Items folder. $false: The action isn't used. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The DeleteSystemCategory parameter specifies an action for the Inbox rule that deletes the specified system category from messages. System categories are available to all mailboxes in the organization. Valid values are: NotDefined Bills Document DocumentPlus Event Family File Flight FromContact Important LiveView Lodging MailingList Newsletter https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 8 of 51 Photo Purchase RentalCar RestaurantReservation RetiredPromotion ShippingNotification Shopping SocialUpdate Travel Video You can specify multiple values separated by commas. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE This parameter is available only in on-premises Exchange. The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory. You identify the domain controller by its fully qualified domain name (FQDN). For example, dc01.contoso.com. Type: Fqdn Default value: None Supports wildcards: False DontShow: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 9 of 51 (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the body of messages. To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is BodyContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 10 of 51 The ExceptIfFlaggedForAction parameter specifies an exception for the Inbox rule that looks messages with the specified message flag. Valid values are: Any Call DoNotForward FollowUp ForYourInformation Forward NoResponseNecessary Read Reply ReplyToAll Review The corresponding condition parameter to this exception is FlaggedForAction. Type: String Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfFrom parameter specifies an exception for the Inbox rule that looks for the specified sender in messages. You can use any value that uniquely identifies the sender. For example: Name Alias Distinguished name (DN) Canonical DN Email address https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 11 of 51 GUID You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . The corresponding condition parameter to this exception is From. Type: RecipientIdParameter[] Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfFromAddressContainsWords parameter specifies an exception for the Inbox rule that looks for messages where the specified words are in the sender's email address. To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is FromAddressContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 12 of 51 DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfHasAttachment parameter specifies an exception for the Inbox rule that looks for messages with attachments. Valid values are: $true: The rule action isn't applied to messages that have attachments. $false: The exception isn't used. The corresponding condition parameter to this exception is HasAttachment. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfHasClassification parameter specifies an exception for the Inbox rule that looks for messages with the specified message classification. You can find message classifications by using the Get-MessageClassification cmdlet. You can specify multiple message classifications separated by commas. https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 13 of 51 The corresponding condition parameter to this exception is HasClassification. Type: MessageClassificationIdParameter[] Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The HeaderContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the header fields of messages. To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is HeaderContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 14 of 51 Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfMessageTypeMatches parameter specifies an exception for the Inbox rule that looks for messages of the specified type. Valid values are: AutomaticReply AutomaticForward Encrypted Calendaring CalendaringResponse PermissionControlled Voicemail Signed ApprovalRequest ReadReceipt NonDeliveryReport The corresponding condition parameter to this exception is MessageTypeMatches. Type: InboxRuleMessageType Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 15 of 51 Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfMyNameInCcBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the Cc field. Valid values are: $true: The rule action isn't applied to messages where the mailbox owner is in the Cc field. $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameInCcBox. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfMyNameInToBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the To field. Valid values are: $true: The rule action isn't applied to messages where the mailbox owner is in the To field. $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameInToBox. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 16 of 51 Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfMyNameInToOrCcBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner is in the To or Cc fields Valid values are. $true: The rule action isn't applied to messages where the mailbox owner is in the To or Cc fields. $false: The exception isn't used. The corresponding condition parameter to this exception is MyNameInToOrCcBox. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfMyNameNotInToBox parameter specifies an exception for the Inbox rule that looks for messages where the mailbox owner isn't in the To field. Valid values are: $true: The rule action isn't applied to messages where the mailbox owner isn't in the To field. $false: The exception isn't used. https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 17 of 51 The corresponding condition parameter to this exception is MyNameNotInToBox. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfReceivedAfterDate parameter specifies an exception for the Inbox rule that looks for messages received after the specified date. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". The corresponding condition parameter to this exception is ReceivedAfterDate. Type: ExDateTime Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 18 of 51 Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfReceivedBeforeDate parameter specifies an exception for the Inbox rule that looks for messages received before the specified date. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". The corresponding condition parameter to this exception is ReceivedBeforeDate. Type: ExDateTime Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfRecipientAddressContainsWords parameter specifies an exception for the Inbox rule that looks for messages where the specified words are in recipient email addresses. To enter multiple values and overwrite any existing entries, use the following syntax: Value1,Value2,...ValueN . If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 19 of 51 The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is RecipientAddressContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfSentOnlyToMe parameter specifies an exception for the Inbox rule that looks for messages where the only recipient is the mailbox owner. Valid values are: $true: The rule action isn't applied to messages where the mailbox owner is the only recipient. $false: The exception isn't used. The corresponding condition parameter to this exception is SentOnlyToMe. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 20 of 51 Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfSentTo parameter specifies an exception that looks for recipients in messages. You can use any value that uniquely identifies the recipient. For example: Name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . The corresponding condition parameter to this exception is SentTo. Type: RecipientIdParameter[] Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfSubjectContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the Subject field of messages. https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 21 of 51 To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is SubjectContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfSubjectOrBodyContainsWords parameter specifies an exception for the Inbox rule that looks for the specified words or phrases in the Subject field or body of messages. To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. The corresponding condition parameter to this exception is SubjectOrBodyContainsWords. Type: MultiValuedProperty Default value: None https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 22 of 51 Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfWithImportance parameter specifies an exception for the Inbox rule that looks for messages with the specified importance level. Valid values are: High Normal Low The corresponding condition parameter to this exception is WithImportance. Type: Importance Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 23 of 51 The ExceptIfWithinSizeRangeMaximum parameter specifies part of an exception for the Inbox rule that looks for messages that smaller than specified maximum size. When you enter a value, qualify the value with one of the following units: B (bytes) KB (kilobytes) MB (megabytes) GB (gigabytes) TB (terabytes) Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the ExceptIfWithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of ExceptIfWithinSizeRangeMinimum. The corresponding condition parameter to this exception is WithinSizeRangeMaximum. Type: ByteQuantifiedSize Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfWithinSizeRangeMinimum parameter specifies part of an exception for the Inbox rule that looks for messages that are larger than the specified minimum size. When you enter a value, qualify the value with one of the following units: B (bytes) KB (kilobytes) MB (megabytes) GB (gigabytes) https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 24 of 51 TB (terabytes) Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the ExceptIfWithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of ExceptIfWithinSizeRangeMaximum. The corresponding condition parameter to this exception is WithinSizeRangeMinimum. Type: ByteQuantifiedSize Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ExceptIfWithSensitivity parameter specifies an exception for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are: Normal Personal Private CompanyConfidential The corresponding condition parameter to this exception is WithSensitivity. Type: Sensitivity Default value: None Supports wildcards: False DontShow: False (All) https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 25 of 51 Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The FlaggedForAction parameter specifies a condition for the Inbox rule that looks for messages with the specified message flag. Valid values are: Any Call DoNotForward FollowUp ForYourInformation Forward NoResponseNecessary Read Reply ReplyToAll Review Type: String Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 26 of 51 Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The Force switch hides warning or confirmation messages. You don't need to specify a value with this switch. A confirmation prompt warns you if the mailbox contains rules that were created by Outlook, because any client-side rules are removed by the actions of this cmdlet. Type: SwitchParameter Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ForwardAsAttachmentTo parameter specifies an action for the Inbox rule that forwards the message to the specified recipient as an attachment. You can use any value that uniquely identifies the recipient. For example: Name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . Type: RecipientIdParameter[] Default value: None https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 27 of 51 Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ForwardTo parameter specifies an action for the Inbox rule that forwards the message to the specified recipient. You can use any value that uniquely identifies the recipient. For example: Name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . Type: RecipientIdParameter[] Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 28 of 51 Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The From parameter specifies a condition for the Inbox rule that looks for the specified sender in messages. You can use any value that uniquely identifies the sender. For example: Name Alias Distinguished name (DN) Canonical DN Email address GUID You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . The corresponding exception parameter to this condition is ExceptIfFrom. Type: RecipientIdParameter[] Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The FromAddressContainsWords parameter specifies a condition for the Inbox rule that looks for messages where the specified words are in the sender's email address. https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 29 of 51 To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfFromAddressContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The HasAttachment parameter specifies a condition for the Inbox rule that looks for messages with attachments. Valid values are: $true: The rule action is applied to messages that have attachments. $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfHasAttachment. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 30 of 51 Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The HasClassification parameter specifies a condition for the Inbox rule that looks for messages with the specified message classification. You can find message classifications by using the Get-MessageClassification cmdlet. You can specify multiple message classifications separated by commas. The corresponding exception parameter to this condition is ExceptIfHasClassification. Type: MessageClassificationIdParameter[] Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The HeaderContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the header fields of messages. To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 31 of 51 To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfHeaderContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The Identity parameter specifies the Inbox rule that you want to modify. You can use any value that uniquely identifies the rule. For example: Name RuleIdentity property (for example, 16752869479666417665). Exchange Online: MailboxAlias\RuleIdentity (for example, rzaher\16752869479666417665 ). On-premises Exchange: MailboxCanonicalName\RuleIdentity (for example, contoso.com/Users/Rick Zaher\16752869479666417665 ). Type: InboxRuleIdParameter Default value: None Supports wildcards: False DontShow: False (All) Position: 1 https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 32 of 51 Mandatory: True Value from pipeline: True Value from pipeline by property name: True Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The Mailbox parameter specifies the mailbox that contains the Inbox rule. You can use any value that uniquely identifies the mailbox. For example: Name Alias Distinguished name (DN) Canonical DN Domain\Username Email address GUID LegacyExchangeDN SamAccountName User ID or user principal name (UPN) Type: MailboxIdParameter Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The MarkAsRead parameter specifies an action for the Inbox rule that marks messages as read. Valid values are: https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 33 of 51 $true: Messages that match the conditions of the rule are marked as read. $false: The action isn't used. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The MarkImportance parameter specifies an action for the Inbox rule that marks messages with the specified importance flag. Valid values are: Low Normal High Type: Importance Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 34 of 51 Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The MessageTypeMatches parameter specifies a condition for the Inbox rule that looks for messages of the specified type. Valid values are: AutomaticReply AutomaticForward Encrypted Calendaring CalendaringResponse PermissionControlled Voicemail Signed ApprovalRequest ReadReceipt NonDeliveryReport The corresponding exception parameter to this condition is ExceptIfMessageTypeMatches. Type: InboxRuleMessageType Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The MoveToFolder parameter specifies an action for the Inbox rule that moves messages to the specified mailbox folder. The syntax is MailboxID:\ParentFolder[\SubFolder] . https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 35 of 51 For the value of MailboxID , you can use any value that uniquely identifies the mailbox. For example: Name Alias Distinguished name (DN) Canonical DN Domain\Username Email address GUID LegacyExchangeDN SamAccountName User ID or user principal name (UPN) Example values for this parameter are john@contoso.com:\Marketing or John:\Inbox\Reports . Type: MailboxFolderIdParameter Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The MyNameInCcBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the Cc field. Valid values are: $true: The rule action is applied to messages where the mailbox owner is in the Cc field. $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameInCcBox. Type: Boolean Default value: None https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 36 of 51 Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The MyNameInToBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the To field. Valid values are: $true: The rule action is applied to messages where the mailbox owner is in the To field. $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameInToBox. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 37 of 51 The MyNameInToOrCcBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner is in the To or Cc fields Valid values are. $true: The rule action is applied to messages where the mailbox owner is in the To or Cc fields. $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameInToOrCcBox. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The MyNameNotInToBox parameter specifies a condition for the Inbox rule that looks for messages where the mailbox owner isn't in the To field. Valid values are: $true: The rule action is applied to messages where the mailbox owner isn't in the To field. $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfMyNameNotInToBox. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 38 of 51 Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The Name parameter specifies a name for the Inbox rule. The maximum length is 512 characters. If the value contains spaces, enclose the value in quotation marks ("). Type: String Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The PinMessage parameter specifies an action for the Inbox rule that pins messages to the top of the Inbox. Valid values are: $true: Message that match the conditions of the rule are pinned to the top of the Inbox. $false: The action isn't used. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 39 of 51 Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The Priority parameter specifies a priority for the Inbox rule that determines the order of rule processing. A lower integer value indicates a higher priority, Type: Int32 Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ReceivedAfterDate parameter specifies a condition for the Inbox rule that looks for messages received after the specified date. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". The corresponding exception parameter to this condition is ExceptIfReceivedAfterDate. https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 40 of 51 Type: ExDateTime Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The ReceivedBeforeDate parameter specifies a condition for the Inbox rule that looks for messages received before the specified date. Use the short date format that's defined in the Regional Options settings on the computer where you're running the command. For example, if the computer is configured to use the short date format MM/dd/yyyy, enter 09/01/2018 to specify September 1, 2018. You can enter the date only, or you can enter the date and time of day. If you enter the date and time of day, enclose the value in quotation marks ("), for example, "09/01/2018 5:00 PM". The corresponding exception parameter to this condition is ExceptIfReceivedBeforeDate. Type: ExDateTime Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 41 of 51 Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The RecipientAddressContainsWords parameter specifies a condition for the Inbox rule that looks for messages where the specified words are in recipient email addresses. To enter multiple values and overwrite any existing entries, use the following syntax: Value1,Value2,...ValueN . If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfRecipientAddressContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The RedirectTo parameter specifies an action for the Inbox rule that redirects the message to the specified recipient. You can use any value that uniquely identifies the recipient. For example: Name Alias Distinguished name (DN) Canonical DN https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 42 of 51 Email address GUID You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . Type: RecipientIdParameter[] Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE This parameter is available only in on-premises Exchange. The SendTextMessageNotificationTo parameter specifies an action for the Inbox rule that send a text message notification to the specified telephone number. To enter multiple values and overwrite any existing entries, use the following syntax: Value1,Value2,...ValueN . If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 43 of 51 (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The SentOnlyToMe parameter specifies a condition for the Inbox rule that looks for messages where the only recipient is the mailbox owner. Valid values are: $true: The rule action is applied to messages where the mailbox owner is the only recipient. $false: The condition isn't used. The corresponding exception parameter to this condition is ExceptIfSentOnlyToMe. Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The SentTo parameter specifies a condition for the Inbox rule that looks for messages with the specified recipients. You can use any value that uniquely identifies the recipient. For example: Name Alias https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 44 of 51 Distinguished name (DN) Canonical DN Email address GUID You can enter multiple values separated by commas. If the values contain spaces or otherwise require quotation marks, use the following syntax: "Value1","Value2",..."ValueN" . The corresponding exception parameter to this condition is ExceptIfSentTo. Type: RecipientIdParameter[] Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Online This parameter is available only in the cloud-based service. {{ Fill SoftDeleteMessage Description }} Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 45 of 51 Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The StopProcessingRules parameter specifies an action for the Inbox rule that stops processing additional rules if the conditions of this Inbox rule are met. Valid values are:If set to $true, the StopProcessingRules parameter instructs Exchange to stop processing additional rules if the conditions of this Inbox rule are met. $true: Stop processing more rules. $false: The action isn't used (continue processing more rules after this one). Type: Boolean Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The SubjectContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the Subject field of messages. To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 46 of 51 The corresponding exception parameter to this condition is ExceptIfSubjectContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The SubjectOrBodyContainsWords parameter specifies a condition for the Inbox rule that looks for the specified words or phrases in the Subject field or body of messages. To specify multiple words or phrases that overwrite any existing entries, use the following syntax: Word1,"Phrase with spaces",word2,...wordN . Don't use leading or trailing spaces. To add or remove one or more values without affecting any existing entries, use the following syntax: @{Add="Value1","Value2"...; Remove="Value3","Value4"...} . The maximum length of this parameter is 255 characters. The corresponding exception parameter to this condition is ExceptIfSubjectOrBodyContainsWords. Type: MultiValuedProperty Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 47 of 51 Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: 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. Type: SwitchParameter Default value: None Supports wildcards: False DontShow: False Aliases: wi (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The WithImportance parameter specifies a condition for the Inbox rule that looks for messages with the specified importance level. Valid values are: High Normal Low The corresponding exception parameter to this condition is ExceptIfWithImportance. Type: Importance Default value: None https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 48 of 51 Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The WithinSizeRangeMaximum parameter specifies part of a condition for the Inbox rule that looks for messages that are smaller than specified maximum size. When you enter a value, qualify the value with one of the following units: B (bytes) KB (kilobytes) MB (megabytes) GB (gigabytes) TB (terabytes) Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the WithinSizeRangeMinimum parameter, and the value of this parameter must be greater than the value of WithinSizeRangeMinimum. The corresponding exception parameter to this condition is ExceptIfWithinSizeRangeMaximum. Type: ByteQuantifiedSize Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 49 of 51 Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online The WithinSizeRangeMinimum parameter specifies part of a condition for the Inbox rule that looks for messages that are larger than the specified minimum size. When you enter a value, qualify the value with one of the following units: B (bytes) KB (kilobytes) MB (megabytes) GB (gigabytes) TB (terabytes) Unqualified values are typically treated as bytes, but small values might be rounded up to the nearest kilobyte. You need to use this parameter with the WithinSizeRangeMaximum parameter, and the value of this parameter must be less than the value of WithinSizeRangeMaximum. The corresponding exception parameter to this condition is ExceptIfWithinSizeRangeMinimum. Type: ByteQuantifiedSize Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False Applicable: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 50 of 51 The WithSensitivity parameter specifies a condition for the Inbox rule that looks for messages with the specified sensitivity level. Valid values are: Normal Personal Private CompanyConfidential The corresponding exception parameter to this condition is ExceptIfWithSensitivity. Type: Sensitivity Default value: None Supports wildcards: False DontShow: False (All) Position: Named Mandatory: False Value from pipeline: False Value from pipeline by property name: False Value from remaining arguments: False This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, - InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters. Input types To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. Output types To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn't return data. Source: https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps https://docs.microsoft.com/en-us/powershell/module/exchange/set-inboxrule?view=exchange-ps Page 51 of 51