I created a new VM from Microsoft Azure portal. On that VM, I need to install my application (a windows service) which must run under an AD user account. In order to add that user on this VM, I need to join the VM to domain first. I tried regular way of connecting machine to domain through System Properties window but I get below error -

An Active Directory Domain Controller (AD DC) for the domain "*.com" could not
be contacted. Ensure that domain name is typed correctly.

Do I need to set any IP address? I checked my desktop's (which is connected to similar domain to which I want to join this VM) network properties but everything (IPV4, DNS IP address etc.) is set to obtain automatically. What do I need to know to join azure VM to domain?


  • is that VM running in a VNET? do you have a S2S VPN connections ? – techmike2kx Aug 18 '16 at 14:29

You need two steps to make this work:

  1. Configure the Site-to-Site VPN between Azure and your corpnet.

  2. Manually configure the DNS to make sure that the VM uses domain controller as its' DNS server.

For the first part, please follow this guide to configure the S2S VPN.

Note: You needn't create the new VNET, just select the existing one when create the connection. Otherwise, you may need to re-create your VM to put it into the new VNET.

For the second part, please use the custom DNS settings. Here is the screenshot of my Azure:

enter image description here

  • Thanks Steven for the reply. I was able to create a new VM in the existing VNET. Now when try to connect it by clicking "Connect" on the dashboard nothing happens. It doeen't downloads the .rdp file. Did I missed something? – Saurabh Aug 19 '16 at 17:07
  • @Saurabh Sorry for the delay response. I not sure the root cause of this issue. As a workaround, we can just simply create e RDP configure file manually. Run mstsc.exe and input the public IP address of the VM, then save the configuration to a file. – Steven Lee - MSFT Aug 29 '16 at 9:57

Virtual network peering is now available for virtual networks that belong to subscriptions in different Azure Active Directory tenants. Virtual network peering enables direct VM-to-VM connectivity across virtual machines deployed in different virtual networks using the Microsoft backbone.

Learn how to get started with peering virtual networks from different Azure Active Directory tenants. If you're not familiar with virtual network peering, learn more from our documentation.

Source: https://azure.microsoft.com/en-us/updates/cross-aad-vnet-peering/

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.