Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Richard Griffiths

My feedback

  1. 1,348 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea


    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…

    An error occurred while saving the comment
    Richard Griffiths commented  · 

    Right now I have this problem: my work email somehow has personal and a work version.

    We never intended to do this at all. Many resources are setup on the personal account for reasons I do not understand.

    I seriously need to lose the personal one with it's own password and have everything on the work one.

    1) Why is these even possible?
    2) How on earth can I kill this very useless feature and keep the stuff we've paid for on the work account only?

    It's causing a LOT of time cost. Right now I'm writing because I cannot access Azure thanks to this very nasty defect.

    Please give us a mechanism that allows accounts with the same email address to be merged - assuming the user has both passwords/credentials to hand.

    This would definitely fix my problem.

    Thank you.

    An error occurred while saving the comment
    Richard Griffiths commented  · 

    Anyway to forbid the creation of a personal account if a work account of the same email already exists in your infrastructure?

    And if a personal account exists, creation of a work one triggers an optional process of migration from the personal one. If the user says No to this, don't create the new work one?

    I'm going to try deleting the personal one and force any resources that use it to accept the work one - as they're both the same email - such a bad idea that was :).

    An error occurred while saving the comment
    Richard Griffiths commented  · 

    I never intended to have two accounts: please, oh for the love of all that's holy, please just offer me the option to merge the **** things. For over a year this has provided me with endless headaches, swearfests and just general wasted time - all for no good useful reasons.

    If it's the same email, then it's gotta be logical that the user probably would at least want the option to merge.

    I seriously do.

    Richard Griffiths supported this idea  · 

Feedback and Knowledge Base