Merge pull request #12728 from MicrosoftDocs/main

[AutoPublish] main to live - 05/07 22:33 PDT | 05/08 11:03 IST

Author: aditisrivastava07

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

@@ -2,7 +2,7 @@
 title: Connect to Exchange Online PowerShell
 author: chrisda
 manager: deniseb
-ms.date: 8/21/2023
+ms.date: 05/07/2025
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -61,15 +61,13 @@ Import-Module ExchangeOnlineManagement
 The command that you need to run uses the following syntax:
 
 ```powershell
-Connect-ExchangeOnline -UserPrincipalName <UPN> [-ExchangeEnvironmentName <Value>] [-ShowBanner:$false] [-DelegatedOrganization <String>] [-SkipLoadingFormatData]
+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).
 
 - _\<UPN\>_ is your account in user principal name format (for example, `[email protected]`).
 
-- With the EXO V3 module (v3.0.0 or later) and the [demise of Basic authentication (remote PowerShell) connections to Exchange Online](https://techcommunity.microsoft.com/t5/exchange-team-blog/deprecation-of-remote-powershell-rps-protocol-in-security-and/ba-p/3815432), you're using REST API cmdlets only. For more information, see [REST API connections in the EXO V3 module](exchange-online-powershell-v2.md#rest-api-connections-in-the-exo-v3-module).
-
 - When you use the _ExchangeEnvironmentName_ parameter, you don't need use the _ConnectionUri_ or _AzureADAuthorizationEndPointUrl_ parameters. Common values for the _ExchangeEnvironmentName_ parameter are described in the following table:
 
   |Environment|Value|
@@ -82,6 +80,8 @@ For detailed syntax and parameter information, see [Connect-ExchangeOnline](/pow
 
   <sup>\*</sup> The required value `O365Default` is also the default value, so you don't need to use the _ExchangeEnvironmentName_ parameter in Microsoft 365 or Microsoft 365 GCC environments.
 
+- In version 3.7.0 or later, command line help for Exchange Online PowerShell cmdlets is no longer loaded by default. Use the _LoadCmdletHelp_ switch so help for Exchange Online PowerShell cmdlets is available to the **Get-Help** cmdlet.
+
 - The _DelegatedOrganization_ parameter specifies the customer organization that you want to manage as an authorized Microsoft Partner. For more information, see the [connection examples later in this article](#connect-to-exchange-online-powershell-in-customer-organizations).
 
 - Depending on the nature of your organization, you might be able to omit the _UserPrincipalName_ parameter in the connection command. Instead, you enter the username and password or select stored credentials after you run the **Connect-ExchangeOnline** command. If it doesn't work, then you need to use the _UserPrincipalName_ parameter.
@@ -92,6 +92,8 @@ For detailed syntax and parameter information, see [Connect-ExchangeOnline](/pow
 
 - Using the module in PowerShell 7 requires version 2.0.4 or later.
 
+- In version 3.7.2 or later, the _DisableWAM_ switch is available to disable Web Account Manager (WAM) if you get WAM-related connection errors.
+
 The connection examples in the following sections use modern authentication, and are incapable of using Basic authentication.
 
 ### Connect to Exchange Online PowerShell with an interactive login prompt

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

@@ -2,7 +2,7 @@
 title: Connect to Security & Compliance PowerShell
 author: chrisda
 manager: deniseb
-ms.date: 12/12/2023
+ms.date: 05/07/2025
 ms.audience: Admin
 audience: Admin
 ms.topic: article

exchange/docs-conceptual/exchange-online-powershell-v2.md

@@ -3,7 +3,7 @@ title: About the Exchange Online PowerShell V3 module
 ms.author: chrisda
 author: chrisda
 manager: deniseb
-ms.date: 03/26/2025
+ms.date: 05/07/2025
 ms.audience: Admin
 audience: Admin
 ms.topic: article
@@ -615,7 +615,7 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
 
 #### Version 3.7.2
 
-- New _DisableWAM_ parameter on **Connect-ExchangeOnline** that disables Web Account Manager (WAM).
+- The _DisableWAM_ switch is available on the **Connect-ExchangeOnline** cmdlet to disable Web Account Manager (WAM) if you get WAM-related connection errors.
 
 ### Previous releases
 
@@ -630,7 +630,7 @@ Unless otherwise noted, the current release of the Exchange Online PowerShell mo
 #### Version 3.7.0
 
 - Integrated Web Account Manager (WAM) in authentication flows to enhance security.
-- Command line help for Exchange Online PowerShell cmdlets is no longer loaded by default. Use the _LoadCmdletHelp_ parameter in the **Connect-ExchangeOnline** command so help for Exchange Online PowerShell cmdlets is available to the **Get-Help** cmdlet.
+- Command line help for Exchange Online PowerShell cmdlets is no longer loaded by default. Use the _LoadCmdletHelp_ switch in the **Connect-ExchangeOnline** command so help for Exchange Online PowerShell cmdlets is available to the **Get-Help** cmdlet.
 - Fixed connection issues with app only authentication in Security & Compliance PowerShell.
 
 #### Version 3.6.0

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

@@ -3,7 +3,7 @@ title: "Exchange Online PowerShell"
 ms.author: chrisda
 author: chrisda
 manager: deniseb
-ms.date: 9/1/2023
+ms.date: 05/07/2025
 ms.audience: Admin
 audience: Admin
 ms.topic: article

exchange/exchange-ps/exchange/Get-FeatureConfiguration.md

@@ -17,7 +17,7 @@ This cmdlet is available only in Security & Compliance PowerShell. For more info
 Use the Get-FeatureConfiguration cmdlet to view Microsoft Purview feature configurations within your organization, including:
 
 - Collection policies.
-- Endpoint DLP trust container.
+- Advanced label based protection.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 

teams/teams-ps/teams/Set-CsOnlineLisCivicAddress.md

@@ -16,6 +16,9 @@ ms.reviewer:
 Use the \`Set-CsOnlineLisCivicAddress\` cmdlet to modify an existing civic address which has not been validated.
 Validated civic addresses cannot be modified.
 
+> [!IMPORTANT]
+> Due to a current issue, the parameters **-CompanyName** and **-CountryOrRegion** are required as an interim workaround for this cmdlet.  
+
 > [!Note]
 > This cmdlet is only available for public use with limited countries and certain fields. The remaining countries and fields are for Microsoft internal use only.