Skip to content

Investigate plan to deprecate/phase out ARM operations in Azure MCP tools in favour of ARM MCP Server integration #3142

Open

Description

@msalaman

Release Tracker: microsoft/mcp-pr#691 (Theme 3.2)
Parent Epic: #3438 (Azure Service and Scenario Coverage)
Priority: P2 (Planned Investigation and Phased Migration)

Objective

Investigate overlapping Azure Resource Manager (ARM) operations in Azure MCP tools, establish replacement coverage through ARM MCP Server integration, and define a phased migration plan that reduces tool surface area without regressing existing customer workflows.

Note: This issue tracks an investigation and evidence-based phased migration plan, not an unconditional blanket removal of all ARM-related tools.

Scope

  • Inventory overlapping ARM operations currently implemented across Azure MCP toolsets (such as generic resource lookups, resource group management, and deployment operations).
  • Evaluate functional parity and replacement coverage provided by the ARM MCP Server.
  • Use production tool usage telemetry (microsoft/mcp-pr#729) to assess customer reliance on candidate ARM commands before proposing deprecations.
  • Define a phased migration schedule with backward-compatible command aliases, deprecation notices, and transition documentation.

Related Issues and Dependencies

  • Tool catalog rationalization and command consolidation: microsoft/mcp#3987
  • Related ARM tool tracking: microsoft/mcp#3764
  • Usage telemetry dashboard input: microsoft/mcp-pr#729

4.0 Exit Criteria

  • Overlap inventory and ARM MCP Server parity mapping documented in this issue with an explicit go/no-go migration scope.
  • Phased deprecation and alias schedule approved with zero regression to supported customer workflows.
  • Migration guidance and updated command references published for any commands scheduled for retirement.

Activity

  1. self-assigned this
    on Jul 23, 2026
  2. changed the title [-]Investigate plan to deprecate/phase out ARM operations in our MCP tools in favour of ARM MCP Server integration[/-] [+]Investigate plan to deprecate/phase out ARM operations in Azure MCP tools in favour of ARM MCP Server integration[/+] on Jul 23, 2026
  3. github-actions commented on Jul 23, 2026

    @github-actions
    Contributor

    Triage Summary

    Classification: engineering item — This is an internal architecture investigation/planning issue to evaluate deprecating ARM operations in Azure MCP tools in favor of ARM MCP Server integration. No broken behavior; this is proactive maintenance/modernization work.

    Labels added:

    • tools-ARM — directly relates to ARM Resource Management tools
    • server-Azure.Mcp — affects the Azure MCP Server

    Issue Type: Task — internal engineering investigation with no end-user feature request or bug.

    Priority: Medium — important architectural direction with clear impact on the toolset, but not broadly blocking current workflows or an active regression.

    Owner recommendation: msalaman (the issue author) appears to be driving this investigation already and is a contributor with context on the ARM tooling. Confidence is moderate — if this requires broader architectural sign-off, the Azure MCP core team should be looped in.

    Generated by Issue Triage Agent for #3142 · 26.2 AIC · ⌖ 5.58 AIC · ⊞ 5.7K · ◷

  4. g2vinay commented on Jul 23, 2026

    @g2vinay
    Contributor

    The goal of this issue is to investigate which ARM tools we can now deprecate/phase out in favor of ARM MCP Server.
    This will help reduce the tool count.
    The work involve coming up with a phased strategy so we don't regress/break our existing users.

  5. added this to the Backlog milestone on Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions