Merge branch 'master' into ChrisdaCopyOfQinezh-test

Author: chrisda

.openpublishing.redirection.json

@@ -6499,6 +6499,121 @@
       "source_path": "exchange/virtual-folder/exchange/users-and-groups/Upgrade-DistributionGroup.md",
       "redirect_url": "https://docs.microsoft.com/powershell/module/exchange/upgrade-distributiongroup",
       "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/office-365-scc/office-365-scc-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/scc-powershell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/connect-to-scc-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/connect-to-scc-powershell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/office-365-scc/connect-to-scc-powershell/mfa-connect-to-scc-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/mfa-connect-to-scc-powershell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/connect-to-exchange-servers-using-remote-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/connect-to-exchange-servers-using-remote-powershell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/control-remote-powershell-access-to-exchange-servers.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/control-remote-powershell-access-to-exchange-servers",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/exchange-cmdlet-syntax.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange-cmdlet-syntax",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/exchange-management-shell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/exchange-management-shell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/find-exchange-cmdlet-permissions.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/find-exchange-cmdlet-permissions",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/open-the-exchange-management-shell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/open-the-exchange-management-shell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/use-update-exchangehelp.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/use-update-exchangehelp.md",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/recipient-filters/filter-properties.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/filter-properties",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/recipient-filters/recipient-filters.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/recipient-filters",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-server/recipient-filters/recipientfilter-properties.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/recipientfilter-properties",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-online/disable-access-to-exchange-online-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/disable-access-to-exchange-online-powershell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/exchange-online-powershell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/connect-to-exchange-online-powershell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/mfa-connect-to-exchange-online-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/mfa-connect-to-exchange-online-powershell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/app-only-auth-powershell-v2.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/app-only-auth-powershell-v2",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/cmdlet-property-sets",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/exchange-online-powershell-v2",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/filters-v2.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/filters-v2",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-eop/connect-to-exchange-online-protection-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/connect-to-exchange-online-protection-powershell",
+      "redirect_document_id": true
+    },
+    {
+      "source_path": "exchange/docs-conceptual/exchange-eop/exchange-online-protection-powershell.md",
+      "redirect_url": "https://docs.microsoft.com/powershell/exchange/exchange-online-protection-powershell",
+      "redirect_document_id": true
     }
-   ] 
+  ] 
   }

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

@@ -113,7 +113,7 @@ If you encounter problems, check the [required permssions](https://docs.microsof
 
      Note that you can't create credentials for [native applications](https://docs.microsoft.com/azure/active-directory/manage-apps/application-proxy-configure-native-client-application), because you can't use that type for automated applications.
 
-   ![Register an application](../../media/app-only-auth-register-app.png)
+   ![Register an application](media/app-only-auth-register-app.png)
 
    When you're finished, click **Register**.
 
@@ -129,13 +129,13 @@ You need to assign the API permission `Exchange.ManageAsApp` so the application
 
 3. In the flyout that appears, select **Exchange**.
 
-   ![Select Exchange API permssions](../../media/app-only-auth-exchange-api-perms.png)
+   ![Select Exchange API permssions](media/app-only-auth-exchange-api-perms.png)
 
 4. In the flyout that appears, click **Application permissions**.
 
 5. In the **Select permissions** section that appears on the page, expand **Exchange** and select **Exchange.ManageAsApp**
 
-   ![Select Exchange API permssions](../../media/app-only-auth-exchange-manageasapp.png)
+   ![Select Exchange API permssions](media/app-only-auth-exchange-manageasapp.png)
 
    When you're finished, click **Add permissions**.
 
@@ -169,7 +169,7 @@ After you register the certificate with your application, you can use the public
 
 5. On the **Certificates & secrets** page that opens, click **Upload certificate**.
 
-   ![Click Upload certificate](../../media/app-only-auth-upload-cert.png)
+   ![Click Upload certificate](media/app-only-auth-upload-cert.png)
 
 6. In the dialog that appears, browse to the self-signed certificate you created in the previous Step, and then click **Add**.
 
@@ -191,4 +191,4 @@ Azure AD has more than 50 admin roles available. For app-only authentication in
 
 4. In the **Add assignments** flyout that appears, find and select the application, and then click **Add**.
 
-   ![Add a role assignment](../../media/app-only-auth-role-assignment.png)
+   ![Add a role assignment](media/app-only-auth-role-assignment.png)

exchange/docs-conceptual/exchange-online/exchange-online-powershell-v2/cmdlet-property-sets.md renamed to exchange/docs-conceptual/cmdlet-property-sets.md

@@ -18,12 +18,12 @@ description: "Learn how to use remote PowerShell to connect to Exchange Online."
 # Connect to Exchange Online PowerShell
 
 > [!NOTE]
-> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](../exchange-online-powershell-v2/exchange-online-powershell-v2.md).
+> We recommend that you use the Exchange Online PowerShell V2 module to connect to Exchange Online PowerShell. For instructions, see [Use the Exchange Online PowerShell V2 module](exchange-online-powershell-v2.md).
 
 Exchange Online PowerShell allows you to manage your Exchange Online settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to Exchange Online. It's a simple three-step process where you enter your Microsoft 365 credentials, provide the required connection settings, and then import the Exchange Online cmdlets into your local Windows PowerShell session so that you can use them.
 
 > [!IMPORTANT]
