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-arc/resource-bridge/overview.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ Custom locations and cluster extension are both Azure resources, which are linke
44
44
45
45
Some resources are unique to the infrastructure. For example, vCenter has a resource pool, network, and template resources. During VM creation, these resources need to be specified. With Azure Stack HCI, you just need to select the custom location, network and template to create a VM.
46
46
47
-
To summarize, the Azure resources are projections of the resources running in your on-premises private cloud. If the on-premises resource is not healthy, it can impact the health of the related resources. For example, if the Arc resource bridge (preview) has been deleted by accident, all the resources hosted in the Arc resource bridge (preview) are impacted. That is, the custom locations and cluster extensions are deleted as a result. The actual VMs are not impacted, as they are running on vCenter, but the management path to those VMs is interrupted, and you won't be able to start or stop the VM from Azure. It is not recommended to manage or modify the Arc resource bridge (preview) using any on-premises applications directly.
47
+
To summarize, the Azure resources are projections of the resources running in your on-premises private cloud. If the on-premises resource is not healthy, it can impact the health of the related resources that are projected in Azure. For example, if the resource bridge is deleted by accident, all the resources projected in Azure by the resource bridge are impacted. The on-premises VMs in your on-premises private cloud are not impacted, as they are running on vCenter but you won't be able to start or stop the VMs from Azure. It is not recommended to directly manage or modify the resource bridge using any on-premises applications.
48
48
49
49
## Benefits of Azure Arc resource bridge (preview)
50
50
@@ -84,7 +84,7 @@ If you are deploying on Azure Stack HCI, the x32 Azure CLI installer can be used
84
84
85
85
### Supported regions
86
86
87
-
Azure Arc resource bridge currently supports the following Azure regions:
87
+
Arc resource bridge currently supports the following Azure regions:
88
88
89
89
* East US
90
90
* West Europe
@@ -99,19 +99,20 @@ While Azure has a number of redundancy features at every level of failure, if a
99
99
100
100
### Private cloud environments
101
101
102
-
The following private cloud environments and their versions are officially supported for the Azure Arc resource bridge:
102
+
The following private cloud environments and their versions are officially supported for Arc resource bridge:
103
103
104
-
* VMware vSphere version 6.7
104
+
* VMware vSphere version 6.7, 7.0
105
105
* Azure Stack HCI
106
+
* SCVMM
106
107
107
108
### Required Azure permissions
108
109
109
-
* To onboard the Arc resource bridge, you must have the [Contributor](../../role-based-access-control/built-in-roles.md#contributor) role for the resource group.
110
-
* To read, modify, and delete the Arc resource bridge, you must have the [Contributor](../../role-based-access-control/built-in-roles.md#contributor) role for the resource group.
110
+
* To onboard Arc resource bridge, you must have the [Contributor](../../role-based-access-control/built-in-roles.md#contributor) role for the resource group.
111
+
* To read, modify, and delete Arc resource bridge, you must have the [Contributor](../../role-based-access-control/built-in-roles.md#contributor) role for the resource group.
111
112
112
113
### Networking
113
114
114
-
The Arc resource bridge communicates outbound securely to Azure Arc over TCP port 443. If the appliance needs to connect through a firewall or proxy server to communicate over the internet, it communicates outbound using the HTTPS protocol.
115
+
Arc resource bridge communicates outbound securely to Azure Arc over TCP port 443. If the appliance needs to connect through a firewall or proxy server to communicate over the internet, it communicates outbound using the HTTPS protocol.
115
116
116
117
You may need to allow specific URLs to [ensure outbound connectivity is not blocked](troubleshoot-resource-bridge.md#restricted-outbound-connectivity) by your firewall or proxy server.
0 commit comments