The above availability zones are in the same vnet. Azure Networking (DNS, Traffic Manager, VPN, VNET) ... Can a subnet in one availability zone communicate with another subnet in a different availability zone. Private IP address – Enter a private IP in that subnet for the load balancer to use. When deploying multiple domain controllers in Azure, each of them should be in a different availability zone or in the same availability set. AWS guarantees that the availability zones within a region are geographically separate (different data centers), while Azure has some regions that have a single availability zone. This "zonal stack" consists of virtual machine instances, NAT gateway resources, public IP address and/or prefix resources on a subnet that is assumed to be serving only the same zone. IP Address assignment – Static. A VPC spans all of the Availability Zones in the Region. Within each availability zone, the hosts/VMs and veos interfaces are connected to their corresponding subnets when the network is operating normally. You can optionally add subnets in a Local Zone, which is an AWS infrastructure deployment that places compute, storage, database, and other select services closer to your end users. Each subnet associates to a route table within the cloud infrastructure. I have been able to create more than one subnet in the same AZ. Subnet – For effective design and control of resources deployed on the cloud, both Azure VNet and AWS VPC segregate the networks with subnets. The pattern you want to use for zone isolation is creating a "zonal stack" per availability zone. All Zone redundant service will replicate data and application across Availability Zone for high resilience. I am trying to create subnets per availability zones in Azure using terraform. Azure Availability Zone is made out of one or more datacentres in the same Azure region, which have independent power, hardware, networking, and cooling. Availability Zone – Select Zone-redundant. Subscription – Select the Azure subscription. I'm a little confused about a statement Ryan made regarding the relationship between a subnet and an availability zone. https://mykloud.wordpress.com/2017/09/22/azure-availability-zones-az Don’t use a spot VM to save costs – a domain controller should be always online. He said to remember that essentially there is a 'one subnet, one availability zone' relationship. Subnet – Select the subnet the firewalls are in. Enter al basic information and don’t forget about the availability options. An AWS VPC spans all the Availability Zones (AZs) in that region, hence, subnets in AWS VPC are mapped to Availability Zones (AZs). What if the availability zones are in different vnet? A subnet must only belong to one AZ and cannot span AZs. Each Azure region contains a minimum of three Azure Availability Zones. After creating a VPC, you can add one or more subnets in each Availability Zone. I am using the code below to create a subnet.