convez.ai
MCP Server
AurelienClere-365

ado-cowork-plugin

AurelienClere-365/ado-cowork-plugin

Ver no GitHub
BomPluginScore · de 0 a 100

Azure DevOps AI plugin for Microsoft 365 Copilot and VS Code — skills for Project Managers, developers, and consultants. Autonomous ADO tool calls via the built-in MCP server.

Instalação

$npx convez-ai AurelienClere-365/ado-cowork-plugin

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
6
Forks
0
Acompanhando
0
Saúde
85%
Último commit
há 1 mês
Versão
v1.2.0
Issues abertas
1
Contribuidores
2

README

A tradução para o português deste README ainda está na fila.

ADO Cowork Plugin

An AI assistant plugin designed for Project Managers who need live Azure DevOps data without leaving their chat window — and for developers and functional consultants who want the same. Works with Microsoft 365 Copilot, VS Code Copilot agent mode, and any AI assistant that supports the Agent Skills open standard (Claude Code, Cursor, Gemini CLI, JetBrains Junie).

Who is this for?

RolePrimary workflows
Project ManagerSprint health, go/no-go readiness, velocity trends, stakeholder updates, backlog grooming, retrospectives, committee PowerPoint decks
DeveloperPipeline triage, PR reviews, branch management, work item creation, commit history
Functional consultantWork item queries, backlog triage, wiki authoring, cross-project search, test plan management
Consultant / partner with guest accessRegister customer orgs once (add org contoso), then switch between your own and any customer Azure DevOps tenant in the same session

What this plugin does

Eliminates context-switching between your AI assistant and the Azure DevOps web portal. Describe what you need in plain English — the plugin routes the request to the correct Azure DevOps MCP tool and returns structured results directly in your chat window.

For Project Managers:

  • "Give me the sprint health report for the Platform team — committed vs completed, slipped items."
  • "Is v2.0 ready to go live? Show open P1 bugs, build status, and test pass rate."
  • "What is our velocity trend over the last 4 sprints? What can we commit to Sprint 13?"
  • "Prepare a PowerPoint deck for tomorrow's release committee call."
  • "Publish the Sprint 12 retrospective notes to the wiki."

For developers & functional consultants:

  • "What failed in the last pipeline run on main for repo api-gateway?"
  • "Show me all open PRs assigned to me in the backend repository."
  • "Find all code usages of TokenService across our repos."
  • "Write the ADR for our new caching strategy to the Architecture wiki page."

For consultants working across customer tenants:

  • "Add customer org contoso — I have guest access there."
  • "Show me all my configured organisations and check which ones I can access."
  • "Switch to the Fabrikam org and list their projects."
  • "I'm now working on the Contoso engagement — use org contoso, project Finance."

Architecture

Five layers — left to right: who uses it → what skills handle it → how it connects → what ADO tools it calls → where the data lives. The PowerPoint output path (M365 only) branches off above the ADO layer.

