Copilot log access now needs the interaction API
Reviewed by Helen Jones
A Microsoft Tech Community post from Tony Redmond says Graph calls that tried to fetch Copilot interaction details from the TeamsMessagesData folder now receive 403 forbidden responses. The suggested replacement is the aiInteractionHistory API. The replacement API can help track Copilot interactions, but it does not return the full text of Copilot responses. Full prompt and response content still requires eDiscovery.
Before this change, some admins and tool builders could treat Copilot interaction records like another Graph-readable mailbox store. That made custom reporting and troubleshooting feel simpler, especially for small Microsoft 365 teams trying to understand how Copilot is being used. Now that direct folder access is blocked, Copilot visibility needs a more deliberate reporting path. SharePoint and Teams admins should separate lightweight interaction tracking from deeper compliance investigation, because the API and eDiscovery routes answer different questions and carry different licensing, permission, and process overhead.
Analysis
Check any Copilot reporting script or vendor tool that reads the TeamsMessagesData folder. If it breaks, test the aiInteractionHistory API for interaction reporting and reserve eDiscovery for cases where you need full prompt and response text.
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Copilot log access now needs the interaction API", Collab365 Spaces. 1 source referenced.