Azure Resource Manager

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Rename Resource Groups

    Need the ability to rename resource groups either via PowerShell or the new portal.

    1,675 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    173 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Rename Resources in Azure Resource Manager or Powershell

    Ability to Rename Resources in Azure Resource Manager or Powershell. Important for adjusting naming conventions after implementation.

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

    We’ll send you updates on this idea

    89 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add ability to rename services

    It would be useful to be able to rename services on occasion. If these are tied to other services or components (eg., DNS entry), then perhaps the ability to migrate could be added. I know there's another vote to rename resource groups, however I'd like to see this possible for anything.

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

    We’ll send you updates on this idea

    14 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. String array function Join

    in some cases, I need to concatenate several references (variables) which have rather long names (or complex object structures).

    The standard approach (Concat(...)) makes for a very long lines.

    Since multi-line values aren't supported (another area for improvement), the current approach I use is to create an array of each segment, since each member of the array can be its own line.

    Ideally I'd like to take that array and just Join(string[], "")... but currently I can't, so I'm forced to concat(var[0], "", var[1], "_", var[2]).

    The inclusion of a JOIN function would SIGNIFICANTLY simplify the variable's definition.

    40 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 →
  5. RBAC rules need an option to block IAM inheritance

    Create an option that allows blocking of inheritance for RBAC rules.

    ATM if you create a generic rule at a top layer it means you cannot block access to a particular item.

    As such the only way to create a rule which doesnt allow access is by creating multiple top layer items that exclude the one item you want to block.

    Need a setup similar to NTFS security inheritance blocking options.

    36 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 →
  6. Support HashTables in Azure Resource Manager (ARM) JSON Templates

    It would be really great if Azure Resource Manager (ARM) JSON Templates supported HashTable variables, in addition to the other primitive types.

    16 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. Create a "Tag Administrator" role

    As a person responsible for maintaining tags on resources, I need a "Tag Administrator" role which allows me to create, modify, and delete tags WITHOUT allowing me to make other configuration changes to the associated resource.

    I had hoped that the "Microsoft.Resources/tags/*" RBAC action would allow the setting of tags on any resource but sadly it does not -- perhaps it could? Otherwise, a ".../tags/write" action will be needed on each resource that supports tags.

    In order to edit tags at present, I basically have to be granted "Contributor" access to the resource, which is not ideal and does not…

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

    We’ll send you updates on this idea

    6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Automatic tagging

    To ensure cost allocation and monitoring which user/admin created/modified which resource(s), we need "automatic tagging" - e.g.:


    • logged in user (name) is used for a "Creator: "-tag

    • current time is used for a "Created on: "-tag

    • ...

    This way, cost allocation and resource monitoring can be done in a straight forward way with Azure tools.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

Azure Resource Manager

Categories

Feedback and Knowledge Base