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

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-api/ https://webkit.org/blog/11545/updates-to-the-storage-access-...