Microsoft 365 Copilot and Copilot Studio
Two organization-level connectors bring Microsoft Copilot activity into ANTS Platform as traces:
| Connector | Source | What you get |
|---|---|---|
| Microsoft 365 Copilot | Microsoft Graph Copilot interaction history for your tenant | One trace per Copilot interaction, with the user's prompt, Copilot's response and the user (UPN) |
| Microsoft Copilot Studio | Copilot Studio telemetry in the Log Analytics workspace behind your Application Insights resource | Agent turns with tool calls |
Both send data into one ANTS Platform project that you choose.
Requirements
- The
enterprise-governanceentitlement (Enterprise plan). Without it, the Integrations tab does not appear in Organization Settings. - The Owner or Department Admin role, or a custom role with write access to Discover AI configuration. See Members & Roles. Saving credentials asks for step-up verification when it is enabled.
- An app registration in Microsoft Entra ID with a client secret.
Deployment requirement. Both connectors run in the Microsoft Graph
Copilot connector service. On self-hosted deployments it is off by default:
set msGraphCopilotConnector.enabled: true in the Helm values. Copilot
Studio is a separate switch, msGraphCopilotConnector.copilotStudio.enabled
(COPILOT_STUDIO_ENABLED), also off by default. Without the service, you can
save a connector but nothing syncs.
Connect
Go to Organization Settings > Integrations. The page lists the identity providers (Okta, Microsoft Entra ID) and the two Copilot cards.
Register an app in Entra ID
Create an app registration and a client secret. Grant it these Microsoft Graph application permissions and grant admin consent:
User.Read.AllAiEnterpriseInteraction.Read.All
Enter the details
Open Microsoft 365 Copilot and fill in:
| Field | Value |
|---|---|
| Send data to project | The ANTS Platform project that receives the traces |
| Directory (tenant) ID | Your Entra tenant ID |
| Application (client) ID | The app registration's client ID |
| Client secret | The secret value |
Test and save
Select Test connection, then Save & connect. The card then shows the project, tenant, client ID and Last sync.
Sync behaviour
- The service polls every 15 minutes by default (
pollCronSchedulein the Helm values). - It reads the Copilot interaction history of users in the tenant who hold a Microsoft 365 Copilot license.
- Each interaction becomes one trace attributed to the user's UPN. Traces have stable IDs, so an interaction that is read twice updates the same trace.
- The connector reads the Microsoft Graph beta interaction history API, which Microsoft may change.
Client secrets are encrypted at rest and never shown again. Disconnecting a connector stops the sync.
Where the data appears
Traces land in the project you chose and appear in Tracing and the Discover AI views for that project.
Troubleshooting
- No Integrations tab in Organization Settings. The organization does not
have the
enterprise-governanceentitlement, or your role lacks Discover AI configuration access. - Test connection fails (Microsoft 365 Copilot). Check the tenant ID, client ID and secret, and that admin consent was granted for both application permissions.
- Test connection fails (Copilot Studio). Check the workspace ID and the Log Analytics Reader role.
- Connected but no traces. On self-hosted deployments, check that the connector service (and the Copilot Studio switch) is enabled. Copilot Studio data can take up to 24 hours to reach Application Insights.