edit pass: architecture-private-clouds

Author: paulth1

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

@@ -1,19 +1,19 @@
 ---
-title: 'Architecture: Private Clouds and Clusters'
+title: Architecture for Private Clouds and Clusters
 description: Understand the key capabilities of Azure VMware Solution software-defined datacenters and VMware vSphere clusters. 
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 12/9/2024
+ms.date: 4/2/2025
 ms.custom: engagement-fy23, references_regions
 ---
 
 # Azure VMware Solution private cloud and cluster concepts
 
-Azure VMware Solution provides VMware-based private clouds in Azure. The private cloud hardware and software deployments are fully integrated and automated in Azure. Deploy and manage the private cloud through the Azure portal, the Azure CLI, or PowerShell.
+Azure VMware Solution provides VMware-based private clouds in Azure. The private cloud hardware and software deployments are fully integrated and automated in Azure. Deploy and manage the private cloud through the Azure portal, Azure CLI, or PowerShell.
 
 A private cloud includes clusters with:
 
-- Dedicated bare-metal server hosts provisioned with VMware ESXi Hypervisor.
+- Dedicated bare-metal server hosts provisioned with VMware vSphere Hypervisor (ESXi).
 - VMware vCenter Server for managing ESXi and vSAN.
 - VMware NSX software-defined networking for vSphere workload virtual machines (VMs).
 - VMware vSAN datastore for vSphere workload VMs.

articles/azure-vmware/includes/azure-vmware-solutions-limits.md

@@ -3,7 +3,7 @@ title: Azure VMware Solution limits
 description: Learn about Azure VMware Solution limits.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 12/24/2024
+ms.date: 4/2/2025
 author: suzizuber
 ms.author: v-szuber
 ms.custom: engagement-fy23
@@ -23,11 +23,11 @@ The following table describes the maximum limits for Azure VMware Solution.
 | Maximum number of HCX site pairings | 25 (any edition) |
 | Maximum number of HCX service meshes | 10 (any edition) |
 | Maximum number of Azure VMware Solution private clouds linked Azure ExpressRoute from a single location to a single virtual network gateway | 4<br />The virtual network gateway used determines the actual maximum number of linked private clouds. For more information, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md).<br />If you exceed this threshold, use [Azure VMware Solution Interconnect](../connect-multiple-private-clouds-same-region.md) to aggregate private cloud connectivity within the Azure region. | 
-| Maximum Azure VMware Solution ExpressRoute throughput | 10 Gbps. (Use Ultra Performance Gateway version with FastPath enabled.)**<br />The virtual network gateway that's used determines the actual bandwidth. For more information, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md).<br />Azure VMware Solution ExpressRoutes don't have any port speed limitations and perform above 10 Gbps. Rates over 10 Gbps aren't guaranteed because of quality of service.| 
+| Maximum Azure VMware Solution ExpressRoute throughput | 10 Gbps (use Ultra Performance Gateway version with FastPath enabled)**<br />The virtual network gateway that's used determines the actual bandwidth. For more information, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md).<br />Azure VMware Solution ExpressRoutes don't have any port speed limitations and perform above 10 Gbps. Rates over 10 Gbps aren't guaranteed because of quality of service.| 
 | Maximum number of Azure Public IPv4 addresses assigned to NSX | 2,000 |
 | Maximum number of Azure VMware Solution Interconnects per private cloud | 10 |
 | Maximum number of Azure ExpressRoute Global Reach connections per Azure VMware Solution private cloud | 8 |
-| vSAN capacity limits | 75% of total usable. (Keep 25% available for service-level agreement.)  |
+| vSAN capacity limits | 75% of total usable (keep 25% available for service-level agreement)  |
 | VMware Site Recovery Manager - Maximum number of protected virtual machines  | 3,000  |
 | VMware Site Recovery Manager - Maximum number of virtual machines per recovery plan  | 2,000  |
 | VMware Site Recovery Manager - Maximum number of protection groups per recovery plan  | 250  |
