Respond to personal data discovery requests (Microsoft Entra ID)
The first step in responding to personal data requests is to find personal data that's subject to the request. This step helps you to determine whether a request meets your organization's requirements for honoring or declining the request.
The following table summarizes the Power Automate resources that may contain the personal data of a user who authenticates using Microsoft Entra ID.
| Resource | Purpose |
|---|---|
| System-generated logs | Records that capture system events and history. |
| Run history | The history of each flow execution for the past 28 days, including the start time, end time, status, and all inputs and outputs. Learn more. |
| Activity feed | Recaps flow activities, including run status, failures, and notifications. |
| User jobs | Not visible to the user; system jobs that run on behalf of a user for flows to execute. |
| Flows | The workflow logic that exists for a cloud flow. Learn more. |
| Flow permissions | Permissions that allow other users to share a flow. Learn more. |
| User details | Not visible to the user; details that support flow execution. |
| Connections | Used by connectors to share data with APIs, systems, databases, etc. Learn more. |
| Connection permissions | Permissions for connections. Learn more. |
| Custom connectors | Custom connectors that a user has created and published that allow connections to custom or third-party systems. Learn more |
| Custom connector permissions | Permissions for custom connectors. Learn more. |
| Gateway | Gateways are on-premises data services that users can install to transfer data quickly and securely between Power Automate and a data source that isn't in the cloud. Learn more. |
| Gateway permissions | Permissions for gateways. Learn more. |