Skip to main content
Blindsight can show how your organisation uses Microsoft 365 Copilot and its agents next to the AI use it sees on your devices. It reads activity records from your Microsoft tenant through a separate, read-only application that an administrator approves. Nothing is installed on devices. Blindsight asks only for the permissions a level needs, and tells you which permission a level adds, and why, before you approve it. Every application Blindsight can ask your tenant to approve is listed in Permissions Blindsight asks for. Access comes in three levels. Each one is a separate approval in Microsoft, and you can stop at any level.

How access is granted

Blindsight reaches your tenant through Blindsight Activity, a multitenant Microsoft Entra application that Blindsight owns. It is separate from the Intune applications, so you can approve one without the other.
  • A Global Administrator or Privileged Role Administrator approves it once on Microsoft’s admin consent screen, which lists the same permissions as this page. Application Administrators and Cloud Application Administrators cannot approve Microsoft Graph application permissions. If the person setting it up cannot approve tenant-wide permissions, Blindsight prepares a link to send to someone who can.
  • Every permission is an application permission and read-only. Blindsight signs in as the application, so no user signs in for collection to run.
  • Blindsight calls three Microsoft hosts only: graph.microsoft.com, manage.office.com, and, at level 3, the Dataverse environment addresses you enter.

Level 1: activity

Metadata only. Microsoft’s audit records for Copilot carry message identifiers, not message text. Without Microsoft Entra ID P1 or P2, Microsoft does not serve sign-ins to applications, and the console shows that view as not available rather than empty.

Level 2: agent catalog

Optional. Level 1 already lists every agent that has been used. Microsoft serves this list only to tenants with a Microsoft Agent 365 licence, in the global Microsoft cloud.

Level 3: content checks

Off by default, approved separately, and limited to the groups you choose. Only this level reads conversation text. Each conversation is checked in memory against the same data policies as your devices. When a policy matches, Blindsight keeps the rule, the person, the time, the app and a short excerpt with the sensitive value masked. Nothing is kept when no policy matches, and in a totals-only workspace only counts are kept.

Microsoft 365 Copilot

Microsoft does not include agents built in Copilot Studio in this source. Those are read from Dataverse.

Copilot Studio agents

Agents built in Copilot Studio keep their conversations in the Dataverse ConversationTranscript table of their Power Platform environment.
1

Add the application user

In the Power Platform admin center, open the environment, then Settings → Users + permissions → Application users → New app user. Search for Blindsight Activity by name, and pick a business unit.
2

Give it a read-only role

Assign a security role with organisation-level Read on the Conversation Transcript and Bot tables and nothing else.
3

Add the environment in Blindsight

Enter the environment’s address. Environments you do not add are never contacted.
Blindsight reads no other Dataverse table, including Dynamics 365 business records. Microsoft deletes transcripts after 30 days by default. Transcripts are not saved in developer environments, Dataverse for Teams environments, or where an admin turned saving off. Blindsight reads what your environment keeps.

What Blindsight never does

With any of the access above, Blindsight never:
  • writes, changes or deletes anything in your tenant or Dataverse environments
  • reads mailboxes, OneDrive or SharePoint files, Teams chats or calendars
  • reads conversation text unless you turn on level 3
  • stores full prompts or responses at any level

Before you connect

  • Audit logging is on. Unified audit logging must be turned on in Microsoft Purview. Copilot and Copilot Studio activity is then recorded as part of Audit (Standard), with no extra licence.
  • The first activity can take up to 12 hours to arrive after you connect. After that it arrives continuously.
  • History starts when you connect. Microsoft keeps delivered activity for 7 days, so Blindsight sees activity from the day it subscribes onward.

Remove access

You can remove access in Microsoft at any time, whatever the console shows.
  • All levels: in the Microsoft Entra admin center, open Enterprise applications and select Blindsight Activity. Under Properties, turn off Enabled for users to sign in? to stop Microsoft issuing it new tokens, or select Delete. A deleted application can be restored for 30 days. To drop one level and keep the rest, revoke just those permissions under Permissions.
  • Copilot Studio transcripts: in the Power Platform admin center, remove the Blindsight Activity application user from each environment.
  • In Blindsight: disconnecting stops collection at once. Stored activity is deleted with the workspace or on request.