Azure Resource Manager

How can we improve the Azure Resource Manager?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Tag inheritance

    The ability for objects contained in a resource group to inherit tags from the resource group. It might be a good idea to allow the user to specify which tags on the resource group should propagate/inherit.

    493 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    35 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Provide option to execute ARM template in preview mode ("This is what I plan to do")

    I would love to be able to run an ARM template with an optional PowerShell parameter that tells the deployment not to make any changes, but instead to report back with the changes it intends to make.

    129 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Being able to recognise configuration drifts in Azure Resources via ARM Templates

    At the moment, we can redeploy an ARM Template to fix non-desired configuration drifts. However, it would be ideal to be able to validate if a Resource Group presents drifts from given Template/Parameters. In some cases, we want to be informed when ad-hoc changes have been applied to any azure resources in a resource group which have not been vetted, tested, or recorded in source control, and act depending on the findings. Continuous deployment of an ARM Template to avoid configuration drifts is not always the best solution, as this might impact uptime of some resources and some intentional changes…

    96 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for taking the time to vote on this request. Work on this has commenced. We will email you once it is completed. Feel free to reach out if you have any additional feedback.

    If you are interested in participating in the preview of this feature please email back.

  4. Add TAG to subscription

    Please add the possibility to add TAG's to subscriptions in the same way it is possible for ResourceGroups. We use TAG's for chargeback (add tag for project codes to charges) and in most cases we do charge back on subscription level. Hence, the possibility to add TAG's on subscriptions would be great.

    66 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Increase maximum Resource group limit when using linked deployment templates

    I'm trying to create a script to deploy my entire system in one deployment using linked templates (the system consists of many microservices, which are isolated in their own resource groups). However I am hitting the following error:

    The template deployment and its nested deployments specifies too many target resource groups. At most '5' different resource groups is allowed

    Can this seemingly arbitrary limit be lifted/removed as this is blocking is from continuing our automation scripts.

    thank you

    66 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Resource tag inherit from ResourceGroup (or Subscription)

    Today we need to TAG all individual resources to get the TAG's available in the billing API for chargeback. Would be much more efficient to set TAGs on subscription level and/or ResourceGroup level and then let all resources inherit the TAG's with option to overide the inherited TAGs on the resources. This way we don't need to add TAG's to every resource.

    65 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Show "created by" user

    It would be handy if the Properties blade showed the Created By user so we didn't have to search through audit logs. Creation Date, Last Modified Date, and Last Modified By would also potentially be useful.

    49 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Parameters in Nested Templates is broken

    For nested templates, you cannot use parameters or variables that are defined within the nested template. It is currently broken (as per the documentation).

    It'd be great if this could be fixed. An example of what I'm talking about can be seen here:

    https://github.com/bmoore-msft/AzureRM-Samples/blob/master/dynamicSecretId/azuredeploy.inline.json

    Note: It's not only with Keyvault references that this is broken, but rather all inline parameters when using an inline template.

    Thanks!

    39 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Unlimited deployments

    At the moment, there is a limitation of 800 deployments per resource group.

    Afterwards, you have to manually delete them in order to be able to perform new deployments.

    It would be nice if there wasn't any limit.

    Another option would be new deployments overriding old ones (you only get to save latest 800).

    30 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Resource Manager

Feedback and Knowledge Base