Skip to main content
This guide explains how to create a GitHub Enterprise Cloud (GHEC) organization that uses Enterprise Managed Users (EMU) and configures data residency to control the geographic location where your enterprise data is stored. Overview
  • EMU lets organizations fully manage identities and access for GitHub accounts using an external identity provider (IdP).
  • Data residency ensures that code, metadata, and other enterprise data are stored in a specific geographic region (for example, Europe or Japan).
  • Use EMU with data residency when you require strict identity provisioning, regional data controls, or need to prevent use of personal GitHub accounts.
A dark-themed GitHub webpage screenshot advertising a 30-day free trial to "Unlock GitHub's premium features," with promotional text and icons on the left. The right side shows an "Enterprise Managed Users" panel and form fields including a data-hosting dropdown for enterprise setup.
When to choose EMU with data residency
  • You need centralized identity provisioning (SAML/OIDC with SCIM).
  • You must ensure enterprise data is stored in a specific country or region.
  • You want to disable use of personal GitHub accounts for employees and contractors.
Quick summary
  • Create a new enterprise and select the “Enterprise with Managed Users” option.
  • Choose a data hosting region during enterprise creation.
  • Configure an external IdP for provisioning and SSO.
  • Onboard admins and users via the IdP — personal GitHub accounts are not allowed for EMU-managed users.
Step-by-step: Create an EMU enterprise with data residency
  1. Navigate to GitHub Enterprise Cloud enterprise creation.
  2. Choose “Enterprise with Managed Users.”
  3. Under Data hosting, select the geographic region where you want enterprise data stored.
  4. Enter an enterprise name (example: “Kode Kloud”). GitHub will suggest a subdomain; you can customize it (for example, kode-kloud).
  5. Select your external identity provider (SAML/OIDC with SCIM is required for provisioning).
  6. Complete the admin contact and enterprise configuration details.
  7. Create the enterprise. After creation, all admin and user provisioning must happen through the configured IdP.
A dark-themed screenshot of the GitHub Enterprise account creation page showing form fields (Data hosting set to Japan, Enterprise name "Kode Kloud", Subdomain "kode-kloud") and identity provider options. The left side has decorative purple-blue tech icons and connecting lines.
Data residency: regions and considerations Identity provider and provisioning
  • EMU enforces that all managed users are provisioned and authenticated through your IdP.
  • Supported patterns: SAML or OIDC for single sign-on plus SCIM for automated provisioning/deprovisioning.
  • Personal GitHub accounts cannot be used as EMU-managed accounts — users must be created or federated from the configured IdP.
Enterprise Managed Users requires an external identity provider for provisioning and single sign-on (for example, SAML/OIDC with SCIM provisioning). Personal GitHub accounts are not permitted for EMU-managed users.
If you need to allow personal GitHub accounts or prefer not to configure an external IdP, create a standard (non-EMU) GitHub Enterprise Cloud organization instead. EMU enforces IdP-based account management and blocks personal account use.
Post-creation: onboarding and lifecycle
  • Admins and regular users must be onboarded via the IdP (SCIM provisioning or manual provisioning through your IdP).
  • Use IdP group mappings and SCIM attributes to control user roles and team membership.
  • Configure SSO enforcement and test login flows before migrating sensitive repositories.
Additional resources and references If your requirements include private internal work, strict identity provisioning, and storing data in specific regions, EMU with data residency is the appropriate choice. If any of those constraints do not apply, consider a standard GitHub Enterprise Cloud account instead.

Watch Video