For personal use, I'd mostly agree, but without a common identity over those SaaS services the user experience isn't as ideal as it could be. As a simple exampl

For personal use, I'd mostly agree, but without a common identity over those SaaS services the user experience isn't as ideal as it could be. As a simple example, consider how you would share a file between two different identity systems - you can't - you effectively have to use the security by obscurity trick of "whoever has this link can {read|write} this file". In enterprise use cases where the company pays for the service, you really want to integrate these SaaS services into a common shell and this is the role that Teams plays. You get single sign-on with enterprise credentials, a way to share data with those 3rd party services, and a way for multiple users in your organization to collaborate together with those 3rd party services. This is the place where Microsoft is currently in a leadership position. Teams is increasingly viewed as being the "cloud OS shell" for enterprise users. Ben has written about this for quite some time - see this earlier piece from 2020: https://stratechery.com/2020/the-slack-social-network/ https://stratechery.com/2020/the-slack-social-network/