Any updates from support on this issue. Having similar issue, even after creating explicit tunnel rules for the Teams app.
didn't hear anything yet..
Did you ever find a resolution to this? We are experiencing the same thing.
1 person found this helpful
HerrMaximilianLeupold — You’ll need to give some more details so we can try to figure out what’s going on there. I was looking at Microsoft Teams call flows - Microsoft Teams | Microsoft Docs and Office 365 URLs and IP address ranges | Microsoft Docs .
What version of the UAG and Tunnel apps are you using? What version of iOS? Can you post some “sanitized” details about what your Device Traffic Rules look like?
We are in the process of trying to get Teams working through the per-app VPN tunnel also. We do not using the calling features of Teams just yet but I am curious of the tunnel server rules you created to get Teams to even begin to work with the VPN app. I have put the domains in per the Microsoft link that shows the URLs and IP addresses needed but the app is still not working. We only allow out public IPs to access the O365 apps so making the Teams app work through the VPN tunnel is a requirement for us. If you can share with me what you craeted for server access rules to make it work would be greatly appreciated.
I’m in a similar situation and hoping for some insight on getting Teams to work through the UAG.
We also have all of our Microsoft Office Suite apps configured for per-app VPN over WS1 Tunnel, including Microsoft Teams. The only reason we did this was to satisfy Azure AD Conditional Access rules. This required that we Tunnel traffic going to login.microsoftonline.com; everything else bypasses the Tunnel. In this configuration, functionality with the Teams app mostly works. What doesn't work is trying to join a meeting. When you click on Join, it will try to connect but you'll get a "Looks like you're offline" window and fails to join. Trying to use "Calls" fails as well.
I opened tickets with Microsoft, VMware, and Apple. Both Microsoft and VMware said this was a known issue and was due to a problem in iOS. Apple stated that a fix is coming in the near future, but at the same time seemed to imply by the logs I provided them that the problem may not be the same.
Is there an official VMWare WS1 known issues page with this information disclosed I wonder?
It would be very helpful to relieve pressure from management if there was a known issues page somewhere since it's something out of our control and we're waiting on Apple to fix.
This is good to know nevertheless and will save from hair pulling.
That is correct, it’s known issue with iOS, which we already report and share feedback from customers.
We already report the Issue to Apple and Microsoft, also sharing the reporting cases by our customers.
I encourage anybody on this thread impacted by this issue to open a case direct with Apple, that can help on the priorization process.
It‘s a good idea to share a kB on this, I will pass this feedback internally.
Well, I will say that when I opened the ticket with VMware regarding this, the engineer stated that this was originally reported back in 2017. I'm not sure how that is possible, considering I don't even believe the Teams app was available then. Even if it was, here we are 3 years later without a resolution. So I'm not sure if the issue he was referring to is the same problem that we're dealing with today, or Apple definitely hasn't put a very high priority on fixing it.
Most likely referred to 2017 because this issue was originally identified with Skype and as today affects Microsoft Teams.