<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Landing Zones on Incredible Technology, Incredibly Simple</title><link>https://damianflynn.com/tags/landing-zones/</link><description>Recent content in Landing Zones on Incredible Technology, Incredibly Simple</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://damianflynn.com/tags/landing-zones/index.xml" rel="self" type="application/rss+xml"/><item><title>Azure Quota Groups: Recycling Capacity You Already Own</title><link>https://damianflynn.com/posts/azure-quota-groups-recycling-capacity-you-already-own/</link><pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/azure-quota-groups-recycling-capacity-you-already-own/</guid><description>&lt;p&gt;The most expensive vCPU in Azure is the one you already had approved, gave back by accident, and now have to ask for again. That is exactly what happens every time an old subscription is cancelled. Years of quota increases, each one a support ticket, a business justification and a few days of waiting, disappear with the subscription. Meanwhile the brand-new subscription that replaces it starts life with default limits, in a region where capacity is tight, and the first deployment into it fails with a quota error the platform team then has to chase.&lt;/p&gt;</description></item></channel></rss>