copilot

Copilot Data Residency & FedRAMP Compliance Now Live

Copilot now keeps your data in the US or EU with FedRAMP compliance for government. 10% cost bump, but admins control the opt-in.

TL;DR

Copilot now supports US and EU data residency — all inference stays in your region
FedRAMP Moderate certification available for US government customers
10% cost increase for data-resident and FedRAMP-compliant requests
Admins must explicitly opt-in; policies are off by default

Data residency for US and EU — All inference processing and associated data remain within your designated geography, no cross-border transfers.
FedRAMP Moderate authorization — US government customers get model hosts and infrastructure certified to FedRAMP standards.
Full feature parity — Agent mode, inline suggestions, chat, Copilot cloud agent, code review, pull request summaries, and Copilot CLI all work with data-resident endpoints.
Broad model support — GPT-5.4, Claude Sonnet 4.6, Claude Opus 4.6, and more available across regions. Gemini models not yet supported pending GCP data-resident endpoints.

Data-resident and FedRAMP requests incur a 10% increase in the model multiplier — a model costing 1 premium request normally costs 1.1 under data residency.

Enterprise and organization admins enable data residency and FedRAMP policies from Copilot settings. Policies are off by default — you must explicitly opt-in.
US and EU regions supported at launch. Japan and Australia roadmapped for later 2026.

Update via GitHub Enterprise Cloud admin console or organization settings. See data residency docs and FedRAMP docs for full model-by-region matrix.