If you want Prod and non-prod to be connected to each other, maybe in future, then plan IPAM in such a way that there are no overlaps between them.
You can have a same name for subnets but for the ease of figuring out which environment you are working on, you can follow some naming convention. From my perspective subnets name can be the same but make sure your VNET name is named with a conversion where you can identify your environment.
Its "naming convention". Got a typo there. yes, you are correct. Something like vnet1-prod-eastus. But as far as subnet goes, I think its upto you. You can either do Appserver-subnet or prod-appserver-subnet
Is there any best practices on the usages of subnets.
i saw from some bicep files in quick templates that microsoft was creating a subnet for function apps and one for private end points.
should there be different ones for different types of azure resources?
There are few services which requires you to create a delegated subnet and not deploy any other resources on that subnet other than the resource which got delegated. And Azure firewall needs subnet to be named as AzureFirewallSubnet. Gateway subnet needs to be named as "GatewaySubnet". So you will need to read through the doc of the respective resource which you will deploy and then proceed according to the recommendation provided
Sign in to comment