<p>I don't understand why a separate resource group is created for all of the infrastructure associated with an ACS cluster, and not the Resource Group I specify when creating the cluster? This leave my defined Resource Group with one lonely entity (the ACS Cluster definition) and a whole new Resource Group whose name I don't control. Not a fan of this.</p>
<p>I am currently using the Azure CLI to create my ACS cluster, so I'm &quot;guessing&quot; if I went the ARM route I'd have more control. Still, where does this limitation reside and why?</p>
<p>Here's my CLI command:</p>
<pre><code>az acs create -n=int-madraskube -g=internal-acs
--orchestrator-type=kubernetes  --agent-count=2 --generate-ssh-keys --windows --admin-username={myadmin} --admin-password={mypassword} --service-principal={sp_guid} --client-secret={secret_guid}
</code></pre>
<p>And I end up with two resource groups:</p>
<blockquote>
<p>internal-acs</p>
<p>internal-acs_int-madraskube_westus2</p>
</blockquote>

<p>This is the new design of the ACS (v2) in some selected regions. In the past (the v1), the created resources are in the same resource group as container service resource is. It makes it really hard to clean up those resources when you delete the container service resource. With those being in a new resource group (preferably locked down and invisible, but not possible right now), it's one step closer to managed service.</p>

<p>For more info about ACS v2, <a href="https://github.com/Azure/ACS" rel="nofollow noreferrer">https://github.com/Azure/ACS</a> </p>
