You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/introduction.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,13 +23,13 @@ The diagram shows the adjacency between private clouds and VNets in Azure, Azure
23
23
24
24
You can deploy new or scale existing private clouds through the Azure portal or Azure CLI.
25
25
26
-
## Azure VMware Solution deployment types
26
+
## Azure VMware Solution private cloud types
27
27
28
-
Azure VMware Solution provides two different deployment types:
28
+
Azure VMware Solution provides two different private cloud generations:
29
29
30
-
1. Azure VMware Solution provides VMware vSphere clusters built from dedicated bare-metal hosts deployed in Azure datacenter facilities. Microsoft-managed **ExpressRoute circuits** provide connectivity between VMware vSphere hosts and native Azure resources deployed in Virtual Networks.
30
+
1. Azure VMware Solution Generation 1 provides VMware vSphere clusters built from dedicated bare-metal hosts deployed in Azure datacenter facilities. Microsoft-managed **ExpressRoute circuits** provide connectivity between VMware vSphere hosts and native Azure resources deployed in Virtual Networks.
31
31
32
-
2.[Azure VMware Solution in a Virtual Network](native-introduction.md) (Public Preview) provides VMware vSphere clusters built from dedicated Azure bare-metal hosts. Azure VMware Solution in an **Azure Virtual Network** features an updated network architecture whereby VMware vSphere hosts are directly attached to Azure Virtual Networks. This offering in only supported on the AV64 SKU.
32
+
1.[Azure VMware Solution Generation 2](native-introduction.md) (Public Preview) provides VMware vSphere clusters built from dedicated Azure bare-metal hosts. Azure VMware Solution in an **Azure Virtual Network** features an updated network architecture whereby VMware vSphere hosts are directly attached to Azure Virtual Networks. This offering in only supported on the AV64 SKU.
#customer intent: As a cloud administrator, I want to connect multiple Azure VMware Solutions so that I can enable seamless communication between private clouds.
10
+
#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.
11
11
---
12
12
13
-
# Connect multiple Azure VMware Solutions in an Azure Virtual Network
In this article, you learn how to connect a private cloud deployed in a Virtual Network to other private clouds. It provides instructions on connecting to multiple Azure VMware Solution private clouds deployed in a Virtual Network.
15
+
In this article, you learn how to connect a Azure VMware Solution Generation (Gen) 2 private cloud to other Gen 2 private clouds.
16
16
17
17
## Prerequisite
18
18
19
-
Have multiple Azure VMware Solution on native private cloud deployed successfully.
19
+
Have multiple Azure VMware Solution Gen 2 private clouds deployed successfully.
20
20
21
-
## Connect multiple Azure VMware Solutions
21
+
## Connect multiple Azure VMware Solution Gen 2
22
22
23
23
Private clouds deployed in different Azure Virtual Networks can be connected using Virtual Network peering. The Virtual Network peering provides the best possible throughput and latency between Azure VMware Solution private clouds in the same region. For more information about how to do Azure Virtual Network peering, see [Create, change, or delete a Virtual Network peering](/azure/virtual-network/virtual-network-peering-overview).
24
24
@@ -30,5 +30,5 @@ Depending on the location of the private cloud, you may require local Virtual Ne
30
30
-[Connectivity to an Azure Virtual Network](native-network-connectivity.md)
31
31
-[Connect to on-premises environment](native-connect-on-premises.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)
34
-
-[Public and Private DNS forward lookup zone configuration](native-dns-forward-lookup-zone.md)
33
+
-[Connect Gen 2 and Gen 1 private clouds](native-connect-private-cloud-previous-edition.md)
34
+
-[Public and Private DNS forward lookup zone configuration](native-dns-forward-lookup-zone.md)
Copy file name to clipboardExpand all lines: articles/azure-vmware/native-connect-on-premises.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,16 +5,16 @@ ms.topic: how-to
5
5
ms.service: azure-vmware
6
6
ms.date: 3/14/2025
7
7
ms.custom: engagement-fy25
8
-
#customer intent: As an IT administrator, I want to connect my on-premises environment to Azure VMware Solution in an Azure Virtual Network so that I can extend my infrastructure seamlessly.
8
+
#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.
9
9
---
10
10
11
11
# Connect to an on-premises environment
12
12
13
-
You require network connectivity between the private cloud and other networks you deployed in an Azure Virtual Network, on-premises, other Azure VMware Solution private clouds, or on the Internet. In this article, you learn how the private cloud gets connectivity to your on-premises environments.
13
+
You require network connectivity between the your Gen 2 private cloud and other networks you deployed in an Azure Virtual Network, on-premises, other Azure VMware Solution private clouds, or on the Internet. In this article, you learn how your Gen 2 private cloud gets connectivity to your on-premises environments.
14
14
15
15
## Prerequisites
16
16
17
-
- Ensure you have an Azure VMware Solution private cloud in an Azure Virtual Network deployed successfully within your Azure Virtual Network.
17
+
- Ensure you have an Azure VMware Solution Gen 2 private cloud deployed successfully within your Azure Virtual Network.
18
18
- Ensure that you have a Virtual Network and a Virtual Network gateway created and fully provisioned. Follow the instructions to create a Virtual Network gateway for ExpressRoute. A Virtual Network gateway for ExpressRoute uses the GatewayType ExpressRoute, not VPN.
19
19
- Ensure you have an active ExpressRoute circuit provisioned.
20
20
@@ -31,6 +31,6 @@ Connectivity to on-premises is performed using a standard ExpressRoute connectio
31
31
32
32
-[Connectivity to an Azure Virtual Network](native-network-connectivity.md)
-[Connect multiple Azure VMware Solution in an Azure Virtual Network private clouds](native-connect-multiple-private-clouds.md)
35
-
-[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)
36
-
-[Public and Private DNS forward lookup zone configuration](native-dns-forward-lookup-zone.md)
34
+
-[Connect multiple Gen 2 private clouds](native-connect-multiple-private-clouds.md)
35
+
-[Connect Gen 2 private clouds and Gen 1 private clouds](native-connect-private-cloud-previous-edition.md)
36
+
-[Public and Private DNS forward lookup zone configuration](native-dns-forward-lookup-zone.md)
description: Learn about connecting Azure VMware Solution Generation 2 private clouds to Azure VMware Solution Generation 1 private clouds.
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
6
ms.date: 3/14/2025
7
7
ms.author: jacobjaygbay
8
-
#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.
8
+
#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.
9
9
---
10
10
11
-
# 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.
13
+
In this article, you learn how to connect Azure VMware Solution Generation (Gen) 2 private clouds to Azure VMware Solution Gen 1 private clouds. After you deploy an Azure VMware Solution Gen 2 private cloud, you may need to have network connectivity between the private cloud and other networks you have in an Azure Virtual Network, on-premises, other Azure VMware Solution private clouds, or the internet.
14
14
15
-
This article discusses how the Azure VMware Solution in an Azure Virtual Network private cloud gets connectivity to the previous edition of (not in an Azure Virtual Network) Azure VMware Solution private cloud.
15
+
This article discusses how the Azure VMware Solution Gen 2 private cloud gets connectivity to Azure VMware Solution Gen 1 private cloud.
16
16
17
17
## Prerequisite
18
18
19
-
Have Azure VMware Solution in an Azure Virtual Network and previous edition of the private cloud deployed successfully.
19
+
Have Azure VMware Solution Gen 2 private cloud and Gen 1 private cloud deployed successfully.
20
20
21
-
## 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.
23
+
A Gen 2 private cloud can be connected to a Gen 1 private cloud using a standard ExpressRoute connection, similar to how Gen 1 private clouds connect to a Virtual Network.
24
24
25
25
For more information about how to connect Virtual Networks using ExtressRoute, see [Azure VMware Solution's previous edition ExpressRoute connectivity to ExpressRoute Gateway](/azure/azure-vmware/deploy-azure-vmware-solution?tabs=azure-portal#connect-to-azure-virtual-network-with-expressroute).
26
26
27
27
### The steps are as follows:
28
-
1. Both types of Azure VMware Solution private clouds deployed; Azure VMware Solution in an Azure Virtual Network and Azure VMware Solution previous edition.
29
-
2. On Azure VMware Solution previous edition, request an ExpressRoute authorization key, and copy the authorization key and ExpressRoute ID.
30
-
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.
28
+
1. Both types of Azure VMware Solution private clouds deployed; Gen 2 and Gen 1.
29
+
2. On Gen 1, request an ExpressRoute authorization key, and copy the authorization key and ExpressRoute ID.
30
+
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.
31
31
4. Add a connection to the ExpressRoute gateway using the ER authorization key and ExpressRoute ID from the previous step.
32
32
33
33
:::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":::
@@ -36,5 +36,5 @@ For more information about how to connect Virtual Networks using ExtressRoute, s
36
36
-[Connectivity to an Azure Virtual Network](native-network-connectivity.md)
37
37
-[Connect to on-premises environment](native-connect-on-premises.md)
description: Learn how to create an Azure VMware Solution in an Azure Virtual Network to apply Azure's infrastructure and VMware expertise effectively.
5
+
description: Learn how to create an Azure VMware Solution Generation 2 Private Cloud to apply Azure's infrastructure and VMware expertise effectively.
6
6
ms.topic: how-to
7
7
ms.service: azure-vmware
8
8
ms.date: 03/11/2025
9
9
ms.custom: engagement-fy25
10
-
#customer intent: As a cloud administrator, I want to create an Azure VMware Solution in a Virtual Network so that I can leverage Azure's infrastructure and VMware expertise.
10
+
#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.
11
11
---
12
12
13
-
# Create an Azure VMware Solution in an Azure Virtual Network (Public Preview)
In this tutorial, you learn how to create an Azure VMware Solution private cloud in an Azure Virtual Network. 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 offering utilizes the existing AV64 SKU.
15
+
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.
16
16
17
-
With this offering, you can directly create the private cloud using the AV64 SKU. You are no longer required to deploy a minimum of three hosts of AV36, AV36P, or AV52 to provision a cluster with AV64.
17
+
With this generation, you can directly create the private cloud using the AV64 SKU. You are no longer required to deploy a minimum of three hosts of AV36, AV36P, or AV52 to provision a cluster with AV64.
18
18
19
19
## Prerequisites
20
20
21
-
Before you begin, these items are required to create an Azure VMware Solution private cloud in an Azure Virtual Network private cloud:
21
+
Before you begin, these items are required to create an Azure VMware Solution Gen 2 private cloud:
22
22
23
23
- Enable the Azure VMware Solution Fleet Rp Service Principal as described in the [enable Azure VMware Solution Fleet Rp service Principal](native-first-party-principle-security.md).
24
24
- Ensure you have appropriate administrative rights and permission to create a private cloud. You must be at minimum Owner or User Access Administrator on the subscription.
25
25
- Hosts provisioned and the "Microsoft.AVS" resource provider is registered.
26
26
- Deploy or us an existing Azure Virtual Network with a minimum network address space of a /22 or four /24s.
27
-
- The newly created Azure Virtual Network and your Azure VMware Solution private cloud must be in the same Resource Group.
27
+
- The newly created Azure Virtual Network and your Azure VMware Solution Gen 2 private cloud must be in the same Resource Group.
28
28
- Ensure you have sufficient AV64 quota allocated to your subscription in the desired region before your deployment.
29
29
- The following Preview feature flags need to be registered under the subscription where your private cloud will reside. This commands can be run using Azure Cloud Shell.
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.
79
79
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).
80
+
81
+
## Next steps
82
+
83
+
- Learn more about [Azure VMware Solution Gen 2 private cloud design considerations](native-network-design-consideration.md)
0 commit comments