Azure Vnets and Subnets best practices

Lance Lyons 86 Reputation points

Hi, Trying to figure out some best practices for Azure Virtual Network/subnet design.

we have 3 subscriptions (sandbox, non production, production). We are going to be deploying to non prod and production using bicep/arm templates.

each subscription has a vnet with 65536 addresses.

we are thinking of subnets with 256 addresses.

there is currently no peering between production and non production and sandbox.

we currently have dedicated VPNs to each subscription but are in the process of setting up an express route.

i noticed with some of the bicep templates for vnets and subnets that are in the Microsoft Azure quick templates that common subnets are created for webapps, functions, private end points, databases, etc

is there a best practice for the different subnets?

From an automation perspective should subnets in the different subscriptions use similar names?

is there any documentation related to this scenario?

thanks in advance

Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
1,841 questions
0 comments No comments
{count} votes

Accepted answer
  1. msrini-MSFT 9,056 Reputation points Microsoft Employee


    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.


    Karthik Srinivas

0 additional answers

Sort by: Most helpful