Merge branch 'main' into EWSCortana-chrisda

Author: chrisda

.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-phishfilterpolicy",
+      "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistppoofitems",
       "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-phishfilterpolicy",
+      "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistppoofitems",
       "redirect_document_id": false
     },
     {
@@ -1977,7 +1977,7 @@
     },
     {
       "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Get-RMSTrustedPublishingDomain.md",
-      "redirect_url": "/powershell/module/exchange/get-rmstrustedpublishingdomain",
+      "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
       "redirect_document_id": false
     },
     {
@@ -1992,7 +1992,7 @@
     },
     {
       "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Import-RMSTrustedPublishingDomain.md",
-      "redirect_url": "/powershell/module/exchange/import-rmstrustedpublishingdomain",
+      "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
       "redirect_document_id": false
     },
     {
@@ -2022,7 +2022,7 @@
     },
     {
       "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Remove-RMSTrustedPublishingDomain.md",
-      "redirect_url": "/powershell/module/exchange/remove-rmstrustedpublishingdomain",
+      "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
       "redirect_document_id": false
     },
     {
@@ -2052,7 +2052,7 @@
     },
     {
       "source_path": "exchange/virtual-folder/exchange/encryption-and-certificates/Set-RMSTrustedPublishingDomain.md",
-      "redirect_url": "/powershell/module/exchange/set-rmstrustedpublishingdomain",
+      "redirect_url": "/powershell/module/exchange/#encryption-and-certificates",
       "redirect_document_id": false
     },
     {
@@ -3152,7 +3152,7 @@
     },
     {
       "source_path": "exchange/virtual-folder/exchange/mailboxes/Import-ContactList.md",
-      "redirect_url": "/powershell/module/exchange/import-contactlist",
+      "redirect_url": "https://support.microsoft.com/office/import-contacts-to-outlook-bb796340-b58a-46c1-90c7-b549b8f3c5f8",
       "redirect_document_id": false
     },
     {
@@ -5282,7 +5282,7 @@
     },
     {
       "source_path": "exchange/virtual-folder/exchange/reporting/Get-MailTrafficTopReport.md",
-      "redirect_url": "/powershell/module/exchange/get-mailtraffictopreport",
+      "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport",
       "redirect_document_id": false
     },
     {
@@ -6839,6 +6839,41 @@
       "source_path": "exchange/virtual-folder/exchange/Set-CustomNudgeSettings.md",
       "redirect_url": "/powershell/module/exchange/",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "exchange/virtual-folder/exchange/Get-MailTrafficTopReport.md",
+      "redirect_url": "/powershell/module/exchange/get-mailtrafficsummaryreport",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "exchange/virtual-folder/exchange/Get-PhishFilterPolicy.md",
+      "redirect_url": "/powershell/module/exchange/get-tenantallowblocklistppoofitems",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "exchange/virtual-folder/exchange/Set-PhishFilterPolicy.md",
+      "redirect_url": "/powershell/module/exchange/set-tenantallowblocklistppoofitems",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "exchange/docs-conceptual/basic-auth-connect-to-eop-powershell.md",
+      "redirect_url": "/powershell/exchange/connect-to-exchange-online-protection-powershell",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "exchange/docs-conceptual/basic-auth-connect-to-exo-powershell.md",
+      "redirect_url": "/powershell/exchange/connect-to-exchange-online-powershell",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "exchange/docs-conceptual/basic-auth-connect-to-scc-powershell.md",
+      "redirect_url": "/powershell/exchange/connect-to-scc-powershell",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "exchange/docs-conceptual/v1-module-mfa-connect-to-exo-powershell.md",
+      "redirect_url": "/powershell/exchange/connect-to-exchange-online-powershell",
+      "redirect_document_id": false
     }
   ]
 }

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

@@ -3,7 +3,7 @@ title: App-only authentication in Exchange Online PowerShell and Security & Comp
 ms.author: chrisda
 author: chrisda
 manager: dansimp
-ms.date:
+ms.date: 01/31/2023
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -29,7 +29,7 @@ Certificate based authentication (CBA) or app-only authentication as described i
 >
 > - The features and procedures described in this article require the following versions of the Exchange Online PowerShell module:
 >   - **Exchange Online PowerShell (Connect-ExchangeOnline)**: Version 2.0.3 or later.
