Merge office365 and live accounts that use the same email address
I use both Azure/msdn and office 365
I already had an msdn account firstname.lastname@example.org ( Windows Live account) and our company recently migrated to Office 365 which resulted in a email@example.com Office365 account.
Wich is causing a lot of grieve when switching between asure web portal / msdn web portal / office 365 web portal
Even when I have no portals open, I cant switch accounts. I need to explicity open the portal that I last logged in to. Log out, and then I can switch accounts.
And having both office 365 portal and Azure portal open at the same time is impossible.
Thanks for the questions and suggestions. And apologies for not sharing any update on this thread for so long. We’ve been working on this problem and have announced changes on our official team blog (see here: https://cloudblogs.microsoft.com/enterprisemobility/2016/09/15/cleaning-up-the-azure-ad-and-microsoft-account-overlap/).
First, we are acutely aware of the UX pain this is causing and we are sorry for this. We are trying to undo a decade and a half of systems divergence. There are literally hundreds of different engineering teams across Microsoft involved in this effort. So this is taking time.
Second, we can’t easily “merge” two accounts, or allow IT to “take over” personal Microsoft accounts. There are two main hurdles: (1) The terms of service are fundamentally different for the two account types and (2) they are based on different technologies with different stacks (different identifiers, SDKs, token formats, etc.). We’re working to converge the two stacks but again this takes time. There are details of this in the blog post linked above.
Third, in the past year we’ve worked with 70+ teams across Microsoft that operate business services but only supported MSA for historical reason. Our goal is for all of these apps to support Azure AD (work accounts) as well. As of Nov 2017, we’re about half way there. Dev Center and MSDN subscriptions (now called Visual Studio subscriptions) are example of apps that now support Azure AD. Microsoft Payment Central and Invoicing are a few weeks away. Volume Licensing and many others are in progress and a couple months away.
The best recommendations we can provide right now are:
1) Use your work account (in Azure AD) to access any work application that supports it.
2) If you had created a personal Microsoft account to access Microsoft business apps, and no longer need it, close the account. Or rename it (which means chancing the user id) to avoid confusion.
Please follow our team blog for future updates on this problem.
OK this doesn't seem as important as some of these but I have a 365 account with the same exact username (email) and password as a completely separate Live account. How is this possible? these must be two separate systems?
David Ruiz commented
This has been a longstanding challenge for us as well. Signed up for BizSpark and Azure using my Microsoft Account, but running our business using a Office 365 Organization account of the same name (email address). Making matters worse, we're building business apps that leverage Azure AD SSO but can't even test it without stumbling over the account naming conflict that emanates from defining O365 users within manage.windowsazure.com and ultimately conflicts with the registered user apps that appear within myapps.microsoft.com.
J Aaron anderson commented
yes this is terrible, dumbfounded this was not thought out before release. Please keep me posted as well on how to thread together O365 4 Business OrgAccounts with pre-established (more personally driven) MSDN WIN:LIVE Accounts both with the same primary email address... shouldnt that distinguishing match SSO/Trust both uniques account GUIDs in multiple systems upon re-authentication ? anyhow please keep us all administrator up on this as this is an almost certain show stopper in many cases
Ariel Gordon (MSFT) commented
I just posted a detailed reply to the duplicate post titled "Merge office365 and live accounts that use the same email address" (link below). Please use that post for further discussion.
Ariel Gordon (MSFT) commented
Thanks for the question and feedback.
Our team owns the Microsoft account and Azure AD sign-in/sign-up experiences. We know that some experiences are confusing for some of you and we’re working hard to simplify them.
1) We know a number of users have multiple accounts with Microsoft, some they created themselves and others they got from their work or school. Today, using multiple accounts in Office 365, Azure.com or VisualStudio.com requires you sign out of one account and sign in to another. To address this we’re building the ability to be signed in with more than one account at the same time, in the same browser. This should start showing up on Microsoft web properties later this year.
2) There’s a small number of Microsoft business services that only support “Live ID” accounts, and not organizational accounts that are used for other business services like Office 365. Examples include MSDN and Volume Licensing. We’re working with these teams to add support for organizational accounts. This will allow everyone who already has an account they use with Office 365 to use the same account to sign in to these services.
3) Some users have two Microsoft-powered accounts with the same sign in string: one they got from their organization (when the organization uses Azure AD account) and one they created themselves (for example to access MSDN or VL). For these users, the sign-in experience to Office and Azure can be confusing. If you’re in this situation, the simplest solution is to rename the account you created yourself. You can use another consumer email address or get a new @outlook.com address. And later his year, you’ll also be able to use your phone number as a sign in string. Longer term, we’re considering different options to remove this overlap.
Keep the great feedback coming and please let us know if you finds other sources of account confusion. We’ll continue to monitor this thread as we refine our plans.
Mdg Rkb commented
This is a mess, and the fact that it hasn't been properly addressed in over a YEAR is VERY disappointing.
Just another thought: If you want to be a "cloud first, mobile first" company you should really figure out processes like this. And I still wonder what will happen to my paid for Windows Phone Apps when I connect it to the migrated Exchange Online mail account, because it keep telling me this will change my identity (it is connected to a Live Account as of now).
This will probably affect every company that moves production services to O365 and/or Azure. We are a Gold Partner, too, and want to make use of our IURs, but this is a pretty big issue because we have mostly developers that will use MSDN, Azure and O365.
Mark Burland commented
Our school was using Live@EDU. When MS disbanded that and folded schools into Office365 for Education they automatically created new Live accounts from the old Live@EDU accounts. What this meant for, for example, is I now have an Office365 account under the username firstname.lastname@example.org and a Live account under the username email@example.com but these are two entirely separate entities. Guess which account I have to use for our eAgreement and VLSC? You guessed it, not my organisational (Office365) account, but the ethereal Live account. Bonkers. Absolutely bonkers. When I queried this with Microsoft they had no clue what I was on about. Drives me insane.
Still no solution to this? We have a scattering of Live ID's and we are looking to fully migrate to O365, but we are sticking with the "onmicrosoft.com" domain for all office services until this gets resolved. Thanks!
same problem here, my company partner account is setup with a microsoft live account but my office 365 and azure are linked to a 2nd account of the same name.
If i now try and activate azure as a partner platform i get a 2nd azure instance created linked to my MS live account, but cannot communicate with the 365 domain.
Mike Sanlon commented
This is a major pain point for us. What's most galling that it effects your best customers. The more Microsoft services you sign up for (with your corporate email as your user id) - the worse it gets.
I too am having this issue, is there any resolution yet? There is no link to where this got moved too as mentioned by the ADMIN post.
I am trying to setup Azure AD and office365 to sync password with windows live account, so remote users whose PC are not on domain can login with single-sign-on.
Is there any way to do this?
Andrew Scothern commented
I have just discovered this issue also. It is a major pain!
We are just moving to Office 365 and also already use both Azure and MSDN. Our devs are going to be spitting tacks at having to constantly log out and back in of different accounts.
Richard Weston commented
Thanks for starting this. Totally agree. Use Azure, 365, Windows sign-in etc and having to use 2 separate accounts is frustrating. Especially when I ended up with both being the same email address :(
Same problem here. Can we get some active support from Microsoft ?
Uri Roitman commented
Marco, thank you for rising this tread.
Same problem here, we are a gold partner with MSDN Azure and Office 365.
Joining to this tread to see if any resolution will be found to this problem.
Separate them. Had the same problem. Have your email Admin give you an extra email alias (i.e. First.last@...) Go to live.com, sign in with current email, add the new email alias, then remove the original.
Jesper Jønsson commented
Agreed. Definitely and issue that needs to be resolved. We have the same situation.