Thank you for reaching out to the Microsoft Q&A forum.
To see the traffic movements from the container through to the firewall and where the traffic is heading?
You can...
Enable Virtual Network Flow Logs to monitor traffic at the VNET level:
- Logs include source/destination IPs, ports, protocols, and flow states.
- You can export logs to SIEM tools or visualize them in dashboards.
- Flow logs help identify blocked traffic, encryption status, and throughput
Reference link to follow:https://free.blessedness.top/en-us/azure/network-watcher/vnet-flow-logs-overview?tabs=Americas
Ensure your container app subnet has a UDR that routes all outbound traffic to the firewall:
- Address prefix:
0.0.0.0/0 - Next hop type:
Virtual appliance - Next hop address: Firewall’s private IP
Reference link to follow:https://free.blessedness.top/en-us/azure/container-apps/use-azure-firewall
Configure Application Rules or Network Rules in Azure Firewall:
Allow traffic to required FQDNs (e.g., mcr.microsoft.com, *.blob.core.windows.net) or service tags (e.g., AzureContainerRegistry, AzureKeyVault)
Verify with curl
curl -s https://mcr.microsoft.com
If allowed, you’ll get a response.
If blocked, no response indicates firewall enforcement is working.
Enable Monitoring and Diagnostics
- Go to Azure Firewall → Logs → Application rule log data.
- Enable
AzureFirewallApplicationRulelogging. - Use these logs to trace outbound requests and verify rule hits
Reference link to follow: https://free.blessedness.top/en-us/azure/app-service/network-secure-outbound-traffic-azure-firewall
If you find this comment helpful, please “up-vote” for the information provided , this can be beneficial to community members.
Kindly let us know if you have any additional questions.
Thanks