04-04-2025 07:31 AM
Microsoft Teams e911 calling does not display the location when connected to Global Protect.
We have split tunneled the Microsoft Teams subnets (i.e. 52.112.0.0/14, 52.122.0.0/15, 52.238.119.141/32, 52.244.160.207/32) as per the Microsoft 365 URLs and IP address ranges (https://learn.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worl...) for the users when in office. The Microsoft Teams e911 calling does not display the location, but when we split tunnel all traffic (i.e. 0.0.0.0/0) the location is displayed. Has anyone been able to identify which domain or IP address or subnets is responsible for the location?
04-07-2025 03:01 PM
Do you have a GlobalProtect subscription? The easiest way to accomplish this is just excluding the actual process instead of trying to utilize IPs.
11-27-2025 02:58 AM
We are having same issue. We already implemented split tunnel excluding all "optimize" MS public IPs and all Teams app paths (using wildcard). Teams is still not showing the correct emergency location. Checking Teams logs we are seeing that it uses the GP network adapter, to assign the location, instead of using the LAN adapter.
How should we setup the split tunnel to avoid this?
11-27-2025 07:12 AM
We have resolved the issue by adding route 24.24.24.24/32 in the excluded routes of GlobalProtect split tunnel settings.
We received this suggestion by PA support, and it worked! We really can't understand why (what is 24.24.24.24/32?????) but it worked.
I hope it will be useful for someone else.
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!
