George

My feedback

  1. 10 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Active Directory » Domain Join  ·  Flag idea as inappropriate…  ·  Admin →
    George shared this idea  · 
  2. 1,151 votes
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Folks,

    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…

    George commented  · 

    2. Microsoft Partner Program as well... which is very telling that it does not support Organizational/Work accounts. Pretty large "oversight" as it IS business by definition and to support O365 instead of ignore it should have been a priority, especially if you expect your partner community to "prioritize it.

    3. The overlap isn't "confusing" for us as described, what it does is NOT work. There is a very big difference between those two things. We don't need more "clarity" so that we understand what is happening and by extension resolve our confusion. Believe me we are VERY clear on exactly what is happening, what we need are systems designed so that they actually work properly that needs to be your focus.

    You use the term "Live ID", however, this is incorrect, and as the owners of these properties you should know that it was officially re-branded to "Microsoft Account" and that this is the current name for what used to be called "Windows Live ID".

    Skype has a Skype ID and a Microsoft Account logon and BOTH still survive, how, those id's coexist is an issue, they should be "mirrored", but they aren't, in essence one user now has two id's.

    Microsoft Account and Organizational account can share the same email address this is creating problems not confusion for us the user but confusion for your systems because when you see that email address and it belongs to both Microsoft Accounts and Organizational accounts your systems handle that distinction DIFFERENTLY under different conditions, SSO, Remember Logged, in etc have serious trouble dealing with this. In addition, for example, in Azure Tenant, Remote Apps, if you try to add to a Microsoft Account tenant the O365 Domain it will fail... this is directly related to the same "email address". https://msdn.microsoft.com/en-us/3d6c4fd1-c981-4c57-9402-59fe31b11883

    Just one example.

    We would be happy to transition completely to Organizational Account and "kill" the Microsoft Account but the Microsoft Account is in existence for a much longer period than the Organizational Account and that will need to be dealt with.

    You will need to provide us the consumer a "list" of what properties are being actively used with the Microsoft Account and allow us to transition those properties to the Organizational Account and how that is done will be an issue.

    For example, we use a Microsoft Account for OneDrive Consumer that email address is shared with an Organizational Account that included Office365. We actively use the Microsoft Account for OneDrive and Skype (consumer) and we need this to remain functioning. We have no problem using the Organizational Account for those services but need a way to "properly" transition to them.

    Hope this helps with understanding what the "confusion" is.

    George supported this idea  · 
  3. 1 vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Virtual Machines » Windows  ·  Flag idea as inappropriate…  ·  Admin →
    George shared this idea  · 
  4. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: oidc
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  (General Feedback)  ·  Flag idea as inappropriate…  ·  Admin →
    George shared this idea  · 

Feedback and Knowledge Base