This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 5%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EW%3C/text%3E%3C/svg%3E)
"Recommended best practice is to associate resource groups, and the resources they contain, with an Azure subscription."
So in what situation or scenario that I would not associate a RG to a subscription? And what impact would that cause?
Want to tag this with 'Azure Resource Manager', but it is not available!
Hi,
An Azure Resource Group is always associated with a subscription.
https://learn.microsoft.com/en-us/rest/api/resources/resource-groups/create-or-update?tabs=HTTP
Please click Accept Answer if the above answers your question or add a comment if you need additional assistance/clarification.
Thanks.
-TP
@Wez As you have noticed, the documentation page you linked to is incorrect. I posted reference to the underlying REST API so you could verify for yourself (if desired) that subscription id is in fact required for a resource group to exist.
Please Accept my answer if you don't need any additional assistance and/or have more questions.
Thank you.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 45%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAO%3C/text%3E%3C/svg%3E)
Good question Wez, It is generally recommended to associate resource groups with an Azure subscription for effective resource management and governance. However, there may be situations where it is not necessary to do so, such as creating temporary or experimental environments or managing shared services or applications used by multiple subscriptions. Nevertheless, not associating a resource group with a subscription can create management and governance challenges, such as difficulty in tracking costs, monitoring resource usage, managing permissions, and applying policies consistently across different resources. Let me know if this clears your doubt
@Ayomide Oluwaga A resource group requires a subscription id. If you try to create a resource group without a subscription id, the operation will fail.
That is obviously true. I assume he knows that but has not structured the question properly, he probably wishes to know about the effect of having the resources and resource groups in different subscriptions.
Read the article from the link please, that statement is directly quoted from it.
It implies RG does not need an Azure subscription!
Either these "contributors" know something we do not, or no expert has spent time to revise these documents!
I don't want to drill into this, but documents suppose to be precise.
Hmm...I see Wez,
I went through the documentation in the link, I believe the issue here is the English construction used by the contributors, please note that a resource group will always have a subscription regardless ND cannot be created without being linked to one.