.png)
Claude Enterprise runs beside Microsoft 365 with no single view
The questions are the ones you already ask of a Team or a SharePoint site: who created it, who has access, what data it holds, what it costs, and who cleans it up.
Who uses it
Claude Enterprise keeps its own users, groups and admin roles. Without a join to Entra ID, you cannot tell which department a Claude Enterprise user belongs to, or whether someone who left the company still holds access.
What they put into it
Teams build chats and projects and load corporate data into them, finance teams included. Project visibility and collaborators decide who else can open that data.
What it costs
Token spend runs across Chat, Claude Code and Cowork. One organization total does not tell you which department is spending, or how close a spend limit is to running out.
Whether it breaks policy
SSO enforcement, admin counts, organization-wide projects and spend limits sit in Claude Enterprise settings, outside the policies you already run on Microsoft 365.
What Rencore sees and does in Claude Enterprise
Claude Enterprise users, joined to Microsoft 365
Every Claude Enterprise user who matches a Microsoft 365 user is related to their Entra ID identity. Usage, risk and cost then read by department, next to everything else Rencore holds about the same people.
- Users with stable IDs, groups (SCIM or direct) and RBAC roles
- Department, country and the external flag from Entra ID
- Claude Code and Cowork sessions per user, plus remote sessions, including the ones agents own, and skill, plugin and connector usage
- Users disabled in Entra ID who still hold Claude Enterprise access
Token spend by department, before the limit runs out
Token spend runs across Chat, Claude Code and Cowork, and one organization total does not tell you which department is spending. Rencore attributes it per user, so the finance team sees it by department.
- Token and cost attribution per user across Chat, Claude Code and Cowork
- Adoption and seat metrics
- The spend limits set on the organization
- A policy for a spend limit more than 80% consumed, or no spend limit configured at all
Policies over projects, and cleanup with an approval
Chats and projects are objects with owner, timestamps, counts, project visibility and collaborators, next to the 46 effective organization settings and an activity feed of 464+ event types. Policies run over them as they run over Microsoft 365.
- Too many or too few Claude Enterprise admins, and SSO not enforced
- Projects visible to the whole organization
- Projects not updated in 90 days
- One automation action: delete a Claude Enterprise project, with or without an approval step. Provisioning and access reviews are not part of the preview
Where the preview stops
What Rencore reads in Claude Enterprise, and what stays out of scope.
Metadata only
Rencore never reads, stores or displays message bodies, session transcripts or file content.
Claude Enterprise only
The connection runs through Anthropic's Compliance API. The Claude Team plan is not supported.
No Claude Console
The developer platform, with its workspaces and API keys, is out of scope.
No runtime inspection
Rencore does not sit in the path of prompts and does not block them as they are sent.
Part of Govern AI Assistants
One Microsoft Entra ID identity joins all three assistants, so seats, spend and access read by department.
- Overview
Govern AI Assistants
What each assistant can reach, side by side, with seats and spend across all three.
See all assistants - Available today
Microsoft 365 Copilot
The deepest coverage: reach, labels, permissions and license cost.
See Govern Copilot - Preview
Claude Enterprise
Users joined to Entra ID, projects and token spend by department.
You are here - Coming soon
ChatGPT Enterprise
Custom GPTs, projects and connectors, and who each is shared with. Preview from October 15, 2026.
See ChatGPT Enterprise
Claude Enterprise questions, answered
Which Claude plan do we need?
A Claude Enterprise organization. The connection runs through Anthropic's Compliance API, and the preview supports Claude Enterprise organizations only. The Claude Team plan is not supported, and the Claude Console, Anthropic's developer platform with its workspaces and API keys, is out of scope.
Does Rencore read our Claude Enterprise conversations?
No. Rencore reads metadata only, and never reads, stores or displays message bodies, session transcripts or file content. What it holds is the record around them: who owns a chat or project, when it was created and updated, how many items it holds, who it is shared with, and the activity events that show who did what and when.
How are Claude Enterprise users mapped to Entra ID?
Every Claude Enterprise user who matches a Microsoft 365 user is related to their Entra ID identity, with department, country and the external flag. From then on, usage, risk and cost read by department and country, and a policy can list the users who are disabled in Entra ID but still hold Claude Enterprise access.
What happens if we are on the Claude Team plan?
The Team plan cannot be connected. The preview connects through Anthropic's Compliance API for Claude Enterprise organizations, and a Team workspace has no such connection. Once your organization runs on Claude Enterprise, the inventory, identity join and policies on this page apply to it.
Does Microsoft Purview already cover Claude Enterprise?
Only in part. Purview covers Claude on pay-as-you-go billing, which is not included in Microsoft 365 E5, and it gives you no single governance model across Claude Enterprise and Microsoft 365. Rencore complements Purview and Entra ID, which keep their roles, with Entra ID staying your identity source: it adds the Claude Enterprise object inventory, the join to Entra ID and the policies and actions that run over both.
How is Claude Enterprise coverage licensed?
It is included in the AI & Agents module, the optional paid module on the Premium and Enterprise plans, alongside the Microsoft Copilot and agent coverage. There is no separate add-on for Claude Enterprise. The pricing page has the full plan comparison.