Hey folks! I'm transitioning from AWS and need some guidance on how to properly organize my Azure networking. At the moment, I have just one subscription since we're starting out. I've set up one resource group to contain our virtual network with a CIDR block of 10.100.0.0/16. I'm planning to tie the naming conventions of the resources within this group to their respective regions.
Additionally, I'm thinking of creating separate resource groups for different services like Azure Postgres and virtual machines, which will reference the subnets defined in the networking resource group. Is this a good approach? I'd really appreciate it if anyone could point me toward some solid documentation on Azure architecture. Thanks for the help!
1 Answer
You might want to check out this resource: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-setup-guide/organize-resources. It has good insights on using resource groups effectively. Remember, a resource group should contain resources that share a common lifecycle, so it might be tricky managing a lot of groups down the road. For naming conventions, keep in mind that resource names can’t be changed after creation, so think carefully about that. Tags can be a great way to include regional information without the hassle of renaming later! Also, for networking guidance, take a look at https://learn.microsoft.com/en-us/azure/networking/foundations/network-foundations-overview.
I’m also going with resource groups per service! I have one for site-to-site VPN, one for Postgres DB, and another for a VM. It helps to keep everything organized and easily deletable when needed. I'm just figuring out how to share the vnet among these services, but your advice points me in the right direction. Thanks!