Merge pull request #31392 from MicrosoftDocs/main

m365-skilling-repo-management[bot] · web-flow · commit 3718a2890c3d · 2026-04-08T20:46:05.000Z
[AutoPublish] main to live - 04/08 13:43 PDT | 04/09 02:13 IST
diff --git a/copilot/TOC.yml b/copilot/TOC.yml
@@ -487,8 +487,12 @@ items:
         items:
         - name: Overview of Workflows
           href: responsible-ai/flow-builder-responsible-ai-faq.md
-        - name: Workflows privacy and data subject request (DSR) FAQ
-          href: flow-builder-privacy-data-subject-request-faq.md
+        - name: Data subject requests (DSRs)
+          items:
+            - name: Workflows privacy and data subject request (DSR) FAQ
+              href: flow-builder-privacy-data-subject-request-faq.md
+            - name: Perform DSRs for Workflows agents
+              href: perform-data-subject-requests-for-workflows-agents.md
       - name: Workforce Insights agent
         items:
           - name: Overview of Workforce Insights agent
diff --git a/copilot/flow-builder-privacy-data-subject-request-faq.md b/copilot/flow-builder-privacy-data-subject-request-faq.md
@@ -3,7 +3,7 @@ title: Workflows agent privacy and data subject request (DSR) FAQ
 description: Frequently asked questions about Workflows agent's privacy and data subject request (DSR) processes.
 author: sbasi19
 ms.author: kisubedi
-ms.date: 01/23/2026
+ms.date: 04/07/2026
 ms.topic: concept-article
 ms.service: microsoft-365-copilot
 ms.reviewer: v-aangie
@@ -22,18 +22,7 @@ Workflows agent is a Copilot agent that enables users to automate tasks by descr
 
 Flows created with Workflows agent are stored in the user's Power Platform environment. These flows are visible within the Workflows agent interface in Microsoft 365 Copilot, but aren't surfaced in Power Automate.
 
