Repository navigation
[REMOTE] Authentication stopped working even if's marked as green #1633
Description
Activity
- assigned and unassigned
on Sep 23, 2026 Additional information: on GitHub Copilot App customize screen I have the green checkmark
On a chat session, I have sometimes "auth needed" (while the checkmarks stays green in customize)
Are you connecting to the root url (https://mcp.dev.azure.com) or to an org-specific url (e.g. https://mcp.dev.azure.com/my-org)
https://mcp.dev.azure.com/my-org
It was working fine before (in June)
Reacted by Robin CartouxBroken for me as well on 2.10.0. Going back to 2.8.1 resolved it. Might be notable that I am not signing in to DevOps with the same account as I am signing in to Windows.
According to my Claude:
Why: 2.10.0 added the Windows WAM broker to interactive auth; sign-in flashed/looped and calls failed. The broker-fallback path also never caches the account, so there's no silent refresh. 2.8.1 uses the plain browser sign-in and works.Jan Steenbeek (@jsteenbeek) interesting, with the remote mcp, can you sepcify a version to use (the 2.8.1 you mention), or it's only possible with stdio?
Issue Type
Select the option that best describes your issue.
Tool(s)
All tools. Issue is linked to authentication.
Description
In GitHub Copilot App, or GitHub Copilot CLI, MCP server is marked as signed in with the green checkmark. But it does not work. Error is the following : "I couldn’t retrieve your current work items: Azure DevOps returned VS30063 — not authorized for
https://dev.azure.com. Reconnect or authorize Azure DevOps, then try again."On Github Copilot CLI, when trying to authenticate using the /mcp command, the error is the following after entering the adress: