Rovo agent Sharepoint knowledge source filter not populating sites and content

Question

I am trying to limit the content, for this Rovo agent, to a single folder in a Sharepoint site.

The connector shows synced with a couple thousand objects indexed.

The connector only has one site allowed.

When I try to filter the agent's Sharepoint knowledge source, nothing populates. I tried searching by the source's nickname and the site name,

I have tried reauthorizing the connector, removing and readding the connector and verified admin consent has been granted.

The Rovo agent was able to find a specific file in the Sharepoint site as well. Seems like everything is connected properly so I'm not sure what is going on.

Dr Valeri Colon (Connect Centric) · Answer

@Jeremy Attard welcome to the community. Your testing suggests the connector itself is working because Rovo can retrieve the SharePoint file. I wouldn’t assume the empty filter is a connector problem. Atlassian’s current agent documentation clearly describes deeper scoping for Confluence, Jira and JSM, but doesn’t clearly document SharePoint folder-level filtering for standard Studio agents. I’d raise this with Atlassian Support to confirm whether the empty picker is a defect or current limitation.

Arkadiusz Wroblewski · Answer

Hi @Jeremy Attard

Your testing shows the SharePoint connector itself is working fine, documents are indexed and searchable so the issue is isolated to the new Rovo Studio filter picker. Keep in mind that connector nicknames are only for the admin UI, so searching by nickname won't yield filter results; you'll need to search by the exact folder or library name instead.

Given the recent rollout of these folder filters, this feels like a picker defect or Graph API discovery glitch, similar to ROVO-685.

Before escalating, try searching for the exact folder name in a fresh subagent with another builder, ensure your personal account is connected in Rovo Search, and check the browser Network tab for failing status codes or request IDs.

If a new subagent still stays empty, stop rebuilding the connector and submit a private Atlassian Support ticket with your connector and agent IDs, UTC timestamps, and network logs.

One more time. If you "Feel" that's not intended by Atlassian. Never ever hesitate to open a ticket. You're not only helping yourself with that. Sometimes you're also helping others.

Best,

Arek 🤠