-> If you want to use multi-factor authentication (MFA) to connect to Exchange Online PowerShell, you need to download and use the Exchange Online Remote PowerShell Module. For more information, see [Connect to Exchange Online PowerShell using multi-factor authentication](mfa-connect-to-exchange-online-powershell.md). <br/><br/> If you're a standalone Exchange Online Protection (EOP) customer (for example, you're using EOP to protect your on-premises email environment), use the connection instructions in [Connect to Exchange Online Protection PowerShell](../../exchange-eop/connect-to-exchange-online-protection-powershell.md). If your on-premises Exchange organization has Exchange Enterprise CAL with Services licenses, EOP is one of the included services, and the connection instructions in this topic will work for you.
+> If you want to use multi-factor authentication (MFA) to connect to Exchange Online PowerShell, you need to download and use the Exchange Online Remote PowerShell Module. For more information, see [Connect to Exchange Online PowerShell using multi-factor authentication](mfa-connect-to-exchange-online-powershell.md). <br/><br/> If you're a standalone Exchange Online Protection (EOP) customer (for example, you're using EOP to protect your on-premises email environment), use the connection instructions in [Connect to Exchange Online Protection PowerShell](connect-to-exchange-online-protection-powershell.md). If your on-premises Exchange organization has Exchange Enterprise CAL with Services licenses, EOP is one of the included services, and the connection instructions in this topic will work for you.
 
 ## What do you need to know before you begin?
 
@@ -134,7 +134,7 @@ If you receive errors, check the following requirements:
 
 - To help prevent denial-of-service (DoS) attacks, you're limited to three open remote PowerShell connections to your Exchange Online organization.
 
-- The account you use to connect to Exchange Online must be enabled for remote PowerShell. For more information, see [Enable or disable access to Exchange Online PowerShell](../disable-access-to-exchange-online-powershell.md).
+- The account you use to connect to Exchange Online must be enabled for remote PowerShell. For more information, see [Enable or disable access to Exchange Online PowerShell](disable-access-to-exchange-online-powershell.md).
 
 - 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.
 

exchange/docs-conceptual/exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md renamed to exchange/docs-conceptual/connect-to-exchange-online-powershell.md

@@ -20,7 +20,7 @@ In standalone Exchange Online Protection (EOP) organizations without Exchange On
 
 - Estimated time to complete: 5 minutes
 
-- The instructions in this topic are for organizations without Exchange Online mailboxes (for example, you have a standalone EOP subscription to protect your on-premises email environment). If you have a Microsoft 365 subscription that includes Exchange Online mailboxes, the same features are available in [Exchange Online PowerShell](../exchange-online/exchange-online-powershell.md).
+- The instructions in this topic are for organizations without Exchange Online mailboxes (for example, you have a standalone EOP subscription to protect your on-premises email environment). If you have a Microsoft 365 subscription that includes Exchange Online mailboxes, the same features are available in [Exchange Online PowerShell](exchange-online-powershell.md).
 
 - You can use the following versions of Windows:
 

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

@@ -18,7 +18,17 @@ description: "Learn how to connect to Security & Compliance Center PowerShell."
 Security & Compliance Center PowerShell allows you to manage your Security & Compliance Center settings from the command line. You use Windows PowerShell on your local computer to create a remote PowerShell session to the Security & Compliance Center. 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 cmdlets into your local Windows PowerShell session so that you can use them.
 
 > [!NOTE]
-> The procedures in this topic won't work if: <br/>* Your account uses multi-factor authentication (MFA). <br/>* Your organization uses federated authentication. <br/>* A ___location condition in an Azure Active Directory conditional access policy restricts your access to trusted IPs. <br/> In these scenarios, you need to download and use the Exchange Online Remote PowerShell Module to connect to Security & Compliance Center PowerShell. For instructions, see [Connect to Security & Compliance Center PowerShell using multi-factor authentication](mfa-connect-to-scc-powershell.md). <br/><br/> Some features in the Security & Compliance Center (for example, mailbox archiving) link to existing functionality in the Exchange admin center (EAC). 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](../../exchange-online/connect-to-exchange-online-powershell/connect-to-exchange-online-powershell.md).
+> The procedures in this topic won't work if:
+> 
+> - Your account uses multi-factor authentication (MFA).
+> 
+> - Your organization uses federated authentication.
+> 
+> - A ___location condition in an Azure Active Directory conditional access policy restricts your access to trusted IPs.
+> 
+> In these scenarios, you need to download and use the Exchange Online Remote PowerShell Module to connect to Security & Compliance Center PowerShell. For instructions, see [Connect to Security & Compliance Center PowerShell using multi-factor authentication](mfa-connect-to-scc-powershell.md).
+> 
+> Some features in the Security & Compliance Center (for example, mailbox archiving) link to existing functionality in the Exchange admin center (EAC). 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).
 
 For more information about the Security & Compliance Center, see [Security & Compliance Center](https://go.microsoft.com/fwlink/p/?LinkId=627054).
 

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

@@ -26,7 +26,7 @@ For additional management tasks related to remote PowerShell, see [Connect to Ex
 
 - By default, all user accounts have access to remote PowerShell. However, to actually use remote PowerShell to connect to an Exchange server, the user needs to be a member of a management role group, or be directly assigned a management role that enables the user to run Exchange cmdlets. For more information about role groups and management roles, see [Exchange Server permissions](https://docs.microsoft.com/Exchange/permissions/permissions).
 
-- For detailed information about OPath filter syntax in Exchange, see [Additional OPATH syntax information](../exchange-server/recipient-filters/recipient-filters.md#additional-opath-syntax-information).
+- 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](https://docs.microsoft.com/Exchange/permissions/feature-permissions/infrastructure-permissions) topic.