Merge pull request #226337 from rvandenbedem/patch-42

Update concepts-design-public-internet-access.md

Author: prmerger-automator[bot]

articles/azure-vmware/concepts-design-public-internet-access.md

@@ -3,7 +3,7 @@ title: Concept - Internet connectivity design considerations
 description: Options for Azure VMware Solution Internet Connectivity. 
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 2/4/2023
+ms.date: 2/5/2023
 ---
 
 # Internet connectivity design considerations 
@@ -67,7 +67,7 @@ The option that you select depends on the following factors:
 - Use an Azure Public IPv4 address to the NSX-T Data Center Edge for a localized exit to the internet from each private cloud in its local region. Using multiple Azure VMware Solution private clouds in several Azure regions that need to communicate with each other and the internet, it can be challenging to match an Azure VMware Solution private cloud with a security service in Azure. The difficulty is due to the way a default route from Azure works.
 
 > [!IMPORTANT]
-> By design, Public IPv4 Address with NSX-T Data Center does not allow the exchange of Azure/Microsoft owned Public IP Addresses over ExpressRoute Private Peering connections. This means you cannot advertise the Public IPv4 addresses to your customer vNET or on-premises network via ExpressRoute.  All Public IPv4 Addresses with NSX-T Data Center traffic must take the internet path even if the Azure VMware Solution private cloud is connected via ExpressRoute. For more information, visit [ExpressRoute Circuit Peering]: ../expressroute/expressroute-circuit-peerings.
+> By design, Public IPv4 Address with NSX-T Data Center does not allow the exchange of Azure/Microsoft owned Public IP Addresses over ExpressRoute Private Peering connections. This means you cannot advertise the Public IPv4 addresses to your customer vNET or on-premises network via ExpressRoute.  All Public IPv4 Addresses with NSX-T Data Center traffic must take the internet path even if the Azure VMware Solution private cloud is connected via ExpressRoute. For more information, visit [ExpressRoute Circuit Peering](../expressroute/expressroute-circuit-peerings.md).
 
 ## Next Steps
 

articles/azure-vmware/configure-storage-policy.md

@@ -3,7 +3,7 @@ title: Configure storage policy
 description:  Learn how to configure storage policy for your Azure VMware Solution virtual machines.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 04/11/2022
+ms.date: 2/5/2023
 
 #Customer intent: As an Azure service administrator, I want set the VMware vSAN storage policies to determine how storage is allocated to the VM.
 
@@ -143,4 +143,4 @@ Now that you've learned how to configure VMware vSAN storage policies, you can l
 
 - [How to attach disk pools to Azure VMware Solution hosts (Preview)](attach-disk-pools-to-azure-vmware-solution-hosts.md) - You can use disks as the persistent storage for Azure VMware Solution for optimal cost and performance.
 
-- [How to configure external identity for vCenter](configure-identity-source-vcenter.md) - vCenter Server has a built-in local user called cloudadmin and assigned to the CloudAdmin role. The local cloudadmin user is used to set up users in Active Directory (AD). With the Run command feature, you can configure Active Directory over LDAP or LDAPS for vCenter as an external identity source.
+- [How to configure external identity for vCenter Server](configure-identity-source-vcenter.md) - vCenter Server has a built-in local user called cloudadmin and assigned to the CloudAdmin role. The local cloudadmin user is used to set up users in Active Directory (AD). With the Run command feature, you can configure Active Directory over LDAP or LDAPS for vCenter as an external identity source.

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

@@ -1,9 +1,9 @@
 ---
 title: Azure VMware Solution limits
-description: Azure VMware Solution limitations.
+description: Azure VMware Solution limits.
 ms.topic: include
 ms.service: azure-vmware
-ms.date: 11/21/2022
+ms.date: 2/5/2023
 author: suzizuber
 ms.author: v-szuber
 ---
@@ -22,7 +22,7 @@ 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 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 Azure VMware Solution ExpressRoute port speed | 10 Gbps<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 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 |
 | vSAN capacity limits | 75% of total usable (keep 25% available for SLA)  |