Skip to content

[Requests and ideas] # Azure DevOps Support #765

@kuhninator

Description

@kuhninator

Mood: 😊
Category: Requests and ideas

Azure DevOps Support

Summary

The GitHub Copilot app currently only supports GitHub accounts and GitHub-hosted repositories for its project/session model. Many enterprise developers (including teams at Microsoft) host their source in Azure DevOps (Azure Repos) and manage planning in Azure Boards. Today there is no way to connect the app to Azure DevOps, which blocks these users from adopting the app for their primary workflow.

Problem / Gap

  • Projects and sessions are tied to GitHub repos, GitHub PRs, and GitHub issues.
  • There is no connector for Azure DevOps Git repositories, so I can't open a session against an Azure Repos repo.
  • There is no integration with Azure Boards, so I can't browse, triage, or assign work items / taskboard tasks from the app.
  • The existing Azure Boards → Copilot coding agent flow requires the code to live in GitHub, which doesn't help teams whose code is in Azure Repos.

Who is affected

Enterprise and Microsoft-internal teams whose code and planning live entirely in Azure DevOps.

Proposed Solution

Add first-class Azure DevOps support to the app, ideally including:

  1. Azure DevOps authentication (Entra ID / PAT / OAuth) alongside the existing GitHub login.
  2. Azure Repos as a project source — clone, branch, and open coding sessions against Azure Repos Git repositories.
  3. Azure Boards integration — list, open, and create sessions from work items and taskboard tasks (analogous to the current GitHub issue → session flow).
  4. Pull request support for Azure Repos PRs (review/work-on flows similar to GitHub PRs).
  5. Optionally, surface this via the Azure DevOps MCP server as an officially supported, click-to-connect integration rather than manual MCP setup.

Alternatives Considered

  • Azure DevOps MCP server in VS Code — works for querying/updating work items, but is not integrated into this app's project/session model and requires manual setup.
  • Mirroring Azure Repos to GitHub — adds overhead, duplicates source of truth, and breaks Boards linkage.

##Impact
Unlocks the app for a large segment of enterprise users currently excluded by the GitHub-only model, and aligns with the broader "agentic DevOps" direction across GitHub and Azure DevOps.


Field Value
App version 0.2.24
OS Windows 10.0.26200
Theme GitHub
Path /chat
Tenure Day 2 (Week 1)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions