How to Manage a Microsoft Copilot Connector

Use this topic when your Microsoft Copilot connector is already set up and you need to check its status, update its authorization, choose which Microsoft 365 services are scanned, or set where sensitive data goes when a DLP action runs.

Before you begin

Microsoft Copilot is already connected. To connect it for the first time, see How to Connect Microsoft Copilot Using Microsoft Sign-In (Admin Consent) or How to Connect Microsoft Copilot Using a Client Secret.

The Microsoft Copilot Connector Details screen is where you control everything about this connection after setup - whether inspection is running, which Microsoft 365 services are in scope, and where quarantined or copied files are stored.

Steps

  1. In the left navigation, click Connector.
  2. Click App Connector.
  3. Locate the Microsoft Copilot connector.
  4. Click Manage connector.

    The Microsoft Copilot Connector Details screen opens.

  5. Check the connection status shown next to the app name.

    Connected means the credentials are valid and inspection is running. Disconnected means authentication failed and you need to update the credentials.

  6. In CONNECTION DETAILS, review Authorization and Last Sync.

    Authorization shows how the connector authenticates, for example OAuth / Microsoft Entra. Last Sync shows the date and time of the most recent successful sync.

    Note: The Last Sync field shows a dash (-) if the connector has not yet completed a sync.
  7. Optional: Click Edit to update the connection details.

    Use this when the connection has dropped or the client secret has expired.

  8. In the Status section, use the toggle to set the connector to Active or Inactive.
    Important: Setting the connector to Inactive pauses all inspection and policy enforcement for Microsoft Copilot. Existing settings are kept, so you can turn inspection back on at any time.
  9. Under Scan Configuration, turn the OneDrive toggle on to scan files in user accounts.
  10. Set the OneDrive SITE SCOPE to All Sites or Select.

    Choose Select to pick individual sites instead of scanning everything.

  11. Turn the SharePoint toggle on to scan SharePoint content.
  12. Set the SharePoint SITE SCOPE to All Sites or Select.
  13. Scroll to DLP Action Settings.

    These paths tell the platform where to place files when a DLP policy triggers a remediation action:

    • Quarantine - the file is removed from its source location and moved to a secure folder for review.
    • Copy - a copy of the file is saved to a folder for review, and the original stays in place.
  14. In Quarantine Directory Path, enter the folder path for quarantined files.

    For example, /forcepoint-quarantine/copilot/.

  15. In Copy Directory Path, enter the folder path for copied files.

    For example, /forcepoint-copies/copilot/.

  16. Click Save.

    Your changes are applied to the Microsoft Copilot connector.

Result

The Microsoft Copilot connector runs with the status, scan scope, and DLP destinations you set. Inspection results appear on the AI Governance Dashboard.

Next steps

Note: Click Discard to leave the screen without applying your changes.
Note: To stop monitoring Microsoft Copilot completely, click Remove Connector at the bottom of the screen. Removing a connector deletes the connection and its settings. Set the connector to Inactive instead if you only want to pause inspection.
Restriction: Options marked SOON - including Scan Configuration and DLP Action Settings - are not available in this Early Access (EA) release. They will be enabled in a future release.
Tip: Use a consistent, connector-specific naming convention for your directory paths, for example /forcepoint-quarantine/<connector-name>/. This keeps quarantined and copied files easy to find during an investigation.