I have been configuring a demonstration environment on Azure and that connected to my local datacenter with S2S VPN.

I created several VM´s in Azure and during that process I connected them to my own network. One thing I noticed once doing this was that these VM´s was not activated.

The reason for this appeared to be quite easy and as I had the plan to setup a DC with DNS I only added that in the networking dns settings and the gallery VM´s points to a KMS in Azure and as I did not have a name resolution working the VM´s could not be activated. Checking that you can do a name resolution of the following url shows if you have any potential issues..

NSLOOKUP kms.core.windows.net 

So after I added an second DNS (excuse me for adding a google dns, but it is so easy to remember) and started the VM´s I could see that they been successfully activated 🙂

Happy Azuring 🙂