{"meta":{"title":"GitHub Copilot with data residency","intro":"Keep AI-powered coding assistance within your designated region, so you can meet compliance requirements while improving developer productivity.","product":"Enterprise administrators","breadcrumbs":[{"href":"/en/enterprise-cloud@latest/admin","title":"Enterprise administrators"},{"href":"/en/enterprise-cloud@latest/admin/data-residency","title":"Data residency"},{"href":"/en/enterprise-cloud@latest/admin/data-residency/github-copilot-with-data-residency","title":"GitHub Copilot"}],"documentType":"article"},"body":"# GitHub Copilot with data residency\n\nKeep AI-powered coding assistance within your designated region, so you can meet compliance requirements while improving developer productivity.\n\nIf your enterprise uses GitHub Enterprise Cloud with data residency, you can enable a policy to ensure that all inference processing and associated data for GitHub Copilot remain **within your designated geographic region**.\n\n## Supported regions\n\nCopilot with data residency is currently available in the following regions:\n\n* United States\n* European Union\n\nGitHub plans to add support for more regions in the near future.\n\n## How restrictions are enforced\n\nWhen you enforce data residency for Copilot, GitHub routes all Copilot requests to model endpoints within your enterprise's designated region. Your code, prompts, and Copilot responses never leave your region during inference processing.\n\nThe enforcement happens at multiple levels:\n\n* **Authentication and routing**: Users' authentication tokens only grant access to your region-specific endpoints, ensuring that traffic never leaves the designated geography.\n* **Model availability**: Copilot will only surface models that are certified and available in your region. Developers cannot access models hosted outside your region.\n* **Logs and telemetry**: All Copilot-related logs and telemetry are stored within region-appropriate, compliant storage.\n\n## Client version requirements\n\nTo use Copilot with model enforcement, developers must use compatible client versions. Generally, any Copilot extension or CLI version released in 2025 or later includes the necessary policy enforcement capabilities.\n\nIf a user attempts to use Copilot with an older, incompatible client, they will be prompted to update their extension or CLI to continue.\n\n## Supported Copilot features\n\nAll generally available Copilot features work with this enforcement. See [GitHub Copilot features](/en/enterprise-cloud@latest/copilot/get-started/features).\n\nPreview features that reach general availability will be supported with compliant model alternatives at the time of their GA release.\n\n## Available AI models by region\n\nThe models available for Copilot vary by region. Users will be able to see available models for your region in the model selector in their Copilot interface.\n\n> \\[!NOTE]\n> Model availability changes over time. New models released on GitHub.com may take additional time to become available as providers deploy regional infrastructure and obtain necessary certifications.\n\n### United States\n\n<!-- Note: US data resident and FedRAMP compliant models are currently the same, but this may not always be the case. However, we should be able to add new models after this reusable reference in the relevant article -->\n\n* GPT-4o mini\n* GPT-4o\n* GPT-4.1\n* GPT-5.2\n* GPT-5.2-Codex\n* GPT-5.3-Codex\n* Claude Haiku 4.5\n* Claude Sonnet 4\n* Claude Sonnet 4.5\n* Claude Opus 4.5\n* Claude Sonnet 4.6\n* Claude Opus 4.6\n\n### European Union\n\n* GPT-4o mini\n* GPT-4.1\n* GPT-5 mini\n* GPT-5.2\n* GPT-5.4\n* Claude Haiku 4.5\n* Claude Sonnet 4\n* Claude Sonnet 4.5\n* Claude Opus 4.5\n* Claude Sonnet 4.6\n* Claude Opus 4.6\n\n## Pricing changes\n\nCopilot requests processed with this enforcement in place include a 10% model multiplier increase. This reflects the additional infrastructure costs that model providers charge for regional and compliance-certified endpoints.\n\nFor example, if a model normally counts as 1 premium request, the same model processed with this enforcement enabled counts as 1.1 premium requests. This pricing applies to all compliant model requests across all providers.\n\nSee [Requests in GitHub Copilot](/en/enterprise-cloud@latest/copilot/concepts/billing/copilot-requests#model-multipliers).\n\n## Policy controls\n\nTo enable this policy, use the **Restrict Copilot to data residency compliant models** policy in the \"Features\" section of your enterprise's Copilot policies. This policy is disabled by default, and enabling it will affect your pricing for Copilot requests.\n\nFor instructions on finding your policies page, see [Managing policies and features for GitHub Copilot in your enterprise](/en/enterprise-cloud@latest/copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies)."}