Copilot app now works with GitHub Enterprise Server, minus cloud sessions

GitHub, a Microsoft company, has made GitHub Enterprise Server (GHES) support generally available in the GitHub Copilot app. The catch: GitHub says cloud sessions are not available for GHES accounts.

How to connect a GHES account

According to the changelog, users can add a GHES account to the Copilot app to work with remote repositories, issues and pull requests. The capability was previously an opt-in preview and is now generally available.

Setup has an unusual first step. A user must sign in with a GitHub.com or GHE.com account first. After that, the path is Settings > Accounts > Add account, where GitHub Enterprise Server is one of the choices. The feature needs Copilot app version 1.2.0 or later. GitHub points to a documentation page on signing in to the Copilot app on GHES.

The one stated limit is blunt: “Cloud sessions aren’t available for GHES.” The changelog does not explain the reason or say whether that will change.

What the changelog leaves unanswered

The announcement is short, and several details a administrator would want are missing. It does not list which GHES versions are supported, and it does not say which Copilot plans or licenses are required. It gives no rollout schedule. Anyone planning a deployment will need to check the linked documentation for those points, because the changelog itself does not establish them.

The requirement to sign in with a GitHub.com or GHE.com account first also matters. It suggests that an organization running only a self-hosted server cannot use the app in isolation, though the changelog does not spell out the reason for the ordering, so that reading is an inference.

A self-hosted foothold for Copilot’s enterprise push

The angle here is strategy. GHES is the version of GitHub that companies run on their own infrastructure, often because of compliance or data-residency rules. Bringing the Copilot app to those accounts extends it to customers who cannot move code to GitHub.com. Leaving out cloud sessions keeps the heaviest remote workloads off that path for now.

GitHub has been adding enterprise controls around Copilot in the same week. As we reported on November 11, enterprise GitHub Apps can now manage Copilot seats through enterprise-level APIs instead of a person’s token, though those endpoints are labeled public preview and may change. That story also noted that the documentation says only enterprise owners can cancel seats, and the changelog did not reconcile the two.

Administrators also face a model shuffle. As we covered on November 14, GitHub will remove six models from all Copilot experiences on December 14, 2026, including Claude Haiku 4.5 and Grok 4.6, and Kimi K3 has no named replacement. For Business and Enterprise customers, replacements are switched on automatically unless an admin has disabled the global default or a specific model. Teams that add GHES accounts to the app will want to review those model policies at the same time.

Taken together, the pattern is a vendor tightening its grip on enterprise administration while widening where its tools run. What the changelog does not show is how many customers use GHES with Copilot, or how the app behaves compared with the experience on GitHub.com beyond the missing cloud sessions. GitHub gives no figures on either point.

Who can use it today

Anyone on Copilot app 1.2.0 or later with access to a GHES instance and a GitHub.com or GHE.com sign-in can follow the steps above. Whether a given GHES server is new enough, or whether a given license covers the app, is not addressed in the announcement. Pricing is not mentioned at all.