Merge pull request #6864 from Paasin/docbug-8025006

Docbug-80025006

Author: rjagiewich

memdocs/configmgr/core/get-started/azure-template.md

@@ -2,7 +2,7 @@
 title: Create a lab in Azure
 titleSuffix: Configuration Manager
 description: Automate the creation of a Configuration Manager technical preview lab or current branch evaluation lab using Azure templates
-ms.date: 07/22/2019
+ms.date: 03/14/2022
 ms.prod: configuration-manager
 ms.technology: configmgr-core
 ms.topic: conceptual
@@ -30,9 +30,11 @@ For more information, see [Configuration Manager on Azure](../understand/configu
 ## Prerequisites
 
 This process requires an Azure subscription in which you can create the following objects: 
-- Two Standard_B2s virtual machines for domain controller, management point, and distribution point.
-- One Standard_B2ms virtual machine for the primary site server and the SQL Server database server.
-- Standard_LRS storage account
+- Two Standard_B2s virtual machines for domain controller, management point, and distribution point. 
+- Zero to three virtual machines for client devices.
+- One Standard_B2ms virtual machine for the primary site server and the SQL Server database server
+- If you choose to create a hierarchy, one other Standard_B2ms virtual machine for the central administration site.
+- Standard_LRS storage account.
 
 > [!Tip]  
 > To help determine potential costs, see the [Azure pricing calculator](https://azure.microsoft.com/pricing/calculator/).  
@@ -62,6 +64,8 @@ This process requires an Azure subscription in which you can create the followin
         - **Admin Username**: The name of a user on the VMs with administrative rights. You use this user to sign in to the VMs.  
 
         - **Admin Password**: The password must meet the Azure complexity requirements. For more information, see [adminPassword](/rest/api/compute/virtualmachines/createorupdate#osprofile).  
+        
+        -  **Configuration**: You can choose "Standalone" or "Hierarchy". This setting is available for the current branch template only. 
 
     > [!Important]  
     > The following settings are required by Azure. Use the default values. Don't change these values.  
@@ -72,22 +76,31 @@ This process requires an Azure subscription in which you can create the followin
     > 
     > - **Location**: The location for all resources
 
+    > [!NOTE]
+    > If you edited the Azure template before you deployed it, then you need to change the `_artifactsLocation` value.
+    >
+    > - For the technical preview template, the value is `https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/application-workloads/sccm/sccm-technicalpreview/azuredeploy.json`
+    > - For the current branch template, the value is `https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/application-workloads/sccm/sccm-currentbranch/azuredeploy.json`
+
 4. Read the terms and conditions. If you agree, select **I agree to the terms and conditions stated above**. Then select **Purchase** to continue. 
 
 Azure validates the settings, and then begins the deployment. Check the status of the deployment in the Azure portal. 
 
 > [!NOTE]
 > The process can take 2-4 hours. Even when the Azure portal shows successful deployment, configuration scripts continue to run. Don't restart the VMs during the process.
 
-To see the status of the configuration scripts, connect to the `<prefix>PS1` server, and view the following file: `%windir%\TEMP\ProvisionScript\PS1.json`. If it shows all steps as complete, the process is done.
+To see the status of the configuration scripts, connect to the `<prefix>PS01` server, and view the following file: `%windir%\TEMP\ProvisionScript\PS01.json`. If it shows all steps as complete, the process is done.
+
+> [!NOTE]
+> When you use the current branch template, it uses the CAS.json file at the same location on the `<prefix>CS01` server.
 
 To connect to the VMs, first get from the Azure portal the public IP addresses for each VM. When you connect to the VM, the domain name is `contoso.com`. Use the credentials that you specified in the deployment template. For more information, see [How to connect and log on to an Azure virtual machine running Windows](/azure/virtual-machines/windows/connect-logon).
 
 
 
 ## Azure VM info
 
-All Three VMs have the following specifications:
+All  VMs have the following specifications:
 - 150 GB of disk space
 - Both a public and private IP address. The public IPs are in a network security group that only allows remote desktop connections on TCP port 3389. 
 
@@ -98,7 +111,7 @@ The prefix that you specified in the deployment template is the VM name prefix.
 
 - Active Directory domain controller
 - Standard_B2s, which has two processors and 4 GB of memory
-- Windows Server 2019 Datacenter edition
+- Windows Server 2022 Datacenter edition
 
 #### Windows features and roles
 - Active Directory Domain Services (ADDS)
@@ -109,7 +122,7 @@ The prefix that you specified in the deployment template is the VM name prefix.
 ### `<prefix>PS01`
 
 - Standard_B2ms, which has two processors and 8 GB of memory
-- Windows Server 2016 Datacenter edition
+- Windows Server 2019 Datacenter edition
 - SQL Server
 - Windows 10 ADK with Windows PE 
 - Configuration Manager primary site
@@ -133,8 +146,8 @@ The prefix that you specified in the deployment template is the VM name prefix.
 - Internet Information Service (IIS)
 - Background intelligent transfer service (BITS)
 
-### `<prefix>CL01`
+### `<prefix>CL01` 
 
 - Only for Configuration Manager current branch evaluation template
 - Windows 10
-- Configuration Manager client
+- Configuration Manager client