How can we improve the Azure Resource Manager?

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.

416 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jason Milczek shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    25 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Danny Hermans commented  ·   ·  Flag as inappropriate

        Thinking for 3 years, this should be a great solution. Please give us an update, especially for billing purposes!

      • Matthew Taylor commented  ·   ·  Flag as inappropriate

        Inherited Tags is needed and seems like a logical requirement. I am surprised that this is not a feature already. Have tried policy to require a Tag but have run into issues creating VM's from PS script where extensions fail (because of tagging policy) and unable to create objects from portal as there is no option to specify a tag during creation. If Tag inheritance was possible, would be able to simply create items in a Resource Group and object would then inherit tag(s) assigned to said Resource Group. This certainly seems like a much desired option.

      • craig gordon commented  ·   ·  Flag as inappropriate

        Any more current updates on tag inheritance on the roadmap? Specifically, it would be nice to just have a checkbox option either at subscription level or resource group level, that allows you to toggle resource group inheritance on/off(default). Desire is to simply have the same tags and values propogate to all resources in a resource group.

      • craig gordon commented  ·   ·  Flag as inappropriate

        agree with all. this is a must have- flag to force tag inheritance from the resource group. ..... so it cascades to all child elements in the resource group. will greatly simplify our and it sounds like others billing.
        Resource Group being used as a container for an "application" which is what we drive billing and our (APM) app portfolio mgt chargeback from

      • MichaelT commented  ·   ·  Flag as inappropriate

        It would be nice if tags that are set by policy on resource groups level should become readonly and automatically appended when a use creates resources or set tags to resources.
        Right now a user that can set tags can remove the inherited tags that were set by the policy.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Tags should be inherited. We need the ability to tag resources and report on them. Ideally the tags should be broken out into separate fields/columns on the billing detail so that users don't need to parse the data out of one field and re-order. This is a time consuming process when trying to attribute the bill for resources to the right application.

      • Anonymous commented  ·   ·  Flag as inappropriate

        any updates? we are a fortunate 50 company and we have a real need now. there are hundreds of application teams and thousands of projects and the F&A people want to ensure chargeback tagging is accurate. they do not want to leave it up to the application/project teams to properly tag their resources.

      ← Previous 1

      Feedback and Knowledge Base