S2S + P2S :: Slow Gateway Creation

I'm currently working with a customer to deploy two different Azure virtual networks. Both VNets were configured for site-to-site (S2S) VPN connectivity, and one of them also had point-to-site (P2S) VPN connectivity. We created a dynamic gateway for both VNets, and they have been taking a very long time to create.

VNet 1 is currently sitting at 1.5 hours (90 minutes) of time to create, and has still not been provisioned.

VNet 2 is currently sitting at 1 hour (60 minutes) of time to create, and has still not been provisioned.

Is there any way to get more insight as to what's going on behind the scenes? How do I know if the process is hung in the background, or what the current status is?

Update: We created two more, and all of them are in the same state. "Creating Gateway". We've usedEast US, West US, and North Central US.

Cheers,
Trevor Sullivan
Microsoft MVP: PowerShell

If this post was helpful, please click the little "Vote as Helpful" button :)