Skip to content

Commit 047818d

Browse files
committed
update with notes
1 parent fc17c61 commit 047818d

File tree

3 files changed

+18
-6
lines changed

3 files changed

+18
-6
lines changed

articles/container-apps/manage-secrets.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -202,6 +202,9 @@ Secrets Key Vault references aren't supported in PowerShell.
202202

203203
---
204204

205+
> [!NOTE]
206+
> If you're using [UDR With Azure Firewall](./networking.md#user-defined-routes-udr---preview), you will need to add the `AzureKeyVault` service tag and the *login.microsoft.com* FQDN to the allow list for your firewall. To learn more, see [configuring UDR with Azure Firewall](./networking.md#configuring-udr-with-azure-firewall).
207+
205208
#### Key Vault secret URI and secret rotation
206209

207210
The Key Vault secret URI must be in one of the following formats:

articles/container-apps/networking.md

Lines changed: 12 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -152,19 +152,25 @@ User Defined Routes (UDR) and controlled egress through NAT Gateway are supporte
152152

153153
### User defined routes (UDR) - preview
154154

155-
You can use UDR on the workload profiles architecture to restrict outbound traffic from your container app through Azure Firewall or other network appliances. Configuring UDR is done outside of the Container Apps environment scope.
155+
> [!NOTE]
156+
> When using UDR with Azure Firewall in Azure Container Apps, you will need to add certain FQDN's and service tags to the allowlist for the firewall. To learn more, see[configuring UDR with Azure Firewall](./networking.md#configuring-udr-with-azure-firewall).
157+
158+
You can use UDR on the workload profiles architecture to restrict outbound traffic from your container app through Azure Firewall or other network appliances. Configuring UDR is done outside of the Container Apps environment scope. UDR isn't supported for external environments.
156159

157160
:::image type="content" source="media/networking/udr-architecture.png" alt-text="Diagram of how UDR is implemented for Container Apps.":::
158161

159-
Important notes for configuring UDR with Azure Firewall:
162+
Azure creates a default route table for your virtual networks upon create. By implementing a user-defined route table, you can control how traffic is routed within your virtual network. For example, you can create a UDR that routes all traffic to the firewall.
163+
164+
#### Configuring UDR with Azure Firewall - preview:
160165

161-
- You need to allow the `MicrosoftContainerRegistry` and its dependency `AzureFrontDoor.FirstParty` service tags to your Azure Firewall. Alternatively, you can add the following FQDNs: *mcr.microsoft.com* and **.data.mcr.microsoft.com*.
166+
UDR is only supported on the workload profiles architecture. For a guide on how to setup UDR with Container Apps to restrict outbound traffic with Azure Firewall, visit the [how to for Container Apps and Azure Firewall](./user-defined-routes.md).
167+
168+
The following FQDNs and service tags must be added to the allowlist for your firewall depending on which resources you are using:
169+
170+
- For all scenarios, you need to allow the `MicrosoftContainerRegistry` and its dependency `AzureFrontDoor.FirstParty` service tags through your Azure Firewall. Alternatively, you can add the following FQDNs: *mcr.microsoft.com* and **.data.mcr.microsoft.com*.
162171
- If you're using Azure Container Registry (ACR), you need to add the `AzureContainerRegistry` service tag and the **.blob.core.windows.net* FQDN in the Azure Firewall.
163172
- If you're using [Docker Hub registry](https://docs.docker.com/desktop/allow-list/) and want to access it through the firewall, you need to add the following FQDNs to your firewall: *hub.docker.com*, *registry-1.docker.io*, and *production.cloudflare.docker.com*.
164173
- If you're using [Azure Key Vault references](./manage-secrets.md#reference-secret-from-key-vault), you will need to add the `AzureKeyVault` service tag and the *login.microsoft.com* FQDN to the allow list for your firewall.
165-
- External environments aren't supported.
166-
167-
Azure creates a default route table for your virtual networks upon create. By implementing a user-defined route table, you can control how traffic is routed within your virtual network. For example, you can create a UDR that routes all traffic to the firewall. For a guide on how to setup UDR with Container Apps to restrict outbound traffic with Azure Firewall, visit the [how to for Container Apps and Azure Firewall](./user-defined-routes.md).
168174

169175
### NAT gateway integration - preview
170176

articles/container-apps/user-defined-routes.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,9 @@ Your virtual networks in Azure have default route tables in place when you creat
121121

122122
## Configure firewall policies
123123

124+
>> [!NOTE]
125+
> When using UDR with Azure Firewall in Azure Container Apps, you will need to add certain FQDN's and service tags to the allowlist for the firewall. For example, the FQDNs *mcr.microsoft.com* and **.data.mcr.microsoft.com* are required for all scenarios. To learn more, see [configuring UDR with Azure Firewall](./networking.md#configuring-udr-with-azure-firewall).
126+
124127
Now, all outbound traffic from your container app is routed to the firewall. Currently, the firewall still allows all outbound traffic through. In order to manage what outbound traffic is allowed or denied, you need to configure firewall policies.
125128

126129
1. In your *Azure Firewall* resource on the *Overview* page, select **Firewall policy**

0 commit comments

Comments
 (0)