Merge pull request #46386 from stgeorgi/patch-11

Chagens made match the new Azure UI

Author: ktoliver

articles/virtual-desktop/create-host-pools-azure-marketplace.md

@@ -50,7 +50,7 @@ Here's what you do for the **Basics** blade:
 3. Enter a comma-separated list of users who can sign in to the Windows Virtual Desktop clients and access a desktop after the Azure Marketplace offering finishes. For example, if you want to assign [email protected] and [email protected] access, enter "[email protected],[email protected]."
 4. Select **Create new** and provide a name for the new resource group.
 5. For **Location**, select the same location as the virtual network that has connectivity to the Active Directory server.
-6. Select **OK**.
+6. Select **Next : Configure virtual machines >**.
 
 >[!IMPORTANT]
 >If you're using a pure Azure Active Directory Domain Services and Azure Active Directory solution, make sure to deploy your host pool in the same region as your Azure Active Directory Domain Services to avoid domain-join and credential errors.
@@ -61,7 +61,7 @@ For the **Configure virtual machines** blade:
 
 1. Either accept the defaults or customize the number and size of the VMs.
 2. Enter a prefix for the names of the virtual machines. For example, if you enter the name "prefix," the virtual machines will be called "prefix-0," "prefix-1," and so on.
-3. Select **OK**.
+3. Select **Next : Virtual machine settings**.
 
 ### Virtual machine settings
 
@@ -75,7 +75,7 @@ For the **Virtual machine settings** blade:
 1. For **Image source**, select the source and enter the appropriate information for how to find it and how to store it. If you choose not to use managed disks, select the storage account that contains the .vhd file.
 2. Enter the user principal name and password for the domain account that will join the VMs to the Active Directory domain. This same username and password will be created on the virtual machines as a local account. You can reset these local accounts later.
 3. Select the virtual network that has connectivity to the Active Directory server, and then choose a subnet to host the virtual machines.
-4. Select **OK**.
+4. Select **Next: Windows Virtual Desktop information**.
 
 ### Windows Virtual Desktop tenant information
 
@@ -85,15 +85,14 @@ For the **Windows Virtual Desktop tenant information** blade:
 2. For **Windows Virtual Desktop tenant name**, enter the name of the tenant where you'll be creating this host pool.
 3. Specify the type of credentials that you want to use to authenticate as the Windows Virtual Desktop tenant RDS Owner. If you completed the [Create service principals and role assignments with PowerShell tutorial](./create-service-principal-role-powershell.md), select **Service principal**. When **Azure AD tenant ID** appears, enter the ID for the Azure Active Directory instance that contains the service principal.
 4. Enter the credentials for the tenant admin account. Only service principals with a password credential are supported.
-5. Select **OK**.
+5. Select **Next : Review + create**.
 
 ## Complete setup and create the virtual machine
 
 For the last two blades:
 
-1. On the **Summary** blade, review the setup information. If you need to change something, go back to the appropriate blade and make your change before continuing. If the information looks right, select **OK**.
-2. On the **Buy** blade, review the additional information about your purchase from the Azure Marketplace.
-3. Select **Create** to deploy your host pool.
+1. On the **Review and Create** blade, review the setup information. If you need to change something, go back to the appropriate blade and make your change before continuing. If the information looks right, select **OK**.
+2. Select **Create** to deploy your host pool.
 
 Depending on how many VMs you’re creating, this process can take 30 minutes or more to complete.