- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
04-09-2025 11:52 AM
Hi,
I have a Azure Palo Alto VM setup with GlobalProtect access.
I can successfully connect via GlobalProtect and connect to all resources on sites connected via IPSec Tunnels. However, I am not able to access anything on the local segment in Azure.
Can someone please provide some thoughts as to why this could be?
Thanks!
04-10-2025 03:25 AM
did you create a user-defined route (UDR) in a route table and associate it with the internal subnet?
You need to redirect the 'default route' towards the firewall's private IP address to establish connectivity (or use hide NAT for all GP ip-pool towards your vnet's subnet)
04-10-2025 05:26 AM
Thanks for the reply. I updated the drawing with some more detail.
I do have a Route Table poiting traffic to the Inside interface of the Firewall. My servers can get out the Internet and I can connect to all resources attached to the IPSec Tunnels to and from my servers from behind my Azure Palo. The only issue is when I connect via GlobalProtect, I am unable to reach my servers on my 10.3.1.0/24 subnet. I even matched my GlobalProtect Pool to 10.3.1.0/24 with the same result.
I appreciate any feedback.
Thanks!
04-10-2025 08:40 AM
Here are my static routes on the PA. I don't have a next hop to point my return traffic to other than the INSIDE interface on the PA. Any chance that plays a role in the issue?
04-10-2025 12:04 PM
Hello,
I typically make the VPN users a different zone to help limit access etc. I would check the unified logs to see where the traffic is getting blocked. Also put your GP users on a different subnet, could make for weird routing issues.
Regards,
04-10-2025 05:11 PM
How will the traffic return if I use a different subnet? I do not have any Layer 3 functionality.
Thanks!
04-11-2025 07:39 AM
Hello,
The Palo Alto has this. Not sure what you mean by you dont have it?
Regards,
04-11-2025 03:21 PM
I should have been clearer. Typically, on-prem there is a next-hop Layer 3 device where I would send traffic to for my inside network from the PA when I have more than 1 Network (VLAN). Since I only have the Virtual PA and the Azure defined networks, I was trying to figure out how I could accomplish this. I ended up creating a 3rd Interface on the PA with the new subnet, put all the relevant routing on the PA and Azure in place and it is all working now. I suspect you were correct. Having my GlobalProtect pool the same as my Inside LAN was probably causing routing issues.
Is there perhaps another way I could have resolved this?
Thanks for the help!
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!