GitHub’s EU data residency explained: who can use it, what stays in Europe, and what does not

Short answer: GitHub does let eligible customers store defined enterprise code and repository data in its EU data-residency region, but this is not a new rule for every GitHub account. The service is part of GitHub Enterprise Cloud with data residency, uses Enterprise Managed Users and a dedicated ghe.com environment, and requires a planned migration. EU hosting became generally available on October 29, 2024. The 2026 change expanded that service region to Norway and Switzerland from May 1, 2026.

What changed, and what did not

GitHub announced EU data residency on September 24, 2024, and made it generally available on October 29, 2024. It was therefore not a new blanket storage right introduced in 2026.

#	Preview	Product	Price
1		Data Privacy and Security Law (American Casebook Series)	$317.00	Buy on Amazon
2		Data Privacy & Compliance Handbook: A Practical Guide to GDPR, CCPA, ISO 27001, Data Protection, and...	$24.99	Buy on Amazon
3		Privacy and Data Protection Law (University Casebook Series)	$287.00	Buy on Amazon
4		Data Privacy: A runbook for engineers	$58.80	Buy on Amazon

The 2026 developments are narrower but important:

• Codespaces became generally available for data-residency enterprises on April 1, 2026.
• From May 1, 2026, GitHub’s EU data-residency region can use Azure infrastructure in Norway and Switzerland, in addition to France, Sweden, Germany and the Netherlands.

Norway and Switzerland are not EU member states. “EU region” is GitHub’s service-region name, not a promise of EU-member-state-only infrastructure. GitHub says the expansion aligns the region with Microsoft’s EU Data Boundary (GitHub’s announcement).

Who can use EU data residency?

The option is designed for customers buying GitHub Enterprise Cloud with data residency. It is not a regional switch in a personal, Free, Pro or ordinary Team account.

#1 Best Overall

Data Privacy and Security Law (American Casebook Series)

$317.00

Buy on Amazon

Onboarding creates an enterprise environment with:

• Enterprise Managed Users, rather than ordinary personal-account identities;
• a dedicated subdomain under ghe.com;
• an external identity provider configured for SAML or OIDC;
• SCIM provisioning for users, groups and team membership.

GitHub’s documentation describes the flow in About GitHub Enterprise Cloud with data residency. This makes the decision an enterprise procurement and architecture project, not an account-preferences change.

What GitHub says is stored in the selected region

GitHub’s scope is specific. It says the following categories are stored in the selected data-residency region:

These are claims about specified enterprise data, not a statement that every service record associated with GitHub remains there. See GitHub’s storage description for the current scope.

What may remain outside Europe

GitHub documents several exceptions or potentially out-of-region categories:

• Telemetry and logs containing persistent identifiers.
• Contact, billing, payment, purchase and licensing information.
• Support requests, case notes, calls, chats and remote-assistance data.
• GitHub Copilot data and logs by default.

Consequently, “our repositories are in GitHub’s EU region” is materially different from “all GitHub data stays in Europe.” GitHub also says it may need to transfer some data outside the selected region.

Rank #2

Data Privacy & Compliance Handbook: A Practical Guide to GDPR, CCPA, ISO 27001, Data Protection, and Secure Data Governance for Security and Cloud Professionals

$24.99

Buy on Amazon

Copilot requires a separate decision

If Copilot residency matters, administrators must examine the Restrict Copilot to data residency compliant models policy. GitHub says enabling it keeps inference, prompts, responses, logs and telemetry in-region. That handling is configuration-dependent; it should not be assumed merely because repositories use EU data residency. Details are in GitHub’s data-storage documentation.

How setup works

GitHub’s documented onboarding involves a new enterprise environment rather than converting an existing ordinary organization in place.

1. Start a GitHub Enterprise Cloud trial.
2. Select Get started with managed users.
3. In Data hosting, choose the EU region.
4. Choose the enterprise subdomain carefully. GitHub says it cannot be changed later.
5. Select Create enterprise and complete the identity-provider configuration.
6. Enable two-factor authentication for the setup user and retain recovery codes.
7. Create a personal access token with at least the scim:enterprise scope for provisioning.
8. Configure SAML or OIDC authentication and SCIM provisioning.
9. Synchronize identity-provider groups with GitHub teams and memberships.
10. Select Activate enterprise and move to paid Enterprise billing.
11. Plan and execute repository migrations with GitHub’s supported tools.

GitHub says the trial lasts 30 days and permits up to three new organizations. Provisioning can take several hours. The complete sequence is documented at Getting started with data residency for GitHub Enterprise Cloud.

Moving existing repositories

There is no instant “move this GitHub.com organization to Europe” button. The documented approach creates the managed-user enterprise and migrates content into it.

Supported migration routes

• GitHub Enterprise Importer for GitHub.com, GitHub Enterprise Server, Azure DevOps, Bitbucket Server and GitLab sources.
• Enterprise Live Migrations for GitHub Enterprise Server 3.17 and later.
• Other documented paths for particular source platforms.

Items to inventory before cutover

