PowerLeap Logo

Copilot Studio Friction

Get notified when this record changes

One email when the status or the fix changes — double opt-in, no tracking, unsubscribe in every email.

"1 error is preventing your agent from being published"

Mitigatedsince 8 July 2026

Last verified

Details & related

Assessment

Confidence
Confirmed officialConfirmed by Microsoft documentation or an official statement.
Severity
Blocking
Typical time lost
Hours

Identification

Governance & DLPPublish & channelsAll channels

Verification & changes

  1. Verified

    Doc check by human: Official DLP troubleshooting page and practitioner governance guidance re-read during seed migration; publish-blocking behavior and verbatim message still documented.

  2. Change

    Provisionally approved by the Product Owner; external LLM quality review pending.

  3. Change

    Initial record created from the seed dossier (migration wave 1).

Related

Are you in the right place?

  • Publishing fails with the message "1 error is preventing your agent from being published" and no detail.
  • The agent works normally in the test pane.
  • Your agent uses a channel or connector your admins may not have approved.
  • Publishing worked before, and a policy or connector changed since.

If a connector fails silently at runtime instead → that is the silent DLP sibling (record planned). If users see "Unable to provision connection" prompts instead → see Users get "Unable to provision connection" prompts. If Teams serves stale behavior after a successful publish → see Teams answers with an old version of your agent.

What's happening

A DLP policy is a data loss prevention rule set by your admins. It decides which connectors and channels agents may use. When policy blocks every channel, Copilot Studio refuses to publish and shows only this one-line error (documented as of 2026-07-08). The detail about which policy blocks what lives on the admin side, not in your error. Since January 6, 2025, this enforcement is no longer opt-in (documented as of 2026-07-08). A policy change elsewhere can therefore block your publish overnight. Think of airport security: one new rule, and your whole tray waits — no sign says which item triggered it. Blocking Direct Line can even raise a false warning when that channel isn't used (documented as of 2026-07-08).

For technicians

The official troubleshooting states the condition plainly: if data policies block all channels, the agent cannot be published. Non-business connectors are blocked by default in many tenants; any new connector stays blocked until an admin reclassifies it. The DLP violation report on the admin side lists which policy and connector combination fails. Misaligned policies do not only block new publishes — they can take running production agents down.

How to fix it

Solution 1

Official workaround

Have an admin check the DLP classification and pull the violation report

  1. Send your admin the agent's environment name and the list of connectors and channels it uses.
  2. Admin: open the Power Platform admin center.
  3. Admin: review the DLP policies that apply to that environment.
  4. Admin: pull the DLP violation workbook to identify the blocked connector or channel.

✅ You should now see: the exact policy and connector combination causing the block.

  1. Admin: reclassify the blocked connector, if company policy permits it.
  2. Publish the agent again.

✅ You should now see: the publish completing without the error.

Check that it worked

Publish the agent, then open it in the target channel and ask a question. Expected: the publish succeeds, and the agent answers in the channel.

If it didn't work

  • Publish works, but the channel behaves oddly. Propagation delay is suspect number one. See Teams answers with an old version of your agent.
  • The error persists. More than one DLP policy can apply to an environment; the admin must check each.
  • A Direct Line warning appears. You may not use Direct Line at all; this false positive is documented.
  • A connector fails silently at runtime after publishing. That is the sibling problem of this record (record planned).

Prevent it next time

  • Check every needed connector and channel against your tenant's DLP policies before you build. The security publish gate includes this step.
  • Agree a notification path with your admin for DLP policy changes — enforcement is immediate, not opt-in.

Evidence

  • Official documentationlearn.microsoft.com

    Official DLP troubleshooting documents that agents cannot be published when data policies block all channels, and covers false positives such as the Direct Line warning.

  • MVP blogpowertricks.io

    Practitioner governance guidance confirms non-business connectors are blocked by default in many tenants and stay blocked until an admin reclassifies them.