Skip to content

Commit d04c832

Browse files
authored
Merge pull request #104013 from dlepow/acrfix
[ACR] MCR firewall rules
2 parents bd21660 + d235afb commit d04c832

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/container-registry/container-registry-firewall-access-rules.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Firewall access rules
33
description: Configure rules to access an Azure container registry from behind a firewall, by allowing access to ("whitelisting") REST API and storage endpoint domain names or service-specific IP address ranges.
44
ms.topic: article
5-
ms.date: 07/17/2019
5+
ms.date: 02/11/2020
66
---
77

88
# Configure rules to access an Azure container registry behind a firewall
@@ -111,6 +111,10 @@ In an Azure virtual network, use network security rules to filter traffic from a
111111

112112
For example, create an outbound network security group rule with destination **AzureContainerRegistry** to allow traffic to an Azure container registry. To allow access to the service tag only in a specific region, specify the region in the following format: **AzureContainerRegistry**.[*region name*].
113113

114+
## Configure client firewall rules for MCR
115+
116+
If you need to access Microsoft Container Registry (MCR) from behind a firewall, see the guidance to configure [MCR client firewall rules](https://github.com/microsoft/containerregistry/blob/master/client-firewall-rules.md). MCR is the primary registry for all Microsoft-published docker images, such as Windows Server images.
117+
114118
## Next steps
115119

116120
* Learn about [Azure best practices for network security](../security/fundamentals/network-best-practices.md)

0 commit comments

Comments
 (0)