pub team feedback 1

jjaygbay1 · jjaygbay1 · commit fee31ea903e0 · 2025-04-07T20:50:11.000-04:00
diff --git a/articles/azure-vmware/media/native-connectivity/native-connect-multiple-solutions-on-premise.png b/articles/azure-vmware/media/native-connectivity/native-connect-multiple-solutions-on-premise.png
diff --git a/articles/azure-vmware/media/native-connectivity/native-connect-on-premise.png b/articles/azure-vmware/media/native-connectivity/native-connect-on-premise.png
diff --git a/articles/azure-vmware/native-connect-multiple-private-clouds.md b/articles/azure-vmware/native-connect-multiple-private-clouds.md
@@ -24,11 +24,11 @@ Private clouds deployed in different Azure Virtual Networks can be connected usi
 
 Depending on the location of the private cloud, you may require local Virtual Network peering or a global Virtual Network peering.
 
-:::image type="content" source="./media/native-connectivity/native-connect-multiple-solutions-onpremise.png" alt-text="Diagram of an Azure VMware Solution connection to on-premise environment":::
+:::image type="content" source="./media/native-connectivity/native-connect-multiple-solutions-on-premise.png" alt-text="Diagram of an Azure VMware Solution connection to on-premise environment." lightbox="media/native-connectivity/native-connect-multiple-solutions-on-premise.png":::
 
 ## Related topics 
 - [Connectivity to an Azure Virtual Network](native-network-connectivity.md)
-- [Connect to on-premises environment](native-connect-onpremises.md)
+- [Connect to on-premises environment](native-connect-on-premises.md)
 - [Internet connectivity options](native-internet-connectivity-design-considerations.md)
 - [Connect Azure VMware Solution private cloud in a Virtual Network to the previous edition of Azure VMware Solution private cloud](native-connect-private-cloud-previous-edition.md)
 - [Public and Private DNS forward lookup zone configuration](native-dns-forward-lookup-zone.md)
diff --git a/articles/azure-vmware/native-connect-on-premises.md b/articles/azure-vmware/native-connect-on-premises.md
@@ -1,5 +1,5 @@
 ---
-title: Connect to On-Premises environment
+title: Connect to on-premises environment
 description: Learn how to connect your on-premises environment to Azure VMware Solution using ExpressRoute or Site-to-Site VPN for seamless integration.
 ms.topic: how-to
 ms.service: azure-vmware
@@ -25,7 +25,7 @@ Connectivity to on-premises is performed using a standard ExpressRoute connectio
 > [!NOTE]
 > You can connect through VPN, but that information is out of scope for this article.
 
-:::image type="content" source="./media/native-connectivity/native-connect-onpremise.png" alt-text="Diagram of an Azure VMware Solution connection to on-premise environment":::
+:::image type="content" source="./media/native-connectivity/native-connect-on-premise.png" alt-text="Diagram of an Azure VMware Solution connection to on-premise environment." lightbox="media/native-connectivity/native-connect-on-premise.png":::
 
 ## Related topics
 
diff --git a/articles/azure-vmware/native-connect-private-cloud-previous-edition.md b/articles/azure-vmware/native-connect-private-cloud-previous-edition.md
@@ -8,7 +8,7 @@ ms.author: jacobjaygbay
 #customer intent: As a cloud administrator, I want to connect Azure VMware Solution on Native private cloud to previous edition of Azure VMware Solution private cloud so that I can enable seamless communication between private clouds.
 ---
 
-# Connect Azure VMware Solution in an Azure Network Network private cloud to previous edition of Azure VMware Solution private cloud
+# Connect Azure VMware Solution in an Azure Virtual Network private cloud to previous edition of Azure VMware Solution private cloud
 
 In this article, you learn how to connect Azure VMware Solution private cloud in an Azure Virtual Network to the previous edition of Azure VMware Solution private cloud. After you deploy Azure VMware Solution in an Azure Virtual Network private clouds, you may need to have network connectivity between the private cloud and other networks you have on Azure Virtual Network, on-premises, other Azure VMware Solution private clouds, or the internet.  
 
