I'd like to know what's the best practice and the recommended Azure architecture for Azure Governance & structuring?
As at the moment, I'm currently working in the company where the existing Tenant (the parent company) have three subscriptions like:
PROD-Subscription - rg_Product1 [Product1Owners & Product1Contributor] - rg_Product2 [Product2Owners & Product2Contributor] - rg_Product3 [Product3Owners & Product3Contributor] ... TEST-Subscription - rg_Test-Product1 [Test-Product1Owners & Product1Contributor] - rg_Test-Product2 [Test-Product2Owners & Product2Contributor] - rg_Test-Product3 [Test-Product3Owners & Product3Contributor] ... DEV-Subscription - rg_Dev-Product1 [Dev-Product1Owners & Product1Contributor] - rg_Dev-Product2 [Dev-Product2Owners & Product2Contributor] - rg_Dev-Product3 [Dev-Product3Owners & Product3Contributor] ...
I wonder if the above structure is correct or according to the best practice or is there any other deployment or architecture pattern?
Because the new Enterprise Architect person wanted to create new Azure Subscription for each Development Team instead of going like the above or existing pattern.
What are the limitations or disadvantages when we have many AzureSubscription that we create and delete or remove after each product team completed its project or dismissed?
Thank you in advance.