In the article we set up Azure AD DS managed domain and the deployed configuration set up the managed domain in its own virtual network and subnet as per below:

Azure Virtual Network Peering allows seamless connectivity between different Azure Virtual Network(s) (Azure VNet). Typical use case for using virtual network peering might include the following:

“There is an existing Azure VNet containing SubNets and Virtual Machines and a new Azure AD DS managed domain is provisioned in a separate virtual network. The Virtual Machines need to be a member of Azure AD DS managed domain and this can be done through Azure Virtual Network peering.”

We will consider the following deployment example:

The following articles will detail how to setup the above lab:

• Setting up AzureVNet
• Creating AzureVM
• Deploying Azure AD DS domain

Choose the default virtual network created in Azure AD DS instance and select Peerings

Select “+Add”

A two-way peering link needs to be created between the two virtual networks and this is highlighted in the information section under “Add peering”

The statuses of two peering links can be viewed under Notifications

And once successful a Peering Status of Connected is shown on individual virtual network(s)

With the above what we have accomplished so far is to allow the following virtual network’s to communicate

iDynamics-VNet has no information about the DNS servers and this needs to be updated/configured manually. The IP Addresses of Azure AD DS domain controllers can be obtained from aadds-vnet virtual network

Enter the above highlighted IP Addresses to the DNS servers custom settings for iDynamics-VNet

Connectivity to various virtual machines within iDynamics-VNet will be controlled through a managed jump box:

Establish RDP connection to AZ-MGMT01

Once connected to the AZ-MGMT01 should be able to ping Azure AD DS managed domain “idynamics.com.au”. The Public IP address in the screen snap shot below will be different this is because the virtual machine is was in a status of Stopped(deallocated) so a new Public IP Address was assigned when the virtual machine was started again.