Configuring Virtual Networking for Azure Active Directory Domain Services - techie

Latest

Monday, November 18, 2019

Configuring Virtual Networking for Azure Active Directory Domain Services




Introduction

An Azure Active Directory Domain Services (Azure AD DS) the managed domain is deployed into an Azure virtual system subnet. It provides availability to clients and applications. This virtual network subnet should be used for the managed domain resources provided by the Azure platform.

As you make own VMs and applications, they shouldn't be deployed into the same virtual system subnet. Rather, you might create and deploy your applications into a different virtual network subnet, or in a different virtual network peered to the Azure AD DS virtual network.

Virtual Network Peering

You may have a current Azure virtual network for VMs or keep your Azure AD DS managed domain virtual network isolated. To use the managed domain, VMs in other virtual networks need an approach to communicate with the Azure AD DS domain controllers. This availability can be given using the Azure virtual network peering.
With Azure virtual network peering, two virtual networks are connected, without the requirement for a virtual private network (VPN) device. Network peering lets you rapidly interface virtual networks and confine traffic streams over your Azure environment.



No comments:

Post a Comment

Note: Only a member of this blog may post a comment.