Merge pull request #6741 from Justinha/patch-1

Update adds-on-azure-vm.md

Author: JillGrant615

WindowsServerDocs/identity/ad-ds/deploy/virtual-dc/adds-on-azure-vm.md

@@ -1,10 +1,10 @@
 ---
 title: Install Active Directory Domain Services on an Azure virtual machine
 description: How to create a new Active Directory forest on a virtual machine (VM) on an Azure virtual machine.
-author: iainfoulds
+author: justinha
 ms.author: justinha
-manager: daveba
-ms.date: 6/28/2022
+manager: femila
+ms.date: 03/18/2025
 ms.topic: article
 ---
 
@@ -19,7 +19,7 @@ AD DS can run on an Azure virtual machine (VM) in the same way it runs in many o
 * An Azure virtual machine [availability set](/azure/virtual-machines/availability-set-overview) to put two Active Directory Domain Services (AD DS) domain controllers in.
 * Two Azure virtual machines to run AD DS and DNS.
 
-### Items that are not covered
+### Items that aren't covered
 
 * [Creating a site-to-site VPN connection](/azure/vpn-gateway/tutorial-site-to-site-portal) from an on-premises location
 * [Securing network traffic in Azure](/azure/security/azure-security-network-security-best-practices)
@@ -39,17 +39,17 @@ If you don't have an Azure subscription, [create a free account](https://azure.m
 
 The following script automates the process of building two Windows Server 2019 VMs, for the purpose of building domain controllers for a new Active Directory Forest in Azure. An administrator can modify the variables below to suit their needs, then complete, as one operation. The script creates the necessary resource group, network security group with a traffic rule for Remote Desktop, virtual network and subnet, and availability group. The VMs are each then built with a 20 GB data disk with caching disabled for AD DS to be installed to.
 
-The script below can be run directly from the Azure portal. If you choose to install and use the CLI locally, this quickstart requires that you are running the Azure CLI version 2.0.4 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI 2.0](/cli/azure/install-azure-cli).
+The script below can be run directly from the Azure portal. If you choose to install and use the CLI locally, this quickstart requires that you're running the Azure CLI version 2.0.4 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI 2.0](/cli/azure/install-azure-cli).
 
 | Variable Name | Purpose |
 | :---: | :--- |
 | AdminUsername | Username to be configured on each VM as the local administrator. |
 | AdminPassword | Cleartext password to be configured on each VM as the local administrator password. |
-| ResourceGroupName | Name to be used for resource group. Should not duplicate an existing name. |
+| ResourceGroupName | Name to be used for resource group. Shouldn't duplicate an existing name. |
 | Location | Azure location name that you would like to deploy to. List supported regions for the current subscription using `az account list-locations`. |
-| VNetName | Name to assign the Azure virtual network Should not duplicate an existing name. |
-| VNetAddress | IP scope to use for Azure networking. Should not duplicate an existing range. |
-| SubnetName | Name to assign the IP subnet. Should not duplicate an existing name. |
+| VNetName | Name to assign the Azure virtual network Shouldn't duplicate an existing name. |
+| VNetAddress | IP scope to use for Azure networking. Shouldn't duplicate an existing range. |
+| SubnetName | Name to assign the IP subnet. Shouldn't duplicate an existing name. |
 | SubnetAddress | Subnet address for the domain controllers. Should be a subnet inside of the VNet. |
 | AvailabilitySet | Name of the availability set the domain controller VMs will join. |
 | VMSize | Standard Azure VM Size available in the location for deployment. |
@@ -60,7 +60,7 @@ The script below can be run directly from the Azure portal. If you choose to ins
 | DC2IP | IP address for second domain controller. |
 
 ```azurecli
-#Update based on your organizational requirements
+#Add lines for AdminUsername and AdminPassword, and update based on your organizational requirements
 Location=westus2
 ResourceGroupName=ADonAzureVMs
 NetworkSecurityGroup=NSG-DomainControllers
@@ -71,8 +71,6 @@ SubnetAddress=10.10.10.0/24
 AvailabilitySet=DomainControllers
 VMSize=Standard_DS1_v2
 DataDiskSize=20
-AdminUsername=azureuser
-AdminPassword=ChangeMe123456
 DomainController1=AZDC01
 DC1IP=10.10.10.11
 DomainController2=AZDC02
@@ -149,7 +147,7 @@ az vm create \
 
 If the Azure virtual machines created as part of this process will be an extension of an existing on-premises Active Directory infrastructure, the DNS settings on the virtual network must be changed to include your on-premises DNS servers before deployment. This step is important to allow the newly created Domain Controllers in Azure to resolve on-premises resources and allow for replication to occur. More information about DNS, Azure, and how to configure settings can be found in the section [Name resolution that uses your own DNS server](/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances#name-resolution-that-uses-your-own-dns-server).
 
-After promoting the new domain controllers in Azure, they will need to be set to the primary and secondary DNS Servers for the virtual network, and any on-premises DNS Servers would be demoted to tertiary and beyond. VMs continue to use their current DNS settings until they are restarted. More information on changing DNS Servers can be found in the article [Create, change, or delete a virtual network](/azure/virtual-network/manage-virtual-network#change-dns-servers).
+After promoting the new domain controllers in Azure, they'll need to be set to the primary and secondary DNS Servers for the virtual network, and any on-premises DNS Servers would be demoted to tertiary and beyond. VMs continue to use their current DNS settings until they're restarted. More information on changing DNS Servers can be found in the article [Create, change, or delete a virtual network](/azure/virtual-network/manage-virtual-network#change-dns-servers).
 
 Information about extending an on-premises network to Azure can be found in the article [Creating a site-to-site VPN connection](/azure/vpn-gateway/vpn-gateway-howto-site-to-site-resource-manager-portal).
 
@@ -174,7 +172,7 @@ Connect to AZDC01 using the credentials you provided in the script.
    * Review the selections made in the wizard and choose **Next**
 
 > [!NOTE]
-> The Prerequisites Check will warn you that the physical network adapter does not have static IP address(es) assigned, you can safely ignore this as static IPs are assigned in the Azure virtual network.
+> The Prerequisites Check will warn you that the physical network adapter doesn't have static IP address(es) assigned, you can safely ignore this as static IPs are assigned in the Azure virtual network.
 
 * Choose **Install**
 
@@ -210,7 +208,7 @@ Connect to AZDC02 using the credentials you provided in the script.
    * Review the selections made in the wizard and choose **Next**
 
 > [!NOTE]
-> The Prerequisites Check will warn you that the physical network adapter does not have static IP address(es) assigned. You can safely ignore this, as static IPs are assigned in the Azure virtual network.
+> The Prerequisites Check will warn you that the physical network adapter doesn't have static IP address(es) assigned. You can safely ignore this, as static IPs are assigned in the Azure virtual network.
 
 * Choose **Install**