|
|
|
|
|
by stickfigure
1587 days ago
|
|
I don't understand this complaint. You want separate logins for every service? You can't even argue that there are privacy issues - these are now all part of the same company. Separate logins incur a cost to both the service operator (who has to run multiple secure identity systems, build multiple 2FA systems, manage multiple customer service teams, etc) and the client (who has to remember multiple passwords). Consolidation of identity services is natural. One secure login is better than dozens of insecure ones. Before you yell "password manager" admit that the average person doesn't even know what a password manager is. "Every user changes their workflow" is not a practical solution. |
|
In short: yes.
In long: I want separate logins for different domains. In no universe should Minecraft share a login service with Azure cloud engineering. And I shouldn't have to log in to use offline applications locally. And teams should support different logins for many accounts, like Slack figured out ages ago. By forcing changes to the login pattern for negligible to negative consumer benefit, it's clear Microsoft continues to be broken.
Microsoft and login services are terrible, and uniting them under one login to rule them all doesn't help.