Error adding SharePoint folder as knowledge source in Copilot agent

(0) Share

Report

Posted on by HC-27051001-0

Hi Copilot Studio team,

I’m attempting to add a SharePoint folder as a knowledge source to my Copilot agent, but encountered an error during connection/provisioning.

---

Error details

Failure: Connection provisioning error
Message:
“An unexpected error occurred while provisioning the connection.”
Recommended action from system:
“Please verify the connection and try again. If the problem persists, contact support.”

---

Request

Could you please advise:

Are there specific permissions, approvals, or configurations required in the Prod environment to enable adding a SharePoint folder as a knowledge source?
Could this be related to connection setup (e.g., authentication, environment-level connectors, or data access policies)?
Is there anything we should reconfigure in the agent setup or SharePoint source to resolve this issue?

Thank you!

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

Vish WR 3,441 on at

Like (0)

Report
Copy link

Link copied!
@HC-27051001-0

The most common causes for this specific error in Prod environments are:

DLP (Data Loss Prevention) policies — The SharePoint connector may be blocked or restricted in the Prod environment's DLP policy. Check Power Platform Admin Center → Policies.

Missing Power Platform connections — The agent's service connection to SharePoint needs to be provisioned under the agent owner's identity. Go to Copilot Studio → Settings → Connections and ensure the SharePoint connection is established.

Environment-level connector restrictions — In Prod, connectors sometimes require explicit allowlisting by an admin.

Agent owner vs. publisher mismatch — The user adding the knowledge source may not have sufficient SharePoint permissions on that specific folder/site.

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
Suggested answer

RaghavMishra 72 on at

Like (0)

Report
Copy link

Link copied!
Hi,

The "Connection provisioning error" when adding SharePoint as a knowledge source is almost always one of three root causes documented on Microsoft Learn: missing prerequisites, blocked connectors via DLP, or environment-level permissions. Here's how to walk through each:

1. Confirm the SharePoint knowledge source prerequisites are met

The agent must be in an environment with Dataverse provisioned.

The SharePoint site must be in the same tenant.

The user adding the source needs at least read access to the SharePoint folder.

The SharePoint connector must be available (not blocked by DLP).

Full list: Add SharePoint as a knowledge source.

2. Check Data Loss Prevention (DLP) policies

If your environment's DLP policy puts the SharePoint connector and Copilot Studio's connector group in different data classifications (e.g., Business vs. Non-Business), the connection provisioning will fail.

Have your admin verify the policy in the Power Platform admin center → Policies → Data policies. Reference: Data loss prevention (DLP) policies.

3. Verify environment security and Connector privileges

Your user needs an Environment Maker (or higher) role, plus at least Create / Append To on the Connector table in Dataverse — otherwise the connection record cannot be saved. Reference: Configure user security to resources in an environment.

4. Confirm SharePoint search and indexing are enabled

Copilot Studio reads SharePoint content via Microsoft 365 search — the site must be search-indexed (not excluded), and the user adding it needs the site to be discoverable to them. Reference: Troubleshoot SharePoint knowledge sources.

5. Specific remediation for "connection provisioning" failure

Remove the partially provisioned connection: in Power Apps → Connections, find the SharePoint connection that's failing and delete it.

In Copilot Studio, re-add the knowledge source — you'll be prompted to sign in to SharePoint freshly. Pick the same account that has access to the site/folder.

If you still see the error, capture the request ID from the error pane and open a support ticket via the Microsoft Power Platform support flow.

Recommended order to fix

Confirm DLP isn't blocking the SharePoint connector.

Confirm your security role has Connector privileges.

Delete the broken connection and re-add the knowledge source.

Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!

Raghav Mishra — LinkedIn | PowerAI Labs

Was this reply helpful? Yes No
Vish WR 3,441 on at

Like (0)

Report
Copy link

Link copied!

@HC-27051001-0

Wanted to check if you are able to resolve your problem? Let me know if you need any clarification

When replying, please don't forget to mention my userid so that it will be notified

Vishnu WR

LinkedIn - My Tech Space

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
HC-27051001-0 2 on at

Like (0)

Report
Copy link

Link copied!

Thanks @Vish WR and @RaghavMishra for your helpful response and suggestions. Really appreciate you taking the time to share your insights.

I’ll check with our internal IT team to further investigate and identify the root cause on our side.

Will update here if we find anything useful!

Was this reply helpful? Yes No