C✳CODEZ.WIN
🌐 English

Localized reading guide

azure-deployPurpose, usage and source

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

Source retrieved:

Source repository
microsoft/skills
SKILL.md
.github/plugins/azure-skills/skills/azure-deploy/SKILL.md
Repository stars
3,157
Repository updated
2026-10-31
Categories
Cloud
Last collected

License: License file needs review

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.

How the upstream workflow works

Steps

> ⛔ URL FORMAT RULE > > When presenting endpoint URLs to the user, you MUST always use fully-qualified URLs with the https:// scheme (e.g. https://myapp.azurewebsites.net, not myapp.azurewebsites.net). Many Azure CLI commands return bare hostnames without a scheme — always prepend https:// before presenting them. > ⛔ 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.

Upstream passage · L57 ↗

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/deployment-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.

Upstream passage · L10 ↗

Triggers

Activate this skill when user wants to: Execute deployment of an already-prepared application (azure.yaml and infra/ exist)

Upstream passage · L34 ↗

Requirements and setup

No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
00d66a64919edca5bca2c673373444e36a4b5461
Source SHA-256
d44c25fde43a5ccfa4c16975ea75518e1d963e1c84f1da2545fb970ef79dd066
Back to the full Skill catalog