Support Needed - Copilot Studio Agent Blocked by DLP Policy

(0) Share

Report

Posted on by WB-09040323-0

I’m building a Copilot Studio agent that uses a Power Automate flow to create items in a SharePoint list (Requests → Projects → Tasks workflow).

The flow is triggered using “When an agent calls the flow”, and includes a SharePoint Create item action.

When I try to publish the agent, I receive the following error:

DlpViolationError (BlockedConnector)
“At least one connector here has been blocked”
Additional message indicating I must configure at least one channel (e.g., Teams), but publishing is still blocked

I’ve confirmed:

The flow works independently
The issue only occurs when the agent attempts to use the flow
The flow includes a SharePoint connector

My understanding is this is related to DLP policy restrictions, but I’m trying to confirm:

Are Copilot Studio agents allowed to call Power Automate flows that use SharePoint connectors?
Does the “When an agent calls the flow” trigger require specific DLP policy alignment?
Are Copilot Studio, Power Automate, and SharePoint required to be in the same DLP policy group?
Is there a supported workaround for this pattern (Agent → Flow → SharePoint) in restricted environments?

This is an internal-only use case for workflow automation (no external data exposure).

Any guidance or examples of a working configuration would be appreciated. Open to suggestions on how to troubleshoot.

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Ashlesha-MSFT Microsoft Employee on at

Like
a
(2)

Report
Copy link

Link copied!
WB-09040323-0, Thanks for the detailed context. Here’s guidance regarding your issue:

Root Cause

The DlpViolationError (BlockedConnector) occurs because the SharePoint connector is currently in the Blocked group in your environment's DLP policy. When a Copilot Studio agent calls a flow, the agent and flow are evaluated together against the environment’s DLP policy — even if the flow works independently, calling it from an agent is treated as a new execution context subject to DLP enforcement.

Answers to your questions

Are agents allowed to call flows that use SharePoint connectors?

Yes, only if the SharePoint connector is in the Business or Non-Business group (not Blocked) in your environment’s DLP policy.

Does “When an agent calls the flow” require specific DLP alignment?

Yes. The connectors used inside the flow must comply with the environment’s DLP policy. The trigger type itself does not need special settings.

Do Copilot Studio, Power Automate, and SharePoint need to be in the same DLP group?

All connectors used together in a flow must be in the same DLP group (Business or Non-Business). Mixing Business and Non-Business connectors in the same flow is not supported

Is there a supported workaround for Agent → Flow → SharePoint in restricted environments?

No bypass exists. The only supported path is updating the DLP policy to allow the connector.

Steps to resolve

Go to Power Platform Admin Center → Policies → Data Policies.

Identify the policy applied to your environment.

Move the SharePoint connector from Blocked to the Business group.

Ensure all other connectors in the flow are also in the Business group.

If you don’t have rights to edit policies, contact your Power Platform admin and provide:

Environment name

Flow name

List of connectors use

After the policy update, test using a minimal agent + flow setup before deploying the full workflow.

Was this reply helpful? Yes No
Ashlesha-MSFT Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Just following up on the answer I shared recently. Could you please let me know if it resolved your issue, or if you need any further clarification?

Was this reply helpful? Yes No
WB-09040323-0 5 on at

Like
a
(0)

Report
Copy link

Link copied!

It's not resolved yet, but shed further light on the issue. Plan on troubleshooting further today with hopes of a resolution. Thanks for the follow up.

Was this reply helpful? Yes No