Cheers @elevator4 , It is the exact same senario, it is clear that in best, the split tunnelling IS working because the performance gains have been phenominal (not sure I've ever typed that word...) But what made me query this, was due to the fact that we had an authentication issue with our Fortigateway / Web filter that was no automatically picking up authenticated users from AD/FSSO so everyone was being asked to re-authenticate.. This seemed to be having an adverse effect on our users being able to use teams, we'd either get a message saying that we weren't connected, or, the pressence side of things wasn't working (available, busy etc) or we couldn't send chat. (Video and audio seemed to not be affected) I had also played with persisten routes on the routing table to ensure that the traffic was destined to the correct gateway, but launching teams seemed to overwrite some of the addresses that would fall into the 52.112.0.0/14 network and send them out over the VPN... I agree, hearing from others would be great. Thanks for your message.
... View more