Skip to main content
Print

How to Deploy Claude for Work Securely in a Microsoft 365 Environment (SSO, SCIM, Data Governance)

Someone in the office is paying for Claude on a personal card, three others use free accounts with their work email, and a partner just asked whether client data is “going into an AI.” You want the productivity gain without the shadow IT: single sign-on through Entra ID, automatic user provisioning, and clear controls over what Claude can reach.

This guide covers deploying Claude for Work (the Team and Enterprise plans) into a Microsoft 365 tenant with Entra ID (formerly Azure AD) as identity provider, SCIM provisioning, and Purview and Defender controls around it, for organizations with 10 to 500 staff.

Why This Happens

Unmanaged AI use grows because the tools are useful and free to start. A consumer Claude account takes a minute to create with a work email. Nothing in Microsoft 365 stops it by default, the pasted data sits outside your retention, eDiscovery, and DLP controls, and consumer plans carry different data terms than business plans.

Business plans change the data posture. Claude Team and Enterprise do not use your prompts or outputs to train models by default, offer organization-level administration, and on Enterprise expose audit logs and a compliance API. None of that helps until every employee is inside the managed organization, which is what SSO, SCIM, and domain capture accomplish.

Identity is the control plane. When Claude authenticates through Entra ID, Conditional Access applies, offboarding in Microsoft 365 removes Claude access the same hour, and sign-ins appear in your Entra logs. Without SSO, Claude is one more password and one more offboarding step to miss.

How to Fix It

Method 1: Choose the plan and set up the organization

  1. Pick Enterprise if you need SSO, SCIM, audit logs, or a HIPAA agreement; pick Team for a small group that needs seat management and no-training terms. Confirm the current feature list with Anthropic, since features have moved between plans.
  2. Create the organization with a role account such as it-admin@yourdomain.com as primary owner, and add a second owner.
  3. Verify your domain in the Claude admin console (a DNS TXT record) and enable domain capture so consumer accounts on your domain are claimed into the organization.

Method 2: Configure SAML single sign-on with Entra ID

  1. In the Entra admin center, go to Entra ID > Enterprise applications > New application. Search the gallery for Claude; if there is no entry, choose Create your own application (non-gallery).
  2. Open Single sign-on > SAML and, in Basic SAML Configuration, paste the Identifier (Entity ID) and Reply URL (ACS URL) from the Claude admin console’s identity settings.
  3. Under Attributes & Claims, set the NameID to user.mail in email address format and include given name and surname claims.
  4. Download the Base64 signing certificate and copy the Login URL and Entra Identifier into Claude’s SSO settings. Test with one account, then make SSO required.
  5. Create a Conditional Access policy targeting the Claude app: require MFA and a compliant device, block on high sign-in risk.

Method 3: Turn on SCIM provisioning

  1. Generate the SCIM URL and bearer token in the Claude admin console.
  2. In the Entra enterprise app, open Provisioning, set mode to Automatic, paste the Tenant URL and Secret Token, and click Test Connection.
  3. Under Users and groups, assign a security group such as SG-Claude-Users, and set Assignment required to Yes.
  4. Map groups to Claude roles where supported. Disabling a user in Entra now deprovisions the Claude seat on the next cycle (about 40 minutes).

Method 4: Set data governance inside Claude

  1. Align retention settings with your records policy and document the choice.
  2. Decide connector policy. Admins control which connectors and MCP servers members may add. Start with none, then enable Microsoft 365 connectors only for groups with a business case; a connector inherits every permission the user holds in SharePoint and Outlook.
  3. Assign roles deliberately: owners for IT, admins for team leads, members for everyone else. Point the audit log or compliance API at your SIEM or Purview.

Method 5: Wrap Microsoft 365 controls around it

  1. Purview DLP. Create an Endpoint DLP policy that audits or blocks pasting and uploading sensitive info types (SSNs, credit cards, health records, client identifiers) to a sensitive service domain group containing claude.ai. Deploy the Purview browser extension through Intune so Data Security Posture Management for AI can see prompts sent to third-party AI sites.
  2. Defender for Cloud Apps. Mark Claude as sanctioned and use app governance to alert on the Claude OAuth app’s Graph permissions.
  3. Endpoints and people. Deploy the Claude desktop app through Intune, allowlist the Claude in Chrome extension by ID in browser policies, publish a one-page acceptable use policy, assign KnowBe4 AI awareness training, and record Claude in your system inventory for HIPAA, CMMC, or cyber insurance questionnaires.

How to Verify the Fix Worked

  • A new hire added to SG-Claude-Users appears in Claude within an hour and signs in through Entra with MFA.
  • Disabling a test account in Entra removes its Claude access within an hour.
  • A consumer account on your domain is prompted to join the organization.
  • Pasting a test SSN into Claude triggers the Purview DLP audit event or block in Activity explorer.

If It Still Isn’t Working

SAML errors. AADSTS50105 means the user is not assigned to the app. A NameID mismatch (UPN versus mail) produces a Claude-side “user not found” error; fix the claim, not the user. The Test button on the Entra SSO page shows what was sent.

SCIM failures. Entra’s Provisioning logs show per-user errors, usually an expired token or a user with no mail attribute.

Connector blocks. If connectors fail with AADSTS53003, Conditional Access is blocking the Graph token request; see the related article.

Escalate when compliance scope is unclear (whether PHI or CUI may enter prompts is a legal question) or when Purview licensing (E5 or the compliance add-on) is missing. Decide those before rollout.

How Capital Techies Handles This for Managed Clients

For managed clients, AI tools get the same treatment as any line-of-business system: identity through Entra ID with Conditional Access, provisioning tied to the group model we already run, endpoint deployment through Intune, and Purview DLP tuned to the client’s real sensitive data, whether PHI in a dental practice, CUI at a government contractor, or donor records at a nonprofit. SentinelOne, Microsoft Defender, and KnowBe4 cover the endpoint and the person.

The outcome is a team using Claude on day one with offboarding control and an audit trail an insurer or assessor can read. Contact Capital Techies about Microsoft 365 and AI governance.

Frequently Asked Questions

What is the difference between Claude Team and Claude Enterprise?

Both exclude your data from model training by default and give admins seat and role management. Enterprise adds SAML or OIDC single sign-on, SCIM provisioning, domain capture, audit logs, a compliance API, and larger usage limits. Team is per seat; Enterprise is a contract.

Can we use Claude with patient or CUI data?

Only under the right agreement and configuration. Anthropic offers HIPAA-eligible configurations with a Business Associate Agreement on qualifying enterprise agreements, and CMMC scoping depends on where CUI flows. Get it in writing, restrict connectors, and keep Purview DLP in place before regulated data touches a prompt.

Do we still need Purview DLP if Claude does not train on our data?

Yes. Not training on data addresses one risk. DLP addresses another: a person pasting a client list or PHI into any AI tool, including personal accounts. Purview endpoint DLP and the browser extension cover that gap for every vendor.

Related Articles

Table of Contents