Gabe_Bratton
Hey Gabe,
I imagine this message is going to come off a bit petulant, but, frankly, I'm angry.
The actions above in which I had to go into the account website and remove my work account has broken Teams. I can't login. When I try, it says my organization has not been setup for password resets. The problem is, I setup the organization. So, I have to use a different address entirely to login to and use Teams. And, with the new restriction, I can't go back to the account to add my work email address that I previously had in the account. So, effectively, the Microsoft account for my work email is broken. I can't login. I can't reset the password. I can't erase the account and start over because that requires me login with my work email address. So, this frozen Microsoft account is on servers somewhere that will not allow me to access it.
What's more, I have another client with the same problem.
For both of us, I've had to setup individual, workaround accounts just to use one damned Microsoft application. And I can't tell you how many work around accounts I have for problems like this among all my clients. (I'm an MSP.) A dozen? Two dozen?
In my opinion, this is all fruit of the poisoned tree. Microsoft wants me to use Microsoft 365 for everything: apps, email, Active Directory, server hosting, everything. Since then, they've provided fragile workaround as teasers, as peeks inside the kingdom, all hoping that I'll give up my wicked ways to go with Microsoft for everything. If I do that, everything works fine.
Well, I can't do that for all of my clients. I wouldn't mind it, but I can't.
Regards,
Mike