Azure Resource Manager

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  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.

    237 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    36 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for voting on this suggestion. It is now completed and can be done via custom Azure Policy. Here is a sample custom policy to apply a specific tag at the RG and have them inherited by the Resources in that RG: https://github.com/Azure/azure-policy/tree/master/samples/ResourceGroup/copy-resourcegroup-tag

    Tag inheritance for existing resources is something that we plan to add support for in 2019.

  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.

    92 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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.

    61 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    11 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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…

    50 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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).

    35 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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

    34 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    33 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    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!

    26 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    20 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Resource Manager

Categories

Feedback and Knowledge Base