MicrosoftAlex_Simons wrote I'm glad to hear you like the Azure portal experience. We worked very hard on it š That experience is the best of class and we are working with teams across the company to get them to align to that model. For some services it's pretty straight forward, for others, it's a lot more work, but we are definitely making progress. Hopefully you'll see a lot of improvements in the next 6 months or so.
While you are waiting for those improvements, I would highly recommend using the profiles feature in the new Edge (the version based on Chrome). It has really nice cookie isolation, so it makes it super easy to maintain different identity contexts. I use it all the time to keep my many Azure AD and MSA accounts all working independently from each other.
I have tried this workaround and it helps to some extent - but what it doesn't help with is if go to google something that brings up an article on a microsoft site sometimes it will randomly sign me in as my personal microsoft account on the way through to the post/article and then when I go to office.com in another tab i find I have suddenly been signed out of my work account and am now signed in as my personal microsoft account.
Why can't they not use separate cookies for each authentication type and then at least we would not get this random switching in and out accounts ? some older microsoft sites still only seem to use personal accounts and this is when it gets in a mess.
You have been promising this since 2016 https://techcommunity.microsoft.com/t5/azure-active-directory-identity/cleaning-up-the-azuread-and-microsoft-account-overlap/ba-p/245105
Even simple modern microsoft web sites like todo can't handle it https://support.microsoft.com/en-gb/office/using-multiple-accounts-with-microsoft-to-do-49d89f46-781a-497b-ac3c-f9ab45b0937f - when you read that article it gives that impression that it handles multiple accounts until you read the small print at the end and find out that actually it is only the windows and android apps that do. Why bother to develop that for the app and not for the web browser which is probably more common used these days ?
Please could you give us a clearer timescale for delivering this from the teams? as sorry I don't believe this when you have been promising it since 2016!
