Troubleshooting Microsoft Copilot Monitoring

Answers to common questions about why Microsoft Copilot activity does not appear in AI Security after you connect the connector.

Most reports of a Copilot connector "not working" turn out to be licensing rather than a fault. The Microsoft API that AI Security reads returns an empty result for an unlicensed user instead of an error, so the connector continues to look correctly configured while collecting nothing.

I connected Microsoft Copilot and the connector is active, but no activity appears in the console. Why?

The monitored users are almost certainly missing the license that Copilot monitoring depends on.

AI Security reads Copilot prompts and responses through the Microsoft Graph AI interaction export API. Microsoft returns data from this API only for users who hold a Microsoft 365 Copilot license with the Microsoft Copilot with Graph-grounded chat service plan enabled.

When the license or the service plan is missing, Microsoft returns an empty result instead of an error. AI Security has nothing to report, so the console stays empty.

To check and correct your licensing, see How to Resolve Missing Copilot Activity After Connecting.

The connector is authorised and Last Sync is recent. Does that mean data is being collected?

No. Both values describe the connection to Microsoft 365, not the data returned by it.

Last Sync confirms that AI Security reached Microsoft successfully and completed an exchange. A successful exchange that returns no interactions still updates this value, so a connector can appear to be working indefinitely while collecting nothing.

A Microsoft 365 Copilot license is assigned to my users. Why is there still no activity?

Check the service plans on the license.

Assigning a Microsoft 365 Copilot license does not guarantee that every service plan within it is enabled. If an administrator has cleared the Microsoft Copilot with Graph-grounded chat service plan for a user, Microsoft treats that user as unlicensed for this API and returns no interaction data, even though the license itself is assigned.

Verify the service plan on the individual user, not only on the license. For the steps, see How to Resolve Missing Copilot Activity After Connecting.

We use the Copilot Chat included with our Microsoft 365 E3 licenses. Is that supported?

No. Copilot monitoring requires the Microsoft 365 Copilot (business) license, which is the license that exposes the Copilot Compliance API. The Copilot Chat bundled with a Microsoft 365 E3 license does not include the required service plan and is not covered.

I tried both authentication methods. Why did neither work?

Both methods authenticate to the same Microsoft Graph API and are subject to the same licensing requirement. Switching between a client secret and admin consent does not change what Microsoft returns.

If no activity appears, check your Copilot licensing rather than changing the authentication method. See Choosing Between Client Secret and Admin Consent for what each method affects.

How long should I wait before I assume something is wrong?

Allow at least one full collection cycle after you connect the connector before you investigate. Historical activity is not available immediately, and an empty console in the first hours after connecting is expected.

Copilot activity appears, but file and SharePoint details are missing. Why?

One or more permissions were probably never consented.

Permissions added to a Microsoft Entra app registration after admin consent was granted remain unconsented until consent is granted again. The connector authenticates normally and collects the data covered by the consented permissions, so the gap appears as missing detail rather than as an error.

Open the API permissions page in your Microsoft Entra app registration and confirm that every permission shows as granted. Select Grant admin consent for your organization if any do not.

For an explanation of what each permission supplies, see Understanding the Permissions Microsoft Copilot Requires.