Skip to content

Microsoft 365 Copilot adoption

Microsoft 365 Copilot supplies per-user adoption and licensing context for AI usage inside Microsoft 365.

Onboarding scope

This guide covers the read-only m365_copilot connector in the Venturi platform connector package. It reads Copilot usage reports and user context and never reads mailbox, file, or chat content.

Required access

Grant these Microsoft Graph application permissions. They are vendor permissions, entered exactly as written:

Microsoft Graph application permission Purpose
Reports.Read.All Read Copilot usage and adoption report rows.
User.Read.All Read user context for attribution.

Do not grant write, mailbox-content, or administration mutation permissions. The report returns rows only for users who hold a Microsoft 365 Copilot license. Microsoft documents the endpoint, its permissions, and its report periods in the Copilot usage user detail API.

Report concealment prerequisite

By default, Microsoft 365 conceals user names, user principal names, and other identifiers in every usage report, including the Microsoft Graph reports that this connector reads. A concealed row carries an obfuscated value in place of the user principal name and display name, and Venturi cannot resolve that value to a person. Before connecting, a Global Administrator decides whether to show identifiers: in the Microsoft 365 admin center, open Settings, then Org Settings, Services, and Reports, and clear Conceal user, group, and site names in all reports. The setting applies tenant-wide, and Microsoft records the change in the Microsoft Purview audit log. See Show user details in usage reports.

If concealment stays on, Venturi keeps each row as cohort-level adoption evidence and makes no person-level attribution from it.

Setup

  1. Create a dedicated app registration for Venturi.
  2. Add the two application permissions above and grant admin consent.
  3. Store the certificate or client secret as an encrypted credential reference in Settings / Admin / Credentials.
  4. Configure VENTURI_M365_TENANT_ID. The default lookback is 30 days, which matches the report’s D30 period. To change it, set VENTURI_M365_COPILOT_LOOKBACK_DAYS to 7, 30, 90, or 180, the single periods Microsoft publishes for the default v1 version of this report (D7, D30, D90, D180). See sync windows and failure behavior.
  5. In Venturi, go to Integrations / Microsoft 365 Copilot and run Test connection.

Verification

  • Test connection passes the read-only boundary check: report and user reads succeed, and the app holds no write or mailbox-content permission.
  • Per-user Copilot adoption rows appear in the latest sync, or cohort-level rows when report concealment is on.
  • Licensed rows with zero activity remain visible for adoption denominator analysis.
  • The connector inventory marks the integration as read-only.

Rotation and offboarding

Rotate the app credential through Microsoft Entra administration, then update the credential reference in Settings / Admin / Credentials. Removing the connector stops new Microsoft 365 Copilot adoption syncs.

Give feedback on this page

Sign in to send feedback. Opens in a new tab.

Copy page details 
Docs feedback: Microsoft 365 Copilot adoption
Page: https://docs.venturi.systems/connectors/m365-copilot/