How do I install the Azure Deploy Ms skill?

Run npx skillmds@latest add jantoniofc/azure-deploy-ms in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Azure Deploy Ms safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Azure Deploy Ms?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Azure Deploy Ms free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Azure Deploy Ms?

JantonioFC (@jantoniofc) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Azure Deploy Ms by jantoniofc — Agent Skill

Name: Azure Deploy Ms
Rating: 4.2 (5 reviews)
Author: JantonioFC

Azure Deploy Ms

Execute deployment to Azure. Final step after preparation and validation. Runs azd up, azd deploy, or infrastructure provisioning commands. USE FOR: run azd up, run azd deploy, execute deployment, provision infrastructure, push to production, go live, ship it, deploy web app, deploy contai...

JantonioFC Updated Sep 8, 2026 6 repo stars

File contents

Azure Deploy

AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE

PREREQUISITE: The azure-validate skill MUST be invoked and completed with status Validated BEFORE executing this skill.

⛔ STOP — PREREQUISITE CHECK REQUIRED Before proceeding, verify BOTH prerequisites are met:

azure-prepare was invoked and completed → .azure/plan.md exists

azure-validate was invoked and passed → plan status = Validated

If EITHER is missing, STOP IMMEDIATELY:

No plan? → Invoke azure-prepare skill first

Status not Validated? → Invoke azure-validate skill first

⛔ DO NOT MANUALLY UPDATE THE PLAN STATUS

You are FORBIDDEN from changing the plan status to Validated yourself. Only the azure-validate skill is authorized to set this status after running actual validation checks. If you update the status without running validation, deployments will fail.

DO NOT ASSUME the app is ready. DO NOT SKIP validation to save time. Skipping steps causes deployment failures. The complete workflow ensures success:

azure-prepare → azure-validate → azure-deploy

Triggers

Activate this skill when user wants to:

Deploy their application to Azure
Publish, host, or launch their app
Push updates to existing deployment
Run azd up or az deployment
Ship code to production
Deploy Azure Functions to the cloud

Rules

Run after azure-prepare and azure-validate
.azure/plan.md must exist with status Validated
Pre-deploy checklist required — Pre-Deploy Checklist
⛔ Destructive actions require ask_user — global-rules

Steps

#	Action	Reference
1	Check Plan — Read `.azure/plan.md`, verify status = `Validated` AND Validation Proof section is populated	`.azure/plan.md`
2	Pre-Deploy Checklist — MUST complete ALL steps	Pre-Deploy Checklist
3	Load Recipe — Based on `recipe.type` in `.azure/plan.md`	recipes/README.md
4	Execute Deploy — Follow recipe steps	Recipe README
5	Handle Errors — See recipe's `errors.md`	—
6	Verify Success — Confirm deployment completed and endpoints are accessible	—

⛔ VALIDATION PROOF CHECK

When checking the plan, verify the Validation Proof section (Section 7) contains actual validation results with commands run and timestamps. If this section is empty, validation was bypassed — invoke azure-validate skill first.

SDK Quick References

Azure Developer CLI: azd
Azure Identity: Python | .NET | TypeScript | Java

MCP Tools

Tool	Purpose
`mcp_azure_mcp_subscription_list`	List available subscriptions
`mcp_azure_mcp_group_list`	List resource groups in subscription
`mcp_azure_mcp_azd`	Execute AZD commands

References

Troubleshooting - Common issues and solutions

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

---name: azure-deploy-msdescription: Execute deployment to Azure. Final step after preparation and validation. Runs azd up, azd deploy, or infrastructure provisioning commands. USE FOR: run azd up, run azd deploy, execute deployment, provision infrastructure, push to production, go live, ship it, deploy web app, deploy contai...license: MIT---# Azure Deploy> **AUTHORITATIVE GUIDANCE — MANDATORY COMPLIANCE**>> **PREREQUISITE**: The **azure-validate** skill **MUST** be invoked and completed with status `Validated` BEFORE executing this skill.> **⛔ STOP — PREREQUISITE CHECK REQUIRED**> Before proceeding, verify BOTH prerequisites are met:>> 1. **azure-prepare** was invoked and completed → `.azure/plan.md` exists> 2. **azure-validate** was invoked and passed → plan status = `Validated`>> If EITHER is missing, **STOP IMMEDIATELY**:> - No plan? → Invoke **azure-prepare** skill first> - Status not `Validated`? → Invoke **azure-validate** skill first>> **⛔ DO NOT MANUALLY UPDATE THE PLAN STATUS**>> You are **FORBIDDEN** from changing the plan status to `Validated` yourself. Only the **azure-validate** skill is authorized to set this status after running actual validation checks. If you update the status without running validation, deployments will fail.>> **DO NOT ASSUME** the app is ready. **DO NOT SKIP** validation to save time. Skipping steps causes deployment failures. The complete workflow ensures success:>> `azure-prepare` → `azure-validate` → `azure-deploy`## TriggersActivate this skill when user wants to:- Deploy their application to Azure- Publish, host, or launch their app- Push updates to existing deployment- Run `azd up` or `az deployment`- Ship code to production- Deploy Azure Functions to the cloud## Rules1. Run after azure-prepare and azure-validate2. `.azure/plan.md` must exist with status `Validated`3. **Pre-deploy checklist required** — [Pre-Deploy Checklist](references/pre-deploy-checklist.md)4. ⛔ **Destructive actions require `ask_user`** — [global-rules](references/global-rules.md)---## Steps| # | Action | Reference ||---|--------|-----------|| 1 | **Check Plan** — Read `.azure/plan.md`, verify status = `Validated` AND **Validation Proof** section is populated | `.azure/plan.md` || 2 | **Pre-Deploy Checklist** — MUST complete ALL steps | [Pre-Deploy Checklist](references/pre-deploy-checklist.md) || 3 | **Load Recipe** — Based on `recipe.type` in `.azure/plan.md` | [recipes/README.md](references/recipes/README.md) || 4 | **Execute Deploy** — Follow recipe steps | Recipe README || 5 | **Handle Errors** — See recipe's `errors.md` | — || 6 | **Verify Success** — Confirm deployment completed and endpoints are accessible | — |> **⛔ VALIDATION PROOF CHECK**>> When checking the plan, verify the **Validation Proof** section (Section 7) contains actual validation results with commands run and timestamps. If this section is empty, validation was bypassed — invoke **azure-validate** skill first.## SDK Quick References- **Azure Developer CLI**: [azd](references/sdk/azd-deployment.md)- **Azure Identity**: [Python](references/sdk/azure-identity-py.md) | [.NET](references/sdk/azure-identity-dotnet.md) | [TypeScript](references/sdk/azure-identity-ts.md) | [Java](references/sdk/azure-identity-java.md)## MCP Tools| Tool | Purpose ||------|---------|| `mcp_azure_mcp_subscription_list` | List available subscriptions || `mcp_azure_mcp_group_list` | List resource groups in subscription || `mcp_azure_mcp_azd` | Execute AZD commands |## References- [Troubleshooting](references/troubleshooting.md) - Common issues and solutions## When to UseThis skill is applicable to execute the workflow or actions described in the overview.

Frequently asked questions