LabscoMCP early access ↗
REPO PACKAGEOFFICIAL

microsoft azure-skills

microsoft · publisher1,539 GitHub starsMIT · Listed as freegithub.com/microsoft/azure-skills

LABSCO SUMMARY

Summary

Microsoft's own Azure Skills Plugin installs most of the skills listed here (the rest come from smaller plugins in the same repository) alongside the Azure MCP Server's 200-plus tools and Foundry MCP in one step — it is a full Azure operating layer, not a skills library meant to be read on its own.

The skills split into two clusters. General Azure lifecycle work covers azure-prepare, azure-validate, azure-deploy, and azure-upgrade for an azd-based deployment end to end, azure-enterprise-infra-planner and azure-kubernetes for landing-zone and AKS design, and azure-diagnostics, azure-compliance, azure-resource-lookup, and azure-resource-visualizer for troubleshooting, security, inventory, and architecture diagrams once something is already running. Spend sits in a separate plugin in the same repository, azure-cost, whose four skills (cost-analysis, cost-estimation, cost-governance, cost-optimization) are listed here too. A second, Azure OpenAI and Foundry-specific cluster covers model deployment split by control level (preset, customize, capacity, deploy-model), fine-tuning (finetuning), and a single router across the rest of Foundry's agent and evaluation surface (microsoft-foundry). A handful of narrower skills sit outside both — azure-storage, azure-kusto, azure-messaging, azure-ai, azure-aigateway, entra-app-registration, entra-agent-id, and a Python-specific python-appservice-deploy.

This is for a team that has already decided to build on Azure and wants an agent calling real Azure and Foundry APIs instead of reciting documentation — most of these skills exist to route a request to the Azure MCP Server or Foundry MCP, and assume that live wiring is already in place. Without an Azure subscription, or without granting an agent az login credentials, none of them does anything on its own.

READ MORE

What it costs before any of it works.

Install requires Node.js 18+, the Azure CLI authenticated with az login, and, for the azd-based deployment skills, the Azure Developer CLI authenticated separately. Most of the skills listed here need an Azure account and credentials before they're useful, several more talk to Azure or Foundry MCP directly, and only a few run on guidance alone with nothing live behind them.

The skills and the MCP tools are written to be read together, not separately.

azure-compute's own description tells the agent to prefer itself "over mcp__azure__get_azure_bestpractices for VM create intents" and use its own sub-commands instead — several skills route around a same-named MCP tool this way, so installing only the MCP server, or only the skills, changes what the agent actually does compared to installing both as the plugin intends.