flowchart LR

    %% ── LAYER 1 — USERS ────────────────────────────────────────────────────
    subgraph USERS["👥  Users"]
        direction TB
        PM(["🗂️  Project Manager\nSprint health · go/no-go\nvelocity · committee deck"])
        DEV(["💻  Developer\nPipelines · PRs\nbranches · code search"])
        FUNC(["📋  Functional Consultant\nBacklog · wiki\ntest plans · search"])
    end

    %% ── LAYER 2 — PLUGIN SKILLS ─────────────────────────────────────────────
    subgraph PLUGIN["🔌  ADO Cowork Plugin  —  11 SKILL.md files"]
        direction TB
        CTX["ado-context\nOrg & project selection\nsession context hub"]
        subgraph PMS["PM Skills  ★"]
            S1["ado-pm-reporting\nSprint health · go/no-go\nvelocity · retro · deck"]
            S2["ado-sprints-capacity"]
            S3["ado-work-items"]
            S4["ado-project-discovery"]
        end
        subgraph DEVS["Dev / All Skills"]
            S5["ado-pipelines"]
            S6["ado-repositories"]
            S7["ado-pull-requests"]
            S8["ado-test-plans"]
            S9["ado-search"]
            S10["ado-wiki"]
        end
        CTX -.->|"activeOrg\nactiveProject"| PMS & DEVS
    end

    %% ── LAYER 3 — DEPLOYMENT ────────────────────────────────────────────────
    subgraph DEPLOY["⚙️  Deployment options"]
        direction TB
        OA["A — Skills-only\nPrompts folder copy\nNo server needed"]
        OB["B — VS Code  mcp.json\ntype: http · Azure AD\nhttps://mcp.dev.azure.com/{org}"]
        OC["C — M365 Copilot\nmanifest.json\nauth: None"]
    end

    %% ── LAYER 4 — MCP SERVER ────────────────────────────────────────────────
    subgraph MCPSVR["☁️  Azure DevOps built-in MCP Server  (Microsoft-hosted · no provisioning)"]
        direction TB
        EP["https://mcp.dev.azure.com/{orgName}\nAzure AD auth"]
        subgraph TOOLS["~37 MCP tools"]
            direction LR
            T1["wit_*\nWork Items"]
            T2["pipelines_*\nCI/CD"]
            T3["repo_*\nRepos & PRs"]
            T4["testplan_*\nTest Plans"]
            T5["search_*\nCode · Wiki · WI"]
            T6["wiki_*\nWiki pages"]
            T7["work_* · core_*\nSprints · Projects"]
        end
        EP --> T1 & T2 & T3 & T4 & T5 & T6 & T7
    end

    %% ── LAYER 5 — ADO DATA ──────────────────────────────────────────────────
    subgraph ADO["🗄️  Azure DevOps Organisation"]
        direction TB
        D1["📋 Boards\n& Work Items"]
        D2["⚙️ Pipelines\n& Builds"]
        D3["🔀 Repos\n& Pull Requests"]
        D4["✅ Test Plans\n& Results"]
        D5["📖 Wikis\n& Pages"]
    end

    %% ── OUTPUT — M365 ONLY ──────────────────────────────────────────────────
    PPT["📊  PowerPoint deck\nOneDrive · SharePoint\nM365 Copilot only"]

    %% ── EDGES ───────────────────────────────────────────────────────────────
    PM & DEV & FUNC -->|"plain-English prompt"| PLUGIN
    PLUGIN --> OA & OB & OC
    OB -->|"HTTP · Azure AD"| EP
    OC -->|"HTTP · Azure AD (user session)"| EP
    OC -->|"create_presentation"| PPT
    T1 & T3 & T7 <-->|"REST API"| D1
    T2 & T7     <-->|"REST API"| D2
    T3          <-->|"REST API"| D3
    T4          <-->|"REST API"| D4
    T5          <-->|"REST API"| D1 & D3 & D5
    T6          <-->|"REST API"| D5

    %% ── STYLES ──────────────────────────────────────────────────────────────
    classDef user   fill:#1e3a5f,stroke:#4fa3e0,color:#cce5ff
    classDef pmsk   fill:#0d3068,stroke:#4fa3e0,color:#fff
    classDef devsk  fill:#1a2a3a,stroke:#4fa3e0,color:#cce5ff
    classDef deploy fill:#1e3a1e,stroke:#6abf69,color:#cfffce
    classDef ep     fill:#003366,stroke:#4fa3e0,color:#fff
    classDef tool   fill:#001a33,stroke:#4fa3e0,color:#99ccff
    classDef ado    fill:#005a9e,stroke:#4fa3e0,color:#fff
    classDef ppt    fill:#c43e1c,stroke:#e8814a,color:#fff
    class CTX ctx
    class PM,DEV,FUNC user
    class S1,S2,S3,S4 pmsk
    class S5,S6,S7,S8,S9,S10 devsk
    class OA,OB,OC deploy
    class EP ep
    class T1,T2,T3,T4,T5,T6,T7 tool
    class D1,D2,D3,D4,D5 ado
    class PPT ppt

Rendered PNG: architecture.png — for attaching to emails, presentations, and environments that do not render Mermaid inline.


Repository structure

