This project documents the deployment of a functional Active Directory environment hosted within Microsoft Azure. I deployed two virtual machines, configured a static IP address for the domain controller, installed Active Directory Domain Services, promoted the server to a domain controller, and verified domain functionality by attaching a Windows client to the new domain. This project demonstrates the foundational steps required to build a Windows Server–based domain environment.
- Microsoft Azure
- Azure Virtual Network
- Remote Desktop Protocol (RDP)
- Active Directory Domain Servies (AD DS)
- Active Directory Users and Computers
- PowerShell
- Deploy a Windows Server domain controller in Azure
- Install and configure Active Directory Domain Services
- Create and configure an Active Directory forest
- Join a Windows client to the domain
- Validate authentication and directory functionality
- Platform: Microsoft Azure
- Domain Controller: Windows Server 2022 Datacenter
- Client Machine: Windows 10 Pro
- Make sure that the DC and Client are on the same subnet
- Select the Domain Controller then select Network Settings then open the Network Interface
- Select ipconfig1
- For Private IP address setting choose Static and save changes
- Select Client virtual machine then select Network Settings and open the Network Interface
- Select DNS Servers and choose Custom
- Enter the DC's Private IP address and save
- Restart the client VM
- Log into the Domain Controller and open the Server Manager then select Add roles and features
- On the Server Roles tab check Active Directory Domain Services then complete the installation
- In the Server Manager click the notification flag and select Promote this server to a domain controller
- Choose Add a new forest and set the root domain name
- Set the Directory Services Restore Mode (DSRM) password and complete the install and reboot the VMM
- Log into the Client Virtual Machine as the Domain Administrator open Windows PowerShell
- Attempt to ping the DC's private IP address
- Ensure the ping succeeded
- Enter the command
ipconfig /allinto Windows Powershell - Confirm the output for the client's DNS settings shows the DC's private IP address
- In the Client Virtual Machine right click the Start Button and select System
- Navigate to the About page and select **Rename this PC (advanced) then click Change
- Check the Member of Domain box and enter the name of the domain and apply the changes
- On the Client Virtual Machine right click the Start Button and select Computer Management
- Go to Local Users and Groups and open the Groups folder
- Select Remote Desktop Users and click Add
- Type Domain Users in the box and click Check Names
- Apply the changes
- Restart the VM
- Open the Server Manager on the Domain Controller
- Select Tools then Active Directory Users and Computers
- Expand the Domain then click Computers
- The client VM should be inside
- Deployed a Windows Server domain controller and a Windows client VM in Microsoft Azure
- Configured a static IP address for the domain controller to ensure consistent DNS and domain availability
- Established a functioning Active Directory Domain Services (AD DS) environment
- Promoted the server to a domain controller and created a new domain for the lab
- Joined the client VM to the domain and confirmed domain connectivity
- Verified that domain authentication and basic domain functionality were working as expected
- Deploying Azure Virtual Machines for server and client environments
- Configuring static IP addresses in Azure for reliable domain controller DNS resolution
- Connecting and configuring virtual machines within the same Azure virtual network
- Installing and managing Active Directory Domain Services (AD DS)
- Promoting a Windows Server to a domain controller and creating a new domain
- Joining Windows client machines to a domain
- Verifying domain functionality, including DNS, authentication, and domain connectivity
- Using Azure Portal and Windows Server administration tools to manage cloud-hosted infrastructure














