Earlier quoted context omitted.
No. It’s over managed. If I was handed teams I could vastly improve it on my own over a 6 month period. However the most significant change would be replacing Azure AD/B2C for auth with literally any other auth solution. I’d need a year to overhaul AD/B2C and would probably want to hire a team of two more devs so we could get it right for all use cases. Even then it could be so broken that it’s almost impossible to f…
I must be misunderstanding. Are you saying the auth mechanism is largely responsible for all the problems with Teams? Like if they added, I dunno, OAuth Login-with-Facebook, then magically all the crashes, disconnects, UI latency, bloated features, broken input text box and other poor UX design issues would somehow resolve themselves? Login is the one thing that I literally did once, on first app launch, and never th…
I’m saying there’s plenty wrong with it, but the thing that would take the LONGEST to fix is Azure B2C, because that’s a whole beast in itself and is tightly coupled with all of the other MS products from Windows to Minecraft, to many many thousands of Web Apps that were unfortunate enough to have used it.
As a user who has multiple Microsoft accounts (due to years of contracting), I can’t log in to teams.
Edit: Teams has lots of problems, fixing AD/B2C is by far the hardest because it is a legacy pile of garbage used in thousands of production apps