Azure NGFW VNet Deployment - No Outbound Internet Access

[GraysonDenny]

Deployed a NGFW deployment for a customer. Using the VNet deployment, not VWAN. Everything is green (DG and Template) and healthy from the Panorama aspect. 

We have created a UDR in a test application VNET, that points only a default route to the NGFW firewalls.

East/West connectivity works great. We are also able to access everything across the expressroute as well.

However, when we trying to ping or curl a website from the test application linux VM from above, we are not able too. The really weird thing is that we do not see ANY logs in Panorama for this connection. We overwrote the default rules, so we could log all traffic, allowed or denied. The Source NAT is configured in the Azure portal.

We deployed a second VNet, same issue. There are no NSGs applied to the VM NICS. UDR is good, confirmed via Network Watcher connection testing. I am at a complete loss on this.

Also, when opening a ticket on this, do we open it with Microsoft or Palo first (or just do both).

Edit: I confirmed outbound works directly from the VM when I change the UDR to Internet just to validate nothing is wrong with the VM.

[JayGolf]

Hi @GraysonDenny ,

Can you access the local firewall and see if there are any logs? Have you assigned Azure Public IP Adresses on network interface of Palo-vm? 

[GraysonDenny]

You can't access the firewalls locally, these are the SaaS firewalls, where "I" don't have access to them.

Public IP's are on them.

[skorbee · Accepted solution]

Had an similair or same issue.

Traffic north sound started working after i placed an Networks security group on the NGFW SAAS Private subnet.

The NSG did need an inbound rule from virtualnetwork to Internet -> allow gave it an any any....

[GraysonDenny]

This was indeed my issue. According to the Palo documentation, when the SaaS firewalls get deployed in the Azure Portal, the template is supposed to deploy the NSGs and attach them to the private subnet. However, that is not the case, Azure does not deploy the required NSGs like documentation suggests. So would be nice if someone from Palo could add that to the deployment guide, because no where does it mention that, that I can find.