What is now generally available
GitHub says you can now bring your work on GitHub Enterprise Server into the GitHub Copilot app. After adding a GHES account, you can work with remote repositories, issues and pull requests. The post makes clear that the feature was previously an opt-in preview and is now generally available.
The changelog entry therefore describes connecting the Copilot app to an existing GHES account. It is not the introduction of GitHub Enterprise Server itself, and it does not automatically include every Copilot capability that exists on github.com.
How to add a GHES account
The changelog records the sequence: you first need to sign in with a GitHub.com or GHE.com account. Only then do you go to Settings, then Accounts, choose Add account and select GitHub Enterprise Server. Without that first sign-in on GitHub.com or GHE.com, the path described is not available.
Which internal permissions, network allowances or device rules you need is not stated in the changelog. Your own administration has to decide that before the feature is recommended widely.
Version and a clear limit
The feature is available in GitHub Copilot app 1.2.0 and later. Older app versions therefore sit outside the documented baseline. GitHub also states that cloud sessions are not available for GHES. Anyone planning a workflow that depends on a cloud session cannot rely on this general availability for that path.
For more detail, GitHub points to the documentation “Sign in on the Copilot app” in the Copilot on GitHub Enterprise Server section. The changelog text itself does not add platforms, prices, or any statement about on-premises models.
What the post does not say
The post does not say which operating systems the app supports in which form, and it does not describe which Copilot chat, agent or review features run fully, only in part, or not at all on GHES compared with github.com – apart from the stated exception for cloud sessions. That gap should be checked internally against the linked documentation and a short test of your own before the app is mandated as the standard path for server operations.
The entry also contains no information about data flows between the app, GHES and any cloud services beyond the recorded sign-in steps and the cloud-session limit. The changelog text alone is not enough for a data-protection impact assessment.
Our assessment for organizations
For teams that already use GHES and want the Copilot app, general availability is a practical step forward: access is documented, and the opt-in preview is no longer a special status. Before a wide rollout, version 1.2.0 or later, the required sign-in via GitHub.com or GHE.com, and the absence of cloud sessions should be written into the internal guide.
This article sits alongside the same day’s model change but does not replace it. Anyone running automated agents on GHES needs to review both topics separately: connecting the app, and the models that disappear on 14 December 2026.
The changelog entry is short; that is all the more reason for internal tests to record the three documented points: app version, sign-in order, and the exclusion of cloud sessions. Anything beyond that remains unverified until the linked documentation and a test of your own confirm it.
Keep it verifiable