@@ -18,7 +18,7 @@ This article discusses how the Azure VMware Solution in an Azure Virtual Network
 
 Have Azure VMware Solution in an Azure Virtual Network and previous edition of the private cloud deployed successfully.
 
-## Connect Azure VMware Solution in an Azure Network Network private cloud to previous edition of Azure VMware Solution private cloud
+## Connect Azure VMware Solution in an Azure Network private cloud to previous edition of Azure VMware Solution private cloud
 
 Azure VMware Solution in an Azure Virtual Network can be connected to the previous edition of Azure VMware Solution using a standard ExpressRoute connection, similar to how earlier Azure VMware Solution editions connect to the Virtual Network.
 
@@ -30,11 +30,11 @@ For more information about how to connect Virtual Networks using ExtressRoute, s
 3. Ensure an ExpressRoute gateway is present or create one on the Azure VNET/peered Virtual Network where Azure VMware Solution in an Azure Virtual Network is deployed.
 4. Add a connection to the ExpressRoute gateway using the ER authorization key and ExpressRoute ID from the previous step.
 
-:::image type="content" source="./media/native-connectivity/native-connect-express-route-previous-edition.png" alt-text="Diagram showing an Azure VMware Solution connection to previous edition of private cloud."::: 
+:::image type="content" source="./media/native-connectivity/native-connect-express-route-previous-edition.png" alt-text="Diagram showing an Azure VMware Solution connection to previous edition of private cloud." lightbox="media/native-connectivity/native-connect-express-route-previous-edition.png":::
 
 ## Related topics
 - [Connectivity to an Azure Virtual Network](native-network-connectivity.md)
-- [Connect to on-premises environment](native-connect-onpremises.md)
+- [Connect to on-premises environment](native-connect-on-premises.md)
 - [Internet connectivity options](native-internet-connectivity-design-considerations.md)
 - [Connect multiple Azure VMware Solution in an Azure Virtual Network private clouds](native-connect-multiple-private-clouds.md)
 - [Public and Private DNS forward lookup zone configuration](native-dns-forward-lookup-zone.md)
diff --git a/articles/azure-vmware/native-dns-forward-lookup-zone.md b/articles/azure-vmware/native-dns-forward-lookup-zone.md
@@ -26,15 +26,15 @@ Azure VMware Solution allows you to configure DNS forward lookup zones in two wa
 
 DNS forward lookup zone can be configured at the time of creation or changed after the private cloud is created. The following diagram shows the configuration page for the DNS forward lookup zone. 
 
-:::image type="content" source="./media/native-connectivity/native-connect-dns-lookup.png" alt-text="Diagram showing an Azure VMware Solution DNS forward lookup."::: 
+:::image type="content" source="./media/native-connectivity/native-connect-dns-lookup.png" alt-text="Diagram showing an Azure VMware Solution DNS forward lookup." lightbox="media/native-connectivity/native-connect-dns-lookup.png":::
 
 ## Configuring Private DNS for your Azure VMware Solution Private Cloud in an Azure Virtual Network  
  
 If you select the Private DNS option, the private cloud will be resolvable from the Virtual Network where the private cloud is provisioned. This is done by linking the private DNS zone to your Virtual Network. If you need to enable this zone to be resolvable outside of this Virtual Network, such as in your on-premises environment, you need to configure an Azure DNS Private Resolver, or deploy your own DNS server in your Virtual Network. Private DNS will use the Azure DNS Service (168.63.129.16) to resolve your private cloud FQDNs. This section explains configuring an Azure DNS Private Resolver. 
  
  ### Prerequisite
  
