Anthropic Brings Enterprise IT Controls to Claude's Tool Connections

30-Second Summary

Anthropic launched Enterprise-Managed Authorisation for Claude's MCP connectors on 18 June 2026, removing the individual setup requirement that has limited enterprise AI adoption in practice. Under the new model, IT administrators provision tool access once through Okta and employees inherit that access automatically on first login, with no individual authentication required. The feature works across Claude chat, Claude Code, and Claude Cowork on Team and Enterprise plans, and launches with support for Asana, Atlassian, Canva, Figma, Granola, Linear, and Supabase, with Slack support following shortly.

At a Glance

• Topic: Agent Systems
• Company: Anthropic
• Date: 18 June 2026
• Announcement: Enterprise-Managed Authorisation (EMA) for MCP connectors in Claude, starting with Okta as the first supported identity provider
• What Changed: Employees no longer need to individually authenticate Claude to each business tool. IT admins provision access once and employees inherit it on login.
• Why It Matters: Removes the setup friction that has limited real-world Claude adoption inside teams, while giving IT security controls over AI tool access
• Who Should Care: Any business with a Claude Team or Enterprise subscription using Okta for identity management, and any IT administrator responsible for AI tool governance

Key Facts

• Company: Anthropic
• Launch Date: 18 June 2026 (beta)
• What Changed: Central IT provisioning of MCP connector access for entire organisations, with zero-touch employee authentication through Okta
• Who It Affects: Businesses on Claude Team and Claude Enterprise plans; Okta customers; administrators managing AI tool access policies
• Primary Source: Anthropic official blog (claude.com/blog/enterprise-managed-auth); Okta newsroom press release; TechTimes (19 June 2026)

What Happened

Anthropic launched Enterprise-Managed Authorisation (EMA) for Model Context Protocol (MCP) connectors in Claude on 18 June 2026. The update marks a meaningful shift in how businesses can manage Claude's access to external tools, moving from a model where each employee configured their own connections to one where IT controls access centrally.

Under the previous model, each employee who wanted to use Claude alongside tools like Asana, Atlassian, or Figma had to individually authenticate those connections through their own Claude account. For teams with dozens or hundreds of employees, this created a consistent adoption problem: low setup rates, inconsistent permission scopes across individuals, and no central visibility into which tools Claude was accessing or on whose behalf.

Enterprise-Managed Authorisation addresses this through integration with Okta, the enterprise identity platform. Administrators configure tool access once within Okta, scoped to the relevant team or role groups they manage. When an employee logs into Claude, their connector access is inherited automatically with no manual authentication required. When that employee leaves the organisation and is deprovisioned in Okta, their connector access revokes quickly rather than lingering on stale tokens.

At launch, the feature supports seven connectors: Asana, Atlassian, Canva, Figma, Granola, Linear, and Supabase. Slack support is listed as coming soon. The feature is available in beta for Team and Enterprise plan subscribers and works across Claude chat, Claude Code, and Claude Cowork. Anthropic also launched companion connector observability tooling, giving administrators a dashboard view of adoption, errors, latency, and usage across all active connectors.

Why It Matters

• The MCP standard has grown rapidly since its introduction in late 2024, reaching 97 million installs by early 2026. The number of tools Claude can connect to is large and still growing, which means central IT management of those connections is now a practical necessity rather than a convenience.
• For businesses deploying Claude across a team of 20 or more people, individual setup requirements have been the single biggest adoption barrier in practice. Removing this friction removes the primary reason most organisations have kept Claude siloed to a small group of power users.
• The Okta integration means AI tool access is now governed by the same identity and access management system most mid-size businesses already use to control access to Salesforce, Atlassian, and Google Workspace. Claude becomes part of the governed IT stack rather than a separate self-service tool.
• Connector observability gives IT administrators the usage data they need to justify or adjust AI tool investment. Shadow AI use remains high in most organisations; a central visibility layer helps identify where employees are working around approved tools.
• Fast deprovisioning through the identity provider reduces the security exposure of former employees retaining AI tool access, a risk that has grown as companies scale up AI use across more systems.
• Additional identity providers beyond Okta are expected in subsequent releases, which will extend this capability to businesses using Microsoft Entra, Google Workspace Identity, or other platforms.

