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
Copy file name to clipboardExpand all lines: exchange/docs-conceptual/app-only-auth-powershell-v2.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,13 +23,13 @@ description: "Learn about using the Exchange Online V2 module in scripts and oth
23
23
> The features and procedures described in this article require the following versions of the EXO V2 module:
24
24
>
25
25
> -**Exchange Online PowerShell (Connect-ExchangeOnline)**: Version 2.0.3 or later.
26
-
> -**Security & Compliance Center PowerShell (Connect-IPPSSession)**: Version 2.0.6 Preview5 or later.
26
+
> -**Security & Compliance PowerShell (Connect-IPPSSession)**: Version 2.0.6 Preview5 or later.
27
27
>
28
28
> For instructions on how to install or update the module, see [Install and maintain the EXO V2 module](exchange-online-powershell-v2.md#install-and-maintain-the-exo-v2-module).
29
29
>
30
30
> You can't use the procedures in this article to modify Microsoft 365 Groups ([Set-UnifiedGroup](/powershell/module/exchange/set-unifiedgroup)). To use Microsoft Graph instead, see [Update group](/graph/api/group-update).
31
31
32
-
Auditing and reporting scenarios in Microsoft 365 often involve unattended scripts in Exchange Online PowerShell and Security & Compliance Center PowerShell. In the past, unattended sign in required you to store the username and password in a local file or in a secret vault that's accessed at run-time. But, as we all know, storing user credentials locally is not a good security practice.
32
+
Auditing and reporting scenarios in Microsoft 365 often involve unattended scripts in Exchange Online PowerShell and Security & Compliance PowerShell. In the past, unattended sign in required you to store the username and password in a local file or in a secret vault that's accessed at run-time. But, as we all know, storing user credentials locally is not a good security practice.
33
33
34
34
Certificate based authentication (CBA) or app-only authentication as described in this article supports unattended script and automation scenarios by using Azure AD apps and self-signed certificates.
35
35
@@ -46,7 +46,7 @@ The following examples show how to use the Exchange Online PowerShell V2 module
@@ -287,7 +287,7 @@ The Security Administrator role does not have the necessary permissions for thos
287
287
For general instructions about assigning roles in Azure AD, see [View and assign administrator roles in Azure Active Directory](/azure/active-directory/roles/manage-roles-portal).
288
288
289
289
> [!NOTE]
290
-
> The following steps are slightly different for Exchange Online PowerShell vs. Security & Compliance Center PowerShell. The steps for both environments are shown. To configure roles for both environments, repeat the steps in this section.
290
+
> The following steps are slightly different for Exchange Online PowerShell vs. Security & Compliance PowerShell. The steps for both environments are shown. To configure roles for both environments, repeat the steps in this section.
291
291
292
292
1. On the Azure AD portal at <https://portal.azure.com/>, under **Manage Azure Active Directory**, click **View**.
293
293
@@ -303,19 +303,19 @@ For general instructions about assigning roles in Azure AD, see [View and assign
303
303
304
304
305
305
306
-
-**Security & Compliance Center PowerShell**:
306
+
-**Security & Compliance PowerShell**:
307
307
308
-
308
+
309
309
310
310
4. On the **Assignments** page that opens, click **Add assignments**.
311
311
312
312
-**Exchange Online PowerShell**:
313
313
314
314
315
315
316
-
-**Security & Compliance Center PowerShell**:
316
+
-**Security & Compliance PowerShell**:
317
317
318
-
318
+
319
319
320
320
5. In the **Add assignments** flyout that opens, find and select the app that you created in [Step 1](#step-1-register-the-application-in-azure-ad).
321
321
@@ -329,6 +329,6 @@ For general instructions about assigning roles in Azure AD, see [View and assign
329
329
330
330
331
331
332
-
-**Security & Compliance Center PowerShell**:
332
+
-**Security & Compliance PowerShell**:
333
333
334
-
334
+
Copy file name to clipboardExpand all lines: exchange/docs-conceptual/basic-auth-connect-to-scc-powershell.md
+13-15Lines changed: 13 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: "Basic auth - Connect to Security & Compliance Center PowerShell"
2
+
title: "Basic auth - Connect to Security & Compliance PowerShell"
3
3
ms.author: chrisda
4
4
author: chrisda
5
5
manager: dansimp
@@ -12,15 +12,15 @@ ms.localizationpriority: medium
12
12
ms.assetid:
13
13
ROBOTS: NOINDEX
14
14
search.appverid: MET150
15
-
description: "Learn how to connect to Security & Compliance Center PowerShell."
15
+
description: "Learn how to connect to Security & Compliance PowerShell."
16
16
---
17
17
18
-
# Basic auth - Connect to Security & Compliance Center PowerShell
18
+
# Basic auth - Connect to Security & Compliance PowerShell
19
19
20
20
> [!NOTE]
21
-
> The connection instructions in this article [will eventually be deprecated](https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-july-update/ba-p/1530163) due to the security concerns around Basic authentication. Instead, you should use the Exchange Online PowerShell V2 module (the EXO V2 module) to connect to Security & Compliance Center PowerShell. For instructions, see [Connect to Security & Compliance Center PowerShell](connect-to-scc-powershell.md).
21
+
> The connection instructions in this article [will eventually be deprecated](https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-july-update/ba-p/1530163) due to the security concerns around Basic authentication. Instead, you should use the Exchange Online PowerShell V2 module (the EXO V2 module) to connect to Security & Compliance PowerShell. For instructions, see [Connect to Security & Compliance PowerShell](connect-to-scc-powershell.md).
22
22
23
-
Security & Compliance Center PowerShell allows you to manage your Microsoft 365 Defender portal and Microsoft Purview compliance portal settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to Security & Compliance Center PowerShell. It's a simple three-step process where you enter your Microsoft 365 credentials, provide the required connection settings, and then import the Security & Compliance Center PowerShell cmdlets into your local Windows PowerShell session so that you can use them.
23
+
Security & Compliance PowerShell allows you to manage your Microsoft 365 Defender portal and Microsoft Purview compliance portal settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to Security & Compliance PowerShell. It's a simple three-step process where you enter your Microsoft 365 credentials, provide the required connection settings, and then import the Security & Compliance PowerShell cmdlets into your local Windows PowerShell session so that you can use them.
24
24
25
25
> [!NOTE]
26
26
> The procedures in this article won't work if:
@@ -31,15 +31,15 @@ Security & Compliance Center PowerShell allows you to manage your Microsoft 365
31
31
>
32
32
> - A location condition in an Azure Active Directory conditional access policy restricts your access to trusted IPs.
33
33
>
34
-
> In these scenarios, you need to download and use the Exchange Online PowerShell V2 module (EXO V2 module) to connect to Security & Compliance Center PowerShell. For instructions, see [Connect to Security & Compliance Center PowerShell using the EXO V2 module](connect-to-scc-powershell.md).
34
+
> In these scenarios, you need to download and use the Exchange Online PowerShell V2 module (EXO V2 module) to connect to Security & Compliance PowerShell. For instructions, see [Connect to Security & Compliance PowerShell using the EXO V2 module](connect-to-scc-powershell.md).
35
35
>
36
-
> Some features in the Microsoft 365 Defender portal and Microsoft Purview compliance portal (for example, mailbox archiving) link to existing functionality in Exchange Online. To use PowerShell with these features, you need to connect to Exchange Online PowerShell instead of Security & Compliance Center PowerShell. For instructions, see [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md).
36
+
> Some features in the Microsoft 365 Defender portal and Microsoft Purview compliance portal (for example, mailbox archiving) link to existing functionality in Exchange Online. To use PowerShell with these features, you need to connect to Exchange Online PowerShell instead of Security & Compliance PowerShell. For instructions, see [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md).
37
37
38
38
## What do you need to know before you begin?
39
39
40
40
- Estimated time to complete: 5 minutes
41
41
42
-
- After you connect, the cmdlets and parameters that you have or don't have access to is controlled by role-based access control (RBAC). For more information, see [Permissions in the Microsoft 365 Defender portal](/microsoft-365/security/office-365-security/permissions-microsoft-365-security-center) and [Permissions in the Microsoft 365 security center](/microsoft-365/compliance/microsoft-365-compliance-center-permissions).
42
+
- After you connect, the cmdlets and parameters that you have or don't have access to is controlled by role-based access control (RBAC). For more information, see [Permissions in the Microsoft 365 Defender portal](/microsoft-365/security/office-365-security/permissions-microsoft-365-security-center) and [Permissions in the Microsoft Purview compliance portal](/microsoft-365/compliance/microsoft-365-compliance-center-permissions).
43
43
44
44
- You can use the following versions of Windows:
45
45
@@ -87,7 +87,7 @@ Security & Compliance Center PowerShell allows you to manage your Microsoft 365
87
87
88
88
> The WinRM client cannot process the request. Basic authentication is currently disabled in the client configuration. Change the client configuration and try the request again.
89
89
90
-
## Connect to Security & Compliance Center PowerShell
90
+
## Connect to Security & Compliance PowerShell
91
91
92
92
1. On your local computer, open Windows PowerShell and run the following command:
93
93
@@ -115,7 +115,7 @@ Security & Compliance Center PowerShell allows you to manage your Microsoft 365
115
115
Import-PSSession $Session -DisableNameChecking
116
116
```
117
117
118
-
If you want to connect to Security & Compliance Center PowerShell in the same window as an active Exchange Online PowerShell connection, you need to add the Prefix parameter and value (for example, `-Prefix "CC"`) to the end of this command to prevent cmdlet name collisions (both environments share some cmdlets with the same names).
118
+
If you want to connect to Security & Compliance PowerShell in the same window as an active Exchange Online PowerShell connection, you need to add the Prefix parameter and value (for example, `-Prefix "CC"`) to the end of this command to prevent cmdlet name collisions (both environments share some cmdlets with the same names).
119
119
120
120
> [!NOTE]
121
121
> Be sure to disconnect the remote PowerShell session when you're finished. If you close the Windows PowerShell window without disconnecting the session, you could use up all the remote PowerShell sessions available to you, and you'll need to wait for the sessions to expire. To disconnect the remote PowerShell session, run the following command:
@@ -126,23 +126,21 @@ Remove-PSSession $Session
126
126
127
127
## How do you know this worked?
128
128
129
-
After Step 3, the Security & Compliance Center PowerShell cmdlets are imported into your local Windows PowerShell session as tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run a Security & Compliance Center cmdlet, for example, **Get-RetentionCompliancePolicy**, and see the results.
129
+
After Step 3, the Security & Compliance PowerShell cmdlets are imported into your local Windows PowerShell session as tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run a Security & Compliance PowerShell cmdlet, for example, **Get-RetentionCompliancePolicy**, and see the results.
130
130
131
131
If you receive errors, check the following requirements:
132
132
133
133
- A common problem is an incorrect password. Run the three steps again and pay close attention to the user name and password you enter in Step 1.
134
134
135
-
- Verify that your account has permission to access the Microsoft 365 Defender portal or the Microsoft Purview compliance portal. For details, see [Give users access to the Security & Compliance Center](/microsoft-365/security/office-365-security/grant-access-to-the-security-and-compliance-center).
136
-
137
-
- To help prevent denial-of-service (DoS) attacks, you're limited to five open remote PowerShell connections to Security & Compliance Center PowerShell.
135
+
- To help prevent denial-of-service (DoS) attacks, you're limited to five open remote PowerShell connections to Security & Compliance PowerShell.
138
136
139
137
- TCP port 80 traffic needs to be open between your local computer and Microsoft 365. It's probably open, but it's something to consider if your organization has a restrictive Internet access policy.
140
138
141
139
- 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:
142
140
143
141
> 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.
144
142
145
-
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 Center PowerShell endpoint.
143
+
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.
Copy file name to clipboardExpand all lines: exchange/docs-conceptual/connect-to-exchange-online-powershell.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ To use the older Exchange Online Remote PowerShell Module to connect to Exchange
33
33
> [!NOTE]
34
34
> The rest of the instructions in the article assume that you've already installed the module.
35
35
>
36
-
> If you're using version 2.0.6 of the module, you must use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** command for access to all cmdlets. Otherwise, you'll only get the 250 REST API backed cmdlets. For more information, see [Updates for version 2.0.6](exchange-online-powershell-v2.md#updates-for-version-206).
36
+
> If you're using version 2.0.6 of the module, if you don't use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** command, you'll have access only to the available REST API cmdlets. For more information, see [Updates for version 2.0.6](exchange-online-powershell-v2.md#updates-for-version-206).
37
37
38
38
- After you connect, the cmdlets and parameters that you have or don't have access to is controlled by role-based access control (RBAC). For more information, see [Permissions in Exchange Online](/exchange/permissions-exo/permissions-exo).
39
39
@@ -50,16 +50,15 @@ These connection instructions use modern authentication and work with or without
50
50
51
51
For other sign in methods that are available in PowerShell 7, see the [PowerShell 7 log in experiences](#powershell-7-log-in-experiences) section later in this topic.
52
52
53
-
1. In a PowerShell window, load the EXO V2 module by running the following command:
53
+
1. In a PowerShell window, load the EXO V2 module by running the following command<sup>\*</sup>:
54
54
55
55
```powershell
56
56
Import-Module ExchangeOnlineManagement
57
57
```
58
58
59
59
**Notes**:
60
60
61
-
- If you've already [installed the EXO V2 module](exchange-online-powershell-v2.md#install-and-maintain-the-exo-v2-module), the previous command will work as written.
62
-
- You might be able to skip this step and run **Connect-ExchangeOnline** without loading the module first.
61
+
<sup>\*</sup> You might be able to skip this step and run **Connect-ExchangeOnline** without loading the module first.
63
62
64
63
2. The command that you need to run uses the following syntax:
0 commit comments