What the preview is
According to Microsoft Learn, Azure Firewall for Containers lets you manage Azure Firewall protection for Azure Kubernetes Service (AKS) workloads through Kubernetes custom resources. An Azure Firewall Controller translates those resources into Azure Firewall configuration and policies.
In practice, Kubernetes platform teams can describe firewall intent in the cluster's own declarative language. They don't have to hand every request to a separate network team that works in the portal. The Learn page lists an AzureFirewall custom resource that creates and manages an Azure Firewall deployment. The same page says the resource can point to either a managed firewall's Kubernetes name and namespace, or an existing firewall's Azure resource ID. That means you can adopt it with a firewall you already run.
The AKS-only scope is my inference from that documentation. The Azure Updates item itself was not readable.
Preview limits
Microsoft's deployment guide lists these constraints:
- The preview supports Azure public cloud only, in the listed preview regions. Sovereign clouds are out.
- Prerequisites include an Azure subscription and access to Azure Firewall for Containers in a supported preview region.
- The guide's validation steps mention checking the preview region, non-Overlay Azure CNI, and the kube-system/azure-ip-masq-agent-config. Clusters using Overlay networking appear to be a poor fit for now.
- The guide notes a fixed supported Azure Firewall Controller version for this preview. Expect to pin that version rather than track the latest.
- A firewall deployed this way uses a firewall subnet, a management subnet, one data-plane public IP resource, and a management public IP resource. Plan your address space and public IP quota ahead of time.
Microsoft's Azure Updates definitions say "In preview" means available to all Azure customers for non-production use and testing. Don't read this as a production SLA or a final feature set. The sources I could inspect don't give a general availability date, pricing, or full region list.
Evidence in Azure's API and tooling
The feature shows up in Azure's tooling too:
- Microsoft's Firewall Policies REST reference documents an
afcManagedproperty. It says the property indicates the policy is managed by AFC (Azure Firewall for Containers). When it's set, the policy is read-only for callers that don't supply the AFC-managed sync marker on writes. - The same reference lists a
kubeSelectorGroupsproperty on firewall policies. It doesn't explain what that property does, so I won't guess. - An Azure CLI issue opened in August 2026 asked for
afcManagedto be exposed inaz network firewall policy show,createandupdate. It notes that PowerShell support already existed. It was closed as completed on October 1, 2026.
The read-only behavior matters for operators. If the controller owns a policy, edits made in the portal or by scripts may be rejected. They might also conflict with the controller's reconciliation. This is how I read the API reference, not a documented procedure. The sources give no supported way to supply the sync marker, so don't try to work around it. Treat the Kubernetes resources as the source of truth for any AFC-managed policy.
How this differs from today's container setups
Microsoft already documents manual patterns that send container traffic through Azure Firewall:
- Container Apps: Microsoft's guide uses user-defined routes. The steps include a route table with a 0.0.0.0/0 route to a virtual appliance next hop and application rules for destinations such as mcr.microsoft.com. The guide then verifies the setup with curl from the app's console.
- AKS: Microsoft's architecture guidance says AKS doesn't provide a built-in solution to secure ingress and egress traffic between the cluster and external networks. It describes Azure Firewall with DNAT, network and application rules to fill that gap.
- Infrastructure as code: the same guidance advises deciding which firewall and routing resources your pipeline owns. Terraform can use
ignore_changesso out-of-band rule edits aren't reverted.
That last point is the interesting one. Azure Firewall for Containers appears aimed at the ownership friction in these patterns. Rules would live next to the workloads that need them. Whether it replaces the UDR approach or sits beside it isn't established in the sources I could read. Nothing I found says it supports Container Apps.
What to do now
- Keep it out of production. Test it in a non-production AKS cluster in a listed preview region.
- Check your networking. Look at your Azure CNI mode and the
azure-ip-masq-agent-configsetting before you deploy. - Decide who owns the policy. If you adopt AFC-managed policies, agree that Kubernetes resources are authoritative. That way portal edits and IaC runs don't fight the controller.
- Inventory egress first. AKS needs a long, changing list of outbound destinations. Microsoft recommends the
AzureKubernetesServiceFQDN tag for that. Build and test your allow rules before enforcing anything restrictive. - Hold off on procurement. Pricing, GA timing and the full region list are unconfirmed.
Unanswered questions
The sources don't say what filtering features are in the preview. They don't say whether threat intelligence or IDPS come along. They don't say how ingress and east-west traffic are handled, what the pricing is, or what the migration path from existing firewalls looks like. Microsoft's preview documentation is the place to settle those before you build on this.
References
- (In preview) Public Preview: Azure Firewall for Containers Azure Updates · 2026-11-20T20:05:17Z
- (Network) Expose Azure Firewall for Containers (AFC) managed Firewall Policy on az network firewall policy · Issue #33903 · Azure/azure-cli · GitHub github.com
- Firewall Policies - Get - REST API (Azure Virtual Networks) | Microsoft Learn learn.microsoft.com