
Deploy a virtual network in Azure to host a domain controller and extend on-prem Active Directory. Use resource groups and a dashboard to track the Azure deployment and VPN connection.
Deploy a network security group to protect the vnet, configure inbound from 10.0.0.0/16 and outbound to 10.0.0.0/16, and associate the NSG with the Azure AD subnet.
Run the address space calculator (PowerShell script) to determine the gateway subnet prefix, such as 192.168.255.240/28, then deploy the gateway subnet in the vnet.
Create a virtual network gateway in central us, name it azure gw, connect to a vnet with a public ip, and deploy a route-based vpn using a basic sku.
Deploy a local network gateway to represent the on-prem VPN endpoint, configuring the public IP, address space, and optional BGP settings in central US.
Deploy a site-to-site vpn in Azure by linking the Azure vnet gateway to on-prem local gateway with a shared key, then verify the connection to extend on-prem ad into Azure.
Configure the Azure vnet to use the on-prem dns server (ip 10.0.0.4) so the new vm resolves AZ 103 exam.com and joins the on-prem ad over vpn.
Deploy a domain controller in Azure by provisioning a Windows Server 2016 data center VM in the lab resource group with a data disk and no public access.
Configure a static internal ip 192168.1.4 for the co2 vm, verify vpn connectivity to the on-prem dc01, and perform post-setup tasks to prepare the new domain controller.
Promote the dc02 VM to a domain controller by joining it to the on-premises Active Directory, ensuring DNS resolution, then restart and finalize the domain controller promotion.
Promote a virtual machine to a domain controller by installing Active Directory Domain Services and DNS, joining an existing on-prem domain in Azure, and replicating to the new DC.
Configure on prem and azure active directory sites by creating an on prem site and an azure site, assigning 10.0.0.0/24 and 192.168.1.0/24 subnets, and moving DCs to avoid VPN traffic.
Reconfigure the Azure vnet DNS to point to the new domain controller DC2 (IP 192.168.1.4), remove the on-prem DNS, and restart VMs to support extended on-prem Active Directory in Azure.
With the race to Microsoft Azure in full sprint mode, you need to know how to PROPERLY extend an on-prem Active Directory forest into Microsoft Azure. Otherwise, you risk getting left behind.
This 30+ lesson course is a little different from most Udemy courses you've encountered.
This course is actually a guided deployment lab that walks you through the process of connecting an on-prem network to Azure with a site-to-site VPN. It then shows you how to properly configure the Azure virtual network and Azure VM to support an on-prem Active Directory.
Lastly, this lab walks you through the process of actually extending an on-prem Active Directory forest into Microsoft Azure. The smallest minute details are covered, as are the steps to protect your Azure virtual network and Azure-based domain controller.
What You'll Learn
Students completing this lab will learn how to deploy the necessary Azure resources for an AD extension into Azure and how to perform the extension of Active Directory into Azure.
We'll kick off the lab by deploying and securing the Azure virtual network that will host the Azure-based domain controller.
With the Azure network provisioned and properly secured with a Network Security Group, we'll walk through the process of establishing VPN connectivity between the on-prem network and the Azure virtual network.
Later in the lab, you'll learn how to properly configure custom DNS on the Azure virtual network so that it properly supports the on-prem Active Directory.
With the Azure infrastructure deployed and configured, you'll learn how to deploy and configure a virtual machine in Azure. This VM will become the Azure-based domain controller for the on-prem AD.
Wrapping up the lab, you'll learn how to correctly promote the Azure-based virtual machine to a domain controller for the on-prem AD. You'll also learn how to configure AD Sites and Services to properly reflect your new Azure site.