ado-cowork-plugin/
├── manifest.json                          # M365 App Manifest v1.28 (Cowork package)
├── color.png                              # 192x192 plugin icon (color)
├── outline.png                            # 32x32 plugin icon (outline)
├── architecture.png                       # Rendered architecture diagram (PNG)
├── architecture.mmd                       # Mermaid source for architecture.png
├── package.ps1                            # ASKILL validation + ZIP packaging
├── README.md                              # This file
├── EXAMPLES.md                            # Usage examples with sample prompts
├── CHANGELOG.md
├── CONTRIBUTING.md
├── PRIVACY.md
├── SECURITY.md
├── LICENSE
└── skills/
    ├── ado-project-discovery/
    │   └── SKILL.md
    ├── ado-work-items/
    │   └── SKILL.md
    ├── ado-sprints-capacity/
    │   └── SKILL.md
    ├── ado-pipelines/
    │   └── SKILL.md
    ├── ado-repositories/
    │   └── SKILL.md
    ├── ado-pull-requests/
    │   └── SKILL.md
    ├── ado-test-plans/
    │   └── SKILL.md
    ├── ado-search/
    │   └── SKILL.md
    ├── ado-wiki/
    │   └── SKILL.md    ├── ado-context/
    │   └── SKILL.md    └── ado-pm-reporting/
        └── SKILL.md

Skills — Azure DevOps MCP tool coverage

SkillAudienceMCP tools coveredUse cases
ado-contextAllcore_list_projectsOrg & project selection, multi-project filtering, session context — used by all other skills
ado-pm-reportingPMwit_query, wit_backlog, wit_work_item_write, work, work_iteration_write, work_capacity_write, pipelines_build, testplan_show_test_results_from_build_id, search_workitem, wiki_upsert_pageSprint health, go/no-go, velocity, stakeholder updates, backlog grooming, retrospectives, PowerPoint decks
ado-sprints-capacityPM / Devwork, work_capacity_write, work_iteration_writeSprint setup, iteration management, team capacity
ado-work-itemsPM / Devwit_work_item, wit_work_item_write, wit_work_item_comment_write, wit_work_item_link_write, wit_work_item_attachment, wit_backlog, wit_queryCreate/update PBIs, bugs, tasks; backlog queries
ado-project-discoveryPM / Allcore_list_projects, core_list_project_teamsOrg structure, project list, team roster
ado-pipelinesDevpipelines_build, pipelines_build_log, pipelines_run, pipelines_write, pipelines_definition, pipelines_artifactBuild status, logs, triggering runs, pipeline YAML
ado-repositoriesDevrepo_repository, repo_branch, repo_create_branch, repo_file, repo_search_commitsBrowse repos, files, branches, commit history
ado-pull-requestsDevrepo_pull_request, repo_pull_request_write, repo_pull_request_thread, repo_pull_request_thread_writePR review, approval, comments, thread resolution
ado-test-plansDev / QAtestplan, testplan_show_test_results_from_build_id, testplan_test_case_write, testplan_test_plan_write, testplan_test_suite_writeTest plan management, test case authoring, build results
ado-searchAllsearch_code, search_wiki, search_workitemCross-project code/wiki/work item search
ado-wikiAllwiki, wiki_upsert_pageRead and write wiki pages

Deployment options

OptionTargetAuthEffortLicences required
A — Skills-onlyAny AI assistantNoneCopy a folderGitHub Copilot (any plan) + Azure DevOps Basic
B — Local MCPVS Code CopilotAzure AD (auto)Edit mcp.jsonGitHub Copilot (any plan) + Azure DevOps Basic
C — M365 CopilotWhole M365 tenantNone (upgradable to OAuthPluginVault)Admin uploadMicrosoft 365 Copilot + Azure DevOps Basic + Frontier preview

Licence requirements

Azure DevOps (required for all options)

Every user who calls ADO MCP tools needs access to the Azure DevOps organisation.

ADO licenceWhat it coversMinimum needed
Basic (free up to 5 users, then ~$6/user/mo)Work items, boards, repos, pipelines, wikis✅ Sufficient for all plugin features
Basic + Test Plans (~$52/user/mo)All Basic features + test plan managementOnly needed if using ado-test-plans skill
Stakeholder (free, unlimited)View/create work items only — no repo/pipeline access⚠ Partial — PM-only read workflows may work; dev skills will not
Visual Studio subscriberIncluded with VS Enterprise / Professional subscription✅ Fully covered

Guest users in a customer tenant: the guest still needs at least a Basic licence (or Stakeholder) assigned in that organisation by the customer's ADO admin. Being a guest in Azure AD is not enough on its own — ADO access level must be set separately.


Option A — Skills-only licence requirements

LicencePlanNotes
GitHub CopilotIndividual, Business, or EnterpriseAny plan works; Business/Enterprise needed for org-managed policies
Azure DevOpsBasic (or Stakeholder for read-only PM use)No MCP calls are made — user pastes results manually; ADO web access is sufficient

