diff --git a/.openpublishing.redirection.exchange.json b/.openpublishing.redirection.exchange.json index a791d72fe9..e13a297239 100644 --- a/.openpublishing.redirection.exchange.json +++ b/.openpublishing.redirection.exchange.json @@ -997,7 +997,7 @@ }, { "source_path": "exchange/virtual-folder/exchange/client-access/New-ClientAccessRule.md", - "redirect_url": "https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809", + "redirect_url": "/powershell/module/exchangepowershell/new-clientaccessrule", "redirect_document_id": false }, { @@ -10372,7 +10372,7 @@ }, { "source_path": "exchange/virtual-folder/exchange/New-ClientAccessRule.md", - "redirect_url": "https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809", + "redirect_url": "/powershell/module/exchangepowershell/new-clientaccessrule", "redirect_document_id": false }, { @@ -14234,11 +14234,6 @@ "source_path": "exchange/virtual-folder/exchange/Write-AdminAuditLog.md", "redirect_url": "/powershell/module/exchangepowershell/write-adminauditlog", "redirect_document_id": true - }, - { - "source_path": "exchange/virtual-folder/exchangepowershell/New-ClientAccessRule.md", - "redirect_url": "https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809", - "redirect_document_id": false } ] } diff --git a/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md b/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md index 3a8f2c1804..3ba710fd8f 100644 --- a/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md +++ b/exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md @@ -504,6 +504,8 @@ Exchange PowerShell is built on PowerShell technology to a powerful command-line ### [Get-TextMessagingAccount](Get-TextMessagingAccount.md) +### [New-ClientAccessRule](New-ClientAccessRule.md) + ### [New-OutlookProvider](New-OutlookProvider.md) ### [New-OwaMailboxPolicy](New-OwaMailboxPolicy.md) diff --git a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md index 954e243ebd..bcdfb71b9e 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md @@ -1,5 +1,5 @@ --- -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE author: chrisda external help file: Microsoft.Exchange.WebClient-Help.xml Locale: en-US @@ -14,11 +14,11 @@ title: Get-ClientAccessRule ## SYNOPSIS > [!NOTE] -> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). +> Client access rules were deprecated for all Exchange Online organizations in September 2025. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). -This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. +This cmdlet is functional only in Exchange Server 2019 or later. -Use the Get-ClientAccessRule cmdlet to view client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection. +Use the Get-ClientAccessRule cmdlet to view client access rules. Client access rules help you control access to your organization based on the properties of the connection. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -57,7 +57,7 @@ This example retrieves details about the client access rule named "Block Client ### -Identity -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The Identity parameter specifies the client access rule that you want to view. You can use any value that uniquely identifies the client access rule. For example: @@ -79,7 +79,7 @@ Accept wildcard characters: False ### -Confirm -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> 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. @@ -100,9 +100,7 @@ Accept wildcard characters: False ### -DomainController -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection - -This parameter is functional only in on-premises Exchange. +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE 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. @@ -120,7 +118,7 @@ Accept wildcard characters: False ### -WhatIf -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> 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. diff --git a/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md new file mode 100644 index 0000000000..0722c38e6e --- /dev/null +++ b/exchange/exchange-ps/ExchangePowerShell/New-ClientAccessRule.md @@ -0,0 +1,573 @@ +--- +applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE +author: chrisda +external help file: Microsoft.Exchange.WebClient-Help.xml +Locale: en-US +Module Name: ExchangePowerShell +ms.author: chrisda +online version: https://learn.microsoft.com/powershell/module/exchangepowershell/new-clientaccessrule +schema: 2.0.0 +title: New-ClientAccessRule +--- + +# New-ClientAccessRule + +## SYNOPSIS +> [!NOTE] +> Client access rules were deprecated for all Exchange Online organizations in September 2025. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). + +This cmdlet is functional only in Exchange Server 2019 or later. + +Use the New-ClientAccessRule cmdlet to create client access rules. Client access rules help you control access to your organization based on the properties of the connection. + +For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). + +## SYNTAX + +``` +New-ClientAccessRule [-Name] -Action + [-AnyOfAuthenticationTypes ] + [-AnyOfClientIPAddressesOrRanges ] + [-AnyOfProtocols ] + [-AnyOfSourceTcpPortNumbers ] + [-Confirm] + [-DomainController ] + [-Enabled ] + [-ExceptAnyOfAuthenticationTypes ] + [-ExceptAnyOfClientIPAddressesOrRanges ] + [-ExceptAnyOfProtocols ] + [-ExceptAnyOfSourceTcpPortNumbers ] + [-ExceptUserIsMemberOf ] + [-ExceptUsernameMatchesAnyOfPatterns ] + [-Priority ] + [-Scope ] + [-UserIsMemberOf ] + [-UsernameMatchesAnyOfPatterns ] + [-UserRecipientFilter ] + [-WhatIf] + [] +``` + +## DESCRIPTION +Client access rules are like mail flow rules (also known as transport rules) for client connections to your organization. You use conditions and exceptions to identify the connections based on their properties, and actions that allow or block the connections. + +**Note**: Not all protocols support authentication type filters, and even protocols that support authentication type filters don't support all authentication types. The supported combinations are described in the following lists. Use caution when mixing protocols and authentication types in the same rule. + +Protocols that support authentication type filters: + +- ExchangeActiveSync: BasicAuthentication, OAuthAuthentication, and CertificateBasedAuthentication. +- ExchangeAdminCenter: BasicAuthentication and AdfsAuthentication. +- IMAP4: BasicAuthentication and OAuthAuthentication. +- OutlookWebApp: BasicAuthentication and AdfsAuthentication. +- POP3: BasicAuthentication and OAuthAuthentication. +- RemotePowerShell: BasicAuthentication and NonBasicAuthentication. + +Protocols that don't support authentication type filters: + +- ExchangeWebServices +- OfflineAddressBook +- OutlookAnywhere +- PowerShellWebServices +- REST +- UniversalOutlook + +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](https://learn.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions). + +## EXAMPLES + +### Example 1 +```powershell +New-ClientAccessRule -Name AllowRemotePS -Action Allow -AnyOfProtocols RemotePowerShell -Priority 1 +``` + +This example creates a highest priority rule that allows access to remote PowerShell. This rule is an important safeguard to preserve access to your organization. Without this rule, if you create rules that block your access to remote PowerShell, or that block all protocols for everyone, you lose the ability to fix the rules yourself (you need to call Microsoft Customer Service and Support). + +### Example 2 +```powershell +New-ClientAccessRule -Name "Block ActiveSync" -Action DenyAccess -AnyOfProtocols ExchangeActiveSync -ExceptAnyOfClientIPAddressesOrRanges 192.168.10.1/24 +``` + +This example creates a new client access rule named Block ActiveSync that blocks access for Exchange ActiveSync clients, except for clients in the IP address range 192.168.10.1/24. + +## PARAMETERS + +### -Name + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The Name parameter specifies a unique name for the client access rule. + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: True +Position: 1 +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Action + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The Action parameter specifies the action for the client access rule. Valid values for this parameter are AllowAccess and DenyAccess. + +```yaml +Type: ClientAccessRulesAction +Parameter Sets: (All) +Aliases: + +Required: True +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfAuthenticationTypes + +> Applicable: Exchange Server 2013, Exchange Server 2016 + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfClientIPAddressesOrRanges + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The AnyOfClientIPAddressesOrRanges parameter specifies a condition for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are: + +- Single IP address: For example, 192.168.1.1 or 2001:DB8::2AA:FF:C0A8:640A. +- IP address range: For example, 192.168.0.1-192.168.0.254 or 2001:DB8::2AA:FF:C0A8:640A-2001:DB8::2AA:FF:C0A8:6414. +- Classless Inter-Domain Routing (CIDR) IP address range: For example, 192.168.3.1/24 or 2001:DB8::2AA:FF:C0A8:640A/64. + +You can enter multiple values separated by commas. + +For more information about IPv6 addresses and syntax, see this Exchange 2013 article: [IPv6 address basics](https://learn.microsoft.com/exchange/ipv6-support-in-exchange-2013-exchange-2013-help#ipv6-address-basics). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfProtocols + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The AnyOfProtocols parameter specifies a condition for the client access rule that's based on the client's protocol. + +Valid values for this parameter are: + +- ExchangeActiveSync +- ExchangeAdminCenter +- ExchangeWebServices +- IMAP4 +- OfflineAddressBook +- OutlookAnywhere +- OutlookWebApp +- POP3 +- PowerShellWebServices +- RemotePowerShell +- REST +- UniversalOutlook (Mail and Calendar app) + +**Note**: In Exchange 2019, the only supported values are ExchangeAdminCenter and RemotePowerShell. + +You can enter multiple values separated by commas. Don't use quotation marks. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -AnyOfSourceTcpPortNumbers + +> Applicable: Exchange Server 2013 + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Confirm + +> 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. + +- 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. + +This cmdlet has a built-in pause, so use `-Confirm:$false` to skip the confirmation. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: cf + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -DomainController + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +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. + +```yaml +Type: Fqdn +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Enabled + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The Enabled parameter specifies whether the client access rule is enabled or disabled. Valid values for this parameter are $true or $false. The default value is $true. + +```yaml +Type: Boolean +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfAuthenticationTypes + +> Applicable: Exchange Server 2013, Exchange Server 2016 + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfClientIPAddressesOrRanges + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The ExceptAnyOfClientIPAddressesOrRanges parameter specifies an exception for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are: + +- Single IP address: For example, 192.168.1.1 or 2001:DB8::2AA:FF:C0A8:640A. +- IP address range: For example, 192.168.0.1-192.168.0.254 or 2001:DB8::2AA:FF:C0A8:640A-2001:DB8::2AA:FF:C0A8:6414. +- Classless Inter-Domain Routing (CIDR) IP address range: For example, 192.168.3.1/24 or 2001:DB8::2AA:FF:C0A8:640A/64. + +You can enter multiple values separated by commas. + +For more information about IPv6 addresses and syntax, see this Exchange 2013 article: [IPv6 address basics](https://learn.microsoft.com/exchange/ipv6-support-in-exchange-2013-exchange-2013-help#ipv6-address-basics). + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfProtocols + +> Applicable: Exchange Server 2013, Exchange Server 2016 + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptAnyOfSourceTcpPortNumbers + +> Applicable: Exchange Server 2013 + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptUserIsMemberOf + +> Applicable: Exchange Server 2013 + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -ExceptUsernameMatchesAnyOfPatterns + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The ExceptUsernameMatchesAnyOfPatterns parameter specifies an exception for the client access rule that's based on the user's account name in the format `\` (for example, `contoso.com\jeff`). This parameter accepts text and the wildcard character (\*) (for example, `*jeff*`, but not `jeff*`). Non-alphanumeric characters don't require an escape character. + +You can enter multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Priority + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The Priority parameter specifies a priority value for the rule that determines the order of rule processing. A lower integer value indicates a higher priority, the value 0 is the highest priority, and rules can't have the same priority value. + +Valid values and the default value for this parameter depend on the number of existing rules. For example, if there are 8 existing rules: + +- Valid priority values for the existing 8 rules are from 0 through 7. +- Valid priority values for a new rule (the 9th rule) are from 0 through 8. +- The default value for a new rule (the 9th rule) is 8. + +If you modify the priority value of a rule, the position of the rule in the list changes to match the priority value you specify. In other words, if you set the priority value of a rule to the same value as an existing rule, the priority value of the existing rule and all other lower priority rules after it is increased by 1. + +```yaml +Type: Int32 +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -Scope + +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The Scope parameter specifies the scope of the client access rule. Valid values are: + +- Users: The rule only applies to end-user connections. +- All: The rule applies to all connections (end-users and middle-tier apps). + +```yaml +Type: ClientAccessRulesScope +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UserIsMemberOf + +> Applicable: Exchange Server 2013 + +This parameter is reserved for internal Microsoft use. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -UsernameMatchesAnyOfPatterns + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The UsernameMatchesAnyOfPatterns parameter specifies a condition for the client access rule that's based on the user's account name in the format `\` (for example, `contoso.com\jeff`). This parameter accepts text and the wildcard character (\*) (for example, `*jeff*`, but not `jeff*`). Non-alphanumeric characters don't require an escape character. This parameter does not work with the -AnyOfProtocols UniversalOutlook parameter. + +You can enter multiple values separated by commas. + +```yaml +Type: MultiValuedProperty +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: True +``` + +### -UserRecipientFilter + +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE + +The UserRecipientFilter parameter specifies a condition for the client access rule that uses OPATH filter syntax to identify the user based on a limited set of recipient properties. Client Access Rules don't support the full list of available recipient properties. + +You can use the following properties with this parameter: + +- City +- Company +- CountryOrRegion (ISO 3166-1 alpha-2 country code.) +- CustomAttribute1 to CustomAttribute15 +- Department +- Office +- PostalCode +- StateOrProvince +- StreetAddress + +The basic syntax for this parameter is `"Property -ComparisonOperator 'Value'"`: + +- Property is one of the filterable properties in the list above (for example `City` or `CustomAttribute1`). +- ComparisonOperator is an OPATH comparison operator (for example `-eq` for equals and `-like` for string comparison). For more information about comparison operators, see [about_Comparison_Operators](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comparison_operators). +- Value is the property value to search for. Enclose text values and variables in single quotation marks (`'Value'` or `'$Variable'`). If a variable value contains single quotation marks, you need to identify (escape) the single quotation marks to expand the variable correctly. For example, instead of `'$User'`, use `'$($User -Replace "'","''")'`. Don't enclose integers or system values in quotation marks (for example, use `500`, `$true`, `$false`, or `$null` instead). +- Enclose the whole OPATH filter in double quotation marks " ". If the filter contains system values (for example, `$true`, `$false`, or `$null`), use single quotation marks ' ' instead. Although this parameter is a string (not a system block), you can also use braces { }, but only if the filter doesn't contain variables. + +For example: + +- `"City -eq 'Redmond'"` +- `"CountryOrRegion -eq 'SG'"`. + +You can chain multiple search criteria together using the logical operators `-and` and `-or`. For example: + +- `"CustomAttribute1 -eq 'AllowOWA' -and CountryOrRegion -eq AU'"` +- `"(CountryOrRegion -eq 'US' -and Department -eq 'Sales') -or Department -eq 'Research'"`. + +For detailed information about OPATH filter syntax in Exchange, see [Additional OPATH syntax information](https://learn.microsoft.com/powershell/exchange/recipient-filters#additional-opath-syntax-information). + +```yaml +Type: String +Parameter Sets: (All) +Aliases: + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### -WhatIf + +> 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. + +```yaml +Type: SwitchParameter +Parameter Sets: (All) +Aliases: wi + +Required: False +Position: Named +Default value: None +Accept pipeline input: False +Accept wildcard characters: False +``` + +### CommonParameters +This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/p/?LinkID=113216). + +## INPUTS + +### Input types +To see the input types that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data. + +## OUTPUTS + +### Output types +To see the return types, which are also known as output types, that this cmdlet accepts, see [Cmdlet Input and Output Types](https://go.microsoft.com/fwlink/p/?linkId=616387). If the Output Type field is blank, the cmdlet doesn't return data. + +## NOTES + +## RELATED LINKS diff --git a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md index 834cc6b4ad..c5e0fee161 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Remove-ClientAccessRule.md @@ -1,5 +1,5 @@ --- -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE author: chrisda external help file: Microsoft.Exchange.WebClient-Help.xml Locale: en-US @@ -14,11 +14,11 @@ title: Remove-ClientAccessRule ## SYNOPSIS > [!NOTE] -> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). +> Client access rules were deprecated for all Exchange Online organizations in September 2025. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). -This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. +This cmdlet is functional only in Exchange Server 2019 or later. -Use the Remove-ClientAccessRule cmdlet to remove client access rules. Client access rules help you control access to your cloud-based organization based on the properties of the connection. +Use the Remove-ClientAccessRule cmdlet to remove client access rules. Client access rules help you control access to your organization based on the properties of the connection. For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax). @@ -50,7 +50,7 @@ This example removes the existing client access rule named "Block Connections fr ### -Identity -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The Identity parameter specifies the client access rule that you want to remove. You can use any value that uniquely identifies the client access rule. For example: @@ -72,7 +72,7 @@ Accept wildcard characters: False ### -Confirm -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> 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. @@ -95,8 +95,6 @@ Accept wildcard characters: False > Applicable: 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. ```yaml @@ -113,7 +111,7 @@ Accept wildcard characters: False ### -WhatIf -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> 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. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md index 1ef7f5daaa..88efdecb83 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-ClientAccessRule.md @@ -1,5 +1,5 @@ --- -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE author: chrisda external help file: Microsoft.Exchange.WebClient-Help.xml Locale: en-US @@ -14,9 +14,9 @@ title: Set-ClientAccessRule ## SYNOPSIS > [!NOTE] -> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). +> Client access rules were deprecated for all Exchange Online organizations in September 2025. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). -This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. +This cmdlet is functional only in Exchange Server 2019 or later. Use the Set-ClientAccessRule cmdlet to modify existing client access rules. Client access rules help you control access to your organization based on the properties of the connection. @@ -88,7 +88,7 @@ This example adds the IP address range 172.17.17.27/16 to the existing client ac ### -Identity -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The Identity parameter specifies the client access rule that you want to modify. You can use any value that uniquely identifies the client access rule. For example: @@ -110,7 +110,7 @@ Accept wildcard characters: False ### -Action -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The Action parameter specifies the action for the client access rule. Valid values for this parameter are AllowAccess and DenyAccess. @@ -128,25 +128,9 @@ Accept wildcard characters: False ### -AnyOfAuthenticationTypes -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection - -This parameter is functional only in the cloud-based service. - -The AnyOfAuthenticationTypes parameter specifies a condition for the client access rule that's based on the client's authentication type. +> Applicable: Exchange Server 2013, Exchange Server 2016 -Valid values for this parameter are: - -- AdfsAuthentication -- BasicAuthentication -- CertificateBasedAuthentication -- NonBasicAuthentication -- OAuthAuthentication - -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"...}`. - -**Note**: Refer to the Description section to see which authentication types can be used with what protocols. +This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty @@ -162,7 +146,7 @@ Accept wildcard characters: False ### -AnyOfClientIPAddressesOrRanges -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The AnyOfClientIPAddressesOrRanges parameter specifies a condition for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are: @@ -190,7 +174,7 @@ Accept wildcard characters: False ### -AnyOfProtocols -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The AnyOfProtocols parameter specifies a condition for the client access rule that's based on the client's protocol. @@ -247,7 +231,7 @@ Accept wildcard characters: False ### -Confirm -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> 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. @@ -270,8 +254,6 @@ Accept wildcard characters: False > Applicable: 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. ```yaml @@ -288,7 +270,7 @@ Accept wildcard characters: False ### -Enabled -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The Enabled parameter specifies whether the client access rule is enabled or disabled. Valid values for this parameter are $true or $false. @@ -306,25 +288,9 @@ Accept wildcard characters: False ### -ExceptAnyOfAuthenticationTypes -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection - -This parameter is functional only in the cloud-based service. - -The ExceptAnyOfAuthenticationTypes parameter specifies an exception for the client access rule that's based on the client's authentication type. - -Valid values for this parameter are: - -- AdfsAuthentication -- BasicAuthentication -- CertificateBasedAuthentication -- NonBasicAuthentication -- OAuthAuthentication +> Applicable: Exchange Server 2013, Exchange Server 2016 -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"...}`. - -**Note**: Refer to the Description section to see which authentication types can be used with what protocols. +This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty @@ -340,7 +306,7 @@ Accept wildcard characters: False ### -ExceptAnyOfClientIPAddressesOrRanges -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The ExceptAnyOfClientIPAddressesOrRanges parameter specifies an exception for the client access rule that's based on the client's IPv4 or IPv6 address. Valid values are: @@ -368,30 +334,9 @@ Accept wildcard characters: False ### -ExceptAnyOfProtocols -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Online, Exchange Online Protection - -This parameter is functional only in the cloud-based service. +> Applicable: Exchange Server 2013, Exchange Server 2016 -The ExceptAnyOfProtocols parameter specifies an exception for the client access rule that's based on the client's protocol. - -Valid values for this parameter are: - -- ExchangeActiveSync -- ExchangeAdminCenter -- ExchangeWebServices -- IMAP4 -- OfflineAddressBook -- OutlookAnywhere -- OutlookWebApp -- POP3 -- PowerShellWebServices -- RemotePowerShell -- REST -- UniversalOutlook (Mail and Calendar app) - -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"...}`. +This parameter is reserved for internal Microsoft use. ```yaml Type: MultiValuedProperty @@ -443,9 +388,7 @@ Accept wildcard characters: False ### -ExceptUsernameMatchesAnyOfPatterns -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection - -This parameter is functional only in the cloud-based service. +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The ExceptUsernameMatchesAnyOfPatterns parameter specifies an exception for the client access rule that's based on the user's account name in the format `\` (for example, `contoso.com\jeff`). This parameter accepts text and the wildcard character (\*) (for example, `*jeff*`, but not `jeff*`). Non-alphanumeric characters don't require an escape character. @@ -467,7 +410,7 @@ Accept wildcard characters: False ### -Name -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The Name parameter specifies a unique name for the client access rule. @@ -485,7 +428,7 @@ Accept wildcard characters: False ### -Priority -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The Priority parameter specifies a priority value for the client access rule. A lower integer value indicates a higher priority, and a higher priority rule is evaluated before a lower priority rule. The default value is 1. @@ -503,7 +446,7 @@ Accept wildcard characters: False ### -Scope -> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE The Scope parameter specifies the scope of the client access rule. Valid values are: @@ -542,9 +485,7 @@ Accept wildcard characters: False ### -UsernameMatchesAnyOfPatterns -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection - -This parameter is functional only in the cloud-based service. +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The UsernameMatchesAnyOfPatterns parameter specifies a condition for the client access rule that's based on the user's account name in the format `\` (for example, `contoso.com\jeff`). This parameter accepts text and the wildcard character (\*) (for example, `*jeff*`, but not `jeff*`). Non-alphanumeric characters don't require an escape character. @@ -566,9 +507,7 @@ Accept wildcard characters: False ### -UserRecipientFilter -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection - -This parameter is functional only in the cloud-based service. +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The UserRecipientFilter parameter specifies a condition for the client access rule that uses OPATH filter syntax to identify the user based on a limited set of recipient properties. Client Access Rules don't support the full list of available recipient properties. @@ -617,7 +556,7 @@ Accept wildcard characters: False ### -WhatIf -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> 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. diff --git a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md index 164572be01..4eae5f7737 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md +++ b/exchange/exchange-ps/ExchangePowerShell/Set-OwaMailboxPolicy.md @@ -197,6 +197,20 @@ Set-OwaMailboxPolicy -Identity OwaMailboxPolicy-Default -UserVoiceEnabled $false This example disables Outlook UserVoice for the default mailbox policy in Microsoft 365. +### Example 5 +```powershell +Set-OwaMailboxPolicy -Identity "Default-OwaMailboxPolicy" -AllowedOrganizationAccountDomains $null +``` + +This example sets the allowed organizational accounts to $null for the default mailbox policy in an Exchange Online Organization, allowing users to add any other Exchange account to Outlook. + +### Example 6 +```powershell +Set-OwaMailboxPolicy -Identity "Default-OwaMailboxPolicy" -AllowedOrganizationAccountDomains "fabrikam.com","contoso.com" +``` + +This example sets the allowed organizational accounts to allow @fabrikam.com and @contoso.com accounts for the default mailbox policy in an Exchange Online Organization, allowing users to add accounts from those domains to Outlook, blocking all other domains. + ## PARAMETERS ### -Identity diff --git a/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md b/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md index c6cb852390..644ee6129b 100644 --- a/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md +++ b/exchange/exchange-ps/ExchangePowerShell/Test-ClientAccessRule.md @@ -1,5 +1,5 @@ --- -applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE author: chrisda external help file: Microsoft.Exchange.WebClient-Help.xml Locale: en-US @@ -14,9 +14,9 @@ title: Test-ClientAccessRule ## SYNOPSIS > [!NOTE] -> Beginning in October 2022, client access rules were deprecated for all Exchange Online organizations that weren't using them. Client access rules will be deprecated for all remaining organizations on September 1, 2025. If you choose to turn off client access rules before the deadline, the feature will be disabled in your organization. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). +> Client access rules were deprecated for all Exchange Online organizations in September 2025. For more information, see [Update on Client Access Rules Deprecation in Exchange Online](https://techcommunity.microsoft.com/blog/exchange/update-on-client-access-rules-deprecation-in-exchange-online/4354809). -This cmdlet is functional only in Exchange Server 2019 and in the cloud-based service. Some parameters and settings might be exclusive to one environment or the other. +This cmdlet is functional only in Exchange Server 2019 or later. Use the Test-ClientAccessRule cmdlet to test how client access rules affect access to your organization. If any of the client properties you specify for this cmdlet match any client access rules, the rules are returned in the results. @@ -63,7 +63,7 @@ This example tests client access by using the following client properties: ### -AuthenticationType -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The AuthenticationType parameter specifies the client authentication type to test. @@ -91,7 +91,7 @@ Accept wildcard characters: False ### -Protocol -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The Protocol parameter specifies the client protocol to test. @@ -125,7 +125,7 @@ Accept wildcard characters: False ### -RemoteAddress -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The RemoteAddress parameter specifies the client IP address to test. Valid input for this parameter is an IP address. For example, 192.168.1.50. @@ -145,7 +145,7 @@ Accept wildcard characters: False ### -RemotePort -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The RemotePort parameter specifies the client TCP port to test. Valid input for this parameter is an integer from 1 to 65535. @@ -163,7 +163,7 @@ Accept wildcard characters: False ### -User -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE The User parameter specifies the user account to test. @@ -201,7 +201,7 @@ Accept wildcard characters: False ### -Confirm -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> 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. @@ -222,7 +222,7 @@ Accept wildcard characters: False ### -OAuthClaims -> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> Applicable: Exchange Server 2016, Exchange Server 2019, Exchange Server SE The OAuthClaims parameter specifies the OAuth claims token of a middle-tier app. @@ -240,7 +240,7 @@ Accept wildcard characters: False ### -WhatIf -> Applicable: Exchange Server 2013, Exchange Server 2016, Exchange Server 2019, Exchange Server SE, Exchange Online, Exchange Online Protection +> 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. diff --git a/exchange/mapping/serviceMapping.json b/exchange/mapping/serviceMapping.json index 1289dfd983..096dc54d4c 100644 --- a/exchange/mapping/serviceMapping.json +++ b/exchange/mapping/serviceMapping.json @@ -244,6 +244,7 @@ "Remove-OutlookProvider": "client-access", "Remove-OwaMailboxPolicy": "client-access", "Send-TextMessagingVerificationCode": "client-access", + "New-ClientAccessRule": "client-access", "Set-CASMailbox": "client-access", "Set-CASMailboxPlan": "client-access", "Set-ClientAccessRule": "client-access",