@@ -37,6 +37,6 @@ The following table describes the maximum limits for Azure VMware Solution.
 
 \* For information about Recovery Point Objective lower than 15 minutes, see [How the 5-Minute Recovery Point Objective Works](https://techdocs.broadcom.com/us/en/vmware-cis/live-recovery/vsphere-replication/8-8/vr-help-plug-in-8-8/replicating-virtual-machines/how-the-recovery-point-objective-affects-replication-scheduling.html#GUID-84FAF645-1C65-413D-A89B-70DBA0990631-en_TITLE_861C526B-20D8-401D-87CD-B3B454A94EC7) in the vSphere Replication Administration documentation.
 
-\** We recommend this soft limit, but it can support higher throughput based on the scenario.
+\** The soft limit is recommended, but it can support higher throughput based on the scenario.
 
 For other VMware-specific limits, use the [VMware by Broadcom configuration maximum tool](https://configmax.broadcom.com).

articles/azure-vmware/includes/disk-capabilities-of-the-host.md

@@ -3,7 +3,7 @@ title: Hardware specifications of the hosts
 description: Hosts used to build or scale clusters come from an isolated pool of hosts.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 3/6/2024
+ms.date: 4/2/2025
 author: suzizuber
 ms.author: v-szuber
 ms.custom: engagement-fy23

articles/azure-vmware/includes/hosts-minimum-initial-deployment-statement.md

@@ -3,7 +3,7 @@ title: Minimum initial host deployment
 description: The minimum initial deployment is three hosts. 
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 1/9/2025
+ms.date: 4/2/2025
 author: suzizuber
 ms.author: v-szuber
 ms.custom: engagement-fy23
@@ -15,9 +15,9 @@ For each private cloud created, there's one vSAN cluster by default. You can add
 
 You use vCenter Server and NSX Manager to manage most aspects of cluster configuration and operation. All local storage of each host in a cluster is under the control of VMware vSAN.
 
-Azure VMware Solution configures each cluster for n+1 availability through vSphere high-availability (HA) percentage-based admission control to protect workloads from the failure of a single node. `Cluster-1` of each Azure VMware Solution private cloud has a resource pool based on vSphere Distributed Resource Scheduler (`MGMT-ResourcePool`). The pool is configured for the management and control plane components (vCenter Server, NSX Manager cluster, NSX Edges, HCX Manager add-on, Site Recovery Manager add-on, and vSphere Replication add-on).
+Azure VMware Solution configures each cluster for n+1 availability through vSphere High Availability percentage-based admission control to protect workloads from the failure of a single node. `Cluster-1` of each Azure VMware Solution private cloud has a resource pool based on vSphere Distributed Resource Scheduler (`MGMT-ResourcePool`). The pool is configured for the management and control plane components (vCenter Server, NSX Manager cluster, NSX Edges, HCX Manager add-on, Site Recovery Manager add-on, and vSphere Replication add-on).
 
-`MGMT-ResourcePool` is configured to reserve 46 GHz CPU and 171.88-GB memory, which you can't change. For a three-node cluster, two nodes are dedicated to customer workloads, excluding the `MGMT-ResourcePool` CPU and memory resources reserved for management and control. One node of resources is held in reserve to protect against node failure. Azure VMware Solution stretched clusters use an admission control policy that's based on n+2 availability vSphere HA percentages.
+`MGMT-ResourcePool` is configured to reserve 46 GHz CPU and 171.88-GB memory, which you can't change. For a three-node cluster, two nodes are dedicated to customer workloads, excluding the `MGMT-ResourcePool` CPU and memory resources reserved for management and control. One node of resources is held in reserve to protect against node failure. Azure VMware Solution stretched clusters use an admission control policy that's based on n+2 availability vSphere High Availability percentages.
 
 The Azure VMware Solution management and control plane have the following resource requirements. They must be accounted for during solution sizing of a *standard private cloud*.
 
@@ -77,7 +77,7 @@ The VMware HCX and VMware Site Recovery Manager resource requirements are option
 
 The VMware Site Recovery Manager add-on has the option of configuring multiple VMware vSphere Replication Server appliances. The previous table assumes that one vSphere Replication Server appliance is used.
 
-Sizing an Azure VMware Solution is an estimate. Validate the sizing calculations from the design phase during the testing phase of a project. You need to ensure that the Azure VMware solution is sized correctly for the application workload.
+Sizing a solution is an estimate. Validate the sizing calculations from the design phase during the testing phase of a project. You need to ensure that the solution is sized correctly for the application workload.
 
 >[!TIP]
 >You can always extend the cluster and add more clusters later if you need to go beyond the initial deployment number.

articles/azure-vmware/includes/vmware-software-versions.md

@@ -3,7 +3,7 @@ title: VMware Solution software versions
 description: Supported software versions that are used for Azure VMware Solution.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 3/20/2025
+ms.date: 4/2/2025
 author: suzizuber
 ms.author: v-suzuber
 ms.custom: engagement-fy23