Virtual Datacenter Concept | 3 of 10 | Resource Groups - Tunecom<\/title>\n<meta name=\"description\" content=\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Virtual Datacenter Concept | 3 of 10 | Resource Groups - Tunecom\" \/>\n<meta property=\"og:description\" content=\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\" \/>\n<meta property=\"og:site_name\" content=\"Tunecom\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-17T08:57:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-02-18T13:58:40+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.tunecom.be\/wp-content\/uploads\/2020\/02\/image.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\">\n\t<meta name=\"twitter:data1\" content=\"8 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\",\"name\":\"Tunecom\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"sameAs\":[],\"logo\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#logo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/wp-content\/uploads\/2019\/09\/Original-on-Transparent-1.png\",\"width\":5000,\"height\":1749,\"caption\":\"Tunecom\"},\"image\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#logo\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#website\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"name\":\"Tunecom Consulting\",\"description\":\"Get in tune with your digital transformation journey\",\"publisher\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/wp-content\/uploads\/2020\/02\/image.png\",\"width\":1139,\"height\":566},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"name\":\"Virtual Datacenter Concept | 3 of 10 | Resource Groups - Tunecom\",\"isPartOf\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\"},\"datePublished\":\"2020-02-17T08:57:00+00:00\",\"dateModified\":\"2020-02-18T13:58:40+00:00\",\"description\":\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"name\":\"Virtual Datacenter Concept | 3 of 10 | Resource Groups\"}}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\"},\"author\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#\/schema\/person\/339cfa79b82ddc2200b535651b955a7d\"},\"headline\":\"Virtual Datacenter Concept | 3 of 10 | Resource Groups\",\"datePublished\":\"2020-02-17T08:57:00+00:00\",\"dateModified\":\"2020-02-18T13:58:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\"},\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\"},\"keywords\":\"Azure,resourcegroups\",\"articleSection\":\"Azure,Azure Networking,Cloud,Virtual Datacenter Concept\",\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#\/schema\/person\/339cfa79b82ddc2200b535651b955a7d\",\"name\":\"admin.yannickd\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#personlogo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f73a5ebb65b1c97d5ef7bfe49bd04e1d?s=96&d=mm&r=g\",\"caption\":\"admin.yannickd\"}}]}<\/script>\n","_links":{"self":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188"}],"collection":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=188"}],"version-history":[{"count":64,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions"}],"predecessor-version":[{"id":559,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions\/559"}],"wp:attachment":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Welcome back to the Azure Virtual Datacenter Concept blog post series.<\/p>\n\n\n\n

