Anonymous

My feedback

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

    We’ll send you updates on this idea

    10 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    Me too! This would make certain things so much easier. We should be able to add Resource ID as a column in all resources (or really any other area where a list of resources is generated)

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

    We’ll send you updates on this idea

    6 comments  ·  Azure portal » Resource management  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Anonymous commented  · 

    OK, never mind my previous comment. I see my expectation that a resource group will be created as part of the move operation is incorrect.

    An error occurred while saving the comment
    Anonymous commented  · 

    Any progress here? The Microsoft documented method using the REST API does not work for many/most move scenarios! It requires providing a destination resource group. But when moving VMs and various other resources, the move operation is AT THE RESOURCE GROUP (yes, I am yelling since Microsoft totally missed this). How are we supposed to give the API a target resource group, when the resource group does not exist until the move operation is executed???!!!

Feedback and Knowledge Base