- First, create two /28 subnets to delegate to the Azure DNS Private Resolver service. As an example. they can be named dns-in and dns-out. 
+ First, create two /28 subnets to delegate to the Azure DNS Private Resolver service. As an example. They can be named dns-in and dns-out. 
  
  ### Deploy Azure DNS Private Resolver
  
@@ -69,7 +69,7 @@ You can now resolve your private cloud DNS records from any workload using the I
 
 ## Related topics
 - [Connectivity to an Azure Virtual Network](native-network-connectivity.md)
-- [Connect to on-premises environment](native-connect-onpremises.md)
+- [Connect to on-premises environment](native-connect-on-premises.md)
 - [Internet connectivity options](native-internet-connectivity-design-considerations.md)
 - [Connect multiple Azure VMware Solution in an Azure Virtual Network private clouds](native-connect-multiple-private-clouds.md)
 - [Connect Azure VMware Solution private cloud in a Virtual Network to the previous edition of Azure VMware Solution private cloud](native-connect-private-cloud-previous-edition.md)
diff --git a/articles/azure-vmware/native-first-party-principle-security.md b/articles/azure-vmware/native-first-party-principle-security.md
@@ -26,7 +26,7 @@ There are two options to enable the service principal for Azure VMware Solution.
 
 1. Select **Microsoft Entra ID**.  
 
-2. Search **Microsoft Entra ID** for the application ID '1a5e141d-70dd-4594-8442-9fc46fa48686'. Select **'Avs Fleet Rp'**.  
+2. Search **Microsoft Entra ID** for the application ID ``1a5e141d-70dd-4594-8442-9fc46fa48686``. Select **'Avs Fleet Rp'**.  
 
 3. Enable the **'Avs Fleet Rp'** Enterprise application for user sign-in by toggling the **Enabled for users to sign-in** toggle to **Yes**.   
 
diff --git a/articles/azure-vmware/native-internet-connectivity-design-considerations.md b/articles/azure-vmware/native-internet-connectivity-design-considerations.md
@@ -20,7 +20,7 @@ After you deploy Azure VMware Solution in an Azure Virtual Network, you may requ
 
 Azure VMware Solution provides necessary internet connectivity to SDDC appliances like vCenter, NSX Manager, and HCX Manager for management functions. This private cloud relies on the internet connectivity configured on the Virtual Network it's deployed in. The customer workload can connect to the internet through either virtual WAN, Azure Firewall, or third-party Network Virtual Appliances. The standard Azure Supported topology for virtual WAN, Azure Firewall, and third-party Network Virtual Appliances are supported.
 
-:::image type="content" source="./media/native-connectivity/native-connect-private-cloud-internet.png" alt-text="Diagram showing an Azure VMware Solution connection to other virtual networks."::: 
+:::image type="content" source="./media/native-connectivity/native-connect-private-cloud-internet.png" alt-text="Diagram showing an Azure VMware Solution connection to other virtual networks." lightbox="media/native-connectivity/native-connect-private-cloud-internet.png":::
 
 Azure VMware Solution internet connectivity using Azure Firewall is similar to the way Azure virtual network internet connectivity is achieved, which is described in more detail in the Azure Firewall documentation. The only thing specific to the Azure VMware solution is the subnets which need to be associated with a user-defined route table (UDR) to point to Azure Firewall or third-party Network Virtual Appliance for internet connectivity.
 
@@ -35,7 +35,7 @@ Azure VMware Solution internet connectivity using Azure Firewall is similar to t
 
 Related topics
 - [Connectivity to an Azure Virtual Network](native-network-connectivity.md)
-- [Connect to on-premises environment](native-connect-onpremises.md)
+- [Connect to on-premises environment](native-connect-on-premises.md)
 - [Connect multiple Azure VMware Solution in an Azure Virtual Network private clouds](native-connect-multiple-private-clouds.md)
 - [Connect Azure VMware Solution private cloud in a Virtual Network to the previous edition of Azure VMware Solution private cloud](native-connect-private-cloud-previous-edition.md)
 - [Public and Private DNS forward lookup zone configuration](native-dns-forward-lookup-zone.md)
