The features available with data residency on GHE.com are similar to the features available to managed user accounts 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.
| Feature | Details | More information |
|---|---|---|
| GitHub Codespaces | Currently unavailable. | "GitHub Codespaces overview" |
| GitHub Marketplace | Currently, 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." | "Searching GitHub Marketplace" |
| macOS runners for GitHub Actions | Currently unavailable. | "About GitHub-hosted runners" |
| Maven and Gradle support for GitHub Packages | Currently unavailable. | "Working with the Apache Maven registry" |
| Achievements | Currently unavailable. | "Viewing contributions on your profile" |
| Microsoft Teams integrations | Currently unavailable. | "Featured GitHub integrations" |
| GitHub Importer | Currently unavailable | "About GitHub Importer" |
| GitHub Copilot Workspaces | Currently unavailable | |
| Interactive maps | Currently can't use GeoJSON/TopoJSON syntax to create interactive maps. | "Creating diagrams" |
| Usage metrics for GitHub Actions | Currently unavailable | "Viewing GitHub Actions metrics for your organization" |
| Some features currently in public preview or private preview | Certain 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
- URL differences
- GitHub Actions workflows from GitHub Marketplace
- Retirement of namespaces for actions accessed on GitHub.com
- GitHub Connect
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.
| Feature | Example on GitHub.com | Example on GHE.com |
|---|---|---|
| GitHub Packages | The Container registry is located at ghcr.io. | The Container registry is located at https://containers.SUBDOMAIN.ghe.com. |
| User provisioning | The "tenant URL" for Microsoft Entra ID is https://api.github.com/scim/v2/enterprises/ENTERPRISE | The "tenant URL" for Microsoft Entra ID is https://api.SUBDOMAIN.ghe.com/scim/v2/enterprises/SUBDOMAIN |
| OIDC trusts for GitHub Actions deployments | The OIDC token is issued from https://token.actions.githubusercontent.com. | The OIDC token is issued from https://token.actions.SUBDOMAIN.ghe.com |
| Raw URLs | https://raw.githubusercontent.com/ | https://raw.SUBDOMAIN.ghe.com/ |
| Anonymized URLs for images and videos | https://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_TOKENwithin 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."