Power Platform Community Forum Thread Details

Hi,

I’m running into an issue when trying to add Confluence as a Knowledge source in Copilot Studio.

When selecting one or more Confluence spaces/pages and clicking “Add to agent”, the process fails with the generic error:

There was a problem creating your knowledge source.

Unfortunately, no further error details are shown in the UI.

The Confluence connection itself shows as connected / healthy
I can browse and select Confluence content without issues (I see the pages and spaces loading, but after selecting one, I get this error)
The error occurs consistently when attempting to actually create the knowledge source
Refreshing, reselecting items, or retrying does not resolve it

Environment details

Product: Copilot Studio (Knowledge feature)
Knowledge source: Confluence
Authentication: Standard Confluence connector (OAuth)
Tenant: Microsoft 365 (commercial)
Browser: (tested in Edge & Firefox)

What I’m looking for

Are there any known issues or limitations with the Confluence Knowledge connector?
Is there any backend logging or diagnostic location where more detailed error information can be found?
Are there specific permissions, page types, or space configurations that can cause this failure?
Any recommended troubleshooting steps beyond reconnecting the datasource?

Screenshots attached showing the error message in Copilot Studio.

Thanks in advance

Categories:

Bot extensibility

Model context protocol

General topics

1. Known Issues & Limitations (as of April 2026)
Confluence Knowledge Connector is still evolving and has some known limitations:

Only supports Confluence Cloud (not Server/Data Center).
Some page types (e.g., archived, restricted, or template pages) may not be supported.
Spaces or pages with complex permissions or custom macros can cause ingestion failures.
Large spaces or pages with many attachments may fail to add.

OAuth token scope: The connector requires sufficient permissions (at least “read:confluence-content.all” and “read:confluence-space.summary”).
Rate limits: Atlassian API rate limits or throttling can cause failures, especially in large tenants.

2. Permissions, Page Types, and Configurations

Permissions: The Confluence user used for the connection must have at least “View” access to all selected spaces/pages. If a page or space has restricted permissions, the connector may fail to ingest it.
Page Types: Avoid selecting archived, restricted, or template pages. Try with a simple, standard page in a public space to isolate the issue.
Space Configurations: Spaces with custom permissions, integrations, or non-standard configurations may cause issues.

3. Recommended Troubleshooting Steps

Test with a Simple Page: Try adding a single, basic page from a public space with no restrictions.
Check Permissions: Ensure the Confluence account used for the connection has full read access to the selected content.
Reconnect the Data Source: Remove and re-add the Confluence connection in Copilot Studio.
Try a Different Browser or Incognito Mode: Rule out browser extension or cache issues.
Review Microsoft 365 Message Center: Look for any service advisories related to Copilot Studio or connectors.