<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure Developer CLI on Top AI Skills</title><link>https://topaiskills.com/tags/azure-developer-cli/</link><description>Recent content in Azure Developer CLI on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 12 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/azure-developer-cli/index.xml" rel="self" type="application/rss+xml"/><item><title>azure-validate: The Gatekeeper Skill for Azure Deployments</title><link>https://topaiskills.com/skills/automation/azure-validate/</link><pubDate>Sat, 12 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/automation/azure-validate/</guid><description>&lt;p&gt;Most Azure failures surface at deploy time, when they cost hours. Microsoft&amp;rsquo;s azure-validate skill (v1.2.2) exists to move that discovery earlier — it runs nine validation gates against your plan, your infrastructure code, and your role assignments before anything ships. I read the full SKILL.md, the workflow script, the role-verification reference, and the azd recipe in &lt;a href="https://github.com/microsoft/azure-skills" rel="nofollow" target="_blank"&gt;microsoft/azure-skills&lt;/a&gt;. The 2026-09-12 skills.sh scrape put it at 576,757 installs, rank 24. The deploy trio — azure-prepare 577,556, azure-deploy 577,309, azure-validate 576,757 — each grew by roughly 12,000 installs in the six days since our last scrape, gaps between them barely moving.&lt;/p&gt;</description></item><item><title>azure-prepare: The Plan-First Azure Deployment Skill</title><link>https://topaiskills.com/skills/automation/azure-prepare/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/automation/azure-prepare/</guid><description>&lt;p&gt;The fix for most Azure deployment failures is a file on disk. Microsoft&amp;rsquo;s azure-prepare skill (v1.3.2, 565.5K installs) writes &lt;code&gt;.azure/deployment-plan.md&lt;/code&gt; into your workspace as its very first action and refuses to generate any infrastructure until you approve it. The classic failure sequence — wrong region, exhausted quota, secrets in templates — becomes visible before it costs you anything. I read the full SKILL.md plus the plan-template, recipe-selection, specialized-routing, and security references in &lt;a href="https://github.com/microsoft/azure-skills" rel="nofollow" target="_blank"&gt;microsoft/azure-skills&lt;/a&gt;. On the 2026-09-06 skills.sh scrape, it held 565,497 installs, the second-highest count in the pack.&lt;/p&gt;</description></item><item><title>Deploy to Azure Without Surprises: The 10-Step azure-deploy Runbook</title><link>https://topaiskills.com/tutorials/guides/azure-deploy-procedural/</link><pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/azure-deploy-procedural/</guid><description>&lt;p&gt;Your Container App revision hangs in provisioning for fifteen minutes, then fails: the image-pull permission exists on paper but had not propagated. Failures like that are why Microsoft&amp;rsquo;s azure-deploy skill (v1.2.1, 565.4K installs) refuses to run until validation has written receipts, and why its runbook puts a propagation gate between provisioning and image deployment. I read the SKILL.md, its 508-line pre-deploy checklist, and the troubleshooting reference in &lt;a href="https://github.com/microsoft/azure-skills" rel="nofollow" target="_blank"&gt;microsoft/azure-skills&lt;/a&gt;. The 2026-09-06 skills.sh scrape put it at 565,378 installs — fifty short of its prepare sibling.&lt;/p&gt;</description></item></channel></rss>