Why DLP blocks your Copilot Studio agents, and how to stop it happening

An agent that works in Preview and then fails the moment it needs a trigger is rarely a bug. It is two policy systems disagreeing about one connector. Here is how to read them, fix them and keep them aligned.

In short

If your tenant uses advanced connector policies on environment groups and classic data policies, both are enforced. A connector works only if the allow list permits it, no data policy blocks it, and every connector in the agent sits in the same data group. Fix all three in your development environment only, a day before you build.

The symptom

The agent behaves in the Copilot Studio test pane. Then you try to give it a trigger, or call it from Power Automate, and you get a red banner: Connection creation of 'Microsoft Copilot Studio' has been blocked by Data Loss Prevention (DLP) policy. You open the environment group, see the connector on the allow list, and nothing makes sense.

Nothing is broken. You are looking at the wrong policy.

Why it happens: two gates, one door

Microsoft now offers two ways to govern connectors. Advanced connector policies (ACP) live on environment groups and are a strict allow list: anything not listed is blocked. ** Classic data policies** live in Security and sort every connector into Business, Non-business or Blocked.

Until you deliberately switch a scope to ACP-only mode, the platform runs in mixed mode and evaluates both. The most restrictive answer wins.

REQUEST Microsoft Copilot Studio GATE 1 Allow list Environment group ACP GATE 2 Data policy Business only, same group Most teams fix gate 1, see the connector allowed, and stop. The block was at gate 2.
Mixed mode: a connector reaches the agent only after it clears both the allow list and the classic data policy.

The allow list tells you what is possible. The data policy tells you what is permitted. You need both answers to be yes.

Data groups: the rule nobody reads

Inside a classic data policy, connectors in different groups cannot share data. A flow that triggers on a new SharePoint item (Business) and sends an Outlook email (Non-business) is a policy violation, even though both are first-party Microsoft 365 services.

In a development environment for agents, the practical answer is simple: put every Microsoft 365 connector your agents use into Business and leave Non-business empty. You keep separation where it matters, between your tenant's data and the outside world, rather than between SharePoint and Outlook.

The connectors you cannot see

Several Copilot Studio capabilities are governed by connectors that are not APIs at all. They appear only in data policies:

Connector in the admin centreWhat it controls
Microsoft Copilot StudioEvent triggers on agents, calling agents from flows, automated evaluations
Microsoft Teams + M365 ChannelPublishing to Teams and Microsoft 365 Copilot
SharePoint channelPublishing to SharePoint
Knowledge source with documentsUploaded files as knowledge
HTTPThe HTTP request node in topics
Chat without Microsoft Entra ID authenticationPublic, unauthenticated agents

If your data policy's default group for new connectors is Blocked, which is the secure choice, every one of these starts blocked. That is correct for production. In development it means you must open the ones your agents need, on purpose.

The fix, without touching production

  1. Give development its own environment group. Policies apply to every environment in a group. If development shares a group with production, any change you make for an agent changes production too.
  2. Copy the production rules, then change one thing at a time. Start from the same allow list and the same blocked actions, so the only differences are the ones you chose and wrote down.
  3. Give development its own classic data policy. Name it after the group. Scope it to the development environment only, and remove development from any tenant-wide or shared policy.
  4. Agree the agent baseline. Microsoft 365 connectors, Microsoft Copilot Studio, the Teams channel and the knowledge sources you use, all in Business. Keep HTTP, unauthenticated chat, external channels and custom connectors blocked until a specific agent needs them.
  5. Start the agent the way its harness expects. Agents built in the new Copilot Studio experience run on the Microsoft Copilot harness and cannot be started from Power Automate: both Run an agent and Execute Agent show an empty list. Create a Copilot Studio workflow instead (a trigger, then an Agent node). Only standard-harness agents are started with Execute Agent.
  6. Write every change down. A decision log entry and an updated baseline. The next person to hit a block should find the answer in one page, not in your memory.

Propagation: why a correct fix still fails

Saving a policy is not the same as enforcing it. Microsoft says most changes take effect within an hour and the slowest can take a day. What we observed in one tenant on a single evening:

0 min Policy saved and correct in the admin centre

25 min First connector unblocked in Power Automate

55 min Second connector still blocked, same policy

88 min Second connector finally allowed

The lesson is planning, not patience: make policy changes the day before you build, as part of the agent's pre-flight, and reload the designer rather than just retrying sign-in.

Pre-build checklist

  • The agent's gate is written: what it reads, writes and decides, and its acceptance tests.
  • Every connector, action, trigger, channel and knowledge source is listed by its admin-centre name.
  • Each one is on the development allow list and in Business in the development data policy.
  • Any change was made at least a day before the build, and logged.
  • You know which harness the agent runs on, and start it with a Copilot Studio workflow (Microsoft Copilot harness) or Execute Agent (standard harness).
  • Writes go through a flow that enforces which fields may change.
  • The agent starts at the lowest autonomy level, on test data only.

Troubleshooting

You seeIt usually meansDo this
Blocked by DLP policy 'X'X is a classic data policy and the connector is Blocked thereMove it to Business in X, if X is your development policy. If not, ask why development is still in X's scope.
Action greyed outMissing from the allow list, or the action is switched offAdd it on the environment group, then apply changes.
Connectors in different data groupsBusiness and Non-business mixed in one flow or agentMove both into Business.
Publish greyed out in Copilot StudioA channel, knowledge or HTTP connector is blockedChannels, Details, Download: the file names the policy and connector.
Agent list empty in Run an agent or Execute AgentThe agent runs on the Microsoft Copilot harnessUse a Copilot Studio workflow with an Agent node. Execute Agent is only for standard-harness agents.
Still blocked after a correct changePropagationWait, reload the page, retry. Plan the next change a day ahead.

Sources