Skip to content

Commit 6214bea

Browse files
authored
Merge pull request #91123 from kgremban/oct9-40096
Add link to ACR firewall rules
2 parents df168df + b466a9b commit 6214bea

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/iot-edge/production-checklist.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -172,10 +172,12 @@ This checklist is a starting point for firewall rules:
172172
| mcr.microsoft.com | 443 | Microsoft container registry |
173173
| global.azure-devices-provisioning.net | 443 | DPS access (optional) |
174174
| \*.azurecr.io | 443 | Personal and third-party container registries |
175-
| \*.blob.core.windows.net | 443 | Download of image deltas |
175+
| \*.blob.core.windows.net | 443 | Download Azure Container Registry image deltas from blob storage |
176176
| \*.azure-devices.net | 5671, 8883, 443 | IoT Hub access |
177177
| \*.docker.io | 443 | Docker Hub access (optional) |
178178

179+
Some of these firewall rules are inherited from Azure Container Registry. For more information, see [Configure rules to access an Azure container registry behind a firewall](../container-registry/container-registry-firewall-access-rules.md).
180+
179181
### Configure communication through a proxy
180182

181183
If your devices are going to be deployed on a network that uses a proxy server, they need to be able to communicate through the proxy to reach IoT Hub and container registries. For more information, see [Configure an IoT Edge device to communicate through a proxy server](how-to-configure-proxy-support.md).

0 commit comments

Comments
 (0)