Skip to content

Commit 10ee81e

Browse files
19BMG0019BMG00
authored
Merge pull request #215504 from JnHs/jh-arcvm-sm1022
fixed formatting
2 parents 47a9486 + dcf6ea8 commit 10ee81e

File tree

1 file changed

+56
-50
lines changed

1 file changed

+56
-50
lines changed

‎articles/azure-arc/vmware-vsphere/support-matrix-for-arc-enabled-vmware-vsphere.md

Lines changed: 56 additions & 50 deletions
Original file line numberDiff line numberDiff line change
@@ -1,34 +1,39 @@
11
---
2-
title: Support matrix for Arc-enabled VMware vSphere (preview)
3-
description: In this article, you'll learn about the support matrix for Arc-enabled VMware vSphere including vCenter Server versions supported, network requirements etc.
2+
title: Support matrix for Azure Arc-enabled VMware vSphere (preview)
3+
description: Learn about the support matrix for Arc-enabled VMware vSphere including vCenter Server versions supported, network requirements, and more.
44
ms.topic: how-to
5-
ms.date: 09/30/2022
5+
ms.date: 10/21/2022
66

77
# Customer intent: As a VI admin, I want to understand the support matrix for Arc-enabled VMware vSphere.
88
---
99

10-
# Support matrix for Arc-enabled VMware vSphere (preview)
10+
# Support matrix for Azure Arc-enabled VMware vSphere (preview)
1111

12-
This article documents the prerequisites and support requirements for using the [Arc-enabled VMware vSphere (preview)](overview.md) to manage your VMware vSphere VMs through Azure Arc.
12+
This article documents the prerequisites and support requirements for using [Azure Arc-enabled VMware vSphere (preview)](overview.md) to manage your VMware vSphere VMs through Azure Arc.
1313

14-
To use Arc-enabled VMware vSphere, you must deploy an Azure Arc resource bridge in your VMware vSphere environment. The resource bridge provides an ongoing connection between your VMware vCenter Server and Azure. Once you've connected your VMware vCenter Server to Azure, components on the resource bridge discover your vCenter inventory. You can enable them in Azure and start performing virtual hardware and guest OS operations on them using Azure Arc.
14+
To use Arc-enabled VMware vSphere, you must deploy an Azure Arc resource bridge (preview) in your VMware vSphere environment. The resource bridge provides an ongoing connection between your VMware vCenter Server and Azure. Once you've connected your VMware vCenter Server to Azure, components on the resource bridge discover your vCenter inventory. You can enable them in Azure and start performing virtual hardware and guest OS operations on them using Azure Arc.
1515

16+
## VMware vSphere requirements
1617

17-
## VMware vSphere Requirements
18+
The following requirements must be met in order to use Azure Arc-enabled VMware vSphere.
1819

1920
### Supported vCenter Server versions
2021

21-
- vCenter Server version 6.7 or 7.
22+
Azure Arc-enabled VMware vSphere (preview) works with vCenter Server versions 6.7 and 7.
23+
24+
> [!NOTE]
25+
> Azure Arc-enabled VMware vSphere (preview) currently supports vCenters with a maximum of 9500 VMs. If your vCenter has more than 9500 VMs, it is not recommended to use Arc-enabled VMware vSphere with it at this point.
2226
2327
### Required vSphere account privileges
2428

2529
You need a vSphere account that can:
26-
- Read all inventory.
30+
31+
- Read all inventory.
2732
- Deploy and update VMs to all the resource pools (or clusters), networks, and VM templates that you want to use with Azure Arc.
2833

2934
This account is used for the ongoing operation of Azure Arc-enabled VMware vSphere (preview) and the deployment of the Azure Arc resource bridge (preview) VM.
3035

31-
### Resource bridge resource requirements
36+
### Resource bridge resource requirements
3237

3338
For Arc-enabled VMware vSphere, resource bridge has the following minimum virtual hardware requirements
3439

