Merge pull request #277027 from rvandenbedem/patch-1

Update architecture-private-clouds.md

Author: v-dirichards

articles/azure-vmware/architecture-private-clouds.md

@@ -3,7 +3,7 @@ title: Architecture - Private clouds and clusters
 description: Understand the key capabilities of Azure VMware Solution software-defined data centers and VMware vSphere clusters. 
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 5/25/2024
+ms.date: 6/3/2024
 ms.custom: engagement-fy23
 ---
 
@@ -55,60 +55,62 @@ When planning your Azure VMware Solution design, use the following table to unde
 
 The Multi-AZ capability for Azure VMware Solution Stretched Clusters is also tagged in the following table. Customer quota for Azure VMware Solution is assigned by Azure region, and you are not able to specify the Availability Zone during private cloud provisioning. An auto selection algorithm is used to balance deployments across the Azure region. If you have a particular Availability Zone you want to deploy to, open a [Service Request](https://rc.portal.azure.com/#create/Microsoft.Support) with Microsoft requesting a "special placement policy" for your subscription, Azure region, Availability Zone, and SKU type. This policy remains in place until you request it be removed or changed.
 
-**SKUs** marked in **bold** are of limited availability due to customer consumption and quota may not be available upon request.
-
-| Azure region | Availability Zone | SKU   | Multi-AZ SDDC |
-| :---         | :---:             | :---: | :---:         |
-| Australia East | AZ01 | AV36P, AV64 | Yes |
-| Australia East | AZ02 | AV36 | No |
-| Australia East | AZ03 | AV36P, AV64 | Yes |
-| Australia South East | AZ01 | AV36 | No |
-| Brazil South | AZ02 | **AV36** | No |
-| Canada Central | AZ02 | AV36, **AV36P** | No |
-| Canada East | N/A | AV36 | No |
-| Central India | AZ03 | AV36P | No |
-| Central US | AZ01 | AV36P | No |
-| Central US | AZ02 | **AV36** | No |
-| Central US | AZ03 | AV36P | No |
-| East Asia | AZ01 | AV36 | No |
-| East US | AZ01 | **AV36P** | Yes |
-| East US | AZ02 | **AV36P**, AV64 | Yes |
-| East US | AZ03 | **AV36**, **AV36P**, AV64 | Yes |
-| East US 2 | AZ01 | **AV36**, AV64 | No |
-| East US 2 | AZ02 | AV36P, **AV52**, AV64 | No |
-| France Central | AZ01 | **AV36** | No |
-| Germany West Central | AZ01 | AV36P | Yes |
-| Germany West Central | AZ02 | **AV36** | Yes |
-| Germany West Central | AZ03 | AV36, **AV36P** | Yes |
-| Italy North | AZ03 | AV36P | No |
-| Japan East | AZ02 | **AV36** | No |
-| Japan West | AZ01 | **AV36** | No |
-| North Central US | AZ01 | **AV36**, AV64 | No |
-| North Central US | AZ02 | AV36P, AV64 | No |
-| North Europe | AZ02 | AV36, AV64 | No |
-| Qatar Central | AZ03 | AV36P | No |
-| South Africa North | AZ03 | AV36 | No |
-| South Central US | AZ01 | AV36, AV64 | No |
-| South Central US | AZ02 | **AV36P**, AV52, AV64 | No |
-| South East Asia | AZ02 | **AV36** | No |
-| Sweden Central | AZ01 | AV36 | No |
-| Switzerland North | AZ01 | **AV36**, AV64 | No |
-| Switzerland North | AZ03 | AV36P | No |
-| Switzerland West | AZ01 | **AV36**, AV64 | No |
-| UAE North | AZ03 | AV36P | No |
-| UK South | AZ01 | AV36, AV36P, AV52, AV64 | Yes |
-| UK South | AZ02 | **AV36**, AV64 | Yes |
-| UK South | AZ03 | AV36P, AV64 | Yes |
-| UK West | AZ01 | AV36 | No |
-| West Europe | AZ01 | **AV36**, AV36P, AV52, AV64 | Yes |
-| West Europe | AZ02 | **AV36**, AV64 | Yes |
-| West Europe | AZ03 | AV36P, AV64 | Yes |
-| West US | AZ01 | AV36, AV36P | No |
-| West US 2 | AZ01 | AV36 | No |
-| West US 2 | AZ02 | AV36P | No |
-| West US 3 | AZ01 | **AV36P** | No |
-| US Gov Arizona | AZ02 | AV36P | No |
-| US Gov Virginia | AZ03 | AV36 | No |
+**SKUs** marked in **bold** are of limited availability due to customer consumption and quota may not be available upon request. The AV64 SKU should be used instead when AV36, AV36P, or AV52 SKUs are limited.
+
+AV64 SKUs are available per Availability Zone, the table below lists the Azure regions that support this SKU. For RAID-6 FTT2 and RAID-1 FTT3 storage policies, six and seven Fault Domains (FDs) are needed respectively, the FD count for each Azure region is listed in the "AV64 FDs Supported" column.
+
+| Azure region | Availability Zone | SKU   | Multi-AZ SDDC | AV64 FDs Supported |
+| :---         | :---:             | :---: | :---:         | :---:           |
+| Australia East | AZ01 | AV36P, AV64 | Yes | 5 (7 Planned H2 2024) |
+| Australia East | AZ02 | AV36 | No | N/A |
+| Australia East | AZ03 | AV36P, AV64 | Yes | 5 (7 Planned H2 2024) |
+| Australia South East | AZ01 | AV36 | No | N/A |
+| Brazil South | AZ02 | **AV36** | No | N/A |
+| Canada Central | AZ02 | AV36, **AV36P** | No | N/A |
+| Canada East | N/A | AV36 | No | N/A |
+| Central India | AZ03 | AV36P | No | N/A |
+| Central US | AZ01 | AV36P | No | N/A |
+| Central US | AZ02 | **AV36** | No | N/A |
+| Central US | AZ03 | AV36P | No | N/A |
+| East Asia | AZ01 | AV36 | No | N/A |
+| East US | AZ01 | **AV36P** | Yes | N/A |
+| East US | AZ02 | **AV36P**, AV64 | Yes | 7 |
+| East US | AZ03 | **AV36**, **AV36P**, AV64 | Yes | 7 |
+| East US 2 | AZ01 | **AV36**, AV64 | No | 5 (7 Planned H2 2024) |
+| East US 2 | AZ02 | AV36P, **AV52**, AV64 | No | 5 (7 Planned H2 2024) |
+| France Central | AZ01 | **AV36** | No | N/A |
+| Germany West Central | AZ01 | AV36P | Yes | N/A |
+| Germany West Central | AZ02 | **AV36** | Yes | N/A |
+| Germany West Central | AZ03 | AV36, **AV36P** | Yes | N/A |
+| Italy North | AZ03 | AV36P | No | N/A |
+| Japan East | AZ02 | **AV36** | No | N/A |
+| Japan West | AZ01 | **AV36** | No | N/A |
+| North Central US | AZ01 | **AV36**, AV64 | No | 5 (7 Planned H2 2024) |
+| North Central US | AZ02 | AV36P, AV64 | No | 5 (7 Planned H2 2024) |
+| North Europe | AZ02 | AV36, AV64 | No | 5 (7 Planned H2 2024) |
+| Qatar Central | AZ03 | AV36P | No | N/A |
+| South Africa North | AZ03 | AV36 | No | N/A |
+| South Central US | AZ01 | AV36, AV64 | No | 5 (7 Planned H2 2024) |
+| South Central US | AZ02 | **AV36P**, AV52, AV64 | No | 5 (7 Planned H2 2024) |
+| South East Asia | AZ02 | **AV36** | No | N/A |
+| Sweden Central | AZ01 | AV36 | No | N/A |
+| Switzerland North | AZ01 | **AV36**, AV64 | No | 7 |
+| Switzerland North | AZ03 | AV36P | No | N/A |
+| Switzerland West | AZ01 | **AV36**, AV64 | No | 7 |
+| UAE North | AZ03 | AV36P | No | N/A |
+| UK South | AZ01 | AV36, AV36P, AV52, AV64 | Yes | 7 |
+| UK South | AZ02 | **AV36**, AV64 | Yes | 7 |
+| UK South | AZ03 | AV36P, AV64 | Yes | 7 |
+| UK West | AZ01 | AV36 | No | N/A |
+| West Europe | AZ01 | **AV36**, AV36P, AV52, AV64 | Yes | 5 (7 Planned H2 2024) |
+| West Europe | AZ02 | **AV36**, AV64 | Yes | 7 |
+| West Europe | AZ03 | AV36P, AV64 | Yes | 5 (7 Planned H2 2024) |
+| West US | AZ01 | AV36, AV36P | No | N/A |
+| West US 2 | AZ01 | AV36 | No | N/A |
+| West US 2 | AZ02 | AV36P | No | N/A |
+| West US 3 | AZ01 | **AV36P** | No | N/A |
+| US Gov Arizona | AZ02 | AV36P | No | N/A |
+| US Gov Virginia | AZ03 | AV36 | No | N/A |
 
 ## Clusters
 
@@ -181,5 +183,3 @@ Now that you've covered Azure VMware Solution private cloud concepts, you might
 [ESXi versions]: https://kb.vmware.com/s/article/2143832
 
 [vSAN versions]: https://kb.vmware.com/s/article/2150753
-
-

articles/azure-vmware/introduction.md

@@ -3,7 +3,7 @@ title: Introduction
 description: Learn the features and benefits of Azure VMware Solution to deploy and manage VMware-based workloads in Azure.
 ms.topic: overview
 ms.service: azure-vmware
-ms.date: 3/29/2024
+ms.date: 6/3/2024
 ms.custom: engagement-fy23
 ---
 
@@ -43,21 +43,23 @@ See the following prerequisites for AV64 cluster deployment.
 When a customer has a deployed Azure VMware Solution private cloud, they can scale the private cloud by adding a separate AV64 vCenter node cluster to that private cloud. In this scenario, customers should use the following steps: 
 
 1. Get an AV64 [quota approval from Microsoft](/azure/azure-vmware/request-host-quota-azure-vmware-solution) with the minimum of three nodes. Add other details on the Azure VMware Solution private cloud that you plan to extend using AV64.
-2. Use an existing Azure VMware Solution add-cluster workflow with AV64 hosts to expand. 
+2. For RAID-6 FTT2 or RAID-1 FTT3 support, ask Microsoft support to provide you with a feature flag to consume seven Fault Domains per AV64 cluster.
+3. Use an existing Azure VMware Solution add-cluster workflow with AV64 hosts to expand. 
 
 **Customer plans to create a new Azure VMware Solution private cloud**: When a customer wants a new Azure VMware Solution private cloud that can use AV64 SKU but only for expansion. In this case, the customer meets the prerequisite of having an Azure VMware Solution private cloud built with AV36, AV36P, or AV52 SKU. The customer needs to buy a minimum of three nodes of AV36, AV36P, or AV52 SKU before expanding using AV64. For this scenario, use the following steps:
 
-1. Get AV36, AV36P, or AV52, and AV64 [quota approval from Microsoft](/azure/azure-vmware/request-host-quota-azure-vmware-solution) with a minimum of three nodes each. 
-2. Create an Azure VMware Solution private cloud using AV36, AV36P, or AV52 SKU. 
-3. Use an existing Azure VMware Solution add-cluster workflow with AV64 hosts to expand. 
+1. Get AV36, AV36P, or AV52, and AV64 [quota approval from Microsoft](/azure/azure-vmware/request-host-quota-azure-vmware-solution) with a minimum of three nodes each.
+2. Create an Azure VMware Solution private cloud using AV36, AV36P, or AV52 SKU.
+3. For RAID-6 FTT2 or RAID-1 FTT3 support, ask Microsoft support to provide you with a feature flag to consume seven Fault Domains per AV64 cluster.
+4. Use an existing Azure VMware Solution add-cluster workflow with AV64 hosts to expand.
 
-**Azure VMware Solution stretched cluster private cloud**: The AV64 SKU isn't supported with Azure VMware Solution stretched cluster private cloud. This means that an AV64-based expansion isn't possible for an Azure VMware Solution stretched cluster private cloud. 
+**Azure VMware Solution stretched clusters private cloud**: The AV64 SKU isn't supported with Azure VMware Solution stretched clusters private cloud. This means that an AV64-based expansion isn't possible for an Azure VMware Solution stretched clusters private cloud. 
 
 ### AV64 Cluster vSAN fault domain (FD) design and recommendations 
 
 The traditional Azure VMware Solution host clusters don't have explicit vSAN FD configuration. The reasoning is the host allocation logic ensures, within clusters, that no two hosts reside in the same physical fault domain within an Azure region. This feature inherently brings resilience and high availability for storage, which the vSAN FD configuration is supposed to bring. More information on vSAN FD can be found in the [VMware documentation](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vsan.doc/GUID-8491C4B0-6F94-4023-8C7A-FD7B40D0368D.html). 
 
-The Azure VMware Solution AV64 host clusters have an explicit vSAN fault domain (FD) configuration. Azure VMware Solution control plane configures five vSAN fault domains (FDs) for AV64 clusters. Hosts are balanced evenly across the five FDs as users scale up the hosts in a cluster from three nodes to 16 nodes. 
+The Azure VMware Solution AV64 host clusters have an explicit vSAN fault domain (FD) configuration. Azure VMware Solution control plane configures seven vSAN fault domains (FDs) for AV64 clusters. Hosts are balanced evenly across the seven FDs as users scale up the hosts in a cluster from three nodes to 16 nodes. Some Azure regions still support a maximum of five FDs as part of the initial release of the AV64 SKU. Refer to the [Azure Region Availability Zone (AZ) to SKU mapping table](architecture-private-clouds.md#azure-region-availability-zone-az-to-sku-mapping-table) for more information.
 
 ### Cluster size recommendation
 
@@ -81,7 +83,7 @@ The following three scenarios show examples of instances that normally error out
 
      :::image type="content" source="media/introduction/remove-host-scenario-2.png" alt-text="Diagram showing how users can't take both of the hosts from the same FDs unless they're reducing the cluster size to four or lower." border="false" lightbox="media/introduction/remove-host-scenario-2.png":::
 
-- A selected host removal causes less than three active vSAN FDs. This scenario isn't expected to occur given that all AV64 regions have five FDs. While adding hosts, the Azure VMware Solution control plane takes care of adding hosts from all five FDs evenly.
+- A selected host removal causes less than three active vSAN FDs. This scenario isn't expected to occur given that all AV64 regions have five or seven FDs. While adding hosts, the Azure VMware Solution control plane takes care of adding hosts from all seven FDs evenly.
 	In the following example, users can remove one of the hosts from FD 1, but not from FD 2 or 3.
 
 	 :::image type="content" source="media/introduction/remove-host-scenario-3.png" alt-text="Diagram showing how users can remove one of the hosts from FD 1, but not from FD 2 or 3." border="false" lightbox="media/introduction/remove-host-scenario-3.png":::
@@ -90,13 +92,15 @@ The following three scenarios show examples of instances that normally error out
 
 ### AV64 supported RAID configuration 
 
-This table provides the list of RAID configuration supported and host requirements in AV64 cluster. The RAID-6 FTT2 and RAID-1 FTT3 policies will be supported in future on AV64 SKU. Microsoft allows customers to use the RAID-5 FTT1 vSAN storage policy for AV64 clusters with six or more nodes to meet the service level agreement (SLA).  
+This table provides the list of RAID configuration supported and host requirements in AV64 clusters. The RAID-6 FTT2 and RAID-1 FTT3 policies are supported with the AV64 SKU in some regions. In Azure regions that are currently constrained to five FDs, Microsoft allows customers to use the RAID-5 FTT1 vSAN storage policy for AV64 clusters with six or more nodes to meet the service level agreement (SLA). Refer to the [Azure Region Availability Zone (AZ) to SKU mapping table](architecture-private-clouds.md#azure-region-availability-zone-az-to-sku-mapping-table) for more information. 
 
-|RAID configuration 	|Failures to tolerate (FTT) |	Minimum hosts required |
+| RAID configuration 	| Failures to tolerate (FTT) |	Minimum hosts required |
 |-------------------|--------------------------|------------------------|
-|RAID-1 (Mirroring) Default setting.| 	1 |	3 |
-|RAID-5 (Erasure Coding) |	1 |	4 |
-|RAID-1 (Mirroring) |	2 |	5 |
+| RAID-1 (Mirroring) Default setting. | 1 | 3 |
+| RAID-5 (Erasure Coding)             | 1 | 4 |
+| RAID-1 (Mirroring)                  | 2 | 5 |
+| RAID-6 (Erasure Coding)             | 2 | 6 |
+| RAID-1 (Mirroring)                  | 3 | 7 |
 
 ## Storage