Power Platform Community Forum Thread Details

Hi there,

I’m unable to publish a Copilot Studio agent because the DLP policy “Productivity (Default)” blocks trigger creation for the Microsoft Copilot Studio (shared_microsoftcopilotstudio) connector.

The idea is that I'd like to share this agent with my team, so that they are able to edit the instructions themselves when they need a change.

Even without adding explicit triggers, it looks like Copilot Studio has created implicit triggers during publish (channels/orchestration), which fails under the current policy.

Could you please allow triggers for this connector or create a Copilot‑specific DLP policy for the environment?

Kind regards

Noah

Categories:

Publish & channel management

Hi @NH-30031609-0,

This is expected behavior. Copilot Studio creates implicit triggers during publish (channels / orchestration), even if you don’t add triggers yourself.
Since DLP enforcement for Copilot Studio is fully enabled, blocking triggers for the shared_microsoftcopilotstudio connector will prevent publishing.

The fix isn’t on the agent side, an admin needs to either:

Allow the Copilot Studio connector (and triggers) in the DLP policy, or
Create a Copilot‑specific DLP policy scoped to this environment.

This is required if you want to share the agent with your team and let them edit instructions.

https://learn.microsoft.com/microsoft-copilot-studio/admin-data-loss-prevention

https://learn.microsoft.com/microsoft-copilot-studio/admin-dlp-troubleshooting