Cost to start: GitHub Copilot Individual ($10/mo) + Azure DevOps Basic (free for ≤5 users). Effectively free for small teams already on GitHub Copilot.


Option B — Local MCP licence requirements

LicencePlanNotes
GitHub CopilotIndividual ($10/mo), Business ($19/user/mo), or Enterprise ($39/user/mo)Agent mode (autonomous tool calls) requires VS Code 1.90+ with Copilot Chat
Azure DevOpsBasic minimumMCP tools make live REST API calls — Stakeholder access is insufficient for pipeline, repo, and test plan operations
VS CodeFree

Agent mode availability: GitHub Copilot agent mode (required for autonomous MCP tool calls) is available on all paid Copilot plans in VS Code 1.90+.


Option C — M365 Copilot licence requirements ★ (recommended)

LicenceSKUNotes
Microsoft 365 CopilotM365 Copilot add-on (~$30/user/mo) on top of M365 E3/E5 or Business PremiumRequired for each end-user who will use the plugin
Microsoft 365 E3 or E5or Microsoft 365 Business PremiumBase plan required — M365 Copilot is an add-on, not standalone
Azure DevOps BasicIncluded with Visual Studio subscriptions or ~$6/user/moRequired for each ADO user — same as Options A/B
M365 Global Admin or Teams AdminIncluded in admin roles — no extra costRequired once for the initial plugin upload to the Admin Centre

Existing M365 E3/E5 tenants: if your organisation already has M365 E3 or E5, the only additional licence needed is the Microsoft 365 Copilot add-on per user.

Visual Studio subscribers: VS Enterprise and VS Professional subscriptions include an Azure DevOps Basic licence — no separate ADO licence purchase needed for those users.

Minimum licence set for a typical consulting team (Option C)

RoleM365 CopilotADO licenceNotes
Project Manager✅ RequiredBasic or StakeholderStakeholder covers PM read/create WI workflows; Basic needed for full feature set
Developer✅ RequiredBasicFull access to all skills
Admin (setup only)OptionalNot neededOnly needs M365 admin role to upload the plugin — no Copilot licence needed for the admin

Licence comparison summary

FeatureSkills-only (A)Local MCP (B)M365 Copilot (C)
Azure DevOps BasicRequiredRequiredRequired
GitHub Copilot (any plan)RequiredRequiredNot needed
Microsoft 365 Copilot add-onNot neededNot neededRequired
M365 E3/E5 or Business PremiumNot neededNot neededRequired (base plan)
VS CodeRequiredRequiredNot needed
M365 Admin roleNot neededNot neededRequired (one-time)
Estimated per-user cost~$10–39/mo~$10–39/mo~$36–69/mo

Pricing is indicative (USD, as of 2026). Check the Microsoft 365 pricing page and Azure DevOps pricing page for current rates in your region.


Option A — Skills-only (fastest, no server required)

Copy the skills/ folder into your VS Code prompts folder. The AI assistant follows the skill workflow and you paste ADO tool results manually.

  • Supported by: GitHub Copilot, Claude Code, Cursor, Continue.dev, Gemini CLI, JetBrains Junie
  • No additional setup required
.\package.ps1 -SkillsOnly   # copies skills/ to your VS Code prompts folder

Option B — Local MCP (fully autonomous, single user)

Connect VS Code to the Azure DevOps MCP server. The assistant calls tools autonomously.

Edit %APPDATA%\Code\User\mcp.json:

{
  "servers": {
    "ADO-MyOrg": {
      "url": "https://mcp.dev.azure.com/YOUR_ORG_NAME",
      "type": "http"
    }
  }
}

Replace YOUR_ORG_NAME with the segment after dev.azure.com/ in your browser URL. Authentication is handled automatically by VS Code via your existing Azure AD session. No PAT required.


Option C — M365 Copilot (recommended · org-wide · main usage) ★

Publishes the plugin to your Microsoft 365 tenant so every Copilot user in the organisation can use it without any local setup. This is the primary intended deployment mode for Project Managers and teams.

Prerequisites

RequirementNotes
Frontier preview programYour tenant must be enrolled — sign up here
Frontier enabled on your admin accountIn M365 admin center: Copilot → Settings → Frontier — must be toggled ON for the uploading account specifically
Microsoft 365 Copilot licencesRequired for end-users
Microsoft 365 admin centre accessGlobal Admin or Copilot Admin role
Azure DevOps organisation nameSegment after dev.azure.com/ in your browser
ado-cowork-plugin.zipProduced by package.ps1

