Azure Resource Group structure — Measure twice, cut once

Everyone is familiar with the adage “Measure twice, cut once”. What you may not realise is that this isn’t only good advice for putting up shelves, it also applies when you’re building infrastructure in Azure. The point here is that it can pay to think twice about your Azure subscription’s structure and where things fit before jumping straight into the juicy, delicious fun that is creating resources.

Recently I found myself tasked with creating the Azure infrastructure that would be used to host an application in its entirety, mainly:

• A frontend that consisted of some static content and a CDN
• …