diff --git a/articles/azure-vmware/native-introduction.md b/articles/azure-vmware/native-introduction.md
@@ -9,11 +9,11 @@ ms.author: jacobjaygbay
 # customer intent: As a cloud administrator, I want to learn about Azure VMware Solution in a Virtual Network so that I can understand the features and benefits of this offering.
 ---
 
-# What's Azure VMware Solution in an Azure Virtual Network (Public Preview) 
+# What's Azure VMware Solution in an Azure Virtual Network (Public preview) 
 
-Azure VMware Solution private clouds can now be deployed inside an Azure Virtual Network, conforming Azure VMware Solution to Azure networking standards. This architecture simplifies networking architecture, enhances data transfer speeds, reduces latency for workloads, and improves performance when accessing other Azure services. Users can now deploy Azure VMware Solution private clouds with the AV64 SKU directly, eliminating the need for a minimum of 3-host AV36, AV36P, or AV52 cluster. The same Azure VMware Solution limits apply as decribed in [Scale clusters in a Private Cloud](tutorial-scale-private-cloud.md).
+Azure VMware Solution private clouds can now be deployed inside an Azure Virtual Network, conforming Azure VMware Solution to Azure networking standards. This architecture simplifies networking architecture, enhances data transfer speeds, reduces latency for workloads, and improves performance when accessing other Azure services. Users can now deploy Azure VMware Solution private clouds with the AV64 SKU directly, eliminating the need for a minimum of 3-host AV36, AV36P, or AV52 cluster. The same Azure VMware Solution limits apply as described in [Scale clusters in a Private Cloud](tutorial-scale-private-cloud.md).
 
-:::image type="content" source="./media/native-connectivity/azure-virtual-network-connectivity.png" alt-text="Diagram showing an Azure VMware Solution Virtual Network connectivity."::: 
+:::image type="content" source="./media/native-connectivity/azure-virtual-network-connectivity.png" alt-text="Diagram showing an Azure VMware Solution Virtual Network connectivity." lightbox="media/native-connectivity/azure-virtual-network-connectivity.png"::: 
 
 > [!NOTE]
 > The product name may change when General Availability is announced.
diff --git a/articles/azure-vmware/native-network-connectivity.md b/articles/azure-vmware/native-network-connectivity.md
@@ -21,7 +21,7 @@ After you deploy Azure VMware Solution private cloud in an Azure Virtual Network
 
 This Azure VMware Solution private cloud deployment is hosted in an Azure Virtual Network. This means the connectivity to the local Virtual Network from an Azure VMware Solution private cloud is established during deployment, with no other configuration required. This private cloud follows the same network connectivity constructs as other Azure services. This means NSX workload segments created in this private cloud will be systematically programmed as Virtual Network address spaces in the Virtual Network domain for routing purposes.
 
-:::image type="content" source="./media/native-connectivity/native-connectivity-private-cloud.png" alt-text="Diagram of an Azure VMware Solution connection to a private cloud":::
+:::image type="content" source="./media/native-connectivity/native-connectivity-private-cloud.png" alt-text="Diagram of an Azure VMware Solution connection to a private cloud" lightbox="media/native-connectivity/native-connectivity-private-cloud.png":::
 
 Azure VMware Solution creates the following read-only management subnets within the hosted Virtual Network to host required private cloud components. These Management Subnets are allocated from the management address block specified for private cloud creation. The following  are sample subnets derived from an SDDC with a 10.74.64.0/22 address block.
 
@@ -34,10 +34,10 @@ Both regional Virtual Network peering and global Virtual Network peering is supp
  >[!Note]
  > The standard Azure peer Virtual Network peering resync needs to be done to propagate any NSX segment, subnet and route changes on Azure VMware Solution private cloud.
 
