<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Azure Policy on Cloudkaramchari</title><link>https://www.cloudkaramchari.com/tags/azure-policy/</link><description>Recent content in Azure Policy on Cloudkaramchari</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>cloudkaramchari</copyright><lastBuildDate>Mon, 19 Oct 2026 23:00:00 +0530</lastBuildDate><atom:link href="https://www.cloudkaramchari.com/tags/azure-policy/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Blueprints Retirement: What Breaks on October 31 and How to Migrate to Deployment Stacks</title><link>https://www.cloudkaramchari.com/blog/azure-blueprints-retirement-october-31-deadline-migrate-to-deployment-stacks/</link><pubDate>Mon, 19 Oct 2026 23:00:00 +0530</pubDate><guid>https://www.cloudkaramchari.com/blog/azure-blueprints-retirement-october-31-deadline-migrate-to-deployment-stacks/</guid><description>
&lt;h1 id="azure-blueprints-retirement-what-breaks-on-october-31-and-how-to-migrate-to-deployment-stacks">Azure Blueprints Retirement: What Breaks on October 31 and How to Migrate to Deployment Stacks&lt;/h1>
&lt;p>If a subscription-vending pipeline in your tenant still runs &lt;code>az blueprint assignment create&lt;/code> or &lt;code>New-AzBlueprintAssignment&lt;/code> to stamp policies, role assignments and a locked resource group onto every new subscription, it has twelve days left. On &lt;strong>October 31, 2026&lt;/strong> Azure Blueprints stops accepting new assignments and freezes existing definitions. That is phase two of a retirement that ends on &lt;strong>January 31, 2027&lt;/strong>, when the service stops responding, unexported definitions are deleted, and every blueprint lock disappears from the resources it was protecting.&lt;/p></description></item></channel></rss>