microsoft / microsoft/GitHub-Copilot-for-Azure

GitHub Enterprise sign-in loops with mixed personal and GHE accounts

Open
#2,492 2 comments 0 reactions 0 assignees View on GitHub
untriaged vscode
Dominant language
Python
Stars
250
Forks
204
Avg merge
1d 12h
Merged PRs (30d)
67

Description

Does this occur consistently? consistently inconsistent
Repro steps:
the sign GitHub Authentication extention stil fails when someone has both a personal and a GHE identity. Using profiles it completely ignores them and keeps trying to direct the user to standerd github for auth instead of providing a mechanism to attach to ghe. simple to reporduce , don't use your corporate microsoft machine. use a standard non domain joined machine, then create a retail github a ccount and then try and sign in with a GHE account and enjoy the death loop of log in prompts. for the real expereince add a tight timeline and pressure from PM to complete a task andn then you will feel what many are dealing with because your auth flow is broken for real people, or at the very least completely unintuitive

Action: @azure.toolInvoke
Error type: Error
Error Message: Cancelled

Version: 1.0.209
OS: darwin
OS Arch: arm64
OS Release: 25.6.0
Product: Visual Studio Code - Insiders
Product Version: 1.123.0-insider
Language: en
UTC time: Tue, 02 Jun 2026 13:13:35 GMT

Call Stack

```
u extension.js:13:53207
async yv.login extension.js:13:53711
async dc.createSession extension.js:13:64826
async file:/extensionHostProcess.js:532:21676
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the mixed personal and GitHub Enterprise account flow in VS Code Insiders on a non-domain-joined macOS machine. Trace the login and createSession calls in extension.js and the extensionHostProcess.js stack, then verify that the flow offers a GitHub Enterprise path and no longer loops or ends with a cancelled session.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, github, vscode
Domain
authentication, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.