Merge pull request #303763 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-03 11:00 UTC

Author: learn-build-service-prod[bot]

articles/communication-services/concepts/chat/concepts.md

@@ -41,8 +41,6 @@ Azure Communication Services supports three levels of user access control, using
 
 Azure Communication Services stores chat threads according to the [data retention policy](/purview/create-retention-policies) in effect when the thread is created. You can update the retention policy if needed during the retention time period you set. After you delete a chat thread (by policy or by a Delete API request), it can't be retrieved.
 
-[!INCLUDE [chat-retention-policy.md](../../includes/chat-retention-policy.md)]
-
 You can choose between:
 - Indefinite thread retention.
 - Automatic deletion between 30 and 90 days via the retention policy on the [Create Chat Thread API](/rest/api/communication/chat/chat/create-chat-thread).

articles/communication-services/concepts/privacy.md

@@ -78,8 +78,6 @@ Azure Communication Services maintains a directory of phone numbers associated w
 
 Azure Communication Services stores chat threads according to the [data retention policy](/purview/create-retention-policies) in effect when the thread is created. You can update the retention policy if needed during the retention time period you set. After you delete a chat thread (by policy or by a Delete API request), it can't be retrieved.
 
-[!INCLUDE [chat-retention-policy.md](../includes/chat-retention-policy.md)]
-
 You can choose between indefinite thread retention, automatic deletion between 30 and 90 days via the retention policy on the [Create Chat Thread API](/rest/api/communication/chat/chat/create-chat-thread), or immediate deletion using the APIs [Delete Chat Message](/rest/api/communication/chat/chat-thread/delete-chat-message) or [Delete Chat Thread](/rest/api/communication/chat/chat/delete-chat-thread). 
 
 Any thread created before the new retention policy isn't affected unless you specifically change the policy for that thread. If you submit a support request for a deleted chat thread more than 30 days after the retention policy deleted that thread, it can no longer be retrieved and no information about that thread is available. If needed, [open a support ticket](/azure/azure-portal/supportability/how-to-create-azure-support-request) as quickly as possible within the 30 day window after you create a thread so we can assist you.

articles/communication-services/includes/chat-retention-policy.md

@@ -3,10 +3,12 @@
 metadata:
   title: Assign Azure roles using the Azure portal - Azure RBAC
   description: Learn how to grant access to Azure resources for users, groups, service principals, or managed identities using the Azure portal and Azure role-based access control (Azure RBAC).
-  author: jenniferf-skc
+
+  author: jenniferf-skc 
   ms.author: jfields
   manager: pmwongera
-  ms.date: 11/11/2024
+  ms.date: 08/01/2025
+
   ms.service: role-based-access-control
   ms.topic: how-to
   ms.custom:
@@ -73,6 +75,20 @@ procedureSection:
           You can search for a role by name or by description. You can also filter roles by type and category.
 
         ![Screenshot of Add role assignment page with Role tab.](./media/shared/roles.png)
+
+        
+        Note, If you're unsure of which role you need to assign, you can now use Copilot to help you select the appropriate role. (Limited preview. This capability is being deployed in stages, so it might not be available yet in your tenant or your interface might look different.)
+        
+      - |
+        (Optional) In the **Role** tab, click the **Copilot can help pick role** button. The Copilot dialog box opens. 
+
+        ![Screenshot of Copilot button in the Add role assignment page.](./media/role-assignments-portal/copilot-for-role-assignment.png)
+        
+        In the dialog box, you can add descriptive prompts to tell Copilot your requirements for the role, and what you need a user to be authorized to do, for example, *"Help me select a role to deploy and manage Azure functions."*, or *"Which role should I use if I
+        want a user to manage and view a workspace?"* Using phrases such as *'Help me select...'* or *'Which role should I use to...'* helps Copilot understand your intent more clearly in order to deliver the best results.
+
+        From the direction of your prompt, Copilot suggests a role, or multiple roles, based on the requirements provided. Copilot asks you to confirm by **Select permissions**. Copilot then recommends a role based on the
+        criteria provided. You can **Select role**, or you can ask Copilot to **Recommend other roles**. If you select **Select role**, you're taken back to the **Add role assignment** page where you can select the recommended role and view its details.
       - |
         If you want to assign a privileged administrator role, select the **Privileged administrator roles** tab to select the role.
 

articles/role-based-access-control/media/role-assignments-portal/copilot-for-role-assignment.png

@@ -97,7 +97,7 @@ external_table("microsoft.entra.id.AADRiskyUsers")
 ## Query considerations and limitations
 
 + Queries are run against a single workspace. Make sure you select the correct workspace before running a query.
-+ Executing KQL queries on the Microsoft Sentinel data lake incurs charges based on query billing meters. For more information, see [../billing.md#data-lake-tier].
++ Executing KQL queries on the Microsoft Sentinel data lake incurs charges based on query billing meters. For more information, see [Plan costs and understand Microsoft Sentinel pricing and billing](../billing.md#data-lake-tier).
 + Review data ingestion and table retention policy. Before setting query time range, be aware of data retention on your data lake tables and whether data is available for selected time range. For more information, see [Manage data tiers and retention in Microsoft Defender portal (preview)](https://aka.ms/manage-data-defender-portal-overview).
 + KQL queries against the data lake are lower performant than queries on analytics tier. It’s recommended to use KQL queries against the data lake only when exploring historical data or when tables are stored in data lake-only mode.
 

articles/role-based-access-control/role-assignments-portal.yml

@@ -1,12 +1,12 @@
 ---
  title: include file
  description: include file
- author: rolyon
+ author: jenniferf-skc
  ms.service: role-based-access-control
  ms.topic: include
- ms.date: 01/08/2021
- ms.author: rolyon
+ ms.date: 08/01/2025
+ ms.author: jfields
  ms.custom: include file
 ---
 
-When you assign roles, you must specify a scope. Scope is the set of resources the access applies to. In Azure, you can specify a scope at four levels from broad to narrow: [management group](../../articles/governance/management-groups/overview.md), subscription, [resource group](../../articles/azure-resource-manager/management/overview.md#resource-groups), and resource.
+When you assign roles, you must specify a scope. A Scope is the set of resources the access applies to. In Azure, you can specify a scope at four levels from broad to narrow: [management group](../../articles/governance/management-groups/overview.md), subscription, [resource group](../../articles/azure-resource-manager/management/overview.md#resource-groups), and resource.