Skip to content

Commit 44ac674

Browse files
Merge pull request #225374 from alt-key/patch-1
Update overview.md
2 parents ec10b7d + 3352054 commit 44ac674

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

articles/azure-arc/resource-bridge/overview.md

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Custom locations and cluster extension are both Azure resources, which are linke
4444

4545
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.
4646

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.
4848

4949
## Benefits of Azure Arc resource bridge (preview)
5050

@@ -84,7 +84,7 @@ If you are deploying on Azure Stack HCI, the x32 Azure CLI installer can be used
8484

8585
### Supported regions
8686

87-
Azure Arc resource bridge currently supports the following Azure regions:
87+
Arc resource bridge currently supports the following Azure regions:
8888

8989
* East US
9090
* West Europe
@@ -99,19 +99,20 @@ While Azure has a number of redundancy features at every level of failure, if a
9999

100100
### Private cloud environments
101101

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:
103103

104-
* VMware vSphere version 6.7
104+
* VMware vSphere version 6.7, 7.0
105105
* Azure Stack HCI
106+
* SCVMM
106107

107108
### Required Azure permissions
108109

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.
111112

112113
### Networking
113114

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.
115116

116117
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.
117118

0 commit comments

Comments
 (0)