<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bicep on Top AI Skills</title><link>https://topaiskills.com/tags/bicep/</link><description>Recent content in Bicep on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/bicep/index.xml" rel="self" type="application/rss+xml"/><item><title>azure-enterprise-infra-planner: Gated 7-Phase Azure IaC</title><link>https://topaiskills.com/skills/automation/azure-enterprise-infra-planner/</link><pubDate>Sat, 05 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/automation/azure-enterprise-infra-planner/</guid><description>&lt;p&gt;Most Azure IaC gets written like a rough draft: resource names invented on the spot, secrets in variables, public endpoints everywhere because private ones are work. Microsoft&amp;rsquo;s azure-enterprise-infra-planner treats that draft as a failure state. It runs a 7-phase pipeline that refuses to deploy until the generated code passes a security scan, and it forces the agent to show you the receipts. I read the current SKILL.md (v1.4.1, MIT) plus the workflow, referenced-workload, and WAF checklist references in &lt;a href="https://github.com/microsoft/azure-skills" rel="nofollow" target="_blank"&gt;microsoft/azure-skills&lt;/a&gt;, then pulled install numbers off the skills.sh leaderboard on 2026-09-05: rank #121, 399.3K installs.&lt;/p&gt;</description></item></channel></rss>