Anonymous

My feedback

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

    We’ll send you updates on this idea

    0 comments  ·  Cost Management » Cost analysis  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous shared this idea  · 
  2. 235 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    22 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    Anonymous supported this idea  · 
  3. 1,112 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    74 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →

    Hey Folks,

    We have made some great progress on this idea and most of our services today do support move resources across groups.

    We are still working towards 100% support and while we do that it would be great if you can help us prioritize the missing services.

    Please file individual asks on each service category present in uservoice and vote for it.

    Thanks,
    Azure Portal Team

    Anonymous commented  · 

    It is enabled on some services but web apps isn't enabled. Where it is implemented sometimes there is a move function and sometimes an edit resource group icon in the Essentials area of the service blade.

    I have moved quite a few things today and they all worked (although storage areas take a long time). I really need to move web apps to segregate and restrict access between ops and dev.

    Anonymous supported this idea  · 
  4. 1,231 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…

    Anonymous supported this idea  · 

Feedback and Knowledge Base