Allan

My feedback

  1. 4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Allan shared this idea  · 
  2. 12 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Azure Active Directory » Admin Portal  ·  Flag idea as inappropriate…  ·  Admin →
    Allan supported this idea  · 
  3. 17 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Allan commented  · 

    Absolutely agree with this one - honestly, any online service which doesn't allow its users to reset their passwords by default and for free is not very modern, to me. Imagine if you had to pay facebook to be able to reset your password...

    Allan supported this idea  · 
  4. 165 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Allan commented  · 

    Custom branding would be great to have too.

    Allan supported this idea  · 
  5. 2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Azure Media Services » Azure Media Player  ·  Flag idea as inappropriate…  ·  Admin →
    Allan shared this idea  · 
  6. 1,971 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  72 comments  ·  Azure Backup  ·  Flag idea as inappropriate…  ·  Admin →
    Allan supported this idea  · 
  7. 119 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    With the release of Azure Functions 2.0, the previously posted template no longer works.

    However, we recognize the need for this request, and are actively scoping and prioritizing the work needed to make it happen.

    I am very interested in speaking with anyone who needs this feature to learn more about your scenarios, particularly any information around cost issues. If you would like to help me scope this feature, please reach out: mogrobin@microsoft.com.

    Morgan Grobin
    4/26/2019

    Allan supported this idea  · 
    An error occurred while saving the comment
    Allan commented  · 

    AD FS and Azure AD based authentication, please

  8. 1,327 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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…

    An error occurred while saving the comment
    Allan commented  · 

    And how about, in Azure AD, getting a report of how many (and which) users have a Microsoft Account that is using the same alias as their Organizational Account?

    OK, I'm done for now, thank you (and sorry for ranting!)

    An error occurred while saving the comment
    Allan commented  · 

    Okay, so I just went to "rename" my account... and what it wants me to do is to input an actual mail address as an alias. This means that I have to have a working mail-address that I can use - you know, one that I would associate with work... but it cannot be my work-address :o

    This is where I should be able to pair it with my organizational account - and Microsoft should just take care of it behind the scenes. I mean there must be some way that you could, let's call it "federate", identities between two different login-providers?

    The other option is to create a new @outlook.com alias, which makes no sense in this context.

    As I am a sysadmin, I can just go and add an extra mail-alias to my Exchange account and move on, but not everyone is in that position. MS is even saying that Azure AD can "integrate" with Microsoft Accounts, but this is the simplest possible form, where you have to enter the access code of the Microsoft account into Azure AD and then it tries to authenticate you with that up against your MA-based services, but only if you were coming from the Apps-list in Office 365...

    An error occurred while saving the comment
    Allan commented  · 

    It is called SINGLE sign on :) - not single-username-but-multiple-accounts-and-multiple-redirects-and-decisions-regarding-which-account-to-log-on-with...

    What is called "Organizational Accounts" today, should replace "Microsoft Accounts" completely (and take its name instead). This could be the how it is implemented:

    1. Anyone with a Microsoft Account (MA) should be given the opportunity to upgrade it to a Microsoft Account 2.0 (ie. Organizational Account).

    2. If you have an existing Organizational Account (OA) you should be given he option of merging them. If the OA had the same name, there would be no other way. If not, you would have to enter in the login details of the OA.

    3. Now you can log in to all pre-existing and future services with Microsoft Account 2.0. For instance, if you had an Office 365 Personal subscription and were logging on with a MA, now you will be logging on with an OA - and you shouldn't really have to feel the difference...

    4. Support for Microsoft Account 1.0 is phased out of all clients again... No longer will we have to decide what type of account we're trying to log on with.

    This, of course, requires that all services that hitherto have supported only MA are transited over so that they will support OA - which is why the actual merge of the two types of accounts can only happen after such a transitioni.

    Until that happens, I will go and rename my Microsoft Account at work, so that it no longer bothers me (as much).

    By the way, real life story: we have users that have access to Office 365 as students and they try to use OneNote/OneDrive/etc. for Business. Unfortunately something happens and then they end up creating new Microsoft Accounts, using the same login-name as we're providing them with. Now they get it working, thinking that they are using the service that we provide them with, when in fact, they've just circumvented the whole offering and simultaneously set themselvs up for problems when they try to log in to Microsoft's services... Very counterproductive.

    Allan supported this idea  · 

Feedback and Knowledge Base