Split tunneling issue for office 365 applications

Reply
Highlighted
L3 Networker

Split tunneling issue for office 365 applications

Recently enabled split tunneling for our Global protect VPN, and have added some domains into the split tunnel.
 
For some users domain split tunneling doesn't work.
 
The domains configured to be included in the split tunnel are as follows
 
*autologon.microsoftazuread-sso.com
*enterpriseregistration.windows.net
*.microsoftonline.com
 
We are trying to add these domains to include domain list- however, when Global protect is connected, effected users are unable to connect to these services at all.
 
Without the split tunnel the functionality was immediately restored for affected users
 
Now we came across this document which says that Microsoft recommends to use IP addresses instead of FQDN  for office 365 applications when configuring split tunneling
 
 
However this document explain excluding routes scenario.
 
So my question is will this method work for include routes too?
 
Highlighted
L7 Applicator

what version of GP are you using, there was a bug in earlier versions of 4 with domain split tunnel.

we use IP's instead of domains, works well for both teams and outlook..

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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 Live Community as a whole!

The Live Community thanks you for your participation!