<p>When a new <em>Kubernetes service</em> is created in Azure a new <em>resource group</em> with a similar name to the cluster is also created. In this &quot;resource group&quot; all the disks etc. which are created from Kubernetes are stored.
Is there a way I can avoid that this sub-<em>resource group</em> is created and that all resources created from Kubernetes are put in the <em>resource group</em> where the cluster is located?</p>
<p>The background is that our Ops team would like to structure the <em>resource groups</em> and therefore the generated <em>resource group</em> structure is not preferred. Note that the information that this is not possible or at least not without a significant amount of effort would also be very useful for me.</p>

Manuel 
<p>According to the <a href="https://learn.microsoft.com/en-us/azure/aks/faq#can-i-provide-my-own-name-for-the-aks-node-resource-group" rel="nofollow noreferrer">documentation</a>, you can't create the cluster resources inside the resource group where the cluster is located.  The only option available is to provide a name for the second resource group at cluster creation.</p>
