/
Container Registries Should Use Private Link

Container Registries Should Use Private Link

Description:

Azure Private Link lets you connect your virtual network to Azure services without a public IP address at the source or destination. The private link platform handles the connectivity between the consumer and services over the Azure backbone network. By mapping private endpoints to your container registries instead of the entire service, you'll also be protected against data leakage risks. Learn more at: https://aka.ms/acr/private-link.



Solution/Reference: 

To enable private links for a registry:
1. Ensure the registry's SKU is set to Premium (SKUs can be upgraded)
2. In the Private endpoints tab, under Network Settings, add basic endpoint information such as name and region
3. On the next page, add registry resource information (such as: name, resource type and subscription)
4. On the next page, add networking and private dns configuration.
5. Create the private endpoint resource.

For more information, see: https://aka.ms/acr/privatelink

Related content

Container Registries Should Not Allow Unrestricted Network Access
Container Registries Should Not Allow Unrestricted Network Access
More like this
App Configuration Should Use Private Link
App Configuration Should Use Private Link
More like this
Container Registries Should be Encrypted with a Customer-Managed Key (CMK)
Container Registries Should be Encrypted with a Customer-Managed Key (CMK)
More like this
Azure Event Grid Domains/Topics Should Use Private Link
Azure Event Grid Domains/Topics Should Use Private Link
More like this
API Management Services Should Use a Virtual Network
API Management Services Should Use a Virtual Network
More like this
Private Endpoint Should be Configured for Key Vault
Private Endpoint Should be Configured for Key Vault
More like this