Skip to main content

Feature overview for GitHub Enterprise Cloud with data residency

Learn about the available features on GHE.com, plus features that work differently from GitHub.com.

The features available with data residency on GHE.com are similar to the features available to cuentas de usuario administradas on GitHub.com, with some additions and exceptions. Some features work differently or require additional configuration compared to the equivalent feature on GitHub.com.

Available features

GitHub Enterprise Cloud is a developer platform that supports the entire software development lifecycle, including planning work, automating tests and deployments, and keeping code secure. To learn about available features, see "Feature overview for GitHub Enterprise Cloud."

Currently unavailable features

The following features are currently unavailable on GHE.com.

FeatureDetailsMore information
GitHub CodespacesCurrently unavailable."Resumen de GitHub Codespaces"
GitHub MarketplaceCurrently, apps from GitHub Marketplace are unavailable. GitHub Actions workflows from GitHub Marketplace may not function as expected. For more information, see "GitHub Actions workflows from GitHub Marketplace.""Buscar en el Mercado de GitHub"
macOS runners for GitHub ActionsCurrently unavailable."Acerca de los ejecutores hospedados en GitHub"
Maven and Gradle support for GitHub PackagesCurrently unavailable."Trabajar con el registro de Apache Maven"
AchievementsCurrently unavailable."Ver contribuciones en tu perfil"
Microsoft Teams integrationsCurrently unavailable."Integraciones destacadas de GitHub"
GitHub ImporterCurrently unavailable"Acerca de Importador GitHub"
GitHub Copilot WorkspacesCurrently unavailable
Interactive mapsCurrently can't use GeoJSON/TopoJSON syntax to create interactive maps."Crear diagramas"
Usage metrics for GitHub ActionsCurrently unavailable"Viewing GitHub Actions metrics for your organization"
Some features currently in versión preliminar pública or versión preliminar privadaCertain features that are in a preview phase on GitHub.com may not be available on GHE.com

Features that work differently

The following features are either specific to GHE.com or work differently compared to GitHub.com.

API access

Integrators with the REST and GraphQL APIs must send requests to your enterprise's dedicated URL on GHE.com. For more information, see "About GitHub Enterprise Cloud with data residency."

URL differences

The URL formats for certain features and services vary between GitHub.com and GHE.com. If you're migrating to GHE.com and have automations or integrations that depend on URL values for GitHub.com, you will need to updates these values.

The following examples are not exhaustive.

FeatureExample on GitHub.comExample on GHE.com
GitHub PackagesThe Container registry is located at ghcr.io.The Container registry is located at https://containers.SUBDOMAIN.ghe.com.
User provisioningThe "tenant URL" for Microsoft Entra ID is https://api.github.com/scim/v2/enterprises/ENTERPRISEThe "tenant URL" for Microsoft Entra ID is https://api.SUBDOMAIN.ghe.com/scim/v2/enterprises/SUBDOMAIN
OIDC trusts for GitHub Actions deploymentsThe OIDC token is issued from https://token.actions.githubusercontent.com.The OIDC token is issued from https://token.actions.SUBDOMAIN.ghe.com
Raw URLshttps://raw.githubusercontent.com/https://raw.SUBDOMAIN.ghe.com/
Anonymized URLs for images and videoshttps://private-user-images.githubusercontent.com/https://SUBDOMAIN.ghe.com/user-attachments/assets/

GitHub Actions workflows from GitHub Marketplace

GitHub Actions workflows from the GitHub Marketplace may not work as users expect.

  • Some actions hard-code API calls to api.github.com, which don't currently work for enterprises on GHE.com.
  • Some actions make requests to resources on GitHub.com, and these actions will not work for enterprises on GHE.com unless the author has built a mechanism to inject a secondary token for API calls. A GITHUB_TOKEN within a workflow run for your enterprise on GHE.com does not grant access to resources on GitHub.com.

Retirement of namespaces for actions accessed on GitHub.com

To ensure workflows use their intended actions and to block the potential for abuse, once an action on GitHub.com is used for the first time, the namespace associated with that action is retired in your enterprise. This blocks users from creating an organization and repository in your enterprise that match the action's namespace on GitHub.com.

To allow people to use namespaces that match actions you have used from GitHub.com, you can make a retired namespace available. See "Making retired namespaces available on GHE.com."

GitHub Connect

You can use GitHub Connect to connect to GHE.com from GitHub Enterprise Server.

  • GitHub Connect features that rely on data from GitHub.com are not available.
  • To enable GitHub Connect, you must configure your GitHub Enterprise Server instance to connect to your GHE.com subdomain. See "Enabling GitHub Connect for GHE.com."