microsoft / microsoft/mcp

[BUG] Guidance needed to configure Azure MCP (Extension version) as on the vs code allowlist

Open
#3,615 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Azure.Mcp.Server customer-reported needs-team-triage packages-VSIX question server-Azure.Mcp
Dominant language
C#
Stars
3.7k
Forks
624
Avg merge
2d 20h
Merged PRs (30d)
220

Description

### Describe the bug

Hello team,

In our scenario, MCP servers are not allowed by default in vs code ghcp. Unless present on the allowlist.
https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-mcp-usage/configure-enterprise-allowlist

The allowlist requires specific run commands to be defined, but currently does not support an extensionId to whitelist an MCP server.

Is there a way to whitelist the Azure MCP so that it works for users who installed it from the marketplace? So that users can use Azure MCP from the marketplace within this environment.

### Expected behavior

Azure MCP Extension version works via the AllowList

### Actual behavior

AllowList does not support extensionId

### Reproduction Steps

Disable MCP access, work with allowlist, install from marketplace.

### Environment

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked GitHub Copilot enterprise allowlist documentation, then reproduce the issue with MCP access disabled by default, an allowlist enabled, and the Azure MCP marketplace extension installed. Done means establishing whether the extension can be allowlisted by extensionId and documenting the supported configuration or confirmed limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, vscode
Domain
cloud, developer-experience, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.