When a user is logged into Webmail, then goes to Team Workspaces and tries to enter a Team Workspace that's been set up (or do anything inside Team Spaces for that matter), they are presented with a perpetual spinning donut and the "Logging you in" message.  It will just hang at that screen.  But if the user hits the browser Refresh button, or closes the tab and clicks into Team Spaces again, it works.

This can be duplicated on Chrome, Firefox, and Edge.

We watched resource utilization from the server console when this happens, and there is no indication resources are being consumed-- i.e., no increased CPU, no increased disk activity, etc.  Constant pings show 15 ms latency with no packet loss.

Any ideas, or anyone seeing similar?  We were pitching Team Spaces as a selling feature to a customer today, and the demo didn't go well because of it.