Merge pull request #233841 from rvandenbedem/patch-1

Update concepts-identity.md

Author: prmerger-automator[bot]

articles/azure-vmware/concepts-identity.md

@@ -3,13 +3,13 @@ title: Concepts - Identity and access
 description: Learn about the identity and access concepts of Azure VMware Solution
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 4/6/2023
+ms.date: 4/7/2023
 ms.custom: "references_regions, engagement-fy23"
 ---
 
 # Azure VMware Solution identity concepts
 
-Azure VMware Solution private clouds are provisioned with a vCenter Server and NSX-T Manager. You'll use vCenter to manage virtual machine (VM) workloads and NSX-T Manager to manage and extend the private cloud. The CloudAdmin role is used for vCenter Server and the CloudAdmin role (with restricted permissions) is used for NSX-T Manager.
+Azure VMware Solution private clouds are provisioned with a vCenter Server and NSX-T Manager. You'll use vCenter Server to manage virtual machine (VM) workloads and NSX-T Manager to manage and extend the private cloud. The CloudAdmin role is used for vCenter Server and the CloudAdmin role (with restricted permissions) is used for NSX-T Manager.
 
 ## vCenter Server access and identity
 

articles/azure-vmware/includes/create-private-cloud-azure-portal-steps.md

@@ -3,7 +3,7 @@ title: Create an Azure VMware Solution private cloud
 description: Steps to create an Azure VMware Solution private cloud using the Azure portal.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 12/05/2022
+ms.date: 4/7/2023
 author: suzizuber
 ms.author: v-szuber
 ---
@@ -38,8 +38,9 @@ You can create an Azure VMware Solution private cloud using the Azure portal or
    | **Subscription** | Select the subscription you plan to use for the deployment. All resources in an Azure subscription are billed together.|
    | **Resource group** | Select the resource group for your private cloud. An Azure resource group is a logical container into which Azure resources are deployed and managed. Alternatively, you can create a new resource group for your private cloud. |
    | **Resource name** | Provide the name of your Azure VMware Solution private cloud. |
-   | **Location** | Select a location, such as **east us**. It's the *region* you defined during the planning phase. |
+   | **Location** | Select a location, such as **(US) East US 2**. It's the *region* you defined during the planning phase. |
    | **Size of host** | Select the **AV36**, **AV36P** or **AV52** SKU. |
+   | **Host Location** | Select **All hosts in one availability zone** for a standard private cloud or **Hosts in two availability zones** for stretched clusters. |
    | **Number of hosts** | Number of hosts allocated for the private cloud cluster. The default value is 3, which you can increase or decrease after deployment. If these nodes are not listed as available, please contact support to [request a quota increase](../request-host-quota-azure-vmware-solution.md?WT.mc_id=Portal-VMCP). You can also click the link labeled **If you need more hosts, request a quota increase** in the Azure portal. |
    | **Address block for private cloud** | Provide an IP address block for the private cloud.  The CIDR represents the private cloud management network and is used for the cluster management services, such as vCenter Server and NSX-T Manager. Use /22 address space, for example, 10.175.0.0/22.  The address should be unique and not overlap with other Azure Virtual Networks and with on-premises networks. |