GitHub Copilot now supports data residency for US and EU regions, ensuring all inference processing and associated data stay within your designated geography. For US government customers, all model hosts and infrastructure also meet FedRAMP Moderate authorization standards.

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 uses only data-resident, compliance-certified model endpoints 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 EU regions are supported for this launch. Additional Proxima regions (e.g., Japan and Australia) are on the roadmap for later in 2026.