@@ -42,23 +47,23 @@ The following firewall URL exceptions are needed for the Azure Arc resource brid
4247

4348
| **Service** | **Port** | **URL** | **Direction** | **Notes**|
4449
| --- | --- | --- | --- | --- |
45-
| Microsoft container registry | 443 | https://mcr.microsoft.com | Appliance VM IP and control plane endpoint need outbound connection. | Required to pull container images for installation. |
46-
| Azure Arc Identity service | 443 | https://*.his.arc.azure.com | Appliance VM IP and control plane endpoint need outbound connection. | Manages identity and access control for Azure resources |
47-
| Azure Arc configuration service | 443 | https://*.dp.kubernetesconfiguration.azure.com | Appliance VM IP and control plane endpoint need outbound connection. | Used for Kubernetes cluster configuration. |
48-
| Cluster connect service | 443 | https://*.servicebus.windows.net | Appliance VM IP and control plane endpoint need outbound connection. | Provides cloud-enabled communication to connect on-premises resources with the cloud. |
49-
| Guest Notification service | 443 | `https://guestnotificationservice.azure.com` | Appliance VM IP and control plane endpoint need outbound connection. | Used to connect on-premises resources to Azure. |
50-
| SFS API endpoint | 443 | msk8s.api.cdp.microsoft.com | Host machine, Appliance VM IP and control plane endpoint need outbound connection. | Used when downloading product catalog, product bits, and OS images from SFS. |
51-
| Resource bridge (appliance) Dataplane service | 443 | https://*.dp.prod.appliances.azure.com | Appliance VM IP and control plane endpoint need outbound connection. | Communicate with resource provider in Azure. |
52-
| Resource bridge (appliance) container image download | 443 | *.blob.core.windows.net, `https://ecpacr.azurecr.io` | Appliance VM IP and control plane endpoint need outbound connection. | Required to pull container images. |
53-
| Resource bridge (appliance) image download | 80 | *.dl.delivery.mp.microsoft.com | Host machine, Appliance VM IP and control plane endpoint need outbound connection. | Download the Arc resource bridge OS images. |
50+
| Microsoft container registry | 443 | `https://mcr.microsoft.com` | Appliance VM IP and control plane endpoint need outbound connection. | Required to pull container images for installation. |
51+
| Azure Arc Identity service | 443 | `https://*.his.arc.azure.com` | Appliance VM IP and control plane endpoint need outbound connection. | Manages identity and access control for Azure resources |
52+
| Azure Arc configuration service | 443 | `https://*.dp.kubernetesconfiguration.azure.com` | Appliance VM IP and control plane endpoint need outbound connection. | Used for Kubernetes cluster configuration. |
53+
| Cluster connect service | 443 | `https://*.servicebus.windows.net` | Appliance VM IP and control plane endpoint need outbound connection. | Provides cloud-enabled communication to connect on-premises resources with the cloud. |
54+
| Guest Notification service | 443 | `https://guestnotificationservice.azure.com` | Appliance VM IP and control plane endpoint need outbound connection. | Used to connect on-premises resources to Azure. |
55+
| SFS API endpoint | 443 | `msk8s.api.cdp.microsoft.com` | Host machine, Appliance VM IP and control plane endpoint need outbound connection. | Used when downloading product catalog, product bits, and OS images from SFS. |
56+
| Resource bridge (appliance) Data plane service | 443 | `https://*.dp.prod.appliances.azure.com` | Appliance VM IP and control plane endpoint need outbound connection. | Communicate with resource provider in Azure. |
57+
| Resource bridge (appliance) container image download | 443 | `*.blob.core.windows.net`, `https://ecpacr.azurecr.io` | Appliance VM IP and control plane endpoint need outbound connection. | Required to pull container images. |
58+
| Resource bridge (appliance) image download | 80 | `*.dl.delivery.mp.microsoft.com` | Host machine, Appliance VM IP and control plane endpoint need outbound connection. | Download the Arc resource bridge OS images. |
5459
| Azure Arc for K8s container image download | 443 | `https://azurearcfork8sdev.azurecr.io` | Appliance VM IP and control plane endpoint need outbound connection. | Required to pull container images. |
55-
| ADHS telemetry service | 443 | adhs.events.data.microsoft.com | Appliance VM IP and control plane endpoint need outbound connection. Runs inside the appliance/mariner OS. | Used periodically to send Microsoft required diagnostic data from control plane nodes. Used when telemetry is coming off Mariner, which would mean any K8s control plane. |
56-
| Microsoft events data service | 443 | v20.events.data.microsoft.com | Appliance VM IP and control plane endpoint need outbound connection. | Used periodically to send Microsoft required diagnostic data from the Azure Stack HCI or Windows Server host. Used when telemetry is coming off Windows like Windows Server or HCI. |
60+
| ADHS telemetry service | 443 | `adhs.events.data.microsoft.com` | Appliance VM IP and control plane endpoint need outbound connection. Runs inside the appliance/mariner OS. | Used periodically to send Microsoft required diagnostic data from control plane nodes. Used when telemetry is coming off Mariner, which would mean any K8s control plane. |
61+
| Microsoft events data service | 443 | `v20.events.data.microsoft.com` | Appliance VM IP and control plane endpoint need outbound connection. | Used periodically to send Microsoft required diagnostic data from the Azure Stack HCI or Windows Server host. Used when telemetry is coming off Windows like Windows Server or HCI. |
5762
| vCenter Server | 443 | URL of the vCenter server | Appliance VM IP and control plane endpoint need outbound connection. | Used to by the vCenter server to communicate with the Appliance VM and the control plane.|
5863

