Merge pull request #226518 from rvandenbedem/patch-42

Update azure-vmware-solutions-limits.md

Author: prmerger-automator[bot]

articles/azure-vmware/concepts-networking.md

@@ -3,7 +3,7 @@ title: Concepts - Network interconnectivity
 description: Learn about key aspects and use cases of networking and interconnectivity in Azure VMware Solution.
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 2/4/2023
+ms.date: 2/7/2023
 ms.custom: engagement-fy23
 ---
 
@@ -41,7 +41,8 @@ The diagram below shows the basic network interconnectivity established at the t
 - Outbound access from VMs on the private cloud to Azure services.
 - Inbound access of workloads running in the private cloud.
 
-When connecting **production** Azure VMware Solution private clouds to an Azure virtual network, an ExpressRoute virtual network gateway with the Ultra Performance Gateway SKU should be used with FastPath enabled to achieve 10Gbps connectivity. Less critical environments can use the Standard or High Performance Gateway SKUs for slower network performance.
+> [!IMPORTANT]
+> When connecting **production** Azure VMware Solution private clouds to an Azure virtual network, an ExpressRoute virtual network gateway with the Ultra Performance Gateway SKU should be used with FastPath enabled to achieve 10Gbps connectivity. Less critical environments can use the Standard or High Performance Gateway SKUs for slower network performance.
 
 :::image type="content" source="media/concepts/adjacency-overview-drawing-single.png" alt-text="Diagram showing the basic network interconnectivity established at the time of an Azure VMware Solution private cloud deployment." border="false":::
 

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

@@ -3,7 +3,7 @@ title: Azure VMware Solution limits
 description: Azure VMware Solution limits.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 2/5/2023
+ms.date: 2/7/2023
 author: suzizuber
 ms.author: v-szuber
 ---
@@ -21,7 +21,7 @@ The following table describes the maximum limits for Azure VMware Solution.
 | Maximum number of vCenter Servers per private cloud | 1 (hard-limit)  |
 | Maximum number of HCX site pairings | 25 (any edition) |
 | Maximum number of HCX service meshes | 10 (any edition) |
-| Maximum number of Azure VMware Solution ExpressRoute max linked private clouds | 4<br />The virtual network gateway used determines the actual max linked private clouds.  For more details, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md) | 
+| Maximum number of Azure VMware Solution ExpressRoute linked private clouds | 4<br />The virtual network gateway used determines the actual max linked private clouds.  For more details, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md) | 
 | Maximum Azure VMware Solution ExpressRoute port speed | 10 Gbps (use Ultra Performance Gateway SKU with FastPath enabled)<br />The virtual network gateway used determines the actual bandwidth. For more details, see [About ExpressRoute virtual network gateways](../../expressroute/expressroute-about-virtual-network-gateways.md) | 
 | Maximum number of Azure Public IPv4 addresses assigned to NSX-T Data Center | 2,000 |
 | Maximum number of Azure VMware Solution Interconnects per private cloud | 10 |

articles/azure-vmware/includes/vmware-software-update-frequency.md

@@ -3,7 +3,7 @@ title: VMware software update frequency
 description: Supported VMware software update frequency for Azure VMware Solution.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 12/12/2022
+ms.date: 2/7/2023
 author: suzizuber
 ms.author: v-szuber
 ---
@@ -15,13 +15,13 @@ One benefit of Azure VMware Solution private clouds is that the platform is main
 > [!NOTE]
 > A T0 gateway is created and configured as part of a private cloud deployment. Any modification to that logical router or the NSX-T Data Center edge node VMs could affect connectivity to your private cloud and should be avoided.
 
-Microsoft is responsible for applying any patches, updates, or upgrades to ESXi, vCenter Server, vSAN, and NSX-T Data Center in your private cloud. The impact of patches, updates, and upgrades on ESXi, vCenter Server, and NSX-T Data Center is different.
+Microsoft is responsible for applying any patches, updates, or upgrades to ESXi, vCenter Server, vSAN, and NSX-T Data Center in your private cloud. The impact of patches, updates, and upgrades on ESXi, vCenter Server, and NSX-T Data Center has the following considerations:
 
 - **ESXi** - There's no impact to workloads running in your private cloud. Access to vCenter Server and NSX-T Data Center isn't blocked during this time.  It's recommended that, during this time, you don't plan any other activities like: scaling up private cloud, scheduling or initiating active HCX migrations, making HCX configuration changes, and so on, in your private cloud.
 
 - **vCenter Server** - There's no impact to workloads running in your private cloud. During this time, vCenter Server will be unavailable and you won't be able to manage VMs (stop, start, create, or delete). It's recommended that, during this time, you don't plan any other activities like scaling up private cloud, creating new networks, and so on, in your private cloud. If you're using VMware Site Recovery Manager or vSphere Replication user interfaces, it's recommended to not configure vSphere Replication, and configure or execute site recovery plans during the vCenter Server upgrade.
 
-- **NSX-T Data Center** - There's workload impact and when a particular host is being upgraded, the VMs on that host might lose connectivity from 2 seconds to maximum 1 minute with any of the following symptoms:
+- **NSX-T Data Center** - There's workload impact and when a particular host is being upgraded, the VMs on that host might lose connectivity from 2 seconds to 1 minute with any of the following symptoms:
 
    - Ping errors
 
@@ -35,7 +35,6 @@ Microsoft is responsible for applying any patches, updates, or upgrades to ESXi,
 
 You'll be notified through Azure Service Health that includes the timeline of the upgrade. This notification also provides details on the upgraded component, its effect on workloads, private cloud access, and other Azure services. You can reschedule an upgrade as needed.
 
-
 Software updates include:
 
 - **Patches** - Security patches or bug fixes released by VMware
@@ -45,6 +44,6 @@ Software updates include:
 - **Upgrades** - Major version change of a VMware stack component
 
 >[!NOTE]
->Microsoft tests a critical security patch as soon as it becomes available from VMware.
+> Microsoft tests a critical security patch as soon as it becomes available from VMware.
 
 Documented VMware workarounds are implemented in lieu of installing a corresponding patch until the next scheduled updates are deployed.