You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -73,7 +73,7 @@ Exchange Online Protection PowerShell allows you to manage your Exchange Online
73
73
74
74
- For Exchange Online Protection subscriptions that are Exchange Enterprise CAL with Services (includes data loss prevention (DLP) and reporting using web services), use the _ConnectionUri_ value: `https://outlook.office365.com/powershell-liveid/`
75
75
76
-
3. Run the following command.
76
+
3. Run the following command:
77
77
78
78
```
79
79
Import-PSSession $Session
@@ -97,7 +97,13 @@ If you receive errors, check the following requirements:
97
97
- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online Protection organization.
98
98
99
99
- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy.
100
-
100
+
101
+
- The **New-PSSession** command (Step 2) might fail to connect if your client IP address changes during the connection request. This can happen if your organization uses a source network address translation (SNAT) pool that contains multiple IP addresses. The connection error looks like this:
102
+
103
+
`The request for the Windows Remote Shell with ShellId <ID> failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation.`
104
+
105
+
To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Exchange Online Protection PowerShell endpoint.
106
+
101
107
## See also
102
108
103
109
The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics.
Copy file name to clipboardExpand all lines: exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md
+9-3Lines changed: 9 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: "Connect to Office 365 Security & Compliance Center PowerShell"
3
3
ms.author: chrisda
4
4
author: chrisda
5
5
manager: serdars
6
-
ms.date: 12/13/2017
6
+
ms.date: 5/9/2018
7
7
ms.audience: Admin
8
8
ms.topic: article
9
9
ms.service: o365-security-and-compliance
@@ -72,7 +72,7 @@ For more information about the Security & Compliance Center, see [Office 365
72
72
73
73
**Note**: For Office 365 Germany, use the _ConnectionUri_ value: `https://ps.compliance.protection.outlook.de/powershell-liveid/`
74
74
75
-
3. Run the following command.
75
+
3. Run the following command:
76
76
77
77
```
78
78
Import-PSSession $Session
@@ -98,7 +98,13 @@ If you receive errors, check the following requirements:
98
98
- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to the Security & Compliance Center.
99
99
100
100
- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy.
101
-
101
+
102
+
- The **New-PSSession** command (Step 2) might fail to connect if your client IP address changes during the connection request. This can happen if your organization uses a source network address translation (SNAT) pool that contains multiple IP addresses. The connection error looks like this:
103
+
104
+
`The request for the Windows Remote Shell with ShellId <ID> failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation.`
105
+
106
+
To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Security & Compliance PowerShell endpoint.
107
+
102
108
## See also
103
109
104
110
The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics.
Copy file name to clipboardExpand all lines: exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md
+5-1Lines changed: 5 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: "Connect to Office 365 Security & Compliance Center PowerShell using multi-factor authentication"
3
3
ms.author: chrisda
4
4
author: chrisda
5
-
ms.date: 12/13/2017
5
+
ms.date: 5/9/2018
6
6
ms.audience: Admin
7
7
ms.topic: article
8
8
ms.service: o365-security-and-compliance
@@ -106,4 +106,8 @@ If you receive errors, check the following requirements:
106
106
107
107
- TCP port 80 traffic needs to be open between your local computer and Office 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy.
108
108
109
+
- The **Connect-IPPSSession** command (Step 2) might fail to connect if your client IP address changes during the connection request. This can happen if your organization uses a source network address translation (SNAT) pool that contains multiple IP addresses. The connection error looks like this:
109
110
111
+
`The request for the Windows Remote Shell with ShellId <ID> failed because the shell was not found on the server. Possible causes are: the specified ShellId is incorrect or the shell no longer exists on the server. Provide the correct ShellId or create a new shell and retry the operation.`
112
+
113
+
To fix the issue, use an SNAT pool that contains a single IP address, or force the use of a specific IP address for connections to the Security & Compliance PowerShell endpoint.
0 commit comments