If Cowork is not visible in your admin center, the Frontier toggle is not enabled on your account. Fix that first — the upload option will not appear without it.

Step 1 — Prepare manifest.json

Open manifest.json and replace the two placeholder values:

// Line to update — mcpServerUrl:
"mcpServerUrl": "https://mcp.dev.azure.com/YOUR_ORG_NAME"
//                                          ↑ replace with your ADO org name
// Line to update — referenceId (from Step 6b below):
"referenceId": "YOUR_OAUTH_REGISTRATION_ID"
//              ↑ paste the OAuth registration ID from Teams Developer Portal (Step 6b)
// Line to update — id (optional but recommended — generate a fresh GUID):
"id": "e8b2a3f1-7c4d-4f91-b2e0-ad01c0ca0001"
//     ↑ replace with: [guid]::NewGuid().ToString() in PowerShell

Finding your org name: open Azure DevOps in a browser → https://dev.azure.com/{orgName} — everything after dev.azure.com/ is your org name. Example: https://dev.azure.com/contoso → org name is contoso.

Step 2 — Add icon files (required by M365)

The manifest references color.png (192×192 px) and outline.png (32×32 px, white icon on transparent background).

Both icons are already included in the repository:

FileSizeDescription
color.png192×192 pxAzure blue (#0078d4) background with white ADO text
outline.png32×32 pxTransparent background with white A letter

To replace them with custom branded icons, simply overwrite these two files with your own PNGs at the same dimensions before running package.ps1.

Step 3 — Build the ZIP package

cd C:\path\to\ado-cowork-plugin
.\package.ps1
# Produces: ado-cowork-plugin.zip

All 88 ASKILL validation checks run automatically. The ZIP is only produced if all pass.

Step 4 — Upload to Microsoft 365 Admin Centre

For sideloading / testing (personal):

  1. Open https://admin.microsoft.com and sign in.
  2. Navigate to Agents → All agents (left navigation).
  3. Click the ... menu (top-right of the agent list) → Add agent.
  4. Upload ado-cowork-plugin.zip.
  5. Open Microsoft 365 Copilot → the plugin appears in the Sources & Skills panel.

For org-wide deployment:

  1. Open https://admin.microsoft.com and sign in.
  2. Navigate to Agents → All agents.
  3. Click the ... menu → Add agent → upload ado-cowork-plugin.zip.
  4. Once added, find ADO Cowork in the list, open it, and under Deploy to select Entire organisation or Specific users/groups → click Deploy.

Deployment propagates automatically — users do not need to install anything. The plugin appears in their Cowork Sources & Skills panel.

Can't find the upload option? Make sure Frontier is enabled on your admin account (Copilot → Settings → Frontier). Without it, Cowork-specific features are not visible.

Step 5 — Validate in Microsoft 365 Copilot

After deployment propagates, open Microsoft 365 Copilot (copilot.microsoft.com or the Copilot app in Teams) and type:

"Show me all organisations I have access to in Azure DevOps."

The ado-context skill should activate and call core_list_projects on your configured org. If the plugin is not responding, check:

  • Open the Sources & Skills panel in Cowork — the plugin should appear there
  • The plugin is enabled (toggle on in Sources & Skills)
  • The mcpServerUrl in manifest.json has your actual ADO org name (not contoso)
  • OAuthPluginVault is configured (see Step 6 below) — without it, mcp.dev.azure.com rejects the connection and Cowork will respond with "I don't have a way to connect to Azure DevOps from here"

Step 6 — Authentication (required for MCP tools to work)

Important: mcp.dev.azure.com requires a Bearer token for every request. The MCP connector will not function until you complete this step. Without it, Cowork cannot call any ADO MCP tools and will respond with "I don't have a way to connect to Azure DevOps from here".

6a — Create an Azure AD app registration
  1. Go to portal.azure.com → Azure Active Directory → App registrations → New registration
  2. Name: ADO Cowork Plugin — Supported account types: Single tenant
  3. Redirect URI: leave blank → Register
  4. API permissions → Add a permission → Azure DevOps → Delegated → tick user_impersonation → Add permissions
  5. Click Grant admin consent for your tenant
  6. Certificates & secrets → New client secret → set an expiry → Add
  7. Copy the secret value immediately (shown once only)
  8. Note down from the Overview page:
    • Application (client) ID
    • Directory (tenant) ID
6b — Register in Teams Developer Portal
  1. Go to dev.teams.microsoft.com → Tools → OAuth client registration → Register
  2. Fill in the form:
FieldValue
Registration nameADO Cowork
Base URLhttps://mcp.dev.azure.com
Restrict usage by organizationMy organization only
Restrict usage by Teams appExisting Teams app
Teams app IDe8b2a3f1-7c4d-4f91-b2e0-ad01c0ca0001 (your manifest id)
Client IDApplication (client) ID from step 6a
Client secretSecret value from step 6a
Authorization endpointhttps://login.microsoftonline.com/{tenantId}/oauth2/v2.0/authorize
Token endpointhttps://login.microsoftonline.com/{tenantId}/oauth2/v2.0/token
Refresh endpointhttps://login.microsoftonline.com/{tenantId}/oauth2/v2.0/token

Replace {tenantId} with your Directory (tenant) ID from step 6a.

  1. Click Save — copy the OAuth registration ID shown. That is your referenceId.
6c — Update manifest.json and redeploy

Open manifest.json and fill in both placeholders:

"mcpServerUrl": "https://mcp.dev.azure.com/YOUR_ORG_NAME",
"authorization": {
  "type": "OAuthPluginVault",
  "referenceId": "YOUR_OAUTH_REGISTRATION_ID"
}

Then bump "version" (e.g. "1.1.0" → "1.2.0"), run .\package.ps1, and update the plugin (Agents → All agents → ADO Cowork → Update).

After updating, Cowork will prompt each user to consent once; tokens are then stored and re-injected automatically on every call to mcp.dev.azure.com.

Updating the plugin

To push an updated version:

  1. Make changes to skills or manifest.
  2. Bump "version" in manifest.json (e.g. "1.0.0" → "1.1.0").
  3. Run .\package.ps1 to produce a new ZIP.
  4. In M365 Admin Centre → Agents → All agents → find ADO Cowork → Update.
  5. Upload the new ZIP. Users get the update automatically.

Prerequisites

See Licence requirements above for the full licence breakdown per option.

Technical requirementSkills-onlyLocal MCPM365 Copilot
VS Code 1.90+RequiredRequiredNot needed
GitHub Copilot ChatRequiredRequiredNot needed
Node.js / npmNot neededNot neededNot needed
Azure DevOps PATNot neededNot neededNot needed
Azure subscriptionNot neededNot neededNot needed
M365 Global / Copilot AdminNot neededNot neededRequired (one-time)
Frontier preview programNot neededNot neededRequired

Options B and C both use the Azure DevOps built-in MCP endpoint (https://mcp.dev.azure.com/{orgName}) — no npm package or Azure infrastructure to provision.


Quick start (Local MCP — Option B)

1. Add the server to VS Code mcp.json:

Edit %APPDATA%\Code\User\mcp.json (user-wide) or .vscode/mcp.json (workspace) and add the snippet from Option B above, replacing YOUR_ORG_NAME with your ADO organisation name (the segment after dev.azure.com/ in your browser URL).

2. Sign in to Azure:

VS Code uses your Azure AD session automatically (same account as the Azure extension). No PAT is required. If prompted, sign in via Azure: Sign In in the command palette.

3. Copy skills (optional — for Copilot skill routing):

.\package.ps1 -SkillsOnly
# or manually copy skills/ into your VS Code prompts folder

4. Try it:

"Show me all projects in my Azure DevOps organisation."


Security notes

  • The ADO MCP endpoint (https://mcp.dev.azure.com/{orgName}) enforces Azure AD authentication at the platform level. No anonymous access is possible.
  • VS Code (Option B) authenticates using your existing Azure AD session — no PAT, no service principal, no Key Vault required.
  • M365 Copilot (Option C) uses authorization.type: None — the ADO MCP server still enforces Azure AD authentication per user at the platform level; secrets are never in source code or committed files. Upgrade to OAuthPluginVault for production (see Step 6).
  • See SECURITY.md for least-privilege PAT scope guidance if your organisation requires PAT-based access instead of Azure AD.

Contributing

See CONTRIBUTING.md.

License

MIT — see LICENSE.

Ver o original no GitHub

Bom para

Relacionados