Safeguard Docs
Compliance ConnectorsSetup by categoryBusiness Applications

Microsoft 365 Copilot

Connect Microsoft 365 Copilot to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.

Connect Microsoft 365 Copilot to record its access review and data terms as attested evidence. Microsoft 365 Copilot offers no admin API for automated tests.

CategoryBusiness Applications
Connect withAPI token
What a connection producesAttested evidence

Connect with an API token

  1. In Microsoft 365 Copilot:

    1. Sign in to the Microsoft Entra admin center as at least a Cloud Application Administrator.
    2. Browse to Entra ID › App registrations, select New registration, name the app, choose Accounts in this organizational directory only, and select Register.
    3. Select Certificates & secrets › Client secrets › New client secret, enter a description and duration, select Add, and copy the value (shown only once).
    4. In the app registration, select API permissions › Add a permission › Microsoft Graph › Application permissions, select Reports.Read.All (the permission the Microsoft 365 Copilot usage report APIs require), then Add permissions.
    5. Select Grant admin consent for {your tenant}; the Microsoft Entra tenant administrator must explicitly grant consent.

    Microsoft 365 Copilot shows the secret only once, so copy it before you leave the page.

    Microsoft 365 Copilot's public documentation does not cover every step.

    Source: learn.microsoft.com, learn.microsoft.com, learn.microsoft.com, learn.microsoft.com, checked 2026-10-07.

  2. On Compliance › Connectors, open Microsoft 365 Copilot, click Connect, choose API token and fill in:

    FieldWhat to enter
    API token / Personal access tokenRequired. Stored encrypted and never shown again.
    Base URL (optional)—
    Account / Org / Workspace (optional)—
  3. Click Connect with token.

Frameworks

Microsoft 365 Copilot publishes no API for what these tests check, so its evidence is an attestation: connect it to record the connection, then attest the result. An accepted attestation counts toward each control below.

FrameworkEvidenceControlsTests
SOC2AttestationC1.2, CC6.2, CC6.3, CC6.52
ISO/IEC 27001AttestationA.5.18, A.5.34, A.8.102
HIPAA Security RuleAttestation164.308(a)(3)1
PCI DSSAttestation7.2.41
NIST CSF 2.0AttestationGV.OC-03, PR.AA-052

These tests are switched on per workspace by the Safeguard team.

On this page