[AutoPublish] main to live - 08/04 15:34 PDT | 08/05 04:04 IST

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

@@ -38,17 +38,17 @@ Certificate based authentication (CBA) or app-only authentication as described i
 >   If the procedures in this article don't work for you, verify that you don't have Beta versions of the PackageManagement or PowerShellGet modules installed by running the following command: `Get-InstalledModule PackageManagement -AllVersions; Get-InstalledModule PowerShellGet -AllVersions`.
 >
 > - In Exchange Online PowerShell, you can't use the procedures in this article with the following Microsoft 365 Group cmdlets:
->   - [New-UnifiedGroup](/powershell/module/exchange/new-unifiedgroup)
->   - [Remove-UnifiedGroup](/powershell/module/exchange/remove-unifiedgroup)
->   - [Remove-UnifiedGroupLinks](/powershell/module/exchange/remove-unifiedgrouplinks)
->   - [Add-UnifiedGroupLinks](/powershell/module/exchange/add-unifiedgrouplinks)
+>   - [New-UnifiedGroup](/powershell/module/exchangepowershell/new-unifiedgroup)
+>   - [Remove-UnifiedGroup](/powershell/module/exchangepowershell/remove-unifiedgroup)
+>   - [Remove-UnifiedGroupLinks](/powershell/module/exchangepowershell/remove-unifiedgrouplinks)
+>   - [Add-UnifiedGroupLinks](/powershell/module/exchangepowershell/add-unifiedgrouplinks)
 >
 >   You can use Microsoft Graph to replace most of the functionality from those cmdlets. For more information, see [Working with groups in Microsoft Graph](/graph/api/resources/groups-overview).
 >
 > - In Security & Compliance PowerShell, you can't use the procedures in this article with the following Microsoft 365 Group cmdlets:
->   - [Get-ComplianceSearchAction](/powershell/module/exchange/get-compliancesearchaction)
->   - [New-ComplianceSearch](/powershell/module/exchange/new-compliancesearch)
->   - [Start-ComplianceSearch](/powershell/module/exchange/start-compliancesearch)
+>   - [Get-ComplianceSearchAction](/powershell/module/exchangepowershell/get-compliancesearchaction)
+>   - [New-ComplianceSearch](/powershell/module/exchangepowershell/new-compliancesearch)
+>   - [Start-ComplianceSearch](/powershell/module/exchangepowershell/start-compliancesearch)
 >
 > - 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.
 >
@@ -523,7 +523,7 @@ To assign custom role groups to the application using service principals, do the
    $SP = Get-ServicePrincipal -Identity "SP for Azure AD App ExO PowerShell CBA"
    ```
 
-   For detailed syntax and parameter information, see [New-ServicePrincipal](/powershell/module/exchange/new-serviceprincipal).
+   For detailed syntax and parameter information, see [New-ServicePrincipal](/powershell/module/exchangepowershell/new-serviceprincipal).
 
 3. In Exchange Online PowerShell or Security & Compliance PowerShell, run the following command to add the service principal as a member of the custom role group:
 
@@ -537,4 +537,4 @@ To assign custom role groups to the application using service principals, do the
    Add-RoleGroupMember -Identity "Contoso View-Only Recipients" -Member $SP.Identity
    ```
 
-   For detailed syntax and parameter information, see [Add-RoleGroupMember](/powershell/module/exchange/add-rolegroupmember).
+   For detailed syntax and parameter information, see [Add-RoleGroupMember](/powershell/module/exchangepowershell/add-rolegroupmember).

exchange/docs-conceptual/client-advanced-settings.md

@@ -21,8 +21,8 @@ description: "Security & Compliance PowerShell advanced settings for Microsoft P
 
 This article contains the [Security & Compliance PowerShell](/powershell/exchange/office-365-scc/office-365-scc-powershell) advanced settings that are supported by [Microsoft Purview Information Protection client](/purview/information-protection-client) when you use the following cmdlets:
 
