Skip to content

Commit 189849e

Browse files
authored
Merge pull request MicrosoftDocs#982 from MicrosoftDocs/ExMigration
ExMigration to Master
2 parents 36d3e55 + 0705903 commit 189849e

File tree

8 files changed

+934
-10
lines changed

8 files changed

+934
-10
lines changed

exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md

Lines changed: 11 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Connect to Exchange Online Protection PowerShell"
33
ms.author: chrisda
44
author: chrisda
55
manager: serdars
6-
ms.date: 7/10/2017
6+
ms.date: 5/9/2018
77
ms.audience: Admin
88
ms.topic: article
99
ms.service: eop
@@ -53,15 +53,15 @@ Exchange Online Protection PowerShell allows you to manage your Exchange Online
5353
5454
## Connect to Exchange Online Protection
5555

56-
1. On your local computer, open Windows PowerShell and run the following command.
56+
1. On your local computer, open Windows PowerShell and run the following command:
5757

5858
```
5959
$UserCredential = Get-Credential
6060
```
6161

6262
In the **Windows PowerShell Credential Request** dialog box, type your work or school account and password, and then click **OK**.
6363

64-
2. Run the following command.
64+
2. Run the following command:
6565

6666
```
6767
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.protection.outlook.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection
@@ -73,7 +73,7 @@ Exchange Online Protection PowerShell allows you to manage your Exchange Online
7373
7474
- 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/`
7575
76-
3. Run the following command.
76+
3. Run the following command:
7777
7878
```
7979
Import-PSSession $Session
@@ -97,7 +97,13 @@ If you receive errors, check the following requirements:
9797
- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online Protection organization.
9898
9999
- 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+
101107
## See also
102108
103109
The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics.

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Connect to Office 365 Security &amp; Compliance Center PowerShell"
33
ms.author: chrisda
44
author: chrisda
55
manager: serdars
6-
ms.date: 12/13/2017
6+
ms.date: 5/9/2018
77
ms.audience: Admin
88
ms.topic: article
99
ms.service: o365-security-and-compliance
@@ -72,7 +72,7 @@ For more information about the Security &amp; Compliance Center, see [Office 365
7272
7373
**Note**: For Office 365 Germany, use the _ConnectionUri_ value: `https://ps.compliance.protection.outlook.de/powershell-liveid/`
7474
75-
3. Run the following command.
75+
3. Run the following command:
7676
7777
```
7878
Import-PSSession $Session
@@ -98,7 +98,13 @@ If you receive errors, check the following requirements:
9898
- To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to the Security &amp; Compliance Center.
9999
100100
- 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+
102108
## See also
103109
104110
The cmdlets that you use in this topic are Windows PowerShell cmdlets. For more information about these cmdlets, see the following topics.

exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: "Connect to Office 365 Security &amp; Compliance Center PowerShell using multi-factor authentication"
33
ms.author: chrisda
44
author: chrisda
5-
ms.date: 12/13/2017
5+
ms.date: 5/9/2018
66
ms.audience: Admin
77
ms.topic: article
88
ms.service: o365-security-and-compliance
@@ -106,4 +106,8 @@ If you receive errors, check the following requirements:
106106
107107
- 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.
108108
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:
109110
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.
Lines changed: 86 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,86 @@
1+
---
2+
external help file: Microsoft.Exchange.RolesAndAccess-Help.xml
3+
applicable: Exchange Online
4+
title: Get-AuthenticationPolicy
5+
schema: 2.0.0
6+
monikerRange: "exchonline-ps"
7+
---
8+
9+
# Get-AuthenticationPolicy
10+
11+
## SYNOPSIS
12+
> [!NOTE]
13+
> This topic describes a preview feature that isn't available to everyone, and is subject to change.
14+
15+
This cmdlet is available only in the cloud-based service.
16+
17+
Use the Get-AuthenticationPolicy cmdlet to view authentication policies in Exchange Online.
18+
19+
For information about the parameter sets in the Syntax section below, see Exchange cmdlet syntax (https://technet.microsoft.com/library/bb123552.aspx).
20+
21+
## SYNTAX
22+
23+
```
24+
Get-AuthenticationPolicy [[-Identity] <AuthPolicyIdParameter>] [<CommonParameters>]
25+
```
26+
27+
## DESCRIPTION
28+
You need to be assigned permissions before you can run this cmdlet. Although this topic lists all parameters for the cmdlet, you may not have access to some parameters if they're not 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://technet.microsoft.com/library/mt432940.aspx).
29+
30+
## EXAMPLES
31+
32+
### -------------------------- Example 1 --------------------------
33+
```
34+
Get-AuthenticationPolicy | Format-Table -Auto Name
35+
```
36+
37+
This example returns a summary list of all authentication policies.
38+
39+
### -------------------------- Example 2 --------------------------
40+
```
41+
Get-AuthenticationPolicy -Identity "Engineering Group"
42+
```
43+
44+
This example returns detailed information for the authentication policy named Engineering Group.
45+
46+
## PARAMETERS
47+
48+
### -Identity
49+
The Identity parameter specifies the authentication policy you want to view. You can use any value that uniquely identifies the policy. For example:
50+
51+
- Name
52+
53+
- Distinguished name (DN)
54+
55+
- GUID
56+
57+
```yaml
58+
Type: AuthPolicyIdParameter
59+
Parameter Sets: (All)
60+
Aliases:
61+
Applicable: Exchange Online
62+
Required: False
63+
Position: 0
64+
Default value: None
65+
Accept pipeline input: False
66+
Accept wildcard characters: False
67+
```
68+
69+
### CommonParameters
70+
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).
71+
72+
## INPUTS
73+
74+
###
75+
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.
76+
77+
## OUTPUTS
78+
79+
###
80+
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.
81+
82+
## NOTES
83+
84+
## RELATED LINKS
85+
86+
[Online Version](https://docs.microsoft.com/powershell/module/exchange/organization/get-authenticationpolicy)

0 commit comments

Comments
 (0)