Merge branch 'main' into patch-1

Author: doochan2

.openpublishing.redirection.json

@@ -312,7 +312,7 @@
     },
     {
       "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Get-PhishFilterPolicy.md",
-      "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistppoofitems",
+      "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistspoofitems",
       "redirect_document_id": false
     },
     {
@@ -422,7 +422,7 @@
     },
     {
       "source_path": "exchange/virtual-folder/exchange/advanced-threat-protection/Set-PhishFilterPolicy.md",
-      "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistppoofitems",
+      "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistspoofitems",
       "redirect_document_id": false
     },
     {
@@ -6847,12 +6847,12 @@
     },
     {
       "source_path": "exchange/virtual-folder/exchange/Get-PhishFilterPolicy.md",
-      "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistppoofitems",
+      "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistspoofitems",
       "redirect_document_id": false
     },
     {
       "source_path": "exchange/virtual-folder/exchange/Set-PhishFilterPolicy.md",
-      "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistppoofitems",
+      "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistspoofitems",
       "redirect_document_id": false
     },
     {
@@ -6929,6 +6929,11 @@
       "source_path": "exchange/docs-conceptual/use-update-exchangehelp.md",
       "redirect_url": "/powershell/exchange/exchange-management-shell",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "exchange/docs-conceptual/v1-module-mfa-connect-to-scc-powershell.md",
+      "redirect_url": "/powershell/exchange/connect-to-scc-powershell",
+      "redirect_document_id": false
     }
   ]
 }

exchange/docs-conceptual/connect-to-exchange-servers-using-remote-powershell.md

@@ -3,7 +3,7 @@ title: "Connect to Exchange servers using remote PowerShell"
 ms.author: chrisda
 author: chrisda
 manager: dansimp
-ms.date:
+ms.date: 9/7/2023
 ms.audience: ITPro
 audience: ITPro
 ms.topic: article
@@ -17,13 +17,13 @@ description: "Use Windows PowerShell on a local computer to connect to an Exchan
 
 # Connect to Exchange servers using remote PowerShell
 
-If you don't have the Exchange management tools installed on your local computer, you can use Windows PowerShell to create a remote PowerShell session to an Exchange server. It's a simple three-step process, where you enter your credentials, provide the required connection settings, and then import the Exchange cmdlets into your local Windows PowerShell session so that you can use them.
+If you don't have the Exchange management tools installed on your local computer, you can use Windows PowerShell to create a remote PowerShell session to an Exchange server. It's a simple three-step process, where you enter your credentials, provide the required connection settings, and then import the Exchange cmdlets into your local Windows PowerShell session.
 
 > [!NOTE]
 >
 > - We recommend that you use the Exchange Management Shell on any computer that you use to extensively administer Exchange servers. You get the Exchange Management Shell by installing the Exchange management tools. For more information, see [Install the Exchange Server Management Tools](/Exchange/plan-and-deploy/post-installation-tasks/install-management-tools) and [Open the Exchange Management Shell](open-the-exchange-management-shell.md). For more information about the Exchange Management Shell, see [Exchange Server PowerShell (Exchange Management Shell)](exchange-management-shell.md).
 >
-> - The **Get-ExchangeCertificate** cmdlet does not fully support remote PowerShell. We recommend that you use the Exchange Management Shell instead to get all the properties of this cmdlet.
+> - The **Get-ExchangeCertificate** cmdlet does not fully support remote PowerShell. We recommend that you use the Exchange Management Shell instead to see all properties of certificate objects.
 
 ## What do you need to know before you begin?
 
