Skip to content

Commit fc69516

Browse files
edits
1 parent a807e84 commit fc69516

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/container-registry/container-registry-vnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Each registry supports a maximum of 100 virtual network rules.
1616

1717
> [!IMPORTANT]
1818
> Azure Container Registry now supports [Azure Private Link](container-registry-private-link.md), enabling private endpoints from a virtual network to be placed on a registry. Private endpoints are accessible from within the virtual network, using private IP addresses. We recommend using private endpoints instead of service endpoints in most network scenarios.
19-
> The container registry does not support enabling both private link and service endpoint features configured from a virtual network. So, we recommend to [list and remove network rules](container-registry-vnet.md#remove-network-rules) as required.
19+
> The container registry does not support enabling both private link and service endpoint features configured from a virtual network. So, we recommend running the list and removing the [network rules](container-registry-vnet.md#remove-network-rules) as required.
2020
2121
Configuring a registry service endpoint is available in the **Premium** container registry service tier. For information about registry service tiers and limits, see [Azure Container Registry service tiers](container-registry-skus.md).
2222

0 commit comments

Comments
 (0)