Azure Governance Scaffold : Resource Groups<\/figcaption><\/figure><\/div>\n\n\n\n
Let’s talk resources!<\/h5>\n\n\n\n
When deploying new resources in Azure, they reside in the Azure Resource Manager<\/a> model. The A<\/strong>zure R<\/strong>esource **M<\/strong>anager model is the successor of the** Azure Service Management<\/a> model which is often referred to as Azure v1 or Azure Classic. Since we are deploying resources in Azure, we want some kind of containerization <\/strong>or **logical <\/strong>management layer on top of that. And that is exactly why we need a resource group before we can deploy a resource in Azure.<\/p>\n\n\n\n**
A resource group is a logical boundary <\/strong>that can organize your resources based on the environment, application or other specific **characteristics<\/strong>. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks. <\/p>\n\n\n\n**
**$\"Resource$**
Azure Resource Manager Model<\/figcaption><\/figure><\/div>\n\n\n\n
Stuff to think about<\/h5>\n\n\n\n
Prior to deploying our first resource in a resource group, we have a couple of recommendations <\/strong>and\/or **limitations <\/strong>that we need to take care of:<\/p>\n\n\n\n**
A resource can only exist in **one <\/strong>resource group<\/li>**
Resources can be **moved <\/strong>from one resource group to another group<\/li>**
Resources are able to **communicate <\/strong>or connect to other resource groups<\/li><\/ul>\n\n\n\n**
Resource groups can be controlled by specific RBAC controls or resource locks.
**Takeway<\/strong>: Our advice is to assign specific roles of access to the resource groups and apply a delete lock by default.<\/li>**
Tip<\/strong>: We can force these roles and locks with Azure Policy<\/li><\/ul><\/li><\/ul>\n\n\n\n
Resource groups can contain resources that are located in different regions
**Takeaway<\/strong>: Our advice is to keep your resources within the same region as your resource group.<\/li>**
Tip<\/strong>: We can force this behavior via Azure Policy<\/li><\/ul><\/li><\/ul>\n\n\n\n
Ready, set, GO? STOP! Let’s first take a couple of design decisions.<\/h5>\n\n\n\n
Taking the above information into account, we don’t want to go and start deploying resources and resource groups via the Azure Portal. Rule of thumb<\/strong> is to use the Azure Portal as much as you can for view \/ read only actions and perform your deployments with **ARM templates, powershell or CLI<\/strong>.<\/p>\n\n\n\n**
Now before we are going to deploy our base set of resource groups, let’s have some thought on which resource groups we are going to deploy and why. Below table gives you an example <\/strong>that you can use in any of your Azure designs to provide an holistic overview of the required resource groups. Have a look here <\/a>at how naming conventions are provisioned \/ enforced.<\/p>\n\n\n\n
Resource Group Name<\/td> Resources<\/td><\/tr>
HUB<\/td><\/tr>
<cus>-hub-storage-rg<\/td> All components related to central\n storage<\/td><\/tr>
<cus>-hub-management-rg<\/td> All components related to central\n management tools<\/td><\/tr>
<cus>-hub-network-rg<\/td> All components related to central\n networking<\/td><\/tr>
<cus>-hub-mig-rg<\/td> All components related to\n migration workloads<\/td><\/tr>
<cus>-hub-backup-rg<\/td> All components related to the central backup instance<\/td><\/tr>
<cus>-hub-identity-rg<\/td> All components related to the\n central Identity instance<\/td><\/tr>
ENV<\/td><\/tr>
<cus>-dev-app-rg<\/td> All components related to the\n development application tier<\/td><\/tr>
<cus>-dev-web-rg<\/td> All components related to the\n development web tier<\/td><\/tr>
<cus>-dev-network-rg<\/td> All components related to the\n development network tier<\/td><\/tr>
<cus>-dev-db-rg<\/td> All components related to the\n development database tier<\/td><\/tr>
<cus>-dev-storage-rg<\/td> All components related to the\n development storage tier<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
The table above gives you guidance on how to deploy a **central HUB<\/strong> for resources and create a set of resource groups per environment.<\/p>\n\n\n\n**
**Our environment specific resource groups are designed in a way that we can re-utilize them for multiple purposes. <\/p>\n\n\n\n**
Design ready, let’s go!<\/h5>\n\n\n\n
Below PowerShell script can be used to deploy a tier based environment <\/strong>starting from a simple hub and production approach to a full blow **DTAP <\/strong>(Development, Test, Acceptance, Production) environment.<\/p>\n\n\n\n**
**Powershell Script<\/strong><\/p>\n\n\n**
\n##################\n\nParam(\n [string]$RG_PurposeHUB,\n [string]$RG_PurposePRD,\n [string]$RG_PurposeACC,\n [string]$RG_PurposeTST,\n [string]$RG_PurposeDEV,\n [string]$Cus,\n [string]$fullLocation,\n [string]$owner,\n [string]$EnvironmentTier\n\n)\n\n\n#####################################################################################\n######## START OF NAMING CONVENTION RESOURCE GROUPS HUB,PRD,DEV,TST ########\n#####################################################################################\n\n################### HUB\n$HUBRGID = $Cus + '-' + $RG_PurposeHUB + '-' + 'identity' + '-rg'\n$HUBRGSTOR = $Cus + '-' + $RG_PurposeHUB + '-' + 'storage' + '-rg'\n$HUBRGMGM = $Cus + '-' + $RG_PurposeHUB + '-' + 'management' + '-rg'\n$HUBRGNET = $Cus + '-' + $RG_PurposeHUB + '-' + 'network' + '-rg'\n$HUBRGMIG = $Cus + '-' + $RG_PurposeHUB + '-' + 'mig' + '-rg'\n$HUBRGRSV = $Cus + '-' + $RG_PurposeHUB + '-' + 'backup' + '-rg'\n\n################### PRD\n\n$PRDRGAPP = $Cus + '-' + $RG_PurposePRD + '-' + 'app' + '-rg'\n$PRDRGDB = $Cus + '-' + $RG_PurposePRD + '-' + 'db' + '-rg'\n$PRDRGSTOR = $Cus + '-' + $RG_PurposePRD + '-' + 'storage' + '-rg'\n$PRDRGNET = $Cus + '-' + $RG_PurposePRD + '-' + 'network' + '-rg'\n$PRDRGWEB = $Cus + '-' + $RG_PurposePRD + '-' + 'web' + '-rg'\n\n################### ACC\n\n$ACCRGAPP = $Cus + '-' + $RG_PurposeACC + '-' + 'app' + '-rg'\n$ACCRGDB = $Cus + '-' + $RG_PurposeACC + '-' + 'db' + '-rg'\n$ACCRGSTOR = $Cus + '-' + $RG_PurposeACC + '-' + 'storage' + '-rg'\n$ACCRGNET = $Cus + '-' + $RG_PurposeACC + '-' + 'network' + '-rg'\n$ACCRGWEB = $Cus + '-' + $RG_PurposeACC + '-' + 'web' + '-rg'\n\n################### TST\n\n$TSTRGAPP = $Cus + '-' + $RG_PurposeTST + '-' + 'app' + '-rg'\n$TSTRGDB = $Cus + '-' + $RG_PurposeTST + '-' + 'db' + '-rg'\n$TSTRGSTOR = $Cus + '-' + $RG_PurposeTST + '-' + 'storage' + '-rg'\n$TSTRGNET = $Cus + '-' + $RG_PurposeTST + '-' + 'network' + '-rg'\n$TSTRGWEB = $Cus + '-' + $RG_PurposeTST + '-' + 'web' + '-rg'\n\n################### DEV\n\n$DEVRGAPP = $Cus + '-' + $RG_PurposeDEV + '-' + 'app' + '-rg'\n$DEVRGDB = $Cus + '-' + $RG_PurposeDEV + '-' + 'db' + '-rg'\n$DEVRGSTOR = $Cus + '-' + $RG_PurposeDEV + '-' + 'storage' + '-rg'\n$DEVRGNET = $Cus + '-' + $RG_PurposeDEV + '-' + 'network' + '-rg'\n$DEVRGWEB = $Cus + '-' + $RG_PurposeDEV + '-' + 'web' + '-rg'\n\n#####################################################################################\n######## END OF NAMING CONVENTION RESOURCE GROUPS HUB,PRD,DEV,TST ########\n#####################################################################################\n\n\n\n#####################################################################################\n######## START OF CREATION RESOURCE GROUPS HUB,PRD,DEV,TST,ACC ########\n#####################################################################################\n\n\nfunction new-resourcegroups\n{\nParam ([string]$fullLocation,[string]$owner,[string]$rsgapp,[string]$rsgdb,[string]$rsgstor,[string]$rsgnet,[string]$rsgweb,[string]$rsgpurpose)\n\n New-AzResourceGroup -Name $rsgapp -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Application";Owner="$owner"}\n New-AzResourceGroup -Name $rsgdb -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Database";Owner="$owner"}\n New-AzResourceGroup -Name $rsgstor -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Storage";Owner="$owner"}\n New-AzResourceGroup -Name $rsgnet -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Networking";Owner="$owner"}\n New-AzResourceGroup -Name $rsgweb -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Web";Owner="$owner"}\n}\n\n\nfunction new-hubresourcegroups\n{\nParam ([string]$fullLocation,[string]$owner,[string]$rsgmgm,[string]$rsgdb,[string]$rsgstor,[string]$rsgnet,[string]$rsgweb,[string]$rsgpurpose,[string]$rsgmig,[string]$rsgrsv,[string]$rsgidentity)\n\n ### HUB AZ Powershell\n New-AzResourceGroup -Name $rsgstor -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Storage";Owner="$owner"}\n New-AzResourceGroup -Name $rsgmgm -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Management";Owner="$owner"}\n New-AzResourceGroup -Name $rsgnet -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Networking";Owner="$owner"} \n New-AzResourceGroup -name $rsgmig -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Migration";Owner="$owner"}\n New-AzResourceGroup -Name $rsgidentity -Location $fullLocation -Tag @{Environment="$rsgpurposeHUB";Purpose="Identity";Owner="$owner"} \n New-AzResourceGroup -Name $rsgrsv -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Backup";Owner="$owner"} \n }\n\n\n\n$EnvironmentTier\n \n# Select the setup steps required for this environment\n Switch ($EnvironmentTier)\n {\n 1 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n }\n 2 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n # new ACC Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $ACCRGAPP -rsgdb $ACCRGDB -rsgstor $ACCRGSTOR -rsgnet $ACCRGNET -rsgweb $ACCRGWEB -rsgpurpose $RG_PurposeACC\n\n }\n 3 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n # new ACC Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $ACCRGAPP -rsgdb $ACCRGDB -rsgstor $ACCRGSTOR -rsgnet $ACCRGNET -rsgweb $ACCRGWEB -rsgpurpose $RG_PurposeACC\n # new TST Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $TSTRGAPP -rsgdb $TSTRGDB -rsgstor $TSTRGSTOR -rsgnet $TSTRGNET -rsgweb $TSTRGWEB -rsgpurpose $RG_PurposeTST\n }\n 4 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n # new ACC Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $ACCRGAPP -rsgdb $ACCRGDB -rsgstor $ACCRGSTOR -rsgnet $ACCRGNET -rsgweb $ACCRGWEB -rsgpurpose $RG_PurposeACC\n # new TST Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $TSTRGAPP -rsgdb $TSTRGDB -rsgstor $TSTRGSTOR -rsgnet $TSTRGNET -rsgweb $TSTRGWEB -rsgpurpose $RG_PurposeTST\n # new DEV Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $DEVRGAPP -rsgdb $DEVRGDB -rsgstor $DEVRGSTOR -rsgnet $DEVRGNET -rsgweb $DEVRGWEB -rsgpurpose $RG_PurposeDEV\n }\n }\n\n\n#####################################################################################\n######## END OF CREATION RESOURCE GROUPS HUB,PRD,DEV,TST ########\n#####################################################################################\n<\/pre>\n\n\n
If we save the script as “1._Create_Az_ResourceGroups_v2.ps1” and run it with the parameters below this should give us the following result.<\/p>\n\n\n
\n.\\1._Create_Az_ResourceGroups_v2.ps1 -RG_PurposeHUB "hub" -RG_PurposePRD "prd" -RG_PurposeACC "acc" -RG_PurposeTST "tst" -RG_PurposeDEV "dev" -Cus "cus" -fullLocation "westeurope" -owner "Yannick Dils" -EnvironmentTier 4\n<\/pre>\n\n\n
$\"\"$ <\/figure>\n\n\n\n
View \/ Read-only on the Azure Portal<\/p>\n\n\n\n
$\"hub$
hub resource groups
<\/figcaption><\/figure><\/div>\n\n\n\n
$\"production$
prd resource groups<\/figcaption><\/figure>\n\n\n\n
Summary<\/h3>\n\n\n\n
Thank you for reading through the resource groups blog post, our aim was to give you an overview and set of best practices on how to implement resource groups based on a couple of design standards. When looking at the virtual datacenter concept. We now have a clear naming standard with a set of policies that are being applied to our management groups, subscriptions and resource groups. Our resource groups have been pre-configured in order to facilitate the deployment of our future resources.<\/p>\n\n\n\n
What\u2019s next?<\/h4>\n\n\n\n
The following aspects of the virtual datacenter concept will be highlighted in the following upcoming posts:<\/p>\n\n\n\n
Virtual Datacenter Concept \u2013 4 of 10 \u2013 Virtual Networking<\/li>
Virtual Datacenter Concept \u2013 5 of 10 \u2013 Cloud Storage<\/li>
Virtual Datacenter Concept \u2013 6 of 10 \u2013 Identity Options<\/li>
Virtual Datacenter Concept \u2013 7 of 10 \u2013 Log Analytics<\/li>
Virtual Datacenter Concept \u2013 8 of 10 \u2013 Security<\/li>
Virtual Datacenter Concept \u2013 9 of 10 \u2013 Business Continuity<\/li>
Virtual Datacenter Concept \u2013 10 of 10 \u2013 Automation<\/li><\/ul>\n\n\n\n
Missed a part or want to review a previous section? Be sure to check out my previous posts:<\/p>\n\n\n\n
Virtual Datacenter Concept \u2013 Introduction<\/a><\/li>
Virtual Datacenter Concept \u2013 1 of 10- Naming Conventions<\/a><\/li>
Virtual Datacenter Concept \u2013 2 of 10 \u2013 Governance <\/a><\/li>
Virtual Datacenter Concept \u2013 3 of 10 \u2013 Resource Groups <\/a><\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
Welcome back to the Azure Virtual Datacenter Concept blog post series. In our previous posts about naming conventions and Azure Governance, we’ve defined our rules of play. Now it’s time to start populating our Azure environment with some Resource Groups. Let’s talk resources! When deploying new resources in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":true,"template":"","format":"standard","meta":[],"categories":[22,29,20,23],"tags":[25,45],"yoast_head":"\nVirtual Datacenter Concept | 3 of 10 | Resource Groups - Tunecom<\/title>\n<meta name=\"description\" content=\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Virtual Datacenter Concept | 3 of 10 | Resource Groups - Tunecom\" \/>\n<meta property=\"og:description\" content=\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\" \/>\n<meta property=\"og:site_name\" content=\"Tunecom\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-17T08:57:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-02-18T13:58:40+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.tunecom.be\/wp-content\/uploads\/2020\/02\/image.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\">\n\t<meta name=\"twitter:data1\" content=\"8 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\",\"name\":\"Tunecom\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"sameAs\":[],\"logo\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#logo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/wp-content\/uploads\/2019\/09\/Original-on-Transparent-1.png\",\"width\":5000,\"height\":1749,\"caption\":\"Tunecom\"},\"image\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#logo\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#website\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"name\":\"Tunecom Consulting\",\"description\":\"Get in tune with your digital transformation journey\",\"publisher\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/wp-content\/uploads\/2020\/02\/image.png\",\"width\":1139,\"height\":566},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"name\":\"Virtual Datacenter Concept | 3 of 10 | Resource Groups - Tunecom\",\"isPartOf\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\"},\"datePublished\":\"2020-02-17T08:57:00+00:00\",\"dateModified\":\"2020-02-18T13:58:40+00:00\",\"description\":\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"name\":\"Virtual Datacenter Concept | 3 of 10 | Resource Groups\"}}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\"},\"author\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#\/schema\/person\/339cfa79b82ddc2200b535651b955a7d\"},\"headline\":\"Virtual Datacenter Concept | 3 of 10 | Resource Groups\",\"datePublished\":\"2020-02-17T08:57:00+00:00\",\"dateModified\":\"2020-02-18T13:58:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\"},\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\"},\"keywords\":\"Azure,resourcegroups\",\"articleSection\":\"Azure,Azure Networking,Cloud,Virtual Datacenter Concept\",\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#\/schema\/person\/339cfa79b82ddc2200b535651b955a7d\",\"name\":\"admin.yannickd\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#personlogo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f73a5ebb65b1c97d5ef7bfe49bd04e1d?s=96&d=mm&r=g\",\"caption\":\"admin.yannickd\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188"}],"collection":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=188"}],"version-history":[{"count":64,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions"}],"predecessor-version":[{"id":559,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions\/559"}],"wp:attachment":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Azure Governance Scaffold : Resource Groups<\/figcaption><\/figure><\/div>\n\n\n\n
Let’s talk resources!<\/h5>\n\n\n\n
When deploying new resources in Azure, they reside in the Azure Resource Manager<\/a> model. The A<\/strong>zure R<\/strong>esource **M<\/strong>anager model is the successor of the** Azure Service Management<\/a> model which is often referred to as Azure v1 or Azure Classic. Since we are deploying resources in Azure, we want some kind of containerization <\/strong>or **logical <\/strong>management layer on top of that. And that is exactly why we need a resource group before we can deploy a resource in Azure.<\/p>\n\n\n\n**
A resource group is a logical boundary <\/strong>that can organize your resources based on the environment, application or other specific **characteristics<\/strong>. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks. <\/p>\n\n\n\n**
**$\"Resource$**
Azure Resource Manager Model<\/figcaption><\/figure><\/div>\n\n\n\n
Stuff to think about<\/h5>\n\n\n\n
Prior to deploying our first resource in a resource group, we have a couple of recommendations <\/strong>and\/or **limitations <\/strong>that we need to take care of:<\/p>\n\n\n\n**
A resource can only exist in **one <\/strong>resource group<\/li>**
Resources can be **moved <\/strong>from one resource group to another group<\/li>**
Resources are able to **communicate <\/strong>or connect to other resource groups<\/li><\/ul>\n\n\n\n**
Resource groups can be controlled by specific RBAC controls or resource locks.
**Takeway<\/strong>: Our advice is to assign specific roles of access to the resource groups and apply a delete lock by default.<\/li>**
Tip<\/strong>: We can force these roles and locks with Azure Policy<\/li><\/ul><\/li><\/ul>\n\n\n\n
Resource groups can contain resources that are located in different regions
**Takeaway<\/strong>: Our advice is to keep your resources within the same region as your resource group.<\/li>**
Tip<\/strong>: We can force this behavior via Azure Policy<\/li><\/ul><\/li><\/ul>\n\n\n\n
Ready, set, GO? STOP! Let’s first take a couple of design decisions.<\/h5>\n\n\n\n
Taking the above information into account, we don’t want to go and start deploying resources and resource groups via the Azure Portal. Rule of thumb<\/strong> is to use the Azure Portal as much as you can for view \/ read only actions and perform your deployments with **ARM templates, powershell or CLI<\/strong>.<\/p>\n\n\n\n**
Now before we are going to deploy our base set of resource groups, let’s have some thought on which resource groups we are going to deploy and why. Below table gives you an example <\/strong>that you can use in any of your Azure designs to provide an holistic overview of the required resource groups. Have a look here <\/a>at how naming conventions are provisioned \/ enforced.<\/p>\n\n\n\n
Resource Group Name<\/td> Resources<\/td><\/tr>
HUB<\/td><\/tr>
<cus>-hub-storage-rg<\/td> All components related to central\n storage<\/td><\/tr>
<cus>-hub-management-rg<\/td> All components related to central\n management tools<\/td><\/tr>
<cus>-hub-network-rg<\/td> All components related to central\n networking<\/td><\/tr>
<cus>-hub-mig-rg<\/td> All components related to\n migration workloads<\/td><\/tr>
<cus>-hub-backup-rg<\/td> All components related to the central backup instance<\/td><\/tr>
<cus>-hub-identity-rg<\/td> All components related to the\n central Identity instance<\/td><\/tr>
ENV<\/td><\/tr>
<cus>-dev-app-rg<\/td> All components related to the\n development application tier<\/td><\/tr>
<cus>-dev-web-rg<\/td> All components related to the\n development web tier<\/td><\/tr>
<cus>-dev-network-rg<\/td> All components related to the\n development network tier<\/td><\/tr>
<cus>-dev-db-rg<\/td> All components related to the\n development database tier<\/td><\/tr>
<cus>-dev-storage-rg<\/td> All components related to the\n development storage tier<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
The table above gives you guidance on how to deploy a **central HUB<\/strong> for resources and create a set of resource groups per environment.<\/p>\n\n\n\n**
**Our environment specific resource groups are designed in a way that we can re-utilize them for multiple purposes. <\/p>\n\n\n\n**
Design ready, let’s go!<\/h5>\n\n\n\n
Below PowerShell script can be used to deploy a tier based environment <\/strong>starting from a simple hub and production approach to a full blow **DTAP <\/strong>(Development, Test, Acceptance, Production) environment.<\/p>\n\n\n\n**
**Powershell Script<\/strong><\/p>\n\n\n**
\n##################\n\nParam(\n [string]$RG_PurposeHUB,\n [string]$RG_PurposePRD,\n [string]$RG_PurposeACC,\n [string]$RG_PurposeTST,\n [string]$RG_PurposeDEV,\n [string]$Cus,\n [string]$fullLocation,\n [string]$owner,\n [string]$EnvironmentTier\n\n)\n\n\n#####################################################################################\n######## START OF NAMING CONVENTION RESOURCE GROUPS HUB,PRD,DEV,TST ########\n#####################################################################################\n\n################### HUB\n$HUBRGID = $Cus + '-' + $RG_PurposeHUB + '-' + 'identity' + '-rg'\n$HUBRGSTOR = $Cus + '-' + $RG_PurposeHUB + '-' + 'storage' + '-rg'\n$HUBRGMGM = $Cus + '-' + $RG_PurposeHUB + '-' + 'management' + '-rg'\n$HUBRGNET = $Cus + '-' + $RG_PurposeHUB + '-' + 'network' + '-rg'\n$HUBRGMIG = $Cus + '-' + $RG_PurposeHUB + '-' + 'mig' + '-rg'\n$HUBRGRSV = $Cus + '-' + $RG_PurposeHUB + '-' + 'backup' + '-rg'\n\n################### PRD\n\n$PRDRGAPP = $Cus + '-' + $RG_PurposePRD + '-' + 'app' + '-rg'\n$PRDRGDB = $Cus + '-' + $RG_PurposePRD + '-' + 'db' + '-rg'\n$PRDRGSTOR = $Cus + '-' + $RG_PurposePRD + '-' + 'storage' + '-rg'\n$PRDRGNET = $Cus + '-' + $RG_PurposePRD + '-' + 'network' + '-rg'\n$PRDRGWEB = $Cus + '-' + $RG_PurposePRD + '-' + 'web' + '-rg'\n\n################### ACC\n\n$ACCRGAPP = $Cus + '-' + $RG_PurposeACC + '-' + 'app' + '-rg'\n$ACCRGDB = $Cus + '-' + $RG_PurposeACC + '-' + 'db' + '-rg'\n$ACCRGSTOR = $Cus + '-' + $RG_PurposeACC + '-' + 'storage' + '-rg'\n$ACCRGNET = $Cus + '-' + $RG_PurposeACC + '-' + 'network' + '-rg'\n$ACCRGWEB = $Cus + '-' + $RG_PurposeACC + '-' + 'web' + '-rg'\n\n################### TST\n\n$TSTRGAPP = $Cus + '-' + $RG_PurposeTST + '-' + 'app' + '-rg'\n$TSTRGDB = $Cus + '-' + $RG_PurposeTST + '-' + 'db' + '-rg'\n$TSTRGSTOR = $Cus + '-' + $RG_PurposeTST + '-' + 'storage' + '-rg'\n$TSTRGNET = $Cus + '-' + $RG_PurposeTST + '-' + 'network' + '-rg'\n$TSTRGWEB = $Cus + '-' + $RG_PurposeTST + '-' + 'web' + '-rg'\n\n################### DEV\n\n$DEVRGAPP = $Cus + '-' + $RG_PurposeDEV + '-' + 'app' + '-rg'\n$DEVRGDB = $Cus + '-' + $RG_PurposeDEV + '-' + 'db' + '-rg'\n$DEVRGSTOR = $Cus + '-' + $RG_PurposeDEV + '-' + 'storage' + '-rg'\n$DEVRGNET = $Cus + '-' + $RG_PurposeDEV + '-' + 'network' + '-rg'\n$DEVRGWEB = $Cus + '-' + $RG_PurposeDEV + '-' + 'web' + '-rg'\n\n#####################################################################################\n######## END OF NAMING CONVENTION RESOURCE GROUPS HUB,PRD,DEV,TST ########\n#####################################################################################\n\n\n\n#####################################################################################\n######## START OF CREATION RESOURCE GROUPS HUB,PRD,DEV,TST,ACC ########\n#####################################################################################\n\n\nfunction new-resourcegroups\n{\nParam ([string]$fullLocation,[string]$owner,[string]$rsgapp,[string]$rsgdb,[string]$rsgstor,[string]$rsgnet,[string]$rsgweb,[string]$rsgpurpose)\n\n New-AzResourceGroup -Name $rsgapp -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Application";Owner="$owner"}\n New-AzResourceGroup -Name $rsgdb -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Database";Owner="$owner"}\n New-AzResourceGroup -Name $rsgstor -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Storage";Owner="$owner"}\n New-AzResourceGroup -Name $rsgnet -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Networking";Owner="$owner"}\n New-AzResourceGroup -Name $rsgweb -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Web";Owner="$owner"}\n}\n\n\nfunction new-hubresourcegroups\n{\nParam ([string]$fullLocation,[string]$owner,[string]$rsgmgm,[string]$rsgdb,[string]$rsgstor,[string]$rsgnet,[string]$rsgweb,[string]$rsgpurpose,[string]$rsgmig,[string]$rsgrsv,[string]$rsgidentity)\n\n ### HUB AZ Powershell\n New-AzResourceGroup -Name $rsgstor -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Storage";Owner="$owner"}\n New-AzResourceGroup -Name $rsgmgm -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Management";Owner="$owner"}\n New-AzResourceGroup -Name $rsgnet -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Networking";Owner="$owner"} \n New-AzResourceGroup -name $rsgmig -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Migration";Owner="$owner"}\n New-AzResourceGroup -Name $rsgidentity -Location $fullLocation -Tag @{Environment="$rsgpurposeHUB";Purpose="Identity";Owner="$owner"} \n New-AzResourceGroup -Name $rsgrsv -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Backup";Owner="$owner"} \n }\n\n\n\n$EnvironmentTier\n \n# Select the setup steps required for this environment\n Switch ($EnvironmentTier)\n {\n 1 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n }\n 2 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n # new ACC Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $ACCRGAPP -rsgdb $ACCRGDB -rsgstor $ACCRGSTOR -rsgnet $ACCRGNET -rsgweb $ACCRGWEB -rsgpurpose $RG_PurposeACC\n\n }\n 3 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n # new ACC Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $ACCRGAPP -rsgdb $ACCRGDB -rsgstor $ACCRGSTOR -rsgnet $ACCRGNET -rsgweb $ACCRGWEB -rsgpurpose $RG_PurposeACC\n # new TST Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $TSTRGAPP -rsgdb $TSTRGDB -rsgstor $TSTRGSTOR -rsgnet $TSTRGNET -rsgweb $TSTRGWEB -rsgpurpose $RG_PurposeTST\n }\n 4 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n # new ACC Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $ACCRGAPP -rsgdb $ACCRGDB -rsgstor $ACCRGSTOR -rsgnet $ACCRGNET -rsgweb $ACCRGWEB -rsgpurpose $RG_PurposeACC\n # new TST Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $TSTRGAPP -rsgdb $TSTRGDB -rsgstor $TSTRGSTOR -rsgnet $TSTRGNET -rsgweb $TSTRGWEB -rsgpurpose $RG_PurposeTST\n # new DEV Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $DEVRGAPP -rsgdb $DEVRGDB -rsgstor $DEVRGSTOR -rsgnet $DEVRGNET -rsgweb $DEVRGWEB -rsgpurpose $RG_PurposeDEV\n }\n }\n\n\n#####################################################################################\n######## END OF CREATION RESOURCE GROUPS HUB,PRD,DEV,TST ########\n#####################################################################################\n<\/pre>\n\n\n
If we save the script as “1._Create_Az_ResourceGroups_v2.ps1” and run it with the parameters below this should give us the following result.<\/p>\n\n\n
\n.\\1._Create_Az_ResourceGroups_v2.ps1 -RG_PurposeHUB "hub" -RG_PurposePRD "prd" -RG_PurposeACC "acc" -RG_PurposeTST "tst" -RG_PurposeDEV "dev" -Cus "cus" -fullLocation "westeurope" -owner "Yannick Dils" -EnvironmentTier 4\n<\/pre>\n\n\n
$\"\"$ <\/figure>\n\n\n\n
View \/ Read-only on the Azure Portal<\/p>\n\n\n\n
$\"hub$
hub resource groups
<\/figcaption><\/figure><\/div>\n\n\n\n
$\"production$
prd resource groups<\/figcaption><\/figure>\n\n\n\n
Summary<\/h3>\n\n\n\n
Thank you for reading through the resource groups blog post, our aim was to give you an overview and set of best practices on how to implement resource groups based on a couple of design standards. When looking at the virtual datacenter concept. We now have a clear naming standard with a set of policies that are being applied to our management groups, subscriptions and resource groups. Our resource groups have been pre-configured in order to facilitate the deployment of our future resources.<\/p>\n\n\n\n
What\u2019s next?<\/h4>\n\n\n\n
The following aspects of the virtual datacenter concept will be highlighted in the following upcoming posts:<\/p>\n\n\n\n
Virtual Datacenter Concept \u2013 4 of 10 \u2013 Virtual Networking<\/li>
Virtual Datacenter Concept \u2013 5 of 10 \u2013 Cloud Storage<\/li>
Virtual Datacenter Concept \u2013 6 of 10 \u2013 Identity Options<\/li>
Virtual Datacenter Concept \u2013 7 of 10 \u2013 Log Analytics<\/li>
Virtual Datacenter Concept \u2013 8 of 10 \u2013 Security<\/li>
Virtual Datacenter Concept \u2013 9 of 10 \u2013 Business Continuity<\/li>
Virtual Datacenter Concept \u2013 10 of 10 \u2013 Automation<\/li><\/ul>\n\n\n\n
Missed a part or want to review a previous section? Be sure to check out my previous posts:<\/p>\n\n\n\n
Virtual Datacenter Concept \u2013 Introduction<\/a><\/li>
Virtual Datacenter Concept \u2013 1 of 10- Naming Conventions<\/a><\/li>
Virtual Datacenter Concept \u2013 2 of 10 \u2013 Governance <\/a><\/li>
Virtual Datacenter Concept \u2013 3 of 10 \u2013 Resource Groups <\/a><\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"
Welcome back to the Azure Virtual Datacenter Concept blog post series. In our previous posts about naming conventions and Azure Governance, we’ve defined our rules of play. Now it’s time to start populating our Azure environment with some Resource Groups. Let’s talk resources! When deploying new resources in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":true,"template":"","format":"standard","meta":[],"categories":[22,29,20,23],"tags":[25,45],"yoast_head":"\nVirtual Datacenter Concept | 3 of 10 | Resource Groups - Tunecom<\/title>\n<meta name=\"description\" content=\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Virtual Datacenter Concept | 3 of 10 | Resource Groups - Tunecom\" \/>\n<meta property=\"og:description\" content=\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\" \/>\n<meta property=\"og:site_name\" content=\"Tunecom\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-17T08:57:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-02-18T13:58:40+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.tunecom.be\/wp-content\/uploads\/2020\/02\/image.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\">\n\t<meta name=\"twitter:data1\" content=\"8 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\",\"name\":\"Tunecom\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"sameAs\":[],\"logo\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#logo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/wp-content\/uploads\/2019\/09\/Original-on-Transparent-1.png\",\"width\":5000,\"height\":1749,\"caption\":\"Tunecom\"},\"image\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#logo\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#website\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"name\":\"Tunecom Consulting\",\"description\":\"Get in tune with your digital transformation journey\",\"publisher\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/wp-content\/uploads\/2020\/02\/image.png\",\"width\":1139,\"height\":566},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"name\":\"Virtual Datacenter Concept | 3 of 10 | Resource Groups - Tunecom\",\"isPartOf\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\"},\"datePublished\":\"2020-02-17T08:57:00+00:00\",\"dateModified\":\"2020-02-18T13:58:40+00:00\",\"description\":\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"name\":\"Virtual Datacenter Concept | 3 of 10 | Resource Groups\"}}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\"},\"author\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#\/schema\/person\/339cfa79b82ddc2200b535651b955a7d\"},\"headline\":\"Virtual Datacenter Concept | 3 of 10 | Resource Groups\",\"datePublished\":\"2020-02-17T08:57:00+00:00\",\"dateModified\":\"2020-02-18T13:58:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\"},\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\"},\"keywords\":\"Azure,resourcegroups\",\"articleSection\":\"Azure,Azure Networking,Cloud,Virtual Datacenter Concept\",\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#\/schema\/person\/339cfa79b82ddc2200b535651b955a7d\",\"name\":\"admin.yannickd\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#personlogo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f73a5ebb65b1c97d5ef7bfe49bd04e1d?s=96&d=mm&r=g\",\"caption\":\"admin.yannickd\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188"}],"collection":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=188"}],"version-history":[{"count":64,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions"}],"predecessor-version":[{"id":559,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions\/559"}],"wp:attachment":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Resource Group Name<\/td>	Resources<\/td><\/tr>
HUB<\/td><\/tr>
<cus>-hub-storage-rg<\/td>	All components related to central\n storage<\/td><\/tr>
<cus>-hub-management-rg<\/td>	All components related to central\n management tools<\/td><\/tr>
<cus>-hub-network-rg<\/td>	All components related to central\n networking<\/td><\/tr>
<cus>-hub-mig-rg<\/td>	All components related to\n migration workloads<\/td><\/tr>
<cus>-hub-backup-rg<\/td>	All components related to the central backup instance<\/td><\/tr>
<cus>-hub-identity-rg<\/td>	All components related to the\n central Identity instance<\/td><\/tr>
ENV<\/td><\/tr>
<cus>-dev-app-rg<\/td>	All components related to the\n development application tier<\/td><\/tr>
<cus>-dev-web-rg<\/td>	All components related to the\n development web tier<\/td><\/tr>
<cus>-dev-network-rg<\/td>	All components related to the\n development network tier<\/td><\/tr>
<cus>-dev-db-rg<\/td>	All components related to the\n development database tier<\/td><\/tr>
<cus>-dev-storage-rg<\/td>	All components related to the\n development storage tier<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n The table above gives you guidance on how to deploy a central HUB<\/strong> for resources and create a set of resource groups per environment.<\/p>\n\n\n\n Our environment specific resource groups are designed in a way that we can re-utilize them for multiple purposes. <\/p>\n\n\n\n Design ready, let’s go!<\/h5>\n\n\n\n Below PowerShell script can be used to deploy a tier based environment <\/strong>starting from a simple hub and production approach to a full blow DTAP <\/strong>(Development, Test, Acceptance, Production) environment.<\/p>\n\n\n\n Powershell Script<\/strong><\/p>\n\n\n \n##################\n\nParam(\n [string]$RG_PurposeHUB,\n [string]$RG_PurposePRD,\n [string]$RG_PurposeACC,\n [string]$RG_PurposeTST,\n [string]$RG_PurposeDEV,\n [string]$Cus,\n [string]$fullLocation,\n [string]$owner,\n [string]$EnvironmentTier\n\n)\n\n\n#####################################################################################\n######## START OF NAMING CONVENTION RESOURCE GROUPS HUB,PRD,DEV,TST ########\n#####################################################################################\n\n################### HUB\n$HUBRGID = $Cus + '-' + $RG_PurposeHUB + '-' + 'identity' + '-rg'\n$HUBRGSTOR = $Cus + '-' + $RG_PurposeHUB + '-' + 'storage' + '-rg'\n$HUBRGMGM = $Cus + '-' + $RG_PurposeHUB + '-' + 'management' + '-rg'\n$HUBRGNET = $Cus + '-' + $RG_PurposeHUB + '-' + 'network' + '-rg'\n$HUBRGMIG = $Cus + '-' + $RG_PurposeHUB + '-' + 'mig' + '-rg'\n$HUBRGRSV = $Cus + '-' + $RG_PurposeHUB + '-' + 'backup' + '-rg'\n\n################### PRD\n\n$PRDRGAPP = $Cus + '-' + $RG_PurposePRD + '-' + 'app' + '-rg'\n$PRDRGDB = $Cus + '-' + $RG_PurposePRD + '-' + 'db' + '-rg'\n$PRDRGSTOR = $Cus + '-' + $RG_PurposePRD + '-' + 'storage' + '-rg'\n$PRDRGNET = $Cus + '-' + $RG_PurposePRD + '-' + 'network' + '-rg'\n$PRDRGWEB = $Cus + '-' + $RG_PurposePRD + '-' + 'web' + '-rg'\n\n################### ACC\n\n$ACCRGAPP = $Cus + '-' + $RG_PurposeACC + '-' + 'app' + '-rg'\n$ACCRGDB = $Cus + '-' + $RG_PurposeACC + '-' + 'db' + '-rg'\n$ACCRGSTOR = $Cus + '-' + $RG_PurposeACC + '-' + 'storage' + '-rg'\n$ACCRGNET = $Cus + '-' + $RG_PurposeACC + '-' + 'network' + '-rg'\n$ACCRGWEB = $Cus + '-' + $RG_PurposeACC + '-' + 'web' + '-rg'\n\n################### TST\n\n$TSTRGAPP = $Cus + '-' + $RG_PurposeTST + '-' + 'app' + '-rg'\n$TSTRGDB = $Cus + '-' + $RG_PurposeTST + '-' + 'db' + '-rg'\n$TSTRGSTOR = $Cus + '-' + $RG_PurposeTST + '-' + 'storage' + '-rg'\n$TSTRGNET = $Cus + '-' + $RG_PurposeTST + '-' + 'network' + '-rg'\n$TSTRGWEB = $Cus + '-' + $RG_PurposeTST + '-' + 'web' + '-rg'\n\n################### DEV\n\n$DEVRGAPP = $Cus + '-' + $RG_PurposeDEV + '-' + 'app' + '-rg'\n$DEVRGDB = $Cus + '-' + $RG_PurposeDEV + '-' + 'db' + '-rg'\n$DEVRGSTOR = $Cus + '-' + $RG_PurposeDEV + '-' + 'storage' + '-rg'\n$DEVRGNET = $Cus + '-' + $RG_PurposeDEV + '-' + 'network' + '-rg'\n$DEVRGWEB = $Cus + '-' + $RG_PurposeDEV + '-' + 'web' + '-rg'\n\n#####################################################################################\n######## END OF NAMING CONVENTION RESOURCE GROUPS HUB,PRD,DEV,TST ########\n#####################################################################################\n\n\n\n#####################################################################################\n######## START OF CREATION RESOURCE GROUPS HUB,PRD,DEV,TST,ACC ########\n#####################################################################################\n\n\nfunction new-resourcegroups\n{\nParam ([string]$fullLocation,[string]$owner,[string]$rsgapp,[string]$rsgdb,[string]$rsgstor,[string]$rsgnet,[string]$rsgweb,[string]$rsgpurpose)\n\n New-AzResourceGroup -Name $rsgapp -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Application";Owner="$owner"}\n New-AzResourceGroup -Name $rsgdb -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Database";Owner="$owner"}\n New-AzResourceGroup -Name $rsgstor -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Storage";Owner="$owner"}\n New-AzResourceGroup -Name $rsgnet -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Networking";Owner="$owner"}\n New-AzResourceGroup -Name $rsgweb -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Web";Owner="$owner"}\n}\n\n\nfunction new-hubresourcegroups\n{\nParam ([string]$fullLocation,[string]$owner,[string]$rsgmgm,[string]$rsgdb,[string]$rsgstor,[string]$rsgnet,[string]$rsgweb,[string]$rsgpurpose,[string]$rsgmig,[string]$rsgrsv,[string]$rsgidentity)\n\n ### HUB AZ Powershell\n New-AzResourceGroup -Name $rsgstor -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Storage";Owner="$owner"}\n New-AzResourceGroup -Name $rsgmgm -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Management";Owner="$owner"}\n New-AzResourceGroup -Name $rsgnet -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Networking";Owner="$owner"} \n New-AzResourceGroup -name $rsgmig -Location $fullLocation -Tag @{Environment="$RG_PurposeHUB";Purpose="Migration";Owner="$owner"}\n New-AzResourceGroup -Name $rsgidentity -Location $fullLocation -Tag @{Environment="$rsgpurposeHUB";Purpose="Identity";Owner="$owner"} \n New-AzResourceGroup -Name $rsgrsv -Location $fullLocation -Tag @{Environment="$rsgpurpose";Purpose="Backup";Owner="$owner"} \n }\n\n\n\n$EnvironmentTier\n \n# Select the setup steps required for this environment\n Switch ($EnvironmentTier)\n {\n 1 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n }\n 2 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n # new ACC Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $ACCRGAPP -rsgdb $ACCRGDB -rsgstor $ACCRGSTOR -rsgnet $ACCRGNET -rsgweb $ACCRGWEB -rsgpurpose $RG_PurposeACC\n\n }\n 3 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n # new ACC Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $ACCRGAPP -rsgdb $ACCRGDB -rsgstor $ACCRGSTOR -rsgnet $ACCRGNET -rsgweb $ACCRGWEB -rsgpurpose $RG_PurposeACC\n # new TST Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $TSTRGAPP -rsgdb $TSTRGDB -rsgstor $TSTRGSTOR -rsgnet $TSTRGNET -rsgweb $TSTRGWEB -rsgpurpose $RG_PurposeTST\n }\n 4 {\n # new HUB Resource Groups\n new-hubresourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $HUBRGAPP -rsgdb $HUBRGDB -rsgstor $HUBRGSTOR -rsgnet $HUBRGNET -rsgweb $HUBRGWEB -rsgpurpose $RG_PurposeHUB -rsgmgm $HUBRGMGM -rsgmig $HUBRGMIG -rsgidentity $HUBRGID -rsgrsv $HUBRGRSV\n # new PRD Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $PRDRGAPP -rsgdb $PRDRGDB -rsgstor $PRDRGSTOR -rsgnet $PRDRGNET -rsgweb $PRDRGWEB -rsgpurpose $RG_PurposePRD \n # new ACC Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $ACCRGAPP -rsgdb $ACCRGDB -rsgstor $ACCRGSTOR -rsgnet $ACCRGNET -rsgweb $ACCRGWEB -rsgpurpose $RG_PurposeACC\n # new TST Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $TSTRGAPP -rsgdb $TSTRGDB -rsgstor $TSTRGSTOR -rsgnet $TSTRGNET -rsgweb $TSTRGWEB -rsgpurpose $RG_PurposeTST\n # new DEV Resource Groups\n new-resourcegroups -fullLocation $fullLocation -owner $owner -rsgapp $DEVRGAPP -rsgdb $DEVRGDB -rsgstor $DEVRGSTOR -rsgnet $DEVRGNET -rsgweb $DEVRGWEB -rsgpurpose $RG_PurposeDEV\n }\n }\n\n\n#####################################################################################\n######## END OF CREATION RESOURCE GROUPS HUB,PRD,DEV,TST ########\n#####################################################################################\n<\/pre>\n\n\n If we save the script as “1._Create_Az_ResourceGroups_v2.ps1” and run it with the parameters below this should give us the following result.<\/p>\n\n\n \n.\\1._Create_Az_ResourceGroups_v2.ps1 -RG_PurposeHUB "hub" -RG_PurposePRD "prd" -RG_PurposeACC "acc" -RG_PurposeTST "tst" -RG_PurposeDEV "dev" -Cus "cus" -fullLocation "westeurope" -owner "Yannick Dils" -EnvironmentTier 4\n<\/pre>\n\n\n $\"\"$ <\/figure>\n\n\n\n View \/ Read-only on the Azure Portal<\/p>\n\n\n\n $\"hub$ hub resource groups <\/figcaption><\/figure><\/div>\n\n\n\n $\"production$ prd resource groups<\/figcaption><\/figure>\n\n\n\n Summary<\/h3>\n\n\n\n Thank you for reading through the resource groups blog post, our aim was to give you an overview and set of best practices on how to implement resource groups based on a couple of design standards. When looking at the virtual datacenter concept. We now have a clear naming standard with a set of policies that are being applied to our management groups, subscriptions and resource groups. Our resource groups have been pre-configured in order to facilitate the deployment of our future resources.<\/p>\n\n\n\n What\u2019s next?<\/h4>\n\n\n\n The following aspects of the virtual datacenter concept will be highlighted in the following upcoming posts:<\/p>\n\n\n\n Virtual Datacenter Concept \u2013 4 of 10 \u2013 Virtual Networking<\/li> Virtual Datacenter Concept \u2013 5 of 10 \u2013 Cloud Storage<\/li> Virtual Datacenter Concept \u2013 6 of 10 \u2013 Identity Options<\/li> Virtual Datacenter Concept \u2013 7 of 10 \u2013 Log Analytics<\/li> Virtual Datacenter Concept \u2013 8 of 10 \u2013 Security<\/li> Virtual Datacenter Concept \u2013 9 of 10 \u2013 Business Continuity<\/li> Virtual Datacenter Concept \u2013 10 of 10 \u2013 Automation<\/li><\/ul>\n\n\n\n Missed a part or want to review a previous section? Be sure to check out my previous posts:<\/p>\n\n\n\n Virtual Datacenter Concept \u2013 Introduction<\/a><\/li> Virtual Datacenter Concept \u2013 1 of 10- Naming Conventions<\/a><\/li> Virtual Datacenter Concept \u2013 2 of 10 \u2013 Governance <\/a><\/li> Virtual Datacenter Concept \u2013 3 of 10 \u2013 Resource Groups <\/a><\/li><\/ul>\n","protected":false},"excerpt":{"rendered":" Welcome back to the Azure Virtual Datacenter Concept blog post series. In our previous posts about naming conventions and Azure Governance, we’ve defined our rules of play. Now it’s time to start populating our Azure environment with some Resource Groups. Let’s talk resources! When deploying new resources in […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":true,"template":"","format":"standard","meta":[],"categories":[22,29,20,23],"tags":[25,45],"yoast_head":"\nVirtual Datacenter Concept \| 3 of 10 \| Resource Groups - Tunecom<\/title>\n<meta name=\"description\" content=\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Virtual Datacenter Concept \| 3 of 10 \| Resource Groups - Tunecom\" \/>\n<meta property=\"og:description\" content=\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\" \/>\n<meta property=\"og:site_name\" content=\"Tunecom\" \/>\n<meta property=\"article:published_time\" content=\"2020-02-17T08:57:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-02-18T13:58:40+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.tunecom.be\/wp-content\/uploads\/2020\/02\/image.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Estimated reading time\">\n\t<meta name=\"twitter:data1\" content=\"8 minutes\">\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\",\"name\":\"Tunecom\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"sameAs\":[],\"logo\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#logo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/wp-content\/uploads\/2019\/09\/Original-on-Transparent-1.png\",\"width\":5000,\"height\":1749,\"caption\":\"Tunecom\"},\"image\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#logo\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#website\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"name\":\"Tunecom Consulting\",\"description\":\"Get in tune with your digital transformation journey\",\"publisher\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-GB\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/wp-content\/uploads\/2020\/02\/image.png\",\"width\":1139,\"height\":566},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"name\":\"Virtual Datacenter Concept \| 3 of 10 \| Resource Groups - Tunecom\",\"isPartOf\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\"},\"datePublished\":\"2020-02-17T08:57:00+00:00\",\"dateModified\":\"2020-02-18T13:58:40+00:00\",\"description\":\"A resource group is a logical boundary that can organize your resources based on the environment, application or other specific characteristics. We can harden our resource group from unwanted changes by implementing role based access controls and resource locks.\",\"breadcrumb\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"position\":2,\"item\":{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"url\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188\",\"name\":\"Virtual Datacenter Concept \| 3 of 10 \| Resource Groups\"}}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\"},\"author\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#\/schema\/person\/339cfa79b82ddc2200b535651b955a7d\"},\"headline\":\"Virtual Datacenter Concept \| 3 of 10 \| Resource Groups\",\"datePublished\":\"2020-02-17T08:57:00+00:00\",\"dateModified\":\"2020-02-18T13:58:40+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#webpage\"},\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#primaryimage\"},\"keywords\":\"Azure,resourcegroups\",\"articleSection\":\"Azure,Azure Networking,Cloud,Virtual Datacenter Concept\",\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.tunecom.be\/stg_ba12f\/?p=188#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#\/schema\/person\/339cfa79b82ddc2200b535651b955a7d\",\"name\":\"admin.yannickd\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/www.tunecom.be\/stg_ba12f\/#personlogo\",\"inLanguage\":\"en-GB\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/f73a5ebb65b1c97d5ef7bfe49bd04e1d?s=96&d=mm&r=g\",\"caption\":\"admin.yannickd\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188"}],"collection":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=188"}],"version-history":[{"count":64,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions"}],"predecessor-version":[{"id":559,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=\/wp\/v2\/posts\/188\/revisions\/559"}],"wp:attachment":[{"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tunecom.be\/stg_ba12f\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

Stuff to think about<\/h5>\n\n\n\nPrior to deploying our first resource in a resource group, we have a couple of recommendations <\/strong>and\/or limitations <\/strong>that we need to take care of:<\/p>\n\n\n\n