How to Connect Microsoft Copilot Using Microsoft Sign-In (Admin Consent)

Use this topic when you want to connect Microsoft Copilot to the Forcepoint Data Security Cloud Platform so that user activity across Copilot, SharePoint, and OneDrive is monitored.

Before you begin

Note: In the current Early Access release, the Sign in with Microsoft (Admin consent) authentication option is not functional. To connect Microsoft Copilot, use the Client secret option instead, see How to Connect Microsoft Copilot Using a Client Secret. Admin consent will be enabled in a future release.

Make sure your Microsoft 365 account meets all of the following requirements. These are shown on the connector page itself under Admin account requirements.

Note: Microsoft Copilot monitoring depends on the Microsoft 365 Copilot (business) licence, which exposes the Copilot Compliance API. The Copilot Chat included with a Microsoft 365 E3 licence is not covered. At least one user in your tenant must hold a Microsoft 365 Copilot licence before any activity appears.
Requirement Details
Admin role Global Administrator in Microsoft 365
Base licence Microsoft 365 Enterprise E1 or higher
OneDrive licence Valid OneDrive licence
Copilot licence Copilot Add-On licence (required for Copilot scanning)

Next steps

  1. Sign in to Forcepoint Data Security Cloud Platform.
  2. In the left navigation under APPLICATIONS, click AI Security, then Dashboard.

  3. The Configure AI Security panel opens. Click on Start Easy Setup.

  4. On the Connect your AI apps screen, click the Copilot tile or Connect app.

  5. The Connect Microsoft Copilot page opens. It has two sections: Configuration on the left and Authentication on the right.
  6. In the Configuration section, review the Connector Name. The field defaults to Microsoft Copilot. Rename it only if you plan to connect multiple Microsoft tenants.
  7. Under Authentication, review the services you want to scan. Both are enabled by default:
    • SharePoint — Scans files at rest across SharePoint sites.
    • OneDrive — Scans files stored in user OneDrive accounts.
  8. Toggle off any service you do not want to scan.
    Note: You can change which services are scanned after setup from AI Security → App Connectors → Manage connector.
  9. In the Authentication section, click Sign in with Microsoft.
  10. The authentication status changes to Awaiting authorization. A Microsoft sign-in popup appears.
  11. Sign in using your Microsoft 365 Global Administrator account.
  12. Review the permissions requested by the Forcepoint Microsoft 365 Connector and click Accept.
    Note: All the permissions listed below are required. If you decline any of them, the connection will not be established.

    Permission Why Forcepoint needs it
    Read and write directory data To read user and group information from your Microsoft Entra ID directory and keep it in sync.
    Have full control of all site collections To scan and monitor files and content stored across all SharePoint site collections.
    Read activity data for your organisation To monitor how users are interacting with Microsoft 365 services, including Copilot activity.
    Read all AI enterprise interactions To capture and inspect prompts and responses within Microsoft Copilot.
    Read calendars in all mailboxes To identify data flows that involve calendar information shared through AI interactions.
    Read directory data To look up user identities and resolve them against your organisation's directory.
    Read and write files in all site collections To scan files stored in SharePoint for sensitive data as defined by your DLP policies.
    Read mail in all mailboxes To monitor email data that may be accessed or referenced through AI interactions.
    Read and write items in all site collections To inspect list items and documents stored across SharePoint for policy violations.
    Note: Accepting these permissions registers the Forcepoint Microsoft 365 Connector as an authorised app in your Microsoft Entra ID tenant. This is a one-time action. You can review or revoke this at any time from https://myapps.microsoft.com.
  13. Once you Accept, the Authentication section now shows Authorized successfully with the admin email you signed in with.
  14. Under Services Enabled, SharePoint and OneDrive are confirmed as active.
  15. Under Select Scope, choose who in your organisation this connector will cover:
    • All Users — Every user in the tenant is monitored.
    • Select Users — Only specific users you add are monitored.
    Note: If you choose Select Users, a text field appears where you can type and add individual users. Added users appear in a Users included panel. You can remove anyone from the list before saving. If you are unsure, start with Select Users and target a small pilot group first. You can widen scope to All Users later from App Connectors → Manage connector.
  16. Click Next.
  17. The wizard moves to Step 2 — Data Protection. The screen asks: What data should AI Security monitor?

    Note: Cloud DLP integration is not available in this Early Access (EA) release, so no policies can be selected here. Click Skip for now. This step will be enabled once DLP integration ships.
  18. Here you select the policies that define what sensitive data AI Security will monitor in Copilot interactions — including activity across SharePoint and OneDrive if you enabled those services. You can either select the policies or use Skip for now button to skip this step.
  19. Once you have selected your policies, click Next on the Data Protection screen.
  20. The wizard moves to Step 3 — Confirm Setup. The screen shows a Setup Summary with two panels:
    • Connected AI Apps — Lists Microsoft Copilot with a Connected status.
    • Policies Activated — Lists the policies you selected in Step 2.
  21. You are returned to the Connect your AI apps screen. The Copilot tile now shows a green Connected badge, and the counter in the top right updates.

    Note: After the connector is added, activity from the last seven days is backfilled. Microsoft provisions the Compliance API at its own pace, so data can take anywhere from a few minutes to a few hours to appear. If nothing appears after several hours, confirm that the monitored users hold a Microsoft 365 Copilot licence.