Purview can now see Claude Enterprise. Here is what you get, and what you do not

In May 2026 Microsoft added an Anthropic Claude data connector to Purview, in preview. Once configured, Claude Enterprise shows up as an Enterprise AI app alongside Microsoft 365 Copilot and ChatGPT Enterprise: who used Claude, when, and what content was involved, visible in DSPM reports, activity explorer's AI activities tab, and the unified audit log.

The connector works through Anthropic's Compliance API rather than network interception, so it sees Claude Enterprise interactions wherever they happen, not just on managed devices or in managed browsers.

Four prerequisites, and the first one rules out most tenants today:

An Anthropic Enterprise plan. Not Free, Pro, Team, or Max. The Compliance API only exists on Enterprise.

Pay-as-you-go billing consent in Purview. Managing Claude interactions runs on the consumption billing model, so finance needs to be in the conversation before you switch it on.

The Data Connector Admin role for whoever builds the connector. Several role groups already include it, or an admin can create a custom role group that holds just that role and add the right people.

Patience. Data starts appearing in DSPM about a day after setup, so do not build this the morning you plan to demo it.

In Anthropic first. This half is not a Microsoft admin task, which is why it is usually where the project stalls. Only the primary owner of the Anthropic organization can do it:

1. Open Organization Settings, then Data and Privacy.
2. Enable the Compliance API.
3. Under Compliance access keys, select Create key, and store the key somewhere safe. It goes into Purview in a moment.

Then in Purview:

1. Sign in to the Purview portal and go to Settings, then Data connectors, then All connectors.
2. Select Anthropic Claude from the list, then Add connector, and accept the terms of service.
3. Name the connector after the Anthropic organization it points at. You may well end up with more than one.
4. On the Authentication page, paste the Compliance API key and select Validate connection, pick your Anthropic organization ID, and confirm the API base URL. The default is https://api.anthropic.com.
5. On the Data scope page, choose what to ingest and how often to sync.
6. Review the summary and select Finish.

Step 5 is the one that deserves a conversation rather than a click. Activity feed is the metadata trail: authentication events, chat interactions, file uploads, admin actions, and compliance audit events across Claude.ai, the Console, and the API. Chat conversations is the full message history, user prompts and Claude's responses included, and it is what makes the DSPM reporting meaningful. It is also the one to clear with your privacy team first, because you are copying employee conversations into a second platform.

Sync frequency sets how often the connector pulls from the Compliance API. Nothing here is live streaming, it is all a scheduled pull.

Give it a day, then look in three places:

• Connector health and sync status: Settings, then Data connectors, then My connectors. Check this first when the reports look empty.
• DSPM reports: total interactions over time and interaction trends by AI app, with Claude sitting alongside your other AI apps.
• Activity explorer, AI activities tab: set the AI app category filter to Enterprise AI apps and the App filter to Anthropic Claude to see individual interactions.

There are no recommendations or one-click policies for Claude yet, so the reports and activity explorer are the whole product. That is worth saying out loud before someone senior goes looking for a policy button.

Microsoft publishes a capability matrix for each AI app, and Claude's is mostly crosses. Supported: DSPM and auditing. Not supported: data classification, sensitivity labels, encryption without labels, DLP, Insider Risk Management, Communication Compliance, eDiscovery, Data Lifecycle Management, and Compliance Manager.

In practice that means you can see a user pasted something into Claude, but Purview will not classify what it was, will not block it, will not flag the user in IRM, and cannot put the conversation on legal hold.

Compare ChatGPT Enterprise, where the connector supports classification and Insider Risk Management. Claude's integration is newer and shallower. Claude agents are not covered at all yet, so they will not appear in AI observability either.

The connector is a witness, not a control. Plan accordingly.

Visibility on the Enterprise side pairs with enforcement on the browser and network side:

Inline web DLP can audit or block sensitive text and files heading to Claude.ai in the browser, on the unmanaged-apps path through Edge or via the Network path for other browsers. That covers consumer Claude too, which the connector never sees.

The connector then tells you what got through on the Enterprise plan, with the audit trail to investigate.

This split matters for policy design: blocking happens before the prompt is sent, the connector records what was sent. Neither replaces the other.

Watch the capability table as the preview matures. ChatGPT Enterprise's deeper support suggests where Claude's integration is likely heading, and classification support would be the signal that real controls are coming.