Azure DevOps remote MCP connection and blocked-state UX

[dubscode]

Parent PRD

#1

What to build

Build the Azure DevOps remote MCP connection slice, including the full user-facing connection experience and explicit blocked-state handling for unsupported or failing remote auth scenarios. This is a vertical slice through auth, persistence, integration status, Integrations UI, and in-chat recovery prompts, with the expectation that real-world Azure DevOps remote MCP behavior may require a human decision.

Acceptance criteria

• A signed-in user can attempt to connect one Azure DevOps organization through the planned remote MCP path.
• Successful, expired, disconnected, blocked, and unsupported connection states are modeled and surfaced clearly in the UI.
• Chat can detect a missing or blocked Azure DevOps connection and route the user into the appropriate recovery flow.
• Real-world Azure DevOps remote MCP behavior is documented well enough to support a go / no-go product decision if needed.

Blocked by

• Blocked by Authenticated app shell and workspace bootstrap #2

User stories addressed

Reference by number from the parent PRD:

• User story 4
• User story 5
• User story 6
• User story 31
• User story 32
• User story 34
• User story 42
• User story 43
• User story 57
• User story 58