Organisation switch does not work when invited with alternative email address instead of UPN

%3CLINGO-SUB%20id%3D%22lingo-sub-2456858%22%20slang%3D%22en-US%22%3EOrganisation%20switch%20does%20not%20work%20when%20invited%20with%20alternative%20email%20address%20instead%20of%20UPN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2456858%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20recently%20switched%20our%20e-mail%20address%20from%20%3CA%20href%3D%22mailto%3Afirstname%40domain.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Efirstname%40domain.com%3C%2FA%3E%26nbsp%3Bto%20%3CA%20href%3D%22mailto%3Afirstname.lastname%40domain.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Efirstname.lastname%40domain.com%3C%2FA%3E.%20Where%20firstname.lastname%40%20is%20our%20UPN%20and%20firstname%40%20is%20an%20alternative%20e-mail%20address%20in%20order%20to%20not%20lose%20any%20contact%20to%20previous%20clients.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20external%20companies%20invite%20us%20with%20our%20old%20e-mail%20(alternative%20e-mail)%20we%20are%20now%20unable%20to%20switch%20Teams%20from%20one%20organisation%20to%20another%20and%20vice%20versa.%20A%20spinning%20wheel%20appears%20that%20never%20disappears%20until%20you%20force%20quit%20Teams%20and%20restart.%20Once%20done%2C%20you%20are%20in%20the%20desired%20organisation.%20However%20switching%20back%20to%20your%20home%20organisation%20is%20not%20possible%20because%20a%20login%20window%20appears%20with%20our%20old%20e-mail%20(alternative%20e-mail).%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnly%20possible%20fix%20is%20to%20ask%20the%20client's%20IT%20department%20to%20remove%20the%20user%20from%20the%20AAD%20and%20re-invite%20with%20the%20correct%20e-mail%20address.%20This%20is%20however%20is%20not%20a%20scalable%20solution.%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EIn%20Summary%3C%2FSTRONG%3E%3A%20Getting%20invited%20by%20a%20client%20with%20an%20alternative%20e-mail%20address%20is%20messing%20up%20single-sign-on%20within%20Teams.%20Is%20this%20problem%20known%20in%20the%20product%20Team%3F%20Any%20advice%20here%20how%20to%20resolve%20a%20e-mail%20address%20%2F%20UPN%20change%3F%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2456858%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

We have recently switched our e-mail address from firstname@domain.com to firstname.lastname@domain.com. Where firstname.lastname@ is our UPN and firstname@ is an alternative e-mail address in order to not lose any contact to previous clients. 

 

When external companies invite us with our old e-mail (alternative e-mail) we are now unable to switch Teams from one organisation to another and vice versa. A spinning wheel appears that never disappears until you force quit Teams and restart. Once done, you are in the desired organisation. However switching back to your home organisation is not possible because a login window appears with our old e-mail (alternative e-mail). 

 

Only possible fix is to ask the client's IT department to remove the user from the AAD and re-invite with the correct e-mail address. This is however is not a scalable solution. 


In Summary: Getting invited by a client with an alternative e-mail address is messing up single-sign-on within Teams. Is this problem known in the product Team? Any advice here how to resolve a e-mail address / UPN change? 


1 Reply
I don't know specifically about Teams, but in general, using the Alternative Email Address works, mostly.
There are a few places where it doesn't work, it sounds like you may have found one. I don't recommend using it to my customers, like I said, it works, but only in limited situations.