Enforce Data Policies for Copilot Studio Agents
Short answer
D Configure data policies to classify connectors and prevent agents from using disallowed connectors and insecure data flows.
Question
The company needs to prevent the agents from using disallowed connectors and insecure data flows. Administrators must be able to enforce the governance controls to prevent and report violations.
You need to enforce governance controls for agents.
What should you do?
Key Takeaways
The question tests knowledge of Power Platform governance controls; the main trap is choosing a monitoring tool (Application Insights or analytics) instead of the preventive control (DLP policies).
Power Platform data policies (DLP) allow administrators to prevent Copilot Studio agents from using disallowed connectors and insecure data flows. This is the correct governance control to enforce and report violations.
Common mistake: Choosing C (Review agent analytics) because it mentions detecting risky connector usage, but analytics only detects problems after they occur and does not enforce or prevent violations.
Expert Analysis
Enforcing Governance with Data Policies
The scenario requires preventing Copilot Studio agents from using disallowed connectors and insecure data flows, while also allowing administrators to enforce and report violations. Option D, Configure data policies, is the correct choice. In the Power Platform admin center, Data Loss Prevention (DLP) policies classify connectors into Business, Non-Business, and Blocked groups. This directly prevents makers from adding blocked connectors to their agents and stops data from flowing between incompatible groups.
Why Monitoring is Not Enough
Options A and C focus on observation rather than enforcement. Option A (Application Insights) collects runtime telemetry and traces, which is useful for diagnosing performance issues but cannot block a connector. Option C (agent analytics) might help detect risky usage after the fact, but it lacks the authority to prevent the usage from occurring. A comment correctly notes that DLP policies are used to "block unauthorized connectors" and "prevent insecure data flows," fulfilling the preventive requirement.
The Adjacent Decision and Operational Consequence
If the question only asked to detect violations without preventing them, analytics or telemetry might be viable. However, because the requirement is to prevent usage, only data policies suffice. Operationally, failing to apply DLP policies allows makers to integrate any connector, risking the exfiltration of sensitive enterprise data to unapproved external services. Configuring data policies ensures that governance is enforced at the environment level before agents are published.
Official Reference
https://learn.microsoft.com/en-us/power-platform/admin/wp-data-loss-prevention
This link opens the official vendor documentation in a new tab.
Exam Strategy
When a question asks for both prevention and reporting of governance violations, look for administrative policy controls rather than monitoring or analytics tools. Monitoring tools like Application Insights or agent analytics can detect or report issues, but only data policies (DLP) can actually prevent disallowed connectors and insecure data flows from being used in the first place.
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
Arcadiuz 👍 1 Answered DPower Platform data policies, also known as Data Loss Prevention (DLP) policies, allow administrators to govern which connectors can be used and how data can flow between services. They can be used to: • Block unauthorized connectors. • Restrict combinations of connectors. • Prevent insecure data flows. • Enforce organizational governance requirements. Why the other options are wrong • A. Application Insights: Collects telemetry and diagnostic information. It does not enforce connector restrictions. • B. Security FAQs: Documentation does not enforce technical controls. • C. Agent analytics: Provides insights into agent usage and performance, not preventive connector governance.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.