-:::image type="content" source="./media/native-connectivity/native-connectivity-private-vnet-peering.png" alt-text="Diagram showing an Azure VMware Solution connection to other Virtual Networks":::
+:::image type="content" source="./media/native-connectivity/native-connectivity-private-vnet-peering.png" alt-text="Diagram showing an Azure VMware Solution connection to other Virtual Networks" lightbox="media/native-connectivity/native-connectivity-private-vnet-peering.png":::
 
 ## Related topics
-- [Connect to on-premises environment](native-connect-onpremises.md)
+- [Connect to on-premises environment](native-connect-on-premises.md)
 - [Internet connectivity options](native-internet-connectivity-design-considerations.md)
 - [Connect multiple Azure VMware Solution in an Azure Virtual Network private clouds](native-connect-multiple-private-clouds.md)
 - [Connect Azure VMware Solution private cloud in a Virtual Network to the previous edition of Azure VMware Solution private cloud](native-connect-private-cloud-previous-edition.md)
diff --git a/articles/azure-vmware/native-network-design-consideration.md b/articles/azure-vmware/native-network-design-consideration.md
@@ -7,7 +7,7 @@ ms.date: 4/3/2025
 # customer intent: As a cloud administrator, I want to learn about Azure VMware Solution in an Azure Virtual Network design consideration so that I can make informed decisions about my Azure VMware Solution deployment.
 ---
 
-# Azure VMware Solution in an Azure Virtual Network design considerations (Public Preview)
+# Azure VMware Solution in an Azure Virtual Network design considerations (Public preview)
 
 In this article, you learn about design considerations for Azure VMware Solution in an Azure Virtual Network. It discusses what this solution offers in a VMware private cloud environment that your applications can access from on-premises and Azure-based environments or resources. There are several considerations to review before you set up your Azure VMware Solution private cloud in an Azure Virtual Network. This article provides solutions for use cases that you might encounter when you're using the private cloud type.
 
@@ -22,7 +22,7 @@ The following functionality is limited during this time. These limitations will
 - You can only deploy **1 Private Cloud per Azure Virtual Network**.
 - You can only create **1 SDDC per Resource Group**. Multiple Private Clouds in a single Resource Group are not supported. 
 - Your Private Cloud and Virtual Network for your Private Cloud must be in the *same* Resource Group.
-- You can not move your Private Cloud from one Resource Group to another after the Private Cloud is created.
+- You cannot move your Private Cloud from one Resource Group to another after the Private Cloud is created.
 - Virtual Network Service Endpoints direct connectivity from Azure VMware Solution workloads is not supported.
 - **vCloud Director** using Private Endpoints is supported. However, vCloud Director using Public Endpoints is not supported.
 - **vSAN Stretched Clusters** is not supported.
@@ -43,7 +43,6 @@ Azure VMware Solution in an Azure Virtual Network provides a VMware private clou
 
 The private cloud connects to your Azure virtual network using standard Azure networking. Azure VMware Solution private clouds require a minimum /22 CIDR network address block for subnets. This network complements your on-premises networks, so the address block shouldn't overlap with address blocks used in other virtual networks in your subscription and on-premises networks. Management, vMotion, and Replication networks are provisioned automatically within this address block as subnets inside your Virtual Network.
 
-
 > [!Note]
 > Permitted ranges for your address block are the RFC 1918 private address spaces (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), except for 172.17.0.0/16. Replication network is not applicable to AV64 nodes and is planned for general deprecation at a future date.
 
diff --git a/articles/azure-vmware/toc.yml b/articles/azure-vmware/toc.yml
@@ -112,7 +112,7 @@ items:
     - name: Connectivity to an Azure Virtual Network
       href: native-network-connectivity.md
     - name: Connect to on-premises environment
-      href: native-connect-onpremises.md
+      href: native-connect-on-premises.md
     - name: Internet connectivity options
       href: native-internet-connectivity-design-considerations.md
     - name: Connect multiple Azure VMware Solution in an Azure Virtual Network private clouds