• Repository history and metadata, including issues, pull requests, discussions, releases and packages.
• Actions workflows, secrets, variables and runner connectivity.
• Webhooks, GitHub Apps, deploy keys, tokens, branch protections and rulesets.
• Hard-coded github.com URLs, API endpoints, OAuth assumptions and developer-tool credentials.
• Public repositories and open-source collaboration that may need to remain on GitHub.com.

GitHub’s migration example uses a target API endpoint under the new subdomain:

Rank #3

Privacy and Data Protection Law (University Casebook Series)

$287.00

Buy on Amazon

export GH_PAT="TARGET-TOKEN"
export GH_SOURCE_PAT="SOURCE-TOKEN"
export TARGET_API_URL="TARGET-GHE-API-URL"
export GITHUB_SOURCE_ORG="SOURCE-GH-ORGANIZATION-NAME"
export SOURCE_REPO="SOURCE-GH-REPOSITORY-NAME"
export GITHUB_TARGET_ORG="TARGET-GHE-ORGANIZATION-NAME"
export TARGET_REPO="TARGET-GHE-REPOSITORY-NAME"

gh gei migrate-repo 
  --target-api-url "$TARGET_API_URL" 
  --github-source-org "$GITHUB_SOURCE_ORG" 
  --source-repo "$SOURCE_REPO" 
  --github-target-org "$GITHUB_TARGET_ORG" 
  --target-repo "$TARGET_REPO" 
  --verbose

GitHub’s example target URL is similar to https://api.octocorp.ghe.com. Replace every placeholder and verify the current GitHub CLI extension and authentication requirements in the official migration guidance.

Codespaces and other developer services

Codespaces is generally available for GitHub Enterprise Cloud with data residency in all listed regions, including the EU (GitHub’s April 1, 2026 announcement). For strict residency controls, the Codespace must be enterprise- or organization-owned. User-owned Codespaces are not supported for these data-residency accounts.

This distinction matters: localizing repository storage does not automatically localize every development environment, log or machine-owned resource.

Price and commercial questions

GitHub’s pricing page displayed $21 per user per month for the first 12 months when observed on August 16, 2026, and advertised a free 30-day trial (GitHub pricing). Treat that as a dated introductory signal, not a permanent worldwide contract price. Confirm taxes, minimum commitments, overages, support levels and regional terms with GitHub sales.

Your total project cost also includes identity integration, migration, testing, retraining, compliance evidence and ongoing administration. Compare that with the infrastructure, patching, backups, high availability and disaster-recovery work required for GitHub Enterprise Server.

Rank #4

Data Privacy: A runbook for engineers

$58.80

Buy on Amazon

Residency is not the same as sovereignty or GDPR compliance

Data residency describes where specified data is stored or processed. Data sovereignty also asks which legal jurisdictions can exercise authority over the provider, its personnel and its subprocessors. GDPR compliance additionally depends on lawful basis, contracts, transfer mechanisms, retention, access controls and security.

Before signing, legal and security teams should review:

• the GitHub Data Protection Agreement;
• subprocessors and international-transfer mechanisms;
• government-access provisions;
• encryption and key-management arrangements;
• support, telemetry, billing and Copilot handling; and
• whether the requirement calls for European ownership, customer-controlled keys or self-hosting.

Selecting the EU region can help meet a defined repository-location requirement. It does not, by itself, guarantee GDPR compliance or prevent every possible international disclosure.

When this option fits—and when it does not

Likely good fit

• You want GitHub’s managed service, Actions and enterprise governance without operating the platform.
• A customer or regulator requires specified repository data to be hosted in a European region.
• Your organization already uses Entra ID or another SAML/OIDC provider with SCIM.
• You can accept Enterprise Managed Users and a dedicated ghe.com environment.
• You can document and control ancillary services such as Copilot and Codespaces.

Likely poor fit

• The requirement is that every support record, billing record, telemetry stream and AI interaction remain in Europe.
• You need customer-controlled encryption keys or fully isolated infrastructure.
• Users must retain ordinary personal accounts and unrestricted public-community workflows.
• Critical integrations assume api.github.com or do not support the dedicated environment.
• Enterprise licensing and migration effort outweigh the value of regional hosting.

Alternatives to evaluate

The Bottom Line

GitHub’s EU data-residency capability is real, but it is an Enterprise Cloud deployment for managed-user organizations—not a new Europe switch for ordinary GitHub accounts. Choose it when regional storage of defined enterprise repository data plus GitHub’s managed platform meets your requirements. Do not treat it as complete European control until your legal, security, identity, migration, Copilot, Codespaces and integration reviews confirm that the documented exceptions are acceptable.

Quick Recap

Bestseller No. 1

Data Privacy and Security Law (American Casebook Series)

$317.00

Bestseller No. 2

Data Privacy & Compliance Handbook: A Practical Guide to GDPR, CCPA, ISO 27001, Data Protection, and Secure Data Governance for Security and Cloud Professionals

$24.99

Bestseller No. 3

Privacy and Data Protection Law (University Casebook Series)

$287.00

Bestseller No. 4

Data Privacy: A runbook for engineers

$58.80

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.