I went looking for why a VM that applied green hung ten minutes later on its first apt-get, and the answer was one subnet field, not a route.
Microsoft's "default outbound access" page now says that for the API version released after March 31, 2026, subnets in new virtual networks have defaultOutboundAccess set to false , and that the portal already defaults to private subnets. Existing VNets are not touched. So a VM dropped into a subnet made this spring in the portal gets no implicit SNAT: it boots, the apply is green, and the first package install waits forever.
The read before you put a NIC there:
az network vnet subnet show -g "$RG" --vnet-name "$VNET" -n "$SUBNET" \ --query "{outbound:defaultOutboundAccess, nat:natGateway.id, rt:routeTable.id}" -o json
outbound: false with nat: null and no route table is the bad combination: private subnet, no egress.…