59-
## Azure permissions required
64+
## Azure role/permission requirements
6065

61-
Following are the minimum Azure roles required for various operations:
66+
The minimum Azure roles required for operations related to Arc-enabled VMware vSphere are as follows:
6267

6368
| **Operation** | **Minimum role required** | **Scope** |
6469
| --- | --- | --- |
@@ -68,57 +73,58 @@ Following are the minimum Azure roles required for various operations:
6873
| VM Provisioning | Azure Arc VMware VM Contributor | On the subscription or resource group where you want to provision VMs |
6974
| VM Operations | Azure Arc VMware VM Contributor | On the subscription or resource group that contains the VM, or on the VM itself |
7075

71-
Any roles with higher permissions such as *Owner/Contributor* role on the same scope, will also allow you to perform all the operations listed above.
76+
Any roles with higher permissions on the same scope, such as Owner or Contributor, will also allow you to perform the operations listed above.
7277

7378
## Guest management (Arc agent) requirements
7479

75-
With Arc-enabled VMware vSphere, you can install the Arc connected machine agent on your VMs at scale and use Azure management services on the VMs. There are additional requirements for this capability:
80+
With Arc-enabled VMware vSphere, you can install the Arc connected machine agent on your VMs at scale and use Azure management services on the VMs. There are additional requirements for this capability.
7681

77-
To enable guest management (install the Arc connected machine agent), ensure
82+
To enable guest management (install the Arc connected machine agent), ensure the following:
7883

