Forum Discussion
Graph Custom Connector data not available in agent
We have created a few different Graph Custom Connectors using the graph proxy. Recently (in the last 2 or 3 weeks) it seems that the agents stopped being able to access this data. In the copilot studio when in test most, I put my query in and it starts to answer the query but then hides the answer and says it couldn't find any data. We are also seeing this with the SQL connector. My initial thought is it has something to do with the way we are handling ACLs in the connector but it would be odd for MSFT to be trimming responses based on ACL after the fetch instead of before or during. Has anyone ran into this type of issue before?
Our custom connectors are crawling correctly and if we do an o365 search, we are seeing the data present from the custom connectors so it does appear to just be an issue with the agents in copilot studio. The custom connectors are also in the "staged" state.
Thanks for any help/assistance you can provide.
4 Replies
Can you try these
- Make sure the users testing in Copilot Studio have access to the connector data via Graph (the same accounts that would pass ACL checks).
- Verify whether the connector is still flagged as “staged”. In that state, the connector is discoverable in search but not always consumable by Copilot agents. Moving it to “published” usually clears that gap.
- Test with the SQL connector and Graph connector side by side. If both fail the same way, that strongly suggests it’s the new ACL enforcement behavior rather than a crawl problem.
- Test with another user account to rule out user-specific access problems.
Hope this will help you.
Thanks for your response pradejain.
- The users do have access to the connector data as I mentioned before, they can retrieve this data doing an o365 search and it lists the connector as the data source.
- The connector is "staged" as that is the state it needs to be in and will be in when targeted to a limited set of people. My understanding is that we are doing a graph search anyhow so as long as people are able to access the search results, copilot should also be able to execute the search on their behalf (using their access token).
- Both are technically graph connectors (sql and custom) but neither are working in the copilot studio agents when used as knowledge sources
- Same issue is seen with different accounts in copilot studio.
Sometimes Staged connectors show up in enterprise search, but Copilot knowledge sources sometimes require explicit assignment to Copilot.
- Try to Test with Published (not Staged)
- As a quick test, publish the connector (target a small pilot group) and re-add it as a knowledge source in Copilot Studio.
If this works, the issue is with staged connectors not being usable by Copilot agents.
