Merge pull request #298256 from rvandenbedem/patch-5

JillGrant615 · web-flow · commit ae85c7244e84 · 2025-04-15T09:45:38.000-06:00
Update native-introduction.md
diff --git a/articles/azure-vmware/native-connect-multiple-private-clouds.md b/articles/azure-vmware/native-connect-multiple-private-clouds.md
@@ -5,7 +5,7 @@ ms.topic: how-to
 ms.service: azure-vmware
 author: jjaygbay1
 ms.author: jacobjaygbay
-ms.date: 3/14/2025
+ms.date: 4/15/2025
 ms.custom: engagement-fy25
 #customer intent: As a cloud administrator, I want to connect multiple Azure VMware Solution Generation 2 Private Clouds so that I can enable seamless communication between private clouds.
 ---
@@ -24,7 +24,7 @@ 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-on-premises.png" alt-text="Diagram of an Azure VMware Solution connection to on-premise environment." lightbox="media/native-connectivity/native-connect-multiple-solutions-on-premises.png":::
+:::image type="content" source="./media/native-connectivity/native-connect-multiple-solutions-on-premises.png" alt-text="Diagram of an multiple Azure VMware Solution Gen 2 private clouds connected together." lightbox="media/native-connectivity/native-connect-multiple-solutions-on-premises.png":::
 
 ## Related topics 
 - [Connectivity to an Azure Virtual Network](native-network-connectivity.md)
diff --git a/articles/azure-vmware/native-connect-on-premises.md b/articles/azure-vmware/native-connect-on-premises.md
@@ -1,9 +1,9 @@
 ---
 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.
+description: Learn how to connect your on-premises environment to Azure VMware Solution Gen 2 using ExpressRoute or Site-to-Site VPN for seamless integration.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 3/14/2025
+ms.date: 4/15/2025
 ms.custom: engagement-fy25
 #customer intent: As an IT administrator, I want to connect my on-premises environment to my Azure VMware Solution Generation 2 private cloud so that I can extend my infrastructure seamlessly.
 ---
@@ -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-on-premises.png" alt-text="Diagram of an Azure VMware Solution connection to on-premise environment." lightbox="media/native-connectivity/native-connect-on-premises.png":::
+:::image type="content" source="./media/native-connectivity/native-connect-on-premises.png" alt-text="Diagram of an Azure VMware Solution connection to on-premises environment." lightbox="media/native-connectivity/native-connect-on-premises.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
@@ -3,7 +3,7 @@ title: Connect Azure VMware Solution Generation 2 private clouds to Azure VMware
 description: Learn about connecting Azure VMware Solution Generation 2 private clouds to Azure VMware Solution Generation 1 private clouds.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 3/14/2025
+ms.date: 4/15/2025
 ms.author: jacobjaygbay
 #customer intent: As a cloud administrator, I want to connect Azure VMware Solution Generation 2 private clouds to Azure VMware Solution Generation 1 private clouds so that I can enable seamless communication between private clouds.
 ---
@@ -30,7 +30,7 @@ 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 Virtual Network or peered Virtual Network where Azure VMware Solution Gen 2 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." lightbox="media/native-connectivity/native-connect-express-route-previous-edition.png":::
+:::image type="content" source="./media/native-connectivity/native-connect-express-route-previous-edition.png" alt-text="Diagram showing an Azure VMware Solution Gen 2 connection to Gen 1 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)
diff --git a/articles/azure-vmware/native-create-azure-vmware-virtual-network-private-cloud.md b/articles/azure-vmware/native-create-azure-vmware-virtual-network-private-cloud.md
@@ -1,16 +1,16 @@
 ---
-title: Create an Azure VMware Solution Generation 2 private cloud (Public Preview)
+title: Create an Azure VMware Solution Generation 2 private cloud (preview)
 author: jjaygbay1
 ms.author: jacobjaygbay
 description: Learn how to create an Azure VMware Solution Generation 2 Private Cloud to apply Azure's infrastructure and VMware expertise effectively.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 03/11/2025
+ms.date: 4/15/2025
 ms.custom: engagement-fy25
 #customer intent: As a cloud administrator, I want to create an Azure VMware Solution Generation 2 Private Cloud so that I can leverage Azure's infrastructure and VMware expertise.
 ---
 
-# Create an Azure VMware Solution Generation 2 Private Cloud (Public Preview)
+# Create an Azure VMware Solution Generation 2 Private Cloud (preview)
 
 In this tutorial, you learn how to create an Azure VMware Solution Generation (Gen) 2 Private Cloud. This solution combines the first-party Azure VMware Solution with Azure hardware and network to simplify your networking architecture, and enhance performance and security. This initial launch of this generation utilizes the AV64 SKU.
 
@@ -76,7 +76,7 @@ az feature registration create --namespace "Microsoft.AVS" --name "FleetGreenfie
 1. Verify that the deployment was successful. Navigate to the resource group you created and select your private cloud. You see the status of **Succeeded** when the deployment is finished.
 
 1. Verify that the deployment was successful. Navigate to the resource group you created and select your private cloud. You see the status of Succeeded when the deployment is finished. 
