Microsoft has launched the preview of Azure VNet Peering. You can find overview information on it and some how to’s.
You need to register for the VNet Peering preview using PowerShell:
Register-AzureRmProviderFeature -FeatureName AllowVnetPeering -ProviderNamespace Microsoft.Network –force
It takes up to 30 minutes for this to complete. You can check your registration status by running:
Get-AzureRmProviderFeature -FeatureName AllowVnetPeering -ProviderNamespace Microsoft.Network
However … there does appear to be issues during these early days of the preview. I’ve tried it out with a couple of subscriptions (Open and CSP) and the registration claims to have succeeded but I cannot peer VNets yet, because I “have not registered yet”.
It’s not unusual for a preview to have issues in the first couple of days – this is the first time the feature (which is still preview!) will have widespread rollout and usage. I would expect that Microsoft has detected issues and is working on a fix for this anticipated feature.
4 thoughts on “Azure VNet Peering Is In Preview – But Has Registration Issues”
“VNet Peering will not be charged for during the review period. Once it is released for General Availability there will be a nominal charge on ingress and egress traffic that utilizes the peering.”
Seems to be a different pricing model. As far as I know, if you connect two VNEts in the same region via vpn gateway, you only pay for the gateway hours and not the traffic.
Strange that it will be different for the VNet peering.
They say “nominal charge”. I suspect it’ll be something tiny, that most of us will see up as a few cents per month.
big Fan of your blog – been reading it for quite a while – Thx for all the real-world-insights and realistic views – appreciate 😉
Dunno if you already know, but i´ve been getting the 400 Bad Request like you in the past but just got a successful feedback of the VNet-Peering-CMDlet …
Thanks. The IIS application pool threw a wobbly one day. An IISRESET sorted it out.