Amazon Web Services → Microsoft Azure
Azure equivalent of VPC subnets
VPC subnets map to Azure virtual network subnets, but placement differs.
About VPC subnets
| Provider | Amazon Web Services |
|---|---|
| Status | Generally available |
| What it is | IP ranges within a VPC. Each subnet lives in exactly one Availability Zone (or Local Zone or Outpost), so multi-AZ designs need one subnet per AZ. |
| Documentation | docs.aws.amazon.com |
| Pricing | Official pricing page |
Azure mappings (1)
| Capability | Azure equivalent | Match |
|---|---|---|
| Subnets and availability zone placement | Azure Virtual Network | Partial match |
Virtual networks, subnets & IP addressing(1)
Subnets and availability zone placement Partial match
VPC subnets map to Azure virtual network subnets, but placement differs. AWS subnets belong to one Availability Zone, while Azure subnets are regional and you pick the zone per resource.
- High availability. On AWS, a three-AZ tier needs three subnets. On Azure, one subnet can serve all zones. If you move a resource to another zone, whether it keeps its private IP depends on the resource type.
- Public and private. AWS calls a subnet public if its route table points to an internet gateway. On Azure, private subnets turn off default outbound access, and new VNets created with API versions released after March 31, 2026 default to private.
- Delegation. Some Azure PaaS services need a dedicated, delegated subnet. AWS services usually just place network interfaces in your subnets.