Teams implementing the Azure Well-Architected Framework, and using the Hub and Spoke network topology often rely on the Azure Firewall to inspect traffic coming from Azure Kubernetes Service (AKS) clusters. However, they face challenges in precisely identifying the origin of that traffic as it traverses the Azure Firewall. With Calico egress gateway you can now identify the Kubernetes namespaces and pods associated with egress traffic outside your clusters when inspected by the Azure Firewall.

In this webinar, you will learn how Calico egress gateway and Azure firewall together can provide the following:

1. Security and Compliance: Allow platform teams to enforce proper security measures, preventing unauthorized access and potential data breaches by identifying the source of outbound traffic.
2. Troubleshooting and Debugging: Pinpoint the exact application or namespace responsible for the traffic, making it easier to identify and resolve problems efficiently
3. Billing and Cost Management: Identify which applications contribute most to egress traffic and make informed decisions on resource allocation and billing.