Before deploying Defenders, pull the Prisma Cloud NAT gateway IP list from the docs and add it to your egress allow lists, and make sure port 443 outbound to the Console is open. If Defenders deploy but show as disconnected or never check in, check the firewall/NAT rules first, not the Defender config. If egress goes through an authenticating proxy, configure the HTTP proxy in Prisma Cloud per the proxy docs instead of expecting direct egress.

Context: Community thread on live.paloaltonetworks.com: users setting up Prisma Cloud for ACR/AKS hit Defender connectivity failures. The verified answer: Prisma Cloud uses NAT gateway IP addresses, and Defenders must be able to reach the Prisma Cloud Compute Console; if those IPs are not in your allow lists, Defenders silently fail to communicate. In the SaaS Enterprise Edition the Defender websocket connects to Console on port 443 (not configurable).