-- [New-Label](/powershell/module/exchange/new-label) or [Set-Label](/powershell/module/exchange/set-label)
-- [New-LabelPolicy](/powershell/module/exchange/new-labelpolicy) or [Set-LabelPolicy](/powershell/module/exchange/set-labelpolicy)
+- [New-Label](/powershell/module/exchangepowershell/new-label) or [Set-Label](/powershell/module/exchangepowershell/set-label)
+- [New-LabelPolicy](/powershell/module/exchangepowershell/new-labelpolicy) or [Set-LabelPolicy](/powershell/module/exchangepowershell/set-labelpolicy)
 
 The advanced settings that are supported by sensitivity labels built into Microsoft 365 apps and services are included on the cmdlet page itself. You might also find useful [PowerShell tips for specifying the advanced settings](/purview/create-sensitivity-labels#powershell-tips-for-specifying-the-advanced-settings).
 

exchange/docs-conceptual/cmdlet-property-sets.md

@@ -49,8 +49,8 @@ The available property sets for the **Get-EXOCasMailbox** cmdlet and the propert
 
 For more information, see:
 
-- [Get-EXOCASMailbox](/powershell/module/exchange/get-exocasmailbox)
-- [Get-CASMailbox](/powershell/module/exchange/get-casmailbox)
+- [Get-EXOCASMailbox](/powershell/module/exchangepowershell/get-exocasmailbox)
+- [Get-CASMailbox](/powershell/module/exchangepowershell/get-casmailbox)
 
 ## Get-EXOMailbox property sets
 
@@ -86,8 +86,8 @@ The available property sets for the **Get-EXOMailbox** cmdlet and the properties
 
 For more information, see:
 
-- [Get-EXOMailbox](/powershell/module/exchange/get-exomailbox)
-- [Get-Mailbox](/powershell/module/exchange/get-mailbox)
+- [Get-EXOMailbox](/powershell/module/exchangepowershell/get-exomailbox)
+- [Get-Mailbox](/powershell/module/exchangepowershell/get-mailbox)
 
 ## Get-EXOMailboxStatistics property sets
 
@@ -100,8 +100,8 @@ The available property sets for the **Get-EXOMailboxStatistics** cmdlet and the
 
 For more information, see:
 
-- [Get-EXOMailboxStatistics](/powershell/module/exchange/get-exomailboxstatistics)
-- [Get-MailboxStatistics](/powershell/module/exchange/get-mailboxstatistics)
+- [Get-EXOMailboxStatistics](/powershell/module/exchangepowershell/get-exomailboxstatistics)
+- [Get-MailboxStatistics](/powershell/module/exchangepowershell/get-mailboxstatistics)
 
 ## Get-EXORecipient property sets
 
@@ -121,5 +121,5 @@ The available property sets for the **Get-EXORecipient** cmdlet and the properti
 
 For more information, see:
 
-- [Get-EXORecipient](/powershell/module/exchange/get-exorecipient)
-- [Get-Recipient](/powershell/module/exchange/get-recipient)
+- [Get-EXORecipient](/powershell/module/exchangepowershell/get-exorecipient)
+- [Get-Recipient](/powershell/module/exchangepowershell/get-recipient)

exchange/docs-conceptual/connect-exo-powershell-managed-identity.md

@@ -28,10 +28,10 @@ The rest of this article explains how to connect using managed identity, and the
 > [!NOTE]
 > In Exchange Online PowerShell, you can't use the procedures in this article with the following Microsoft 365 Group cmdlets:
 >
-> - [New-UnifiedGroup](/powershell/module/exchange/new-unifiedgroup)
-> - [Remove-UnifiedGroup](/powershell/module/exchange/remove-unifiedgroup)
-> - [Remove-UnifiedGroupLinks](/powershell/module/exchange/remove-unifiedgrouplinks)
-> - [Add-UnifiedGroupLinks](/powershell/module/exchange/add-unifiedgrouplinks)
+> - [New-UnifiedGroup](/powershell/module/exchangepowershell/new-unifiedgroup)
+> - [Remove-UnifiedGroup](/powershell/module/exchangepowershell/remove-unifiedgroup)
+> - [Remove-UnifiedGroupLinks](/powershell/module/exchangepowershell/remove-unifiedgrouplinks)
+> - [Add-UnifiedGroupLinks](/powershell/module/exchangepowershell/add-unifiedgrouplinks)
 >
 > You can use Microsoft Graph to replace most of the functionality from those cmdlets. For more information, see [Working with groups in Microsoft Graph](/graph/api/resources/groups-overview).
 >

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

@@ -61,7 +61,7 @@ The command that you need to run uses the following syntax:
 Connect-ExchangeOnline [-UserPrincipalName <UPN>] [-ExchangeEnvironmentName <Value>] [-ShowBanner:$false] [-LoadCmdletHelp] [-DelegatedOrganization <String>] [-SkipLoadingFormatData] [-DisableWAM]
    ```
 
-For detailed syntax and parameter information, see [Connect-ExchangeOnline](/powershell/module/exchange/connect-exchangeonline).
+For detailed syntax and parameter information, see [Connect-ExchangeOnline](/powershell/module/exchangepowershell/connect-exchangeonline).
 
 - _\<UPN\>_ is your account in user principal name format (for example, `[email protected]`).
 

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

@@ -54,7 +54,7 @@ The command that you need to run uses the following syntax:
 Connect-IPPSSession -UserPrincipalName <UPN> [-ConnectionUri <URL>] [-AzureADAuthorizationEndpointUri <URL>] [-DelegatedOrganization <String>] [-PSSessionOption $ProxyOptions]
 ```
 
-For detailed syntax and parameter information, see [Connect-IPPSSession](/powershell/module/exchange/connect-ippssession).
+For detailed syntax and parameter information, see [Connect-IPPSSession](/powershell/module/exchangepowershell/connect-ippssession).
 
 - _\<UPN\>_ is your account in user principal name format (for example, `[email protected]`).
 

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

@@ -36,7 +36,7 @@ For additional management tasks related to remote PowerShell, see [Connect to Ex
 
 - 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 non-Microsoft 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.
+- If you're using non-Microsoft 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/exchangepowershell/set-mailbox) cmdlet.
 
 > [!TIP]
 > Having problems? Ask for help in the [Exchange Server](https://go.microsoft.com/fwlink/p/?linkId=60612) forums.