Editor’s note (April 24, 2026): Updated this post to include more detailed and specific information about these offerings. We also added links for reference. These changes were made in an effort to add some clarity about what has changed.

GitHub Copilot now supports data residency for US and EU regions, ensuring all inference processing and associated data stay within your designated geography. EU aligns with Microsoft’s EU Data Boundary, which covers EU member states plus EFTA countries (i.e., Iceland, Liechtenstein, Norway, and Switzerland) as of May 1, 2026. For US government customers, the underlying model hosts and infrastructure are FedRAMP Moderate authorized. Copilot itself will become FedRAMP authorized as part of GHEC-DR’s authorization path.

What’s included

All generally available Copilot features are supported: agent mode, inline suggestions, chat, Copilot cloud agent, code review, pull request summaries, and Copilot CLI. Every feature routes exclusively through data-resident model endpoints, and for US government customers, through FedRAMP Moderate–authorized model infrastructure within your designated region.

Model availability

A broad set of models is available at launch across both OpenAI and Anthropic, including GPT-5.4, Claude Sonnet 4.6, Claude Opus 4.6, and more. The full model-by-region matrix is available in our documentation for data residency and our FedRAMP docs. Gemini models are not yet supported, as GCP does not currently offer data-resident inference endpoints. We’ll bring them in once they become available. Recently released models may take additional time to appear in data-resident regions.

Pricing

Data-resident and FedRAMP requests carry a 10% increase in the model multiplier, reflecting provider costs for regional and compliance-certified endpoints. For example, a model that normally costs 1 premium request will cost 1.1 premium requests under data residency.

Getting started

Enterprise and organization admins can enable data residency and FedRAMP policies from their Copilot settings, to restrict their enterprise or organization to models that are data-resident or FedRAMP compliant. The policies are off by default, so admins will need to explicitly opt-in to the model restrictions and understand the pricing implications.

US and the EU Data Boundary (i.e., EU + EFTA) are supported for this launch. Additional Proxima regions (e.g., Japan and Australia) are on the roadmap for later in 2026.