Merge branch 'main' into main

Author: alejandramunozv

.github/workflows/StaleBranch.yml

@@ -2,6 +2,7 @@ name: (Scheduled) Stale branch removal
 
 permissions:
   contents: write
+  pull-requests: read
 
 # This workflow is designed to be run in the days up to, and including, a "deletion day", specified by 'DeleteOnDayOfMonth' in env: in https://github.com/MicrosoftDocs/microsoft-365-docs/blob/workflows-prod/.github/workflows/Shared-StaleBranch.yml.
 # On the days leading up to "deletion day", the workflow will report the branches to be deleted. This lets users see which branches will be deleted. On "deletion day", those branches are deleted.

README.md

@@ -8,6 +8,8 @@ ms.date: 9/15/2023
 
 Anyone who is interested can contribute to the articles. When you contribute, your work goes into the content set after it's been reviewed and merged. It's then published to [Microsoft Learn](https://learn.microsoft.com/), and you're listed as a contributor at: <https://github.com/MicrosoftDocs/office-docs-powershell/graphs/contributors>.
 
+If you get stuck and are a Microsoft employee or vendor, post a message to [Ask an Admin](https://aka.ms/askanadmin).
+
 ### Quickly update an article using GitHub.com
 
 Contributors who make infrequent or small updates can edit the file directly on GitHub.com without installing any software. This article shows you how. [This two-minute video](https://learn-video.azurefd.net/vod/player?id=b5167c5a-9c69-499b-99ac-e5467882bc92) also covers how to contribute.

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,18 +17,15 @@ 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).
 
 ## SYNTAX
 
 ```
 Get-FeatureConfiguration [[-Identity] <PolicyIdParameter>] [-FeatureScenario] <PolicyScenario>
- [-All]
  [-Confirm]
- [-GeneralDiscovery]
- [-IrmDiscovery]
  [-WhatIf]
  [<CommonParameters>]
 ```
@@ -92,22 +89,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -All
-This parameter is reserved for internal Microsoft use.
-
-```yaml
-Type: SwitchParameter
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -Confirm
 This parameter is reserved for internal Microsoft use.
 
@@ -124,38 +105,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -GeneralDiscovery
-This parameter is reserved for internal Microsoft use.
-
-```yaml
-Type: SwitchParameter
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -IrmDiscovery
-This parameter is reserved for internal Microsoft use.
-
-```yaml
-Type: SwitchParameter
-Parameter Sets: (All)
-Aliases:
-Applicable: Security & Compliance
-
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -WhatIf
 This parameter is reserved for internal Microsoft use.
 

exchange/exchange-ps/exchange/Get-VivaModuleFeaturePolicy.md

@@ -15,14 +15,22 @@ ms.reviewer:
 ## SYNOPSIS
 This cmdlet is available only in the Exchange Online PowerShell module v3.2.0 or later. For more information, see [About the Exchange Online PowerShell module](https://aka.ms/exov3-module).
 
-Use the Get-VivaModuleFeaturePolicy cmdlet to view the access policies for a specified feature in a Viva module in Viva. Policies are used to restrict or grant access to the specified feature for specific users, groups, or the entire tenant. This cmdlet provides details about the policies, including the policy's identifier, name, and creation date.
+Use the Get-VivaModuleFeaturePolicy cmdlet to view the access policies for a specified feature in a Viva module in Viva. Policies are used to restrict or grant access to the specified feature for specific users, groups, or the entire tenant. This cmdlet provides details about the policies, including the policy's identifier, name, and creation date. The cmdlet can filter policies based on MemberIds, allowing admins to view policies specific to certain users or groups.
 
 For information about the parameter sets in the Syntax section below, see [Exchange cmdlet syntax](https://learn.microsoft.com/powershell/exchange/exchange-cmdlet-syntax).
 
 ## SYNTAX
+
+### FeaturePolicy
+```
+Get-VivaModuleFeaturePolicy -FeatureId <String> -ModuleId <String> [[-PolicyId] <String>]
+ [-ResultSize <Unlimited>]
+ [<CommonParameters>]
+```
+
+### FeaturePolicyWithMembers
 ```
-Get-VivaModuleFeaturePolicy -FeatureId <String> -ModuleId <String>
- [[-PolicyId] <String>]
+Get-VivaModuleFeaturePolicy -ModuleId <String> [[-FeatureId] <String>] [[-MemberIds] <String[]>]
  [-ResultSize <Unlimited>]
  [<CommonParameters>]
 ```
@@ -32,6 +40,8 @@ Use the Get-VivaModuleFeaturePolicy cmdlet to view the access policies for a spe
 
 You can view all policies for a specified feature in a Viva module in Viva. To view a specific policy, you can include the PolicyId parameter.
 
+The cmdlet can filter policies based on MemberIds, allowing admins to view policies specific to certain users or groups.
+
 You need to use the Connect-ExchangeOnline cmdlet to authenticate.
 
 This cmdlet requires the .NET Framework 4.7.2 or later.
@@ -61,6 +71,20 @@ Get-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -Policy
 
 This example returns details about a specific policy added for the Reflection feature in Viva Insights.
 
+### Example 3
+```powershell
+Get-VivaModuleFeaturePolicy -ModuleId VivaInsights -FeatureId Reflection -MemberIds [email protected]
+```
+
+This example returns details about the policies for the Reflection feature in Viva Insights that apply to the user with the email [email protected].
+
+### Example 4
+```powershell
+Get-VivaModuleFeaturePolicy -ModuleId * -FeatureId * -MemberIds [email protected],[email protected]
+```
+
+This example returns details about the policies for all features across all Viva modules that apply to the user with the email [email protected] and the group with the email [email protected].
+
 ## PARAMETERS
 
 ### -FeatureId
@@ -70,7 +94,7 @@ To view details about the features in a Viva module that support feature access
 
 ```yaml
 Type: String
-Parameter Sets: (All)
+Parameter Sets: FeaturePolicy
 Aliases:
 Applicable: Exchange Online
 
@@ -81,6 +105,19 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+```yaml
+Type: String
+Parameter Sets: FeaturePolicyWithMembers
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: True
+```
+
 ### -ModuleId
 The ModuleId parameter specifies the Viva module of the feature policies that you want to view.
 
@@ -104,7 +141,7 @@ To view details about all policies for a feature in a Viva module, run this cmdl
 
 ```yaml
 Type: String
-Parameter Sets: (All)
+Parameter Sets: FeaturePolicy
 Aliases:
 Applicable: Exchange Online
 
@@ -115,6 +152,24 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -MemberIds
+The MemberIds parameter specifies the specific users or groups for which you want to view the policies for the feature in the Viva module. 
+
+You can provide up to three member IDs. Use the \* character to specify all modules or features.
+
+```yaml
+Type: String[]
+Parameter Sets: FeaturePolicyWithMembers
+Aliases:
+Applicable: Exchange Online
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ### -ResultSize
 This parameter is reserved for internal Microsoft use.
 

exchange/exchange-ps/exchange/New-AppRetentionCompliancePolicy.md

@@ -50,7 +50,9 @@ New-AppRetentionCompliancePolicy [-Name] <String> -Applications <String[]>
 ```
 
 ## DESCRIPTION
-\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies that cover Teams private channels, Viva Engage chats, and Viva Engage community messages. Eventually, you'll use these cmdlets for most retention locations and policy types. The \*-RetentionCompliance\* cmdlets will continue to support Exchange and SharePoint locations primarily. For policies created with the \*-AppRetentionCompliance\* cmdlets, you can only set the list of included or excluded scopes for all included workloads, which means you'll likely need to create one policy per workload.
+\*-AppRetentionCompliance\* cmdlets are used for policies with adaptive policy scopes and all static policies in the locations described in [Retention cmdlets for newer locations](https://learn.microsoft.com/purview/retention-cmdlets#retention-cmdlets-for-newer-locations). You can only set the list of included or excluded scopes for all included workloads, which means you likely need to create one policy per workload.
+
+\*-RetentionCompliance\* cmdlets continue to primarily support the locations described in [Retention cmdlets for older locations](https://learn.microsoft.com/purview/retention-cmdlets#retention-cmdlets-for-older-locations).
 
 To use this cmdlet in Security & Compliance PowerShell, you need to be assigned permissions. For more information, see [Permissions in the Microsoft Purview compliance portal](https://learn.microsoft.com/purview/microsoft-365-compliance-center-permissions).
 
@@ -104,13 +106,31 @@ Accept wildcard characters: False
 ```
 
 ### -Applications
-The Applications parameter specifies the applications to include in the policy and is relevant only for the following location parameters:
+The Applications parameter specifies the applications to include in the policy.
+
+This parameter uses the following syntax: `"LocationType:App1,LocationType:App2,...LocationType:AppN`:
+
+`LocationType` is User or Group.
+
+`App` is a supported value as shown in the following examples.
+
+- **Microsoft 365 apps**: For example:
+
+  `"User:Exchange,User:OneDriveForBusiness,Group:Exchange,Group:SharePoint"` or `"User:MicrosoftTeams","User:VivaEngage"`
+
+- **Microsoft Copilot experiences**: Currently in Preview. You must use *all* of the following values at the same time:
+
+  `"User:M365Copilot,CopilotForSecurity,CopilotinFabricPowerBI,CopilotStudio,CopilotinBusinessApplicationplatformsSales,SQLCopilot"`
+
+  **Note**: Even though you must use `CopilotinBusinessApplicationplatformsSales` and `SQLCopilot`, those values are currently irrelevant.
+
+- **Enterprise AI apps**: Currently in Preview. You must use *all* of the following values at the same time:
+
+  `"User:Entrabased3PAIApps,ChatGPTEnterprise,AzureAIServices"`
 
-- ExchangeLocation
-- ModernGroupLocation
-- AdaptiveScopeLocation
+- **Other AI apps**: Currently in Preview. You must use *all* of the following values at the same time:
 
-This parameter uses the following syntax: `"LocationtType:App1,LocationType:App2,...LocationType:AppN` where LocationType is User or Group. For example, `"User:Exchange,User:OneDriveForBusiness,Group:Exchange,Group:SharePoint"` or `"User:MicrosoftTeams","User:VivaEngage"`.
+  `"User:CloudAIAppChatGPTConsumer,CloudAIAppGoogleGemini,BingConsumer,DeepSeek"`
 
 ```yaml
 Type: String[]