->   - **Security & Compliance PowerShell (Connect-IPPSSession)**: Version 2.0.6-Preview5 or later.
+>   - **Security & Compliance PowerShell (Connect-IPPSSession)**: Version 3.0.0 or later.
 >
 >   For instructions on how to install or update the module, see [Install and maintain the Exchange Online PowerShell module](exchange-online-powershell-v2.md#install-and-maintain-the-exchange-online-powershell-module). For instructions on how to use the module in Azure automation, see [Manage modules in Azure Automation](/azure/automation/shared-resources/modules).
 >
@@ -48,7 +48,7 @@ Certificate based authentication (CBA) or app-only authentication as described i
 >   - [Get-ComplianceCase](/powershell/module/exchange/get-compliancecase)
 >   - [Get-CaseHoldPolicy](/powershell/module/exchange/get-caseholdpolicy)
 >
-> - Delegated scenarios are supported in **Exchange Online** using multi-tenant applications. The required steps are called out within the regular instructions in this article.
+> - Delegated scenarios are supported in Exchange Online. The recommended method for connecting with delegation is using GDAP and App Consent. For more information, see [Use the Exchange Online PowerShell v3 Module with GDAP and App Consent](/powershell/partnercenter/exchange-online-gdap-app). You can also use multi-tenant applications when CSP relationships are not created with the customer. The required steps for using multi-tenant applications are called out within the regular instructions in this article.
 
 ## How does it work?
 
@@ -63,7 +63,9 @@ The following examples show how to use the Exchange Online PowerShell module wit
 >
 > The following connection commands have many of the same options available as described in [Connect to Exchange Online PowerShell](connect-to-exchange-online-powershell.md) and [Connect to Security & Compliance PowerShell](connect-to-scc-powershell.md). For example:
 >
-> - In Exchange Online PowerShell using the EXO V3 module, you can omit or include the _UseRPSSession_ switch to use REST API cmdlets or original remote PowerShell cmdlets. For more information, see [Updates for version 3.0.0 (the EXO V3 module)](exchange-online-powershell-v2.md#updates-for-version-300-the-exo-v3-module).
+> - In Exchange Online PowerShell using the EXO V3 module, you can omit or include the _UseRPSSession_ switch to use REST API cmdlets or original remote PowerShell cmdlets. For more information, see [Updates for the EXO V3 module)](exchange-online-powershell-v2.md#updates-for-the-exo-v3-module).
+>
+>   Remote PowerShell support in Exchange Online PowerShell will be deprecated. For more information, see [Announcing Deprecation of Remote PowerShell (RPS) Protocol in Exchange Online PowerShell](https://aka.ms/RPSDeprecation).
 >
 > - Microsoft 365 GCC High or Microsoft 365 DoD environments require the following additional parameters and values:
 >   - **Connect-ExchangeOnline in GCC High**: `-ExchangeEnvironmentName O365USGovGCCHigh`.
@@ -297,20 +299,20 @@ After you register the certificate with your application, you can use the privat
 
 If you made the application multi-tenant for **Exchange Online** delegated scenarios in [Step 1](#step-1-register-the-application-in-azure-ad), you need to grant admin consent to the Exchange.ManageAsApp permission so the application can run cmdlets in Exchange Online **in each tenant organization**. To do this, generate an admin consent URL for each customer tenant. Before anyone uses the multi-tenant application to connect to Exchange Online in the tenant organization, an admin in the customer tenant should open the following URL:
 
-  `https://login.microsoftonline.com/<tenant-id>/adminconsent?client_id=<client-id>&scope=https://outlook.office365.com/.default`
+`https://login.microsoftonline.com/<tenant-id>/adminconsent?client_id=<client-id>&scope=https://outlook.office365.com/.default`
 
-  - `<tenant-id>` is the customer's tenant ID.
-  - `<client-id>` is the ID of the multi-tenant application.
-  - The default scope is used to grant application permissions.
+- `<tenant-id>` is the customer's tenant ID.
+- `<client-id>` is the ID of the multi-tenant application.
+- The default scope is used to grant application permissions.
 
-  For more information about the URL syntax, see [Request the permissions from a directory admin](/azure/active-directory/develop/v2-admin-consent#request-the-permissions-from-a-directory-admin).
+For more information about the URL syntax, see [Request the permissions from a directory admin](/azure/active-directory/develop/v2-admin-consent#request-the-permissions-from-a-directory-admin).
 
 ### Step 5: Assign Azure AD roles to the application
 
 You have two options:
 
 - **Assign Azure AD roles to the application**: This method is supported in Exchange Online PowerShell and Security & Compliance PowerShell.
-- **Assign custom Exchange Online role groups to the application**: Currently, this method is supported only in Exchange Online PowerShell, and only when you connect in [REST API mode](exchange-online-powershell-v2.md#updates-for-version-300-the-exo-v3-module) (don't use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** command).
+- **Assign custom Exchange Online role groups to the application**: Currently, this method is supported only in Exchange Online PowerShell, and only when you connect in [REST API mode](exchange-online-powershell-v2.md#updates-for-the-exo-v3-module) (don't use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** command).
 
 > [!NOTE]
 > You can also combine both methods to assign permissions. For example, you can use Azure AD roles for the "Exchange Recipient Administrator" role and also assign your custom RBAC role to extend the permissions.
@@ -389,7 +391,7 @@ For general instructions about assigning roles in Azure AD, see [View and assign
 #### Assign custom Exchange Online role groups to the application
 
 > [!NOTE]
-> Remember, this method is supported only in Exchange Online PowerShell, and only when you connect in [REST API mode](exchange-online-powershell-v2.md#updates-for-version-300-the-exo-v3-module) (don't use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** command).
+> Remember, this method is supported only in Exchange Online PowerShell, and only when you connect in [REST API mode](exchange-online-powershell-v2.md#updates-for-the-exo-v3-module) (don't use the _UseRPSSession_ switch in the **Connect-ExchangeOnline** command).
 
 For information about creating custom role groups, see [Create role groups](/exchange/permissions-exo/role-groups#create-role-groups). The custom role group that you assign to the application can contain any combination of built-in and custom roles.