Skip to main content
Print

Fix: Claude MCP Server or Connector Blocked by Microsoft 365 Conditional Access Policy

A user connects Claude to Microsoft 365 (the Outlook, SharePoint, OneDrive, or Teams connector) or to a custom MCP server protected by Entra ID, the Microsoft sign-in page appears, and instead of returning to Claude they see AADSTS53003: Access has been blocked by Conditional Access policies. The access policy does not allow token issuance. Variants include AADSTS53000: Device is not in required device state, AADSTS50105 (user not assigned), AADSTS65001 with a Need admin approval prompt, or AADSTS7000112: Application is disabled.

A subtler version: the connector works for an hour, then disconnects. This affects Claude Team and Enterprise customers whose tenant uses Entra ID (formerly Azure AD) Conditional Access, which today means nearly every business on Microsoft 365.

Why This Happens

Claude is an OAuth client asking Entra ID for Microsoft Graph tokens. The user signs in through the browser and consents to delegated Graph permissions (reading mail, files, sites, chats); Entra ID issues an access token and a refresh token to Anthropic’s connector service, which calls Graph on the user’s behalf and later redeems the refresh token without the user present. A custom remote MCP server using Entra ID works the same way, with your API as the resource.

Conditional Access evaluates each token request, including refreshes, against the user, the target resource (Microsoft Graph sits inside the app group the policy picker still labels Office 365), client app type, device state claims, and source IP address. Any of those can fail while the same user opens Outlook on the web without trouble.

Device compliance policies

A policy requiring a compliant or hybrid joined device passes only when the browser performing the sign-in presents device claims. A personal laptop, or a browser on a managed device without the Microsoft SSO components, produces AADSTS53000 or AADSTS53003.

Location and session policies

Location policies evaluate the IP address Entra ID sees. The interactive sign-in comes from the office and passes; the later refresh comes from Anthropic’s infrastructure, fails, and the connector drops. A one-hour or “every time” sign-in frequency has the same effect, because a background service cannot reauthenticate.

Consent, assignment, and app governance

With user consent restricted (the recommended state), users hit “Need admin approval” until an admin grants tenant-wide consent. Assignment required gives unassigned users AADSTS50105. An OAuth app disabled by Defender for Cloud Apps app governance or an admin gives everyone AADSTS7000112.

How to Fix It

Method 1: Read the sign-in log first

  1. In the Microsoft Entra admin center open Entra ID > Monitoring & health > Sign-in logs, both the interactive and non-interactive views.
  2. Filter Application to the Claude application and note Failure reason, IP address, and Client app.
  3. Open the event: the Conditional Access tab lists each policy as Success, Failure, or Not applied with the failed grant control; Device info shows whether compliance claims were present.

Method 2: Grant admin consent and assignment

  1. In Entra ID > Enterprise applications, open the Claude application and choose Permissions > Grant admin consent after reviewing the scopes.
  2. Under Properties, confirm Enabled for users to sign in is Yes. If Assignment required is Yes, add a security group of approved users under Users and groups.
  3. If a policy disabled the app, find it under Defender XDR > Cloud apps > App governance and add an exception.

Method 3: Fix device-based failures

  1. Confirm the device is compliant in Intune. On Windows, sign in to Edge with the work account or force-install the Microsoft Single Sign On extension in Chrome via policy. The Claude desktop app uses the default browser for OAuth, so that browser must carry device claims. On macOS, deploy the Enterprise SSO plug-in through Intune.
  2. Allowing Claude from unmanaged devices is a policy decision: exclude a specific group from the compliant-device policy and cover it with MFA plus sign-in risk controls.

Method 4: Fix location and session disconnects

  1. Confirm in the non-interactive log that the failing refresh came from an IP outside your named locations.
  2. Replace the IP block for the affected group with identity-based controls: MFA, compliant device, and block on high sign-in risk. Do not add Anthropic’s egress ranges as trusted locations unless Anthropic publishes them for that purpose; a trusted range relaxes MFA for everything from it.
  3. Scope short Sign-in frequency settings to privileged roles and unmanaged devices.

Method 5: Custom MCP servers using Entra ID

  1. Register the MCP server’s API in Entra ID and expose a scope. Register Claude as a client using Anthropic’s documented redirect URI for remote MCP connectors (currently https://claude.ai/api/mcp/auth_callback).
  2. Entra ID lacks dynamic client registration, so enter the client ID and secret under Advanced settings when adding the custom connector in Claude.
  3. Your API is now its own Conditional Access resource; give it a dedicated policy.

Then reconnect on the Claude side. A Claude owner confirms the connector is enabled under admin Settings > Connectors, and the user disconnects and reconnects Microsoft 365 from a compliant device, because policy changes do not repair refresh tokens that already failed.

How to Verify the Fix Worked

  • The interactive sign-in for the Claude application shows Success with every policy in Success state.
  • A day later, the non-interactive log shows successful token refreshes.
  • In Claude, “Summarize my unread email from today” returns results, and the connector is still connected the next day.

If It Still Isn’t Working

Collect the Request ID and Correlation ID from the failed event; Anthropic and Microsoft support need them. Check Anthropic’s status page too.

Look beyond Conditional Access. Cross-tenant access settings block guests from consenting. Tenant restrictions v2 and Global Secure Access can block token requests at the network layer without a sign-in log entry. Continuous access evaluation can revoke a token after a risk event; check Identity Protection > Risky sign-ins.

Escalate when the log shows Success but Claude still errors, when the failing policy needs a security review to change, or when CMMC or HIPAA obligations govern which SaaS tools may hold Graph tokens.

How Capital Techies Handles This for Managed Clients

For managed clients we design Conditional Access with AI connectors in mind: compliant-device requirements enforced through Intune, identity and risk-based controls instead of brittle IP blocks, an admin consent workflow, and Defender for Cloud Apps app governance policies that alert on new OAuth grants rather than silently breaking them. Claude enterprise apps are consented once, scoped to a security group, and recorded in the compliance inventory.

Staff get Claude with Microsoft 365 data without weakening the controls insurers, HIPAA, and CMMC assessors expect. Contact Capital Techies about securing AI tools in Microsoft 365.

Frequently Asked Questions

Can I exempt just the Claude connector from my Conditional Access policies?

Not directly. Conditional Access targets the resource being accessed (Microsoft Graph), not the third-party client asking for it. You control the outcome through who is in scope, the device state you require, and whether you rely on IP location.

Why does the connector work for an hour and then say it is disconnected?

The first sign-in succeeded in the browser, but a later token refresh from Anthropic’s servers failed a policy, usually a trusted-location requirement or a short sign-in frequency. The non-interactive sign-in log shows the failure.

Is connecting Claude to Microsoft 365 safe from a compliance standpoint?

Yes, when the Claude organization is on a Team or Enterprise plan that does not train on your data, admin consent has been reviewed, Purview labels and DLP remain in force on the files, and access is limited to compliant devices. Record the connector in your HIPAA or CMMC system inventory.

Related Articles

Table of Contents