Enable Data Residency Selection Per Organization in GitHub Enterprise Cloud

[catatafishen]

Select Topic Area

Product Feedback

Body

Problem
Currently, GitHub Enterprise Cloud allows data residency to be set only at the enterprise-account level, meaning all organizations share the same region. For global enterprises operating across multiple jurisdictions, this limits compliance with regional data sovereignty requirements.

Use Case
Our company operates GitHub organizations in both the EU and the US. Regulatory and corporate policies require EU data to remain within EU boundaries and US data within the US. Managing separate enterprise accounts to segregate data is not viable due to licensing and identity provider constraints with Managed Enterprise Users.

Proposal
Allow per-organization data residency settings within a single enterprise account.
Residency should be selectable during organization creation, and ideally configurable later in organization settings.
Maintain an enterprise-wide default, with the ability for individual organizations to override that setting.

We understand that GitHub may still process some global metadata, but the primary organization data should be stored according to the selected region for each organization.

Benefits
Enables global companies to comply with multi-region data laws without the overhead of multiple enterprise accounts.
Simplifies identity and access management across regions.
Reduces unnecessary additional licensing and administrative complexity.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