Skip to main content
Telara

Integrations / Microsoft 365 Copilot

Microsoft 365 Copilot logo

Microsoft 365 Copilot

Microsoft 365 Copilot usage via Microsoft Graph Reports API — per-user daily activity (chat queries, document interactions, meeting summaries) for M365 Copilot seat governance.

OAuth 2.0
Spend
Actions

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions YesReal-time events No

Before you connect

Prerequisites

A Microsoft 365 tenant with Copilot licenses.
An Entra admin who can grant tenant-wide consent.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → Microsoft 365 Copilot. Sign in as an admin and accept consent. You do not paste a client secret.
2
Re-consent if usage is empty
If the connection succeeds but Copilot usage stays empty, an admin must connect again and grant the Graph reports permission this page lists.

Permissions Telara requests

  • https://graph.microsoft.com/.default
    OAuth 2.0

In Telara

Connect in Telara

OAuth 2.0

Azure AD application credentials with Reports.Read.All permission (Microsoft Graph). Create an app registration in the Azure portal, grant application permission Reports.Read.All, and generate a client secret. Supply the Directory (tenant) ID, Application (client) ID, and the client secret value.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for
  • Tenant Id

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

  • copilot_active_users
    count
  • teams_chat_queries
    count
  • word_usage
    count
  • excel_usage
    count
  • powerpoint_usage
    count
  • outlook_usage
    count
  • onenote_usage
    count
  • loop_usage
    count

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

The scopes above are the permissions this connector requests. They come from the catalog, not from a hand-written page.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Delegated user consent is not enough for tenant Copilot reports.
This is not the Microsoft 365 files connector.