<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Governance on Incredible Technology, Incredibly Simple</title><link>https://damianflynn.com/categories/governance/</link><description>Recent content in Governance 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/categories/governance/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><item><title>Azure Enterprise Agreement: Delegating Roles for Subscription Creation</title><link>https://damianflynn.com/posts/azure-ea-delegating-privileges/</link><pubDate>Fri, 24 Apr 2020 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/azure-ea-delegating-privileges/</guid><description>&lt;h1 class="relative text-5xl font-semibold leading-tense text-secondary-500 mb-4 -ml-px" id="azure-enterprise-agreement-privilages-delegating"&gt;&lt;a href="#azure-enterprise-agreement-privilages-delegating" class="header-mark" aria-label="Header mark for 'Azure Enterprise Agreement, Privilages Delegating'"&gt;&lt;/a&gt;
 &lt;div id="azure-enterprise-agreement-privilages-delegating" class="absolute -top-28"&gt;&lt;/div&gt;
 Azure Enterprise Agreement, Privilages Delegating
&lt;/h1&gt;
&lt;p&gt;Under the Enterprise agreement we have some different Persona&amp;rsquo;s, which have quite different abilities and operations upon which they are permitted to preform.&lt;/p&gt;
&lt;p&gt;Billing account simplifies billing for your organization while providing you enhanced billing and cost management capabilities. The following diagram explains how billing is organized in the new billing account.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/mca-setup-account" target="_blank" rel="noopener noreferrer"&gt;https://learn.microsoft.com/en-us/azure/cost-management-billing/manage/mca-setup-account&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;





 
 
 
 


&lt;figure class="my-8"&gt;
 &lt;img src="https://damianflynn.com/posts/azure-ea-delegating-privileges/az-billing-ea_privilege_delegation.new_structure.png" alt="" class="w-full rounded-lg" /&gt;
 
&lt;/figure&gt;
&lt;/p&gt;
&lt;h2 class="relative text-3xl font-bold leading-tight text-secondary-500 mb-2 mt-12 -ml-px"&gt;
 &lt;div id="roles-and-accounts" class="absolute -top-28"&gt;&lt;/div&gt;
 Roles and Accounts
&lt;/h2&gt;
&lt;p&gt;Before we being the process of delegation, It is important to understand this Hierarchy, so we can correctly proceed with the technical work ahead.&lt;/p&gt;</description></item><item><title>Azure Policy as Code: Escaping Quotes in ARM Templates</title><link>https://damianflynn.com/posts/defining-policy-as-code-with-arm-templates/</link><pubDate>Tue, 20 Nov 2018 00:00:00 +0000</pubDate><guid>https://damianflynn.com/posts/defining-policy-as-code-with-arm-templates/</guid><description>&lt;p&gt;My colleagues and friends &lt;a href="https://blog.tyang.org/2018/06/06/using-arm-templates-to-deploying-azure-policy-definitions-that-requires-input-parameters/" target="_blank" rel="noopener noreferrer"&gt;Tao Yang&lt;/a&gt; , and &lt;a href="https://cloudadministrator.net/2018/07/17/defining-input-parameters-for-policy-definitions-in-arm-template/" target="_blank" rel="noopener noreferrer"&gt;Stanislav Zhelyazkov&lt;/a&gt; have both recently posts interesting topics on how to implement your Azure Policy as Code which I strongly recommend you take a few moments to review&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://blog.tyang.org/2018/06/06/using-arm-templates-to-deploying-azure-policy-definitions-that-requires-input-parameters/" target="_blank" rel="noopener noreferrer"&gt;Using ARM Templates to deploy azure policy definitions that require input parameters&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://cloudadministrator.net/2018/07/17/defining-input-parameters-for-policy-definitions-in-arm-template/" target="_blank" rel="noopener noreferrer"&gt;Defining input parameters for policy definitions in ARM Templates&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 class="relative text-3xl font-bold leading-tight text-secondary-500 mb-2 mt-12 -ml-px"&gt;
 &lt;div id="improving-readability" class="absolute -top-28"&gt;&lt;/div&gt;
 Improving Readability
&lt;/h2&gt;
&lt;p&gt;Both of these topics address the core of the challenges we face when approaching policy as an Infrastructure as Code problem. However, one of the things that is lost in the translation is the readability of the templates which they are deploying.&lt;/p&gt;</description></item></channel></rss>