-Users can export or delete flows using standard Power Platform tools. Flows are subject to Microsoft’s Data Subject Request (DSR) processes.
-
-**Export**: Admins can export all data pertaining to a user's usage on Workflows agents. Learn more here:
-[List flows for a user](/connectors/flowmanagement/#list-flows-as-admin-(v2)), 
-[Get flow definition](/connectors/flowmanagement/#get-flow-as-admin) 
-
-**Delete/Reassign**: Admins can delete/reassign Workflows agents created by a user. [Learn More](/power-automate/privacy-dsr-delete#reassign-and-copy-the-users-flows)
-
-Here are some resources about DSR requests:
-
-- [Responding to DSR delete requests for Microsoft Dataverse customer data](/power-platform/admin/dataverse-privacy-dsr-guide)
-- [Responding to DSR delete requests to delete Power Apps customer data](/power-platform/admin/powerapps-privacy-delete-dsr)
+Users can export or delete flows using standard Power Platform tools. Flows are subject to Microsoft’s [Data Subject Request (DSR) processes](perform-data-subject-requests-for-workflows-agents.md).
 
 ## Is conversation history stored or exportable?
 
@@ -43,11 +32,11 @@ Learn more about how Microsoft 365 Copilot handles data in [Data, Privacy, and S
 
 ## How is Workflows agent managed by administrators?
 
-Administrators can manage Workflows agent in the Microsoft 365 admin center under **Copilot > Agents**. Available controls include:
+Administrators can manage Workflows agent in the Microsoft 365 admin center under **Copilot** > **Agents**. Available controls include:
 
 - Enable or disable the agent
 - Assign, block, or remove access
-- Control visibility using “Allow users access to agents”
+- Control visibility using **Allow users access to **agents**
 
 Workflows agent respects tenant-level settings configured in the Microsoft 365 admin center and Power Platform Admin Center (PPAC). These settings determine:
 
@@ -69,7 +58,7 @@ Workflows agent currently supports the following connectors:
 - Run a prompt
 - SharePoint
 
-Connector availability may vary depending on tenant policies and data loss prevention (DLP) configurations.
+Connector availability might vary depending on tenant policies and data loss prevention (DLP) configurations.
 
 ## How is user feedback handled and controlled?
 
@@ -84,7 +73,7 @@ Here are some important points about feedback collection. Feedback data:
 
 Feedback collection settings apply consistently across all Workflows agent surfaces. If Workflows agent is embedded in an iframe or accessed through other Microsoft 365 interfaces, feedback controls configured at the tenant level apply to both entry points.
 
-Here's some additional information about feedback collection:
+Here's some information about feedback collection:
 
 - [Providing feedback about Microsoft Copilot with Microsoft 365 apps](https://support.microsoft.com/topic/providing-feedback-about-microsoft-copilot-with-microsoft-365-apps-c481c26a-e01a-4be3-bdd0-aee0b0b2a423)
 - [Manage feedback for Microsoft 365 apps](/microsoft-365/admin/manage/manage-feedback-ms-org?view=o365-worldwide&preserve-view=true)
diff --git a/copilot/perform-data-subject-requests-for-workflows-agents.md b/copilot/perform-data-subject-requests-for-workflows-agents.md
@@ -0,0 +1,85 @@
+---
+title: Perform data subject requests (DSRs) for Workflows agents
+description: Learn how to perform DSRs for Workflows agents, and admin features like export, delete, and reassign.
+author: sbasi19
+ms.author: kisubedi
+ms.date: 04/07/2026
+ms.topic: concept-article
+ms.service: microsoft-365-copilot
+ms.reviewer: v-aangie
+ms.update-cycle: 180-days
+---
+
+# Perform data subject requests (DSRs) for Workflows agents
+
+Before performing a DSR, you must identify where the user's *Workflows* data resides.
+
+## Identify the scope
+
+1. Locate the Environment: Navigate to the [Power Platform admin center](https://admin.powerplatform.microsoft.com/), **Inventory**.
+
+1. Check two locations. Workflows artifacts are typically in one of two places:
+
+    - The default environment of the tenant.
+    - The user's Personal Development Environment (PDE).
+
+1. Go to **Inventory**, filter by the user's email, and make a note of the **Environment ID** where their Workflows agents are listed.
+
+Each Workflows agent's workflows are backed by specific Dataverse entities. Because these aren't surfaced in the standard Power Automate UI, you must use the following methods to locate them.
+
+## Method A: Web-based management (UI)
+
+For a manual, UI-based approach, navigate to the environment identified in [Identify the scope](#identify-the-scope) and use the **Tables** view in Power Apps or the maker portal.
+
+In the identified environment, refer to the following Dataverse entities on the environment to perform DSR export/delete.
+
+| Target data | Dataverse table |
+| :--- | :--- |
+| Process | Workflows (Category 5: Modern Flow *and* ModernFlowType: M365CopilotFlow) |
+| Process | AI Flows (Category 7: AI Flow) |
+| ConnectionReference | Connections |
+| AI Model | AI Prompts - AI Model |
+| AI Configurations | AI Prompt Prompt Data |
+| WorkflowMetadata | WorkflowMetadata |
+| FlowRun | Flow Run (If Flow Run Ingestion is enabled) |
+| AI FlowRun | Flow Run |
+| Approvals | Approvals (Subject to a 28-day automatic deletion retention policy) |
+
+## Method B: API-based management (bulk/automation)
+
+If you're handling multiple requests, use the environment-scoped APIs.
+
+| API | Notes |
+| :--- | :--- |
+| [Get Conversation Transcripts With Environment](/rest/api/power-platform/workflowsagent/dsr-compliance/get-conversation-transcripts-with-environment) | Get conversation transcripts for DSR export (environment-scoped). |
+| [Get Flow Run Actions With Environment](/rest/api/power-platform/workflowsagent/dsr-compliance/get-flow-run-actions-with-environment) | Get flow run actions for DSR export (environment-scoped). |
+| [Get Flow Runs (default/PDE)](/rest/api/power-platform/workflowsagent/dsr-compliance/get-flow-runs-non-singleton) | Get flow runs for DSR export (environment-scoped). |
+| [Get Run History Data (default/PDE)](/rest/api/power-platform/workflowsagent/dsr-compliance/get-run-history-data-non-singleton) | Get run history customer data for DSR export (environment-scoped). |
+
+### API permissions setup
+
+Learn more about permissions needed for API access in [Role-based access control (RBAC) permissions](/power-platform/admin/security/role-based-access-control).
+
+The following table provides specific permissions for Workflows agent DSR.
+
+| Role name | Role ID | Description | Assignable scope |
+| :--- | :--- | :--- | :--- |
+| Workflows agent Data Subject Rights Environment Reader | `38a014c1-0485-4e5e-b784-782ea373b34b` | Grants full access to perform read operations for Data Subject Rights requests for Workflows agent flows for a given environment. | `/tenants/{0}/environments/{1}` |
+
+Find a tutorial for customers in [Assign roles to service principals](/power-platform/admin/programmability-tutorial-rbac-role-assignment?tabs=PowerShell).
+
+### Export
+
+Admins can export all data pertaining to a user's usage on Workflows agents. Learn more in the following articles:
+
+- [List flows for a user](/connectors/flowmanagement/#list-flows-as-admin-(v2))
+- [Get flow definition](/connectors/flowmanagement/#get-flow-as-admin)
+
+### Delete/Reassign
+
+Admins can delete/reassign Workflows agents created by a user. Learn more in [Reassign and copy the user's flows](/power-automate/privacy-dsr-delete#reassign-and-copy-the-users-flows).
+
+The following list contains resources about DSR requests:
+
+- [Responding to DSR delete requests for Microsoft Dataverse customer data](/power-platform/admin/dataverse-privacy-dsr-guide)
+- [Responding to DSR delete requests to delete Power Apps customer data](/power-platform/admin/powerapps-privacy-delete-dsr)
diff --git a/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps.md b/microsoft-365/admin/manage/manage-copilot-agents-integrated-apps.md
@@ -52,7 +52,7 @@ You can manage agents for Copilot by using the [Microsoft 365 admin center](http
 
 Agents enhance the functionality of Copilot by adding search capabilities, custom actions, connectors, and APIs. Agents are custom versions of Microsoft 365 Copilot that combine instructions, knowledge, and skills to perform specific tasks or scenarios. For more information, see [Get started with agents for Microsoft 365 Copilot](https://support.microsoft.com/topic/169469d7-328d-4d37-9090-bfc2058a39bd).
 
-However, before users can access these agents, the agents must undergo a streamlined process of submission and approval. To learn more, see [Publish agents](agent-registry.md#publish-agents).
+However, before users can access these agents, the agents must undergo a streamlined process of submission and approval. To learn more, see [Publish agents](agent-registry.md).
 
 The hub Copilot experience shows the list of agents that are available and deployed for the user. Users can toggle it on or off to restrict access of Copilot to any specific agents during the interaction. Users can also add or remove agents in their Copilot experience by right-clicking on the agents and selecting the appropriate option. Users can only access the agents that the admin allows and that they install or are assigned to.
 
