Claude Team vs Claude Enterprise: When Should a Microsoft Shop Upgrade?

A growing Microsoft shop on Claude Team eventually hits a point where someone asks if it is time for Claude Enterprise. Usually a department is nearing the seat cap, IT wants automatic Entra ID offboarding across your M365 tenant, or a client security questionnaire just landed on your desk.

Stay on Claude Team if your company has under 150 seats and no one requires automatic Entra ID directory offboarding, audit logs or a HIPAA business associate agreement (BAA). Move to Claude Enterprise when you cross 150 users, need every department unified under one governance roof, or hit a compliance requirement Team cannot meet. Expect the bill to change shape: the base seat stays $20 per month on an annual plan (matching a Team Standard seat), but Enterprise removes included usage allowances and bills every prompt at API rates.

This guide compares the two plans for owner-led and mid-market companies running on Microsoft 365. If you are still choosing between Microsoft and Anthropic, read our Microsoft 365 Copilot vs Claude Enterprise comparison. If you just bought Team, start with our first-week Claude Team setup checklist.

Claude Team vs Enterprise at a glance

Prices and plan rules below were checked on November 2, 2026, from Claude's pricing page. Annual figures are paid yearly in US dollars.

The Lilac upgrade check: five triggers that mean you've outgrown Team

In our work with companies running on Microsoft 365, three forces push a business off Team: headcount, wanting every department unified under one governance umbrella, and compliance requirements. Run through these five triggers to see where your company sits. If none apply, stay on Team.

1. You will pass 150 seats, or you are splitting departments into multiple Team orgs. Each Team organization stops at 150 seats. You can run multiple Team organizations for separate departments, and in our experience that can cost less than Enterprise if you don't need unified governance. The tradeoffs are real: every Team org has separate billing, projects and custom skills cannot cross org boundaries, new sign-ups see multiple discoverable orgs on your domain, and you still cannot get SCIM on Team.
2. IT requires automatic offboarding through Microsoft Entra ID. Both plans include Entra ID single sign-on, which handles login. Only Enterprise includes SCIM, which automatically creates and deactivates Claude accounts when IT adds or removes someone in an Entra group.
3. A client contract, auditor or insurer requires audit logs, custom retention or HIPAA. Audit logs, the Compliance API, custom data retention, customer-managed encryption keys, US-only inference and IP allowlisting are all Enterprise-only. For the Claude apps, HIPAA readiness and a click-through BAA are also exclusive to Enterprise, though Anthropic offers a separate API BAA in the Claude Console with feature exclusions.
4. Staff opened personal Claude accounts on work emails and connected company tools. Personal Free, Pro, Max and Ultra accounts run under Anthropic's Consumer Terms, where your company has no admin control, offboarding or audit trail. Moving everyone into a managed company workspace closes that gap.
5. Your heavy users keep hitting limits, or you need group-level spend controls. On Team, your only levers are upgrading individuals to $100 Premium seats or buying extra usage credits. Enterprise removes seat tiers and gives you group budgets, per-user spend caps, and org-wide model and effort defaults.

What Standard vs Premium seats look like vs Enterprise metered billing

On Claude Team, you mix $20 Standard seats and $100 Premium seats on an annual bill. In our rollouts, 80% to 90% of staff stay well within their Standard seat limits, and a smaller group needs Premium. That split is normal, just like any other software tool in your suite: not everyone uses it the same amount, and the people who do heavier work should get the larger seat.

At 20, 50 and 150 seats on annual billing, an all-Standard Team plan costs $400, $1,000 and $3,000 a month. Moving 15% of a 50-person team (8 people) to Premium adds $640 a month, bringing the predictable monthly bill to $1,640. Team also includes Fable on Premium seats for up to half of the weekly limit, while Standard seats need optional usage credits turned on to use Fable.

Anthropic's Enterprise plan drops the Standard and Premium split completely. Every seat costs $20 a month billed annually ($400 at 20 seats, $1,000 at 50 seats, $3,000 at 150 seats), and every prompt in Chat, Claude Code and Cowork bills on top at API rates. Enterprise only beats Team on price when metered API usage for your heavy users runs less than the extra $80 per month you would have paid for their Premium seats.

How we budget Claude Enterprise: tasks, shared skills and a 5-step formula

Because Enterprise bills per token, handing out open-ended access makes the monthly invoice hard to predict. We keep usage predictable by mapping tasks granularly before launch and unifying repeated department work into shared skills and routines. When a sales team uses one agreed proposal-quote skill instead of ten people writing their own long prompts, token spend drops and output quality evens out.

Staff also need to know which surface to open. We train teams on when to use a quick chat, when to run a saved skill, and when to open Claude Code or Cowork, which consume far more tokens than standard chat. Admins can reinforce this on Enterprise by setting the organization's default model, capping reasoning effort, and rolling out Claude Code and Cowork in waves.

When we build an Enterprise budget with a client, we set a cap up front, run a pilot, check the return, and raise limits one step at a time:

