Merge pull request #12711 from MicrosoftDocs/ARCP-chrisda

ARCP-chrisda to Main

Author: chrisda

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. and is relevant only for the following location parameters:
+
+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[]