Comment by close04
9 hours ago
> IAM can stay MS
That's leaving the most critical component still with a US company. Doesn't fly if the goal is what the Danish agency is trying to achieve.
> It actually depends how you use it.
Obviously but the larger the company, the more ways to use it, and one of those ways will be a nightmare to tackle. You want one solution, not a patchwork. So the one that does everything gets picked. MS throws everything and the kitchen sink in their ecosystem to fit every need even if sometimes at mediocre or crappy quality.
> For Teams, as long as you use it for conferencing and chat (no file sharing or editing), you can replace it with Slack
Taken in isolation you're right. But in a world of network effects every company, supplier, service provider you work with might use Teams and you can federate. Switch to Slack alone and you make your life harder.
I mentioned this in another comment, if protocols and formats were mandated to be open or interoperable (in practice) to allow usage in the public sector, replacing MS would be a notch or 2 simpler.
> That's leaving the most critical component still with a US company. Doesn't fly if the goal is what the Danish agency is trying to achieve.
Yes, because it is very hard to replace. I said that you could move to Okta or something similar (in this or in another comment), but this requires you have pretty modern apps that can integrate with SAML/OAuth/OIDC.
And, even staying with MS for a few more years while you migrate IAM to something else is not as bad as having the full Office stack. You can't just yank out everything overnight - I mean you could, but you have to spend a ton of money to have a 1:1 solution from the get-go.
> You can't just yank out everything overnight
Yeah, it's that transition period - "it's going to get worse before it gets any better" - that hurts the most and that everyone tries to avoid.