-1. Connect to vCenter and NSX Manager using the VMware credentials shown in your Private Cloud. For more information, see [Access an Azure VMware Solution private cloud](tutorial-access-private-cloud.md). 
+1. Connect to vCenter Server and NSX Manager using the VMware credentials shown in your Private Cloud. For more information, see [Access an Azure VMware Solution private cloud](tutorial-access-private-cloud.md). 
 
 ## Next steps
   
diff --git a/articles/azure-vmware/native-dns-forward-lookup-zone.md b/articles/azure-vmware/native-dns-forward-lookup-zone.md
@@ -3,7 +3,7 @@ title: Private and Public DNS forward lookup zone configuration
 description: Learn about DNS forward lookup zone for Azure VMware Solution Generation 2 private clouds.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 3/14/2025
+ms.date: 4/15/2025
 ms.custom: engagement-fy25
 # customer intent: As a cloud administrator, I want to configure DNS forward lookup zone for Azure VMware Solution Generation 2 private clouds so that I can manage domain name resolution for private cloud appliances.
 ---
@@ -18,15 +18,15 @@ Gen 2 private cloud successfully deployed.
 
 ## DNS forward lookup zone configuration options 
 
-Azure VMware Solution allows you to configure DNS forward lookup zones in two ways: public or private. This configuration defines how DNS name resolution for Azure VMware Solution components, such as vCenter, ESX hosts, and NSX Managers, is performed. 
+Azure VMware Solution allows you to configure DNS forward lookup zones in two ways: public or private. This configuration defines how DNS name resolution for Azure VMware Solution components, such as vCenter Server, ESX hosts, and NSX Manager, is performed. 
 
 **Public**: The public DNS forward lookup zone allows domain names to be resolved using any public DNS servers. 
 
 **Private**: The private DNS forward lookup zone makes it resolvable only within a private customer environment and provides other security compliance. If a customer chooses Private Forward Lookup Zone, the Software-Defined Data Center (private cloud) Fully Qualified Domain Names (FQDNs) are resolvable from the Virtual Network where the private cloud is provisioned. If need to enable this zone to be resolvable outside of this Virtual Network, such as in a customer on-premises environment, you need to configure an Azure DNS Private Resolver or deploy your own DNS server in your Virtual Network that uses the Azure DNS Service (168.63.129.16) to resolve your private cloud FQDNs. 
 
 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." lightbox="media/native-connectivity/native-connect-dns-lookup.png":::
+:::image type="content" source="./media/native-connectivity/native-connect-dns-lookup.png" alt-text="Diagram showing an Azure VMware Solution Gen 2 DNS forward lookup." lightbox="media/native-connectivity/native-connect-dns-lookup.png":::
 
 ## Configuring Private DNS for your Azure VMware Solution Generation 2 Private Cloud  
  
@@ -56,7 +56,7 @@ You can now resolve your private cloud DNS records from any workload using the I
  
  ### Enable Resolution for private cloud Workload Virtual Machines
  
- If you need workload Virtual Machines deployed in your private cloud to resolve the private cloud management components you must add a forwarder to NSX. 
+ If you need workload Virtual Machines deployed in your private cloud to resolve the private cloud management components you must add a forwarder to VMware NSX. 
  
  1. In your Resource group, open your private cloud. 
  2. Expand Workload Networking and click on DNS. 
diff --git a/articles/azure-vmware/native-internet-connectivity-design-considerations.md b/articles/azure-vmware/native-internet-connectivity-design-considerations.md
@@ -3,7 +3,7 @@ title: Internet Configuration for Azure VMware Solution Generation 2 Private Clo
 description: Learn about Azure VMware Solution in an Azure Virtual Network Internet connectivity configuration.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 3/28/2025
+ms.date: 4/15/2025
 ms.custom: engagement-fy25
 ---
 
@@ -20,9 +20,9 @@ After you deploy an Azure VMware Solution Generation (Gen) 2 private cloud, you
 
 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." lightbox="media/native-connectivity/native-connect-private-cloud-internet.png":::
+:::image type="content" source="./media/native-connectivity/native-connect-private-cloud-internet.png" alt-text="Diagram showing an Azure VMware Solution Gen 2 connection to internet via Azure Firewall." lightbox="media/native-connectivity/native-connect-private-cloud-internet.png":::
 
-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.
+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 Gen 2 private cloud 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.
 
 ## Steps:
 
diff --git a/articles/azure-vmware/native-introduction.md b/articles/azure-vmware/native-introduction.md
@@ -1,29 +1,28 @@
 ---
-title: Introduction to Azure VMware Solution Generation 2 Private Clouds (Public preview) 
+title: Introduction to Azure VMware Solution Generation 2 Private Clouds (preview) 
 description: Learn about Azure VMware Solution Gen 2 private clouds.
 ms.topic: overview
 ms.service: azure-vmware
