2

I'm deploying a global networking solution and using Terraform as my IaC solution. I have ExpressRoutes, VPN Gateways, Vnet-to-Vnet connections etc.

I've deployed a VPN Gateway in Azure North Central US and now when I come to deploy and IP address for it I can't. By default I use Zone-Redundant availability zones. Ie. Zone 1, 2 and 3. When I try to deploy an IP using Terraform, I can't use any of the available options - no zone string list, no single zone, not the No-Zone or None parameter. All I get is an error from the MS API saying the available zones for the region are ''. It's literally empty.

If I deploy it manually then get the IP properties of the address it shows the zones as an empty array. Are MS experiencing issues right now? I find it incomprehensible that the North Central US zone which is the regional pair of South Central US (which has 3 availability zones) has...no zones. I'm confused. Could someone share their experiences please, and advise whether this is a temporary issue. I scoured the internet and found nothing. I'm normally working in the European Azure regions so this is the first time I've used this particular one.

Architect Jamie
  • 1,621
  • 4
  • 18
  • This is a really bad state of affairs. A VPN Gateway IP must have zones configured. I can't deploy a gateway to North Central US, can't leverage the pairing for BC/DR, I have to change my ExpressRoute VXC and all my network peerings and Terraform all to transition to Azure Central. I don't know what the politics is behind this but it was 12 years ago North Central (Illinois) was first opened. And in 12 years MS couldn't pair it with at least one other datacenter. I'm dumbfounded. – Architect Jamie Oct 19 '21 at 04:20

1 Answers1

0

Currently, there are no availability zones present for North Central US in Azure but as per the document here, availability zones will be coming soon for North Central US. As of now, these are the Azure Regions with Availability zones.

enter image description here

ChaitanyaN-MSFT
  • 466
  • 2
  • 5