79-
- VM is powered on
80-
- VM has VMware tools installed and running
81-
- Resource bridge has access to the host on which the VM is running
82-
- VM is running a [supported operating system](#supported-operating-systems)
84+
- VM is powered on.
85+
- VM has VMware tools installed and running.
86+
- Resource bridge has access to the host on which the VM is running.
87+
- VM is running a [supported operating system](#supported-operating-systems).
8388
- VM has internet connectivity directly or through proxy. If the connection is through a proxy, ensure [these URLs](#networking-requirements) are allow-listed.
8489

90+
Additionally, be sure that the requirements below are met in order to enable guest management.
91+
8592
### Supported operating systems
8693

87-
The officially supported versions of the Windows and Linux operating system for the Azure Connected Machine agent are listed [here](../servers/prerequisites.md#supported-operating-systems). Only x86-64 (64-bit) architectures are supported. x86 (32-bit) and ARM-based architectures, including x86-64 emulation on arm64, aren't supported operating environments.
94+
Make sure you are using a version of the Windows or Linux [operating systems that are officially supported for the Azure Connected Machine agent](../servers/prerequisites.md#supported-operating-systems). Only x86-64 (64-bit) architectures are supported. x86 (32-bit) and ARM-based architectures, including x86-64 emulation on arm64, aren't supported operating environments.
8895

8996
### Software requirements
9097

9198
Windows operating systems:
9299

93-
* NET Framework 4.6 or later is required. [Download the .NET Framework](/dotnet/framework/install/guide-for-developers).
94-
* Windows PowerShell 5.1 is required. [Download Windows Management Framework 5.1.](https://www.microsoft.com/download/details.aspx?id=54616).
100+
- NET Framework 4.6 or later is required. [Download the .NET Framework](/dotnet/framework/install/guide-for-developers).
101+
- Windows PowerShell 5.1 is required. [Download Windows Management Framework 5.1.](https://www.microsoft.com/download/details.aspx?id=54616).
95102

96103
Linux operating systems:
97104

98-
* systemd
99-
* wget (to download the installation script)
105+
- systemd
106+
- wget (to download the installation script)
100107

101108
### Networking requirements
102109

103110
The following firewall URL exceptions are needed for the Azure Arc agents:
104111

105112
| **URL** | **Description** |
106113
| --- | --- |
107-
| aka.ms | Used to resolve the download script during installation |
108-
| download.microsoft.com | Used to download the Windows installation package |
109-
| packages.microsoft.com | Used to download the Linux installation package |
110-
| login.windows.net | Azure Active Directory |
111-
| login.microsoftonline.com | Azure Active Directory |
112-
| pas.windows.net | Azure Active Directory |
113-
| management.azure.com | Azure Resource Manager - to create or delete the Arc server resource |
114-
| *.his.arc.azure.com | Metadata and hybrid identity services |
115-
| *.guestconfiguration.azure.com | Extension management and guest configuration services |
116-
| guestnotificationservice.azure.com, *.guestnotificationservice.azure.com | Notification service for extension and connectivity scenarios |
117-
| azgn*.servicebus.windows.net | Notification service for extension and connectivity scenarios |
118-
| *.servicebus.windows.net | For Windows Admin Center and SSH scenarios |
119-
| *.blob.core.windows.net | Download source for Azure Arc-enabled servers extensions |
120-
| dc.services.visualstudio.com | Agent telemetry |
121-
114+
| `aka.ms` | Used to resolve the download script during installation |
115+
| `packages.microsoft.com` | Used to download the Linux installation package |
116+
| `download.microsoft.com` | Used to download the Windows installation package |
117+
| `login.windows.net` | Azure Active Directory |
118+
| `login.microsoftonline.com` | Azure Active Directory |
119+
| `pas.windows.net` | Azure Active Directory |
120+
| `management.azure.com` | Azure Resource Manager - to create or delete the Arc server resource |
121+
| `*.his.arc.azure.com` | Metadata and hybrid identity services |
122+
| `*.guestconfiguration.azure.com` | Extension management and guest configuration services |
123+
| `guestnotificationservice.azure.com`, `*.guestnotificationservice.azure.com` | Notification service for extension and connectivity scenarios |
124+
| `azgn*.servicebus.windows.net` | Notification service for extension and connectivity scenarios |
125+
| `*.servicebus.windows.net` | For Windows Admin Center and SSH scenarios |
126+
| `*.blob.core.windows.net` | Download source for Azure Arc-enabled servers extensions |
127+
| `dc.services.visualstudio.com` | Agent telemetry |
122128

123129
## Next steps
124130

0 commit comments

Comments
 (0)