Yeah, if you work in consulting right now, this isn't surprising. You've probably developed work for a client who needed to integrate third-party sign in. This is primarily an issue prior to macOS 11.5(?) as updates to the Storage Access API[1] were heavily limited. This isn't some quirky Microsoft thing, it's a limitation with heavy handed third-party cookie support from Apple.

This will continue to be an issue for a little while as developers start to integrate with the Storage Access APIs as intended, but it will take time.

As a result, you should fully expect vendors to be suggesting these troubleshooting steps.

Google Chrome, Microsoft Edge, and Firefox still support third-party cookies out-of-the-box today, but Safari does not.

[1]: https://webkit.org/blog/11545/updates-to-the-storage-access-...

I never thought I'd ever be defending Microsoft, but 2nd screenshot 1. tells you why 2. tells you that once Teams fully supports Safari, this workaround will not be necessary.

As a linux user, stuck in microsoft's 99% world, using their apps are painful. Use of standard browser plugins like noscript and ublock origin, they constantly complain about insecure sites using office365, forcing me to whitelist and/or bypass xss security notices constantly otherwise. Same reason IE was the best malware delivery engine for 25 years, now their chrome-based edge, they _do_not_ get browser hygiene, security, or why people would want to use any of it, still.

that's why Safari is the world fastest and most power efficient browser in the market

because they don't comply to bloat driven companies like Google/Microsoft and their friends