-ms.date: 3/28/2025
+ms.date: 4/15/2025
 ms.custom: engagement-fy25
 ms.author: jacobjaygbay
 # customer intent: As a cloud administrator, I want to learn about Azure VMware Solution Gen 2 private clouds so that I can understand the features and benefits of this offering.
 ---
 
-# Introduction to Azure VMware Solution Generation 2 Private Clouds (Public preview) 
+# Introduction to Azure VMware Solution Generation 2 Private Clouds (preview) 
 
 Azure VMware Solution Generation (Gen) 2 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." lightbox="media/native-connectivity/azure-virtual-network-connectivity.png"::: 
+:::image type="content" source="./media/native-connectivity/azure-virtual-network-connectivity.png" alt-text="Diagram showing an Azure VMware Solution Gen 2 Virtual Network connectivity." lightbox="media/native-connectivity/azure-virtual-network-connectivity.png"::: 
 
 ## Differences
 
 The following table summarizes the differences between Gen 1 and Gen 2 private clouds:
 
-| Feature               | Azure VMware Solution Gen 1 private clouds    | Azure VMware Solution Gen 2 private clouds |
+| Feature               | Azure VMware Solution Gen 1 private clouds    | Azure VMware Solution Gen 2 private clouds       |
 |-----------------------|-----------------------------------------------|--------------------------------------------------|
-| Supported SKU type    | - AV36, AV36P, AV52, AV48                     | - AV64                                           |
-|                       | - AV64 (with minimum of 3 AV36, AV36P, AV52, or AV48) |                                                  |
-| Network Attach Model  | ExpressRoute                                  | Virtual Network                                  |
+| Supported SKU type    | <ul><li>AV36, AV36P, AV52, AV48</li><li>AV64 (with seed cluster of at least three AV36, AV36P, AV52, or AV48 nodes)</li></ul>| <ul><li>AV64</li></ul> |
+| Network Attach Model  | <ul><li>ExpressRoute</li></ul>                | <ul><li>Virtual Network</li></ul>                |
 
 ## Benefits
 With the Azure VMware Solution Gen 2 private clouds offering, you get the following benefits: 
@@ -50,14 +49,14 @@ Gen 2 private clouds are supported on the following SKU type:
 
 ## Regional availability
 
-Azure VMware Solution Gen 2 private clouds are available in the following regions for Public Preview.
+Azure VMware Solution Gen 2 private clouds are available in the following regions for Preview.
 
 | Region | Status |
 |--------|--------|
-| East US | Public Preview |
-| UK South | Public Preview |
-| Japan East | Public Preview |
-| Switzerland North | Public Preview |
+| East US | Preview |
+| UK South | Preview |
+| Japan East | Preview |
+| Switzerland North | Preview |
 
 ## Next steps
 
diff --git a/articles/azure-vmware/native-network-connectivity.md b/articles/azure-vmware/native-network-connectivity.md
@@ -3,7 +3,7 @@ title: Connectivity to an Azure Virtual Network
 description: Learn about key concepts and use cases on connectivity to Azure Virtual Networks.
 ms.topic: conceptual
 ms.service: azure-vmware
-ms.date: 3/14/2025
+ms.date: 4/15/2025
 ms.custom: engagement-fy25
 # customer intent: As a cloud administrator, I want to learn about connectivity to Azure Virtual Networks so that I can understand the features and benefits of this offering.
 ---
@@ -19,13 +19,13 @@ After you deploy Azure VMware Solution Generation (Gen) 2 private cloud, you nee
 
 ## Azure VMware Solution Hosted (Local) 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.
+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 VMware 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." lightbox="media/native-connectivity/native-connectivity-private-cloud.png":::
+:::image type="content" source="./media/native-connectivity/native-connectivity-private-cloud.png" alt-text="Diagram of an Azure VMware Solution Gen 2 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.
 
-:::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-virtual-network-management-subnets.png":::
+:::image type="content" source="./media/native-connectivity/native-connectivity-private-vnet-peering.png" alt-text="Diagram showing an Azure VMware Solution Gen 2 connection to other Virtual Networks." lightbox="media/native-connectivity/native-virtual-network-management-subnets.png":::
 
 ## Other Virtual Networks
 
@@ -36,7 +36,7 @@ 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." lightbox="media/native-connectivity/native-connectivity-private-vnet-peering.png":::
+:::image type="content" source="./media/native-connectivity/native-connectivity-private-vnet-peering.png" alt-text="Diagram showing an Azure VMware Solution Gen 2 connection to other Virtual Networks." lightbox="media/native-connectivity/native-connectivity-private-vnet-peering.png":::
 
 ## Related topics
 - [Connect to on-premises environment](native-connect-on-premises.md)
diff --git a/articles/azure-vmware/native-network-design-consideration.md b/articles/azure-vmware/native-network-design-consideration.md
