SpyBara
Go Premium

third-party-integrations.md 2026-08-06 15:02 UTC to 2026-08-07 23:57 UTC

26 added, 24 removed.

2026
Thu 20 20:58 Wed 19 17:02 Tue 18 23:59 Mon 17 22:57 Sun 16 14:59 Sat 15 16:00 Fri 14 23:00 Thu 13 23:57 Wed 12 23:59 Tue 11 22:03 Mon 10 22:57 Sun 9 04:02 Sat 8 04:59 Fri 7 23:57 Thu 6 15:02 Wed 5 22:02 Tue 4 22:59 Mon 3 20:02 Sun 2 19:00

Enterprise deployment overview

Learn how Claude Code can integrate with various third-party services and infrastructure to meet enterprise deployment requirements.

export const ContactSalesCard = ({surface}) => { const utm = content => utm_source=claude_code&utm_medium=docs&utm_content=${surface}_${content}; const iconArrowRight = (size = 13) => <svg width={size} height={size} viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2.5" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true"> ; const STYLES = .cc-cs { --cs-slate: #141413; --cs-clay: #d97757; --cs-clay-deep: #c6613f; --cs-gray-000: #ffffff; --cs-gray-700: #3d3d3a; --cs-border-default: rgba(31, 30, 29, 0.15); font-family: inherit; } .dark .cc-cs { --cs-slate: #f0eee6; --cs-gray-000: #262624; --cs-gray-700: #bfbdb4; --cs-border-default: rgba(240, 238, 230, 0.14); } .cc-cs-card { display: flex; align-items: center; justify-content: space-between; gap: 16px; padding: 14px 16px; margin: 0; background: var(--cs-gray-000); border: 0.5px solid var(--cs-border-default); border-radius: 8px; flex-wrap: wrap; } .cc-cs-text { font-size: 13px; color: var(--cs-gray-700); line-height: 1.5; flex: 1; min-width: 240px; } .cc-cs-text strong { font-weight: 550; color: var(--cs-slate); } .cc-cs-actions { display: flex; align-items: center; gap: 8px; flex-shrink: 0; } .cc-cs-btn-clay { display: inline-flex; align-items: center; gap: 8px; background: var(--cs-clay-deep); color: #fff; border: none; border-radius: 8px; padding: 8px 14px; font-size: 13px; font-weight: 500; transition: background-color 0.15s; white-space: nowrap; } .cc-cs-btn-clay:hover { background: var(--cs-clay); } .cc-cs-btn-ghost { display: inline-flex; align-items: center; gap: 8px; background: transparent; color: var(--cs-gray-700); border: 0.5px solid var(--cs-border-default); border-radius: 8px; padding: 8px 14px; font-size: 13px; font-weight: 500; } .cc-cs-btn-ghost:hover { background: rgba(0, 0, 0, 0.04); } .dark .cc-cs-btn-ghost:hover { background: rgba(255, 255, 255, 0.04); } @media (max-width: 720px) { .cc-cs-actions { width: 100%; } }; return <div className="cc-cs not-prose"> <div className="cc-cs-card"> <div className="cc-cs-text"> Deploying Claude Code across your organization? Talk to sales about enterprise plans, SSO, and centralized billing.

<div className="cc-cs-actions"> <a href={https://claude.com/pricing?${utm('view_plans')}#plans-business} className="cc-cs-btn-ghost"> View plans <a href={https://claude.com/contact-sales?${utm('contact_sales')}} className="cc-cs-btn-clay"> Contact sales {iconArrowRight()}
; };

Organizations can deploy Claude Code through Anthropic directly or through a cloud provider. This page helps you choose the right configuration.

Compare deployment options

For most organizations, Claude for Teams or Claude for Enterprise provides the best experience. Team members get access to both Claude Code and Claude on the web with a single subscription, centralized billing, and no infrastructure setup required.

Claude for Teams is self-service and includes collaboration features, admin tools, and billing management. Best for smaller teams that need to get started quickly.

Claude for Enterprise adds SSO and domain capture, role-based permissions, compliance API access, and managed policy settings for deploying organization-wide Claude Code configurations. Best for larger organizations with security and compliance requirements.

Learn more about Team plans and Enterprise plans.

The deployment options compared below cover where model inference runs. To run Claude Code on the web sessions on compute your organization operates, see self-hosted environments.

If your organization has specific infrastructure requirements, compare the options below:

<tr>
  <td>Billing</td>
  <td><strong>Teams:</strong> \$150/seat (Premium) with PAYG available<br /><strong>Enterprise:</strong> <a href="https://claude.com/contact-sales?utm_source=claude_code&utm_medium=docs&utm_content=third_party_enterprise">Contact Sales</a></td>
  <td>PAYG</td>
  <td>PAYG through AWS</td>
  <td>PAYG through AWS Marketplace</td>
  <td>PAYG through GCP</td>
  <td>PAYG through Azure</td>
</tr>

<tr>
  <td>Regions</td>
  <td>Supported [countries](https://www.anthropic.com/supported-countries)</td>
  <td>Supported [countries](https://www.anthropic.com/supported-countries)</td>
  <td>Multiple AWS [regions](https://docs.aws.amazon.com/bedrock/latest/userguide/models-regions.html)</td>
  <td>Multiple AWS regions</td>
  <td>Multiple GCP [regions](https://cloud.google.com/vertex-ai/generative-ai/docs/learn/locations)</td>
  <td>Multiple Azure [regions](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/)</td>
</tr>

<tr>
  <td>Prompt caching</td>
  <td>Enabled by default</td>
  <td>Enabled by default</td>
  <td>Enabled by default</td>
  <td>Enabled by default</td>
  <td>Enabled by default</td>
  <td>Enabled by default</td>
</tr>

<tr>
  <td>Authentication</td>
  <td>Claude.ai SSO or email</td>
  <td>API key</td>
  <td>API key or AWS credentials</td>
  <td>API key or AWS credentials</td>
  <td>GCP credentials</td>
  <td>API key or Microsoft Entra ID</td>
</tr>

<tr>
  <td>Cost tracking</td>
  <td>Usage dashboard</td>
  <td>Usage dashboard</td>
  <td>AWS Cost Explorer</td>
  <td>AWS Cost Explorer</td>
  <td>GCP Billing</td>
  <td>Azure Cost Management</td>
</tr>

<tr>
  <td>Includes Claude on web</td>
  <td>Yes</td>
  <td>No</td>
  <td>No</td>
  <td>No</td>
  <td>No</td>
  <td>No</td>
</tr>

<tr>
  <td>Enterprise features</td>
  <td>Team management, SSO, usage monitoring</td>
  <td>None</td>
  <td>IAM policies, CloudTrail</td>
  <td>IAM policies, CloudTrail</td>
  <td>IAM roles, Cloud Audit Logs</td>
  <td>RBAC policies, Azure Monitor</td>
</tr>
Feature Claude for Teams/Enterprise Anthropic Console Amazon Bedrock Claude Platform on AWS Google Cloud's Agent Platform, formerly Vertex AI Microsoft Foundry
Best for Most organizations (recommended) Individual developers AWS-native deployments AWS Marketplace billing with Claude API features GCP-native deployments Azure-native deployments

For a feature-by-feature breakdown of what's available on each option, see Feature availability.

Select a deployment option to view setup instructions:

For Amazon Bedrock and Google Vertex AI, you can also run claude and select 3rd-party platform at the login prompt to launch an interactive setup wizard.

Configure proxies and gateways

Most organizations can use a cloud provider directly without additional configuration. However, you may need to configure a corporate proxy or LLM gateway if your organization has specific network or management requirements. These are different configurations that can be used together:

The following examples show the environment variables to set in your shell or shell profile (.bashrc, .zshrc). See Settings for other configuration methods.

Amazon Bedrock

Route Amazon Bedrock traffic through your corporate proxy by setting the following environment variables:

# Enable Bedrock
export CLAUDE_CODE_USE_BEDROCK=1
export AWS_REGION=us-east-1

# Configure corporate proxy
export HTTPS_PROXY='https://proxy.example.com:8080'

Microsoft Foundry

Route Microsoft Foundry traffic through your corporate proxy by setting the following environment variables:

# Enable Microsoft Foundry
export CLAUDE_CODE_USE_FOUNDRY=1
export ANTHROPIC_FOUNDRY_RESOURCE=your-resource
export ANTHROPIC_FOUNDRY_API_KEY=your-api-key  # Or omit for Entra ID auth

# Configure corporate proxy
export HTTPS_PROXY='https://proxy.example.com:8080'

Google Cloud's Agent Platform

Route Google Cloud's Agent Platform traffic through your corporate proxy by setting the following environment variables:

# Enable Agent Platform
export CLAUDE_CODE_USE_VERTEX=1
export CLOUD_ML_REGION=us-east5
export ANTHROPIC_VERTEX_PROJECT_ID=your-project-id

# Configure corporate proxy
export HTTPS_PROXY='https://proxy.example.com:8080'

Best practices for organizations

Invest in documentation and memory

We strongly recommend investing in documentation so that Claude Code understands your codebase. Organizations can deploy CLAUDE.md files at multiple levels:

Learn more in Memory and CLAUDE.md files.

Simplify deployment

If you have a custom development environment, we find that creating a "one click" way to install Claude Code is key to growing adoption across an organization.

Start with guided usage

Encourage new users to try Claude Code for codebase Q&A, or on smaller bug fixes or feature requests. Ask Claude Code to make a plan. Check Claude's suggestions and give feedback if it's off-track. Over time, as users understand this new paradigm better, then they'll be more effective at letting Claude Code run more agentically.

Pin model versions for cloud providers

If you deploy through Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry, or Claude Platform on AWS, pin specific model versions using ANTHROPIC_DEFAULT_FABLE_MODEL, ANTHROPIC_DEFAULT_OPUS_MODEL, ANTHROPIC_DEFAULT_SONNET_MODEL, and ANTHROPIC_DEFAULT_HAIKU_MODEL. Without pinning, model aliases resolve to Claude Code's built-in default for that provider, which can lag the newest release and may not yet be enabled in your account. Pinning lets you control when your users move to a new model. See Model configuration for what each provider does when the default is unavailable.

Configure security policies

Security teams can configure managed permissions for what Claude Code is and is not allowed to do, which cannot be overwritten by local configuration. Learn more.

Leverage MCP for integrations

MCP is a great way to give Claude Code more information, such as connecting to ticket management systems or error logs. We recommend that one central team configures MCP servers and checks a .mcp.json configuration into the codebase so that all users benefit. Learn more.

At Anthropic, we trust Claude Code to power development across every Anthropic codebase. We hope you enjoy using Claude Code as much as we do.

Next steps

Once you've chosen a deployment option and configured access for your team:

  1. Roll out to your team: Share installation instructions and have team members install Claude Code and authenticate with their credentials.
  2. Set up shared configuration: Create a CLAUDE.md file in your repositories to help Claude Code understand your codebase and coding standards.
  3. Configure permissions: Review security settings to define what Claude Code can and cannot do in your environment.