<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure Functions on Top AI Skills</title><link>https://topaiskills.com/tags/azure-functions/</link><description>Recent content in Azure Functions on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 04 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/azure-functions/index.xml" rel="self" type="application/rss+xml"/><item><title>azure-upgrade: Assess, Then Migrate Azure Plans and SKUs</title><link>https://topaiskills.com/skills/automation/azure-upgrade/</link><pubDate>Fri, 04 Sep 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/automation/azure-upgrade/</guid><description>&lt;p&gt;Most Azure upgrades get attempted as a chain of CLI commands typed from memory. Microsoft&amp;rsquo;s azure-upgrade skill refuses that pattern: it produces an assessment report before it changes anything, and it documents rollback before it executes. I read the current SKILL.md (v1.2.1, MIT), the workflow-details and global-rules files, plus the functions, Redis, and Java scenario references, then pulled install numbers off the skills.sh leaderboard on 2026-09-04.&lt;/p&gt;
&lt;h2 id="the-seven-step-flow-gates-every-upgrade"&gt;The Seven-Step Flow Gates Every Upgrade&lt;/h2&gt;
&lt;p&gt;The pipeline runs Identify → Assess → Pre-migrate → Upgrade → Validate → Ask User → hand off. No phase is skippable, and a failure inside any phase stops the run: log it in &lt;code&gt;upgrade-status.md&lt;/code&gt;, do not proceed, tell the user what broke, offer retry or rollback.&lt;/p&gt;</description></item></channel></rss>