Skip to content

Commit 280a3dc

Browse files
authored
Merge pull request #10002 from MicrosoftDocs/chrisda
Chrisda to Main
2 parents 7b49a7a + 549abf1 commit 280a3dc

File tree

2 files changed

+13
-0
lines changed

2 files changed

+13
-0
lines changed

exchange/docs-conceptual/app-only-auth-powershell-v2.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,14 @@ The following examples show how to use the Exchange Online PowerShell module wit
5050

5151
> [!IMPORTANT]
5252
> In the following **Connect-** commands, be sure to use an `.onmicrosoft.com` domain for the _Organization_ parameter value. Otherwise, you might encounter cryptic permission issues when you run commands in the app context.
53+
>
54+
> In Microsoft 365 GCC High or DoD environments, the connection commands require the following additional parameters and values:
55+
>
56+
> - **Connect-ExchangeOnline in GCC High**: `-ExchangeEnvironmentName O365USGovGCCHigh`.
57+
> - **Connect-IPPSSession in GCC High**: `-ConnectionUri https://ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndpointUri https://login.microsoftonline.us/common`.
58+
>
59+
> - **Connect-ExchangeOnline in DoD**: `-ExchangeEnvironmentName O365USGovDoD`.
60+
> - **Connect-IPPSSession in DoD**: `-ConnectionUri https://l5.ps.compliance.protection.office365.us/powershell-liveid/ -AzureADAuthorizationEndpointUri https://login.microsoftonline.us/common`.
5361
5462
- **Connect using a certificate thumbprint**:
5563

exchange/docs-conceptual/disable-access-to-exchange-online-powershell.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,11 @@ Exchange Online PowerShell enables you to manage your Exchange Online organizati
2424

2525
- Microsoft 365 global admins have access to Exchange Online PowerShell, and can use the procedures in this article to configure Exchange Online PowerShell access for other users. For more information about permissions in Exchange Online, see [Feature Permissions in Exchange Online](/exchange/permissions-exo/feature-permissions).
2626

27+
> [!IMPORTANT]
28+
> Don't run commands like `Get-User | Set-User -RemotePowerShellEnabled $false` to universally remove remote PowerShell access without considering admin accounts. Use the procedures in this article to selectively remove remote PowerShell access, or preserve admin access for at least one account by using the following syntax in your removal command: `Get-User | Where-Object {$_.UserPrincipalName -ne '[email protected]'} | Set-User -RemotePowerShellEnabled $false`.
29+
>
30+
> If you accidentally lock yourself out of remote PowerShell access, create a new admin user account, and then use that account to give yourself remote PowerShell access.
31+
2732
- You can only use Exchange Online PowerShell to perform this procedure. To connect to Exchange Online PowerShell, see [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md).
2833

2934
- For detailed information about OPath filter syntax in Exchange Online, see [Additional OPATH syntax information](recipient-filters.md#additional-opath-syntax-information).

0 commit comments

Comments
 (0)