@@ -43,7 +43,7 @@ If you don't have the Exchange management tools installed on your local computer
 
   <sup>\*</sup> This version of Windows has reached end of support, and is now supported only in Azure virtual machines. To use this version of Windows, you need to install the Microsoft .NET Framework 4.5 or later and then an updated version of the Windows Management Framework: 3.0, 4.0, or 5.1 (only one). For more information, see [Install the .NET Framework](/dotnet/framework/install/on-windows-7), [Windows Management Framework 3.0](https://aka.ms/wmf3download), [Windows Management Framework 4.0](https://aka.ms/wmf4download), and [Windows Management Framework 5.1](https://aka.ms/wmf5download).
 
-- Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You'll get the following error when you try to connect:
+- Windows PowerShell needs to be configured to run scripts, and by default, it isn't. You get the following error when you try to connect:
 
   > Files cannot be loaded because running scripts is disabled on this system. Provide a valid certificate with which to sign the files.
 
@@ -66,7 +66,7 @@ If you don't have the Exchange management tools installed on your local computer
    $UserCredential = Get-Credential
    ```
 
-   In the **Windows PowerShell Credential Request** dialog box that opens, enter your user principal name (UPN) (for example, `[email protected]`) and password, and then click **OK**.
+   In the **Windows PowerShell Credential Request** dialog box that opens, enter your user principal name (UPN) (for example, `[email protected]`) and password, and then select **OK**.
 
 2. Replace `<ServerFQDN>` with the fully qualified domain name of your Exchange server (for example, `mailbox01.contoso.com`) and run the following command:
 
@@ -89,7 +89,7 @@ If you don't have the Exchange management tools installed on your local computer
 Remove-PSSession $Session
 ```
 
-## How do you know this worked?
+## How do you know that you've successfully connected?
 
 After Step 3, the Exchange cmdlets are imported into your local Windows PowerShell session and tracked by a progress bar. If you don't receive any errors, you connected successfully. A quick test is to run an Exchange cmdlet (for example, **Get-Mailbox**) and review the results.
 

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

@@ -2,7 +2,7 @@
 title: Connect to Security & Compliance PowerShell
 author: chrisda
 manager: dansimp
-ms.date: 8/21/2023
+ms.date: 9/7/2023
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -24,8 +24,6 @@ The Exchange Online PowerShell module uses modern authentication for connecting
 
 To connect to Security & Compliance PowerShell for automation, see [App-only authentication for unattended scripts](app-only-auth-powershell-v2.md).
 
-To use the older Exchange Online Remote PowerShell Module (the V1 module) to connect to Security & Compliance PowerShell using MFA, see [V1 module - Connect to Security & Compliance PowerShell using MFA](v1-module-mfa-connect-to-scc-powershell.md). This older version of the module will eventually be retired.
-
 ## What do you need to know before you begin?
 
 - The requirements for installing and using the module are described in [Install and maintain the Exchange Online PowerShell module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module).

exchange/docs-conceptual/control-remote-powershell-access-to-exchange-servers.md

@@ -3,7 +3,7 @@ title: "Control remote PowerShell access to Exchange servers"
 ms.author: chrisda
 author: chrisda
 manager: dansimp
-ms.date:
+ms.date: 9/7/2023
 ms.audience: ITPro
 audience: ITPro
 ms.topic: article
@@ -15,7 +15,7 @@ description: "Administrators can learn how to block or allow users' remote Power
 
 # Control remote PowerShell access to Exchange servers
 
-Remote PowerShell in Microsoft Exchange allows you to manage your Exchange organization from a remote computer that's on your internal network or from the Internet. You can disable or enable a user's ability to connect to an Exchange server using remote PowerShell. For more information about remote PowerShell, see [Exchange Server PowerShell (Exchange Management Shell)](exchange-management-shell.md).
+Remote PowerShell in Microsoft Exchange allows you to manage your Exchange organization from a remote computer that's on your internal network or from the internet. You can disable or enable a user's ability to connect to an Exchange server using remote PowerShell and the Exchange Management Shell. For more information about remote PowerShell, see [Exchange Server PowerShell (Exchange Management Shell)](exchange-management-shell.md).
 
 For additional management tasks related to remote PowerShell, see [Connect to Exchange servers using remote PowerShell](connect-to-exchange-servers-using-remote-powershell.md).
 
@@ -30,17 +30,43 @@ For additional management tasks related to remote PowerShell, see [Connect to Ex
   >
   > If you accidentally lock yourself out of remote PowerShell access, you'll need to use the otherwise highly discouraged method of directly loading the Exchange Management Shell snap-in (`Add-PSSnapIn Microsoft.Exchange.Management.PowerShell.SnapIn`) to give yourself access. Minimize the time and changes you're using with this method. Fix one account and open the Exchange Management Shell to make any additional changes.
 
-- You can only use PowerShell to perform this procedure. To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see [Open the Exchange Management Shell](open-the-exchange-management-shell.md).
+- You can only use PowerShell to perform these procedures. To learn how to open the Exchange Management Shell in your on-premises Exchange organization, see [Open the Exchange Management Shell](open-the-exchange-management-shell.md).
 
 - For detailed information about OPATH filter syntax in Exchange, see [Additional OPATH syntax information](recipient-filters.md#additional-opath-syntax-information).
 
 - You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Remote PowerShell" entry in the [Exchange infrastructure and PowerShell permissions](/Exchange/permissions/feature-permissions/infrastructure-permissions) article.
 
-- If you're using third-party tools to customize email addresses of users, you need to disable email address policies on the affected users before you do the procedures in this article. If you don't, the **Set-User** commands will change the email addresses of the users to match the applicable email address policy. To disable email address policies on users, set the value of the EmailAddressPolicyEnabled parameter to $false on the [Set-Mailbox](/powershell/module/exchange/set-mailbox) cmdlet.
+- If you're using third-party tools to customize email addresses of users, you need to disable email address policies on the affected users before you do the procedures in this article. If you don't, the **Set-User** commands change the email addresses of the users to match the applicable email address policy. To disable email address policies on users, set the value of the EmailAddressPolicyEnabled parameter to $false on the [Set-Mailbox](/powershell/module/exchange/set-mailbox) cmdlet.
 
 > [!TIP]
 > Having problems? Ask for help in the [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612) forums.
 
+## View the remote PowerShell access for users
+
+To view the remote PowerShell access status for a specific user, replace \<UserIdentity\> with the name or user principal name (UPN) of the user, and then run the following command:
+
+```powershell
+Get-User -Identity "<UserIdentity>" | Format-List RemotePowerShellEnabled
+```
+
+To display the remote PowerShell access status for all users, run the following command:
+
+```powershell
+Get-User -ResultSize unlimited | Format-Table Name,DisplayName,RemotePowerShellEnabled -AutoSize
+```
+
+To display all users who don't have access to remote PowerShell, run the following command:
+
+```powershell
+Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $false'
+```
+
+To display all users who have access to remote PowerShell, run the following command:
+
+```powershell
+Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $true'
+```
+
 ## Use the Exchange Management Shell to enable or disable remote PowerShell access for a user
 
 This example disables remote PowerShell access for the user named Therese Lindqvist.
@@ -102,29 +128,3 @@ $NPS = Get-Content "C:\My Documents\NoPowerShell.txt"
 
 $NPS | foreach {Set-User -Identity $_ -RemotePowerShellEnabled $false}
 ```
-
-## View the remote PowerShell access for users
-
-To view the remote PowerShell access status for a specific user, replace \<UserIdentity\> with the name or user principal name (UPN) of the user, and then run the following command:
-
-```powershell
-Get-User -Identity "<UserIdentity>" | Format-List RemotePowerShellEnabled
-```
-
-To display the remote PowerShell access status for all users, run the following command:
-
-```powershell
-Get-User -ResultSize unlimited | Format-Table Name,DisplayName,RemotePowerShellEnabled -AutoSize
-```
-
-To display all users who don't have access to remote PowerShell, run the following command:
-
-```powershell
-Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $false'
-```
-
-To display all users who have access to remote PowerShell, run the following command:
-
-```powershell
-Get-User -ResultSize unlimited -Filter 'RemotePowerShellEnabled -eq $true'
-```