loading . . . Github Copilot now available with Data Residency in the EU With the current political climate there has quite a bit of buzz around Data Residency and Data Sovereignty. And the number of inquiries to migrate from GitHub Enterprise Cloud to the Data Resident version have gone up.
One of the gaps in GitHub with Data Residency, was that all Copilot data could still leave the region.
This is now a thing of the past:
Copilot data residency in US + EU and FedRAMP compliance now available - GitHub ChangelogGitHub 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…The GitHub BlogAllison
To make use of this new feature, you must already be using the Data Resident version of GitHub Enterprise Cloud (also known as `ghe.com` or by GitHub's internal codename Proxima).
To restrict Copilot to only use Data Resident models, a policy must be enabled at the Enterprise or Organization level:
Set ****Restrict Copilot to Data Residency Models**** to ****Enabled everywhere**** to ensure copilot data is processed in your Data Residency region.
Currently all **Generally available** copilot features are included according to GitHub, but new features may take a bit longer to be enabled on your GitHub environment, as they may not yet be available for Data Residency during preview phases.
This has been the case with other GitHub features as well, so this shouldn't come as a surprise. https://jessehouwing.net/github-copilot-now-with-data-residency-in-europe/
