PuppyIP Resource Center
Developer Integration 4 min Published 2026-11-14

Sign In to GitHub Enterprise Server in the GitHub Copilot App

GHES support is generally available in GitHub Copilot app version 1.2.0 and later. First sign in with a GitHub.com or GHE.com account, then go to Settings > Accounts > Add account > GitHub Enterprise Server and authorize in a browser. To make requests, you also need a cloud account with a Copilot license or your own model provider; adding the GHES account alone does not satisfy that requirement.

GitHub Copilot app GitHub Enterprise Server GHES account Developer tools

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • On November 13, GitHub announced that GHES support is generally available in GitHub Copilot app version 1.2.0 and later.
  • Sign in to GitHub.com or GHE.com first, then choose GitHub Enterprise Server from Settings > Accounts > Add account and authorize the app in a browser.
  • The GHES account connects work on enterprise repositories, issues, and pull requests; making requests has a separate cloud-license or own-provider requirement.
  • GHES cloud sessions remain unavailable. That boundary is separate from adding a GHES account and working with enterprise repositories.

The November 13 release: GHES support is generally available

On November 13, 2026, GitHub announced that GitHub Enterprise Server (GHES) support in the GitHub Copilot app is generally available. It had previously been an opt-in preview. The changelog lists GitHub Copilot app version 1.2.0 and later and says the integration brings GHES remote repositories, issues, and pull requests into the app.

This guide follows the official announcement and documentation. No real account sign-in, authorization, or connection test was performed.

Add the GHES account in the documented order

Start by signing in to the GitHub Copilot app with an account on GitHub.com or GHE.com. GitHub’s setup documentation requires this cloud sign-in before you add the self-hosted GHES account. Keep that order even when the repositories you use every day live on your organization’s own server.

In the app, open Settings, select Accounts, choose Add account, then choose GitHub Enterprise Server. Follow the prompts to open a browser and authorize the app. The GitHub.com or GHE.com account used for the initial sign-in and the GHES account added afterward are two distinct identities in this flow.

Adding an account does not establish request eligibility

Connecting an account and making model requests are separate checks. GitHub’s documentation says you must also be signed in to a cloud account with a Copilot license to start making requests. It lists configuring your own model provider as an alternative. The sign-in guide does not explain provider setup or fees, so this article does not add configuration steps.

Consider a hypothetical setup: Account A is the initial GitHub.com or GHE.com sign-in, and Account B is the company’s GHES account. Sign in with A before adding B from Accounts. To make requests, separately check that a signed-in cloud account has a Copilot license, or that your own model provider is configured. Seeing B in the account list alone does not establish either condition.

Cloud sessions and account sign-in have different boundaries

GitHub’s announcement explicitly says that cloud sessions are not available for GHES. Keep that limitation separate from the integration that lets you add a GHES account and work with remote repositories, issues, and pull requests in the app. A successful account sign-in does not mean cloud sessions are enabled.

The two sources do not provide a complete operating-system, region, plan, or fee matrix, or details about every organization’s network policy and repository permissions. Check which repositories, issues, and pull requests the selected account can access through your organization’s normal process.

Sources

Frequently Asked Questions

Will every repository on GHES appear in the app after browser authorization?

The sources say you can work with GHES remote repositories, issues, and pull requests, but they do not promise that every resource in every organization will appear. If a repository is missing, check the selected GHES account and its organization access. No instance visibility test was performed for this article.

The current documentation shows GHES 3.22. Is that the minimum server version?

That cannot be inferred. During review, the latest documentation entry resolved to the English GHES 3.22 page. The version of that page is not a product minimum, and the reviewed sources do not specify a minimum GHES release.