Skills

Install Azure Skills with apm so a compatible Agent can do real Azure work

For people who want a compatible coding Agent to do real Azure work, not generic cloud advice; the preconditions are Node.js 18+ on this machine and Azure CLI already logged in with az login, and the only path is apm install microsoft/azure-skills.

Official source · azure-skills

Install

apm install microsoft/azure-skills

Who this is for

This guide is for people who need a compatible coding Agent to do real Azure work, not just give generic cloud advice. Officially it is written as Azure Skills Plugin: it packages Azure expertise together with MCP-backed execution.

Before you start, confirm both preconditions at the same time: this machine has Node.js 18+ on PATH (npx is used to start MCP servers), and Azure CLI is installed and az login is complete. Do not start installing if either condition is missing.

The page states that the same set of Azure capabilities can be used in GitHub Copilot in VS Code, Copilot CLI, Claude Code, and other compatible hosts. This is a multi-host description, not an exclusive list, and do not generalize the apm install into a marketplace install on a platform that only supports manual copy.

First try in 3 minutes

Use only the recommended install command given on the page:

apm install microsoft/azure-skills

Precondition: Node.js 18+ and az login are already satisfied, and the current environment is one of the compatible coding Agents named on the page. Treat the install location as whatever this official command itself does; the excerpt does not name a plugin directory or skill file path, so do not rewrite the command, and do not assume it writes into a directory that does not appear.

Side-effect confirmation point: after install the plugin connects Azure MCP Server, giving the Agent 200+ structured tools across 40+ Azure services; npx will also start MCP servers. This is not a read-only documentation pack. If you have not yet run az login, or the current host is not the compatible host you intend to use, stop first. Confirm, then run the install.

Success signal: apm install microsoft/azure-skills finishes normally. The excerpt does not name a specific tool to run after install or a command to inspect a subscription, so do not use “list tools/subscription” as the completion criterion. Then do only a check in the already-compatible Agent: confirm it now does real Azure work as Azure Skills Plugin, and is not still giving generic cloud advice. Do not create, modify, or delete any resources. If it is about to call an unnamed tool that would change resources, stop at the confirmation point.

Use cases

Case 1: Install as-is on a machine that already meets the preconditions. Confirm Node.js 18+ is on PATH, Azure CLI has already run az login, then run apm install microsoft/azure-skills. The evidence covers this install command, and the Node/npx and Azure CLI preconditions. The completion criterion stops at a successful command return. The page does not write uninstall, upgrade, or an on-disk directory; do not add those.

Case 2: Before installing, confirm host compatibility and understand the MCP side effect. The evidence states Multi-host support covers GitHub Copilot in VS Code, Copilot CLI, Claude Code, and other compatible hosts; after install it connects Azure MCP Server and 200+ tools. Do not call a specific unnamed Azure tool on the first try. The observable success signal is: you can check whether your own host falls inside that description, and you accept that “install means introducing MCP-backed execution”. Do not read “200+ tools” as authorization to change production resources directly, and do not invent steps to list tools or inspect a subscription.

Boundaries

The main install path is only apm install microsoft/azure-skills. Do not install if Node.js 18+ is missing or az login has not been run. The listed hosts are not the only usable range. MCP tools can do real Azure work; any create, change, or delete must be confirmed first. On-disk directory, uninstall, individual tool names and parameters do not appear in the excerpt and cannot be treated as safety conclusions.