Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 2 additions & 7 deletions .openpublishing.redirection.exchange.json
Original file line number Diff line number Diff line change
Expand Up @@ -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
},
{
Expand Down Expand Up @@ -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
},
{
Expand Down Expand Up @@ -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
}
]
}
2 changes: 2 additions & 0 deletions exchange/exchange-ps/ExchangePowerShell/ExchangePowerShell.md
Original file line number Diff line number Diff line change
Expand Up @@ -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)
Expand Down
18 changes: 8 additions & 10 deletions exchange/exchange-ps/ExchangePowerShell/Get-ClientAccessRule.md
Original file line number Diff line number Diff line change
@@ -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
Expand All @@ -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).

Expand Down Expand Up @@ -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:

Expand All @@ -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.

Expand All @@ -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.

Expand All @@ -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.

Expand Down
Loading