Kubernetes Network Policies decide who can talk to whom inside your cluster. They are the firewall of your containerized environment, defined at the pod level. With Microsoft Entra, you can extend that control by binding identity to network flow, enforcing zero-trust at the infrastructure layer.
A Network Policy in Kubernetes uses labels and selectors to define ingress and egress rules. By default, if no policy exists, all traffic is allowed. When a policy is applied, anything not explicitly permitted is blocked. Microsoft Entra brings identity-aware access to this process. It lets you link traffic permissions to the authenticated identity of the workload or user, not just IPs or namespaces.
Integrating Kubernetes Network Policies with Microsoft Entra starts with configuring Azure Kubernetes Service (AKS) to use Azure CNI networking. This ensures each pod gets its own IP in the virtual network. From there, Entra can enforce Conditional Access rules and verify identities before packets are allowed.