A company has agents in Copilot Studio.

Comprehensive and Detailed Explanation From Microsoft AB-620 Study Guide: Power Platform data policies are the preventive governance control for connectors, HTTP endpoints, knowledge sources, and combinations of data groups used by Copilot Studio agents. Administrators can classify or block connectors, restrict endpoint use, require authentication, and surface policy violations during authoring or publishing. This meets both enforcement and reporting requirements. Application Insights records runtime telemetry but does not prevent a maker from adding a disallowed connector. Security FAQs provide guidance only. Agent analytics can reveal behavior and usage trends but are detective, not an administrative guardrail. Data policies should be scoped deliberately at tenant or environment level and tested against representative agent configurations. When a violation occurs, Copilot Studio can block publishing and provide downloadable details identifying the policy conflict, enabling the administrator and maker to correct the design. Governance should also include least-privilege connections, environment segmentation, solution-based ALM, and review of exceptions; a broadly permissive policy followed by manual monitoring is not equivalent to enforcing the control at design and deployment time. Study Guide alignment: Plan and configure agent solutions > Plan an agent solution > Evaluate security and governance considerations.

===============