The David and Goliath View

The adoption gap in enterprise AI is not a capability problem. It is a friction problem. Businesses that have invested in Claude subscriptions often see a handful of committed users extracting real value while the majority of the team never gets past the setup phase. That gap does not exist because Claude is hard to use once you are in. It exists because the path from "we have a licence" to "every relevant employee has Claude connected to the tools they actually use every day" has been longer than most IT teams can absorb alongside their other priorities.

Enterprise-Managed Authorisation changes that equation. For a business using Okta, the deployment work now happens once at the administrator level. The team wakes up with their tools already connected. They do not need to know what MCP is. They do not need to separately authenticate Asana or Figma. They open Claude and their working context is already there.

For businesses of 20 to 200 people, this is a practical inflection point. The question is no longer "can we get Claude to work with our tools" but "what should our team actually do with Claude now that it can access everything they work in." That is a considerably more interesting problem to be solving. Organisations that move through this setup barrier first will have a genuine head start over competitors who are still managing individual authentication tickets.

Where This Fits in the AI Stack

Secure AI Brain: Enterprise-Managed Authorisation extends governance to how AI tool access is granted, scoped, audited, and revoked. IT controls over MCP connectors, fast deprovisioning through the identity provider, and centralised token management are exactly the security controls that belong in a well-governed AI architecture.

Employee Amplification Systems: Removing individual setup friction is the single largest lever for increasing AI adoption rates inside a team. An employee who opens Claude and immediately has access to their Asana projects, Atlassian documentation, and Figma files is an employee who will actually use AI in their daily work rather than finding workarounds or not bothering at all.

Questions Operators Are Asking

What is Enterprise-Managed Authorisation and who does it affect? It is a feature for Claude Team and Enterprise customers that lets IT administrators configure MCP connector access organisation-wide through their identity provider, starting with Okta. Employees on Okta-managed accounts inherit connector access automatically when they log in, removing the need for individual setup. It launched in beta on 18 June 2026.

We already have Claude. Do our employees automatically get this? No. The feature is in beta and requires configuration by an IT administrator with access to your Okta environment. It is available to Team and Enterprise plan subscribers but does not activate automatically. Your IT team needs to enable it and configure the appropriate connector scopes for the relevant groups.

What tools are supported at launch? Asana, Atlassian, Canva, Figma, Granola, Linear, and Supabase are supported at launch. Slack support is listed as coming soon. Anthropic has indicated that additional connectors will be added to the directory over time.

We do not use Okta. Does this apply to us? Not immediately. Okta is the only identity provider supported at launch. Anthropic has indicated that additional providers are in progress. Businesses using Microsoft Entra, Google Workspace Identity, or other platforms should expect support in a later release.

What about deprovisioning? Can former employees still access tools through Claude? The feature is specifically designed to address this. When an employee is deprovisioned in Okta, their connector access expires quickly rather than persisting on stale tokens. Administrators can also reduce token lifetimes to tighten this window further. This is one of the most significant security improvements the update delivers.

Citable Summary

What happened: Anthropic launched Enterprise-Managed Authorisation for Claude's MCP connectors on 18 June 2026, allowing IT administrators to provision tool access organisation-wide through Okta with zero individual employee setup required.

Why it matters: Individual authentication requirements have been the primary barrier to enterprise-wide Claude adoption in practice. Centralised IT control, combined with fast deprovisioning through the identity provider, brings AI tool access into the same governance framework businesses use for the rest of their stack.

David and Goliath view: For businesses of 20 to 200 people, this is a practical inflection point. The question shifts from "can we get Claude working with our tools" to "what should our team actually do with Claude now that context is already there." Organisations that move through this barrier first will pull ahead of those still managing individual authentication.

Offer relevance:

• Secure AI Brain: IT-governed AI tool access, centralised deprovisioning, connector observability, and auditability across Claude products
• Employee Amplification Systems: zero-friction Claude deployment across the whole team drives significantly higher adoption rates and more consistent productivity gains