1. Set a fixed-dollar pilot cap. Put a small pilot group into its own group limit with a fixed dollar ceiling so you can measure real work without risking an open tab.
2. Measure cost per task. Check the Enterprise Analytics Skills view to see the average cost per run for each skill, then multiply expected monthly runs by that cost per run.
3. Build the department budget from the distribution. Add the department's task budgets to its baseline ad-hoc chat spend, and set your buffer using the gap between the pilot's median user and 90th-percentile user rather than a flat percentage.
4. Set tier caps near the pilot 90th percentile. Group staff into light, standard and power tiers, set group and per-user caps near each tier's 90th percentile from the pilot, and watch the automated alerts at 75% and 90%.
5. Review and ladder the raises. Review spend weekly during the pilot and monthly after launch. Raise a group's cap one step only when its time-at-limit metric is climbing and its skill ROI, calculated as (value per run minus cost per use) times total uses, is positive.

For software teams budgeting Claude Code specifically, Anthropic publishes one benchmark: developer usage averages about $13 per active day ($150 to $250 per month), with 90% of users staying under $30 per active day. Anthropic does not publish equivalent averages for general chat or Cowork, which is why the pilot step matters.

What IT and MSPs ask first: SSO, SCIM and Microsoft 365 connector scopes

When an IT lead or managed service provider (MSP) reviews a Claude rollout, they ask about identity and access before anything else. You do not need Enterprise just to put Claude behind Microsoft sign-in: Microsoft Entra ID SSO works on both Team and Enterprise. You can link multiple orgs to one parent org to share a single identity provider, though SCIM still requires an Enterprise plan and Entra ID P1 or P2.

Connectors need admin scoping in both Claude and Entra. On both Team and Enterprise, an Owner must enable the Microsoft 365 connector, and an Entra Global Admin must grant tenant-wide consent. Decide early who holds the Claude Primary Owner role and who holds Entra Global Admin, because only the Primary Owner can accept the Enterprise HIPAA BAA and only an Entra Global Admin can approve the Microsoft 365 connector.

By default, the Microsoft 365 connector is read-only. If you enable write tools, note that Microsoft Graph's Files.ReadWrite.All and Calendars.ReadWrite permissions include delete as well as create and update. To allow writes while preventing deletions, leave the Graph permission in place and set the individual delete tools to Blocked inside Claude's per-tool connector policy (which offers Always allow, Needs approval and Blocked).

Two Microsoft 365 tenant rules apply to both plans. First, connector token exchanges come from Anthropic's IP range (160.79.104.0/21), so location or sign-in-frequency Conditional Access policies will block the connector unless you exclude that range as a named location (never exclude it from device-compliance policies). Second, the connector uses each person's existing Microsoft 365 permissions and searches SharePoint across the whole tenant, so run our Copilot readiness checklist for SharePoint oversharing before turning it on.

Personal Claude accounts on work email: the Microsoft 365 blind spot

Before a rollout, we occasionally find staff using personal Pro or Max accounts registered with their company email address. Personal plans sit under Anthropic's Consumer Terms, while Team and Enterprise run under Commercial Terms with Anthropic's data processing terms and a standard 30-day retention window. On personal accounts, Anthropic can use chats to train its models unless the user turns off "Help improve our AI models" under Settings > Privacy, and opting out is not retroactive for training runs already underway.

If anyone on your team signed up for a personal account with a work email, have them check that "Help improve our AI models" is off right away, then use our guide to move personal Claude accounts to a Team plan. On Team, you can pull people in with invites or org discovery and turn on "Restrict organization creation" once your domain is verified.

There is a bigger catch for any Microsoft shop. Once an Entra Global Admin grants tenant-wide consent for the Microsoft 365 connector, that connector works on all Claude plans in your tenant, including personal Pro and Max accounts. Unless your admin sets "Assignment required = Yes" on both M365 MCP apps in Entra ID and assigns only your approved group, an employee's personal Pro account signed in with work credentials can read company SharePoint, OneDrive and Outlook data.

How the Team-to-Enterprise upgrade works (and the one-way door)

When you are ready to move, a Primary Owner can upgrade an existing Team organization at claude.ai/upgrade by selecting Get Enterprise plan and then Upgrade an existing organization. Follow Anthropic's Team-to-Enterprise migration guide so nothing breaks during the cutover. Existing chats, projects, memberships and roles carry over in place.

Treat the self-serve upgrade as a one-way door: once a Team org converts to self-serve Enterprise, the upgrade cannot be undone. Before you click upgrade, check your organization spend limit and raise it above your current Team spend. If the existing spend limit is lower than what the org has already used, every user is locked out the moment the upgrade completes.

Finally, review your feature toggles right after cutover. Several capabilities that default to On under Team default to Off on Enterprise, though your existing data is preserved once you turn them back on. Self-serve upgrades pay the initial invoice by credit card and can switch to ACH afterward.

If your company is weighing whether to stay on Team, split departments across workspaces, or move to Claude Enterprise, our AI implementation team can run the seat math, configure your Entra ID and connector policies, and set up your pilot budgets alongside your IT provider.