Test: "Continue with Microsoft" sign in for GitHub

[TylerLeonhardt]

Refs: #332948

• anyOS Christof Marti (@chrmarti)
• anyOS Aaron Munger (@amunger)

Complexity: 4

Create Issue

---

Context

If you're already signed in to Microsoft in VS Code, you shouldn't need a second trip through the browser to reach Copilot. Sign-in dialogs now offer Continue with Microsoft, which trades the Entra token you already have for a GitHub one.

Two exchanges with a confirmation in between: we ask GitHub which account your Microsoft identity maps to, show you that account, and publish nothing until you agree. The GitHub token never touches the Keychain — it lives in memory for the life of the window. What's saved is your consent, so a new window can mint a session again without asking.

Setup

Insiders only — the exchange uses a client secret that isn't in OSS builds. code-insiders --transient gets you a throwaway instance signed out of everything; keep the relaunch command it prints. Then "chat.microsoftAuthentication.enabled": true and reload. Signing out of GitHub in your normal install works just as well.

Sign-in dialogs only. The Accounts menu's own GitHub sign-in doesn't offer this.

What I want to know

Does the confirmation modal give you enough to say yes?

Your organization's Microsoft sign-in is linked to this GitHub account:

Your Handle (@your-handle)

Sign in to GitHub with this account?

It shows the handle and nothing else on purpose, since a display name is free text the account holder controls.

Does auth survive a reload, a restart, a second window?

Does signing out of GitHub or of Microsoft do what you expect? They're deliberately asymmetric: signing out of Microsoft takes away the means, not the agreement, so signing back in should restore GitHub on its own.

With multiple GitHub or Microsoft accounts, does the flow make sense? The modal's Use a Different Microsoft Account is the way to switch.

And the one I don't know the answer to: what happens if your Microsoft account has no GitHub account behind it? I think you get "GitHub did not accept your Microsoft account for sign in," but I haven't seen it, and whether that message helps is what I want to find out.

Notes

• Windows brokers through the OS so you may never see a browser; macOS and Linux will.
• No token should show up in the GitHub Authentication output channel at any log level.
• Shipped in Add "Continue with Microsoft" sign in for GitHub #332948; no separate feature issue.
• chat.microsoftAuthentication.enabled is experimental, off by default, read when a sign-in dialog opens.
• No known issues, first pass over the flow.

[chrmarti]

I only have a single Microsoft account (ignoring the githubazure one that doesn't seem to work, see #333497) and two corp GitHub accounts (only one I can pick, see #333492). So my testing is limited to these. HTH

[amunger]

Does the confirmation modal give you enough to say yes?

It might be helpful to see the microsoft account that it is referring to, but otherwise it's fine: the gh account to use is isolated and easy to identify, that feels like the most important thing