Azure Resource Manager

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow changing the api-version query string parameter in Resource Explorer

    The Azure Resource Explorer (https://resources.azure.com/) is an invaluable tool to look at Azure resources at low level, particularly for crafting ARM templates.

    However, one issue in the current implementation is that the api-version query string parameter used by the tool to call the ARM REST APIs is fixed for each resource type.

    Most of the time, this works fine, but there are times where this is very limited. For example, I was recently trying to obtain/modify some resource information from the tool for an Application Gateway resource, and this was not possible because the api-version used by default…

    11 votes
    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 →
  2. Improve provisioning of Power BI workspace collection through ARM template

    Right now we can provision a Power BI workspace collection through ARM template. But once the collection is there we get an error if we execute the template again. In general this is not the behavior for the other resources and probably needs to be changed. You can see here more for info. https://stackoverflow.com/questions/42209695/error-when-updating-a-powerbi-workspace-collection-from-an-arm-template

    11 votes
    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 →
  3. Allow us to change the location of resources

    It is inconvenient and outage-prone to migrate a resource to a new location at present.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Ability to use a naming convention pattern in Azure

    It could be useful to define per subscription/per resource group/ or per object level a naming convention pattern in order to facilitate the naming and coherency of objects in Azure.
    Using a prefix / suffix / incremental / regexp patterns

    11 votes
    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 →
  5. Use a DSL rather than JSON for authoring templates

    Scrap the JSON thing and use a DSL with real language features for declaring the templates.

    The syntax itself can be compressed and much easier to use. (for example defining a parameters or a variables without unnecessary syntactic sugar or properties in properties)

    Replace concat with full expressions (and partly numeric ones for easier construction of names) and skip all the variable('xx') and parameter('ccc') and just use the names (xx, ccc) directly in expressions.

    Replace the copy/copyIndex thing with a flexible iterator definition that allows you to use any sequence of values as input (custom number sequences, custom arrays etc)

    11 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 →
  6. Resource Namespace Pollution

    Currently, all resources (storage, redis, websites, etc.) require that I come up with a unique name for the service that will be suffixed by something related to the resource type. The naming restrictions on these varies but tends to be short and often disallows anything other than alphabetic characters.

    After creating a handful of Azure resources, I quickly run into problems with coming up with new names for my resources that are meaningful yet not already taken by someone else. I am very close to just generating random character sequences for names and giving up on having them be usefully…

    11 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. Support linked ARM templates on private vnets

    In short, I'd like to be able to use BLOB storage on private vnets, and allow access to that storage when deploying with ARM templates. It shouldn't be necessary to open the BLOB storage up to public access (even if protected by SAS tokens) just to use the storage account during ARM deployment.

    My preferred solution is to either have the ARM deploy servers included in the "trusted Microsoft services" that I've granted access to the storage account; or add another checkbox (similar to keyvault) granting network access to the storage account when accessed during deployment.

    For example, I should…

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  8. Remove DNS Zone 'child' records (CNAMEs, etc) with Complete Deployments

    https://stackoverflow.com/questions/49073063/

    Expectation: If a template is deployed in Complete mode, Resources which are not represented in the template should be removed.

    Actual: Once a child resource (like CNAME) is deployed with an ARM Template, it cannot be removed with an ARM Template, regardless of the Deployment Mode.

    This effectively breaks a core tenet of ARM Templates+Deployments and requires additional an out-of-band control/automation plane.

    While this behavior /can/ vary across Resource Providers, I haven't seen a good argument for why it /should be/ inconsistently implemented, especially without the capacity to control the behavior.

    10 votes
    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 →
  9. Stop generating random resource names

    Azure needs an overarching policy when developing new features to ensure when resources are being created that all names can be managed or templated according to sane conventions.

    Spinning up a new container service (AKS, ACS, whatever) generates many unpredictable resources and resource groups. There are many things in Azure that cause this to happen.

    Stop doing this! Please, adopt a policy across all your development teams that enforces a little more care and caution with naming and structure when automatically provisioning resources!

    10 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 →
  10. 10 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 →
  11. Allow use of copyIndex inside variable definition...

    This would be helpful in ensuring consistent naming schemes when deploying multiple resources of the same type. I've attached a sample ARM template to demonstrate a use case.

    10 votes
    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 →
  12. Allow a securestring parameter to be returned inside an object in the outputs section and remain as a securestring

    Imagine a scenario where you have a template parameter (let's call it assetsSasToken) of type securestring. You want assetsSasToken to be included into a complex object and be returned in the outputs section while remaining a securestring. Right now if you attempt this, the value of assetsSasToken returned as part of the complex object is not secured anymore.

    Here is now to reproduce the problematic scenario:

    {
    "$schema": "http://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
    "assetsSasToken": {
    "type": "securestring",
    "defaultValue": "?someSasToken",
    "metadata": {
    "description": "SAS Token associated with parameters artifactsLocation"
    }
    }
    },
    "variables": { },
    "resources": [ ],
    "outputs":…

    10 votes
    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 →
  13. Ability to add, edit and save custom JSON templates in portal with RBAC for reuse and self-service

    Ability to add, edit and save custom JSON templates in portal for reuse. Currently we can do this in Visual Studio, and you can even paste those templates in to https://portal.azure.com/#create/Microsoft.Template to deploy, but it would be nice to be able to save them for repeat use in a self-service kind of scenario for developers to use by giving them RBAC access.

    Also, deploying machine this way provides no way to join them to the domain, and I've had mixed results with DSC for various reasons. Need a way to join the domain at machine creation time, preferably with credentials…

    10 votes
    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 →

    The first part of your request is under discussion – it’s something we hear frequently and are thinking about quite a bit!

    For domain join, please see https://github.com/Azure/azure-quickstart-templates/tree/master/201-vm-domain-join

    If you’re having issues with DSC or custom script extensions working as expected, please open an item in the Virtual Machines section – the right folks will see it there :)

  14. Delete resource with ARM template

    With delivery pipeline it is often needed to create and drop resources for the environments.
    Currently resource manager does not support deprovision deployment mode.
    It means that there is no way to delete exact resources which are specified within the template and were deployed during environment creation.
    Unfortunately Delete Resource Group is not an option because often resources are deployed in different resource groups.
    Actually Delete is part of Complete mode deployment, could you please just make it separate.

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

    We’ll send you updates on this idea

    0 comments  ·  Azure Deployment Manager  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote & comment on. This allows us to effectively prioritize your request against our existing feature backlog and also gives us insight into the potential impact of implementing the suggested feature.

  15. Increase RBAC Role assignment limit or allow Resource Group nesting

    With the limit for RBAC Role assignment at 2000, the number of role per resource groups can be attained relatively quickly with larger deployments. I was thinking of 2 ways to bypass the issue, either allow us to increase the limit to Role Assignments in a subscriptions or allow us to do resource group nesting. That way we could apply the roles to the main resource group to use inheritance instead of using multiple role assignments for all the similar resources.

    9 votes
    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 →
  16. Automation script should copy storage account settings

    Azure Portal can export its Automation script in order to deploy from ARM template, of course in case of Azure Functions on dynamic hosting plan.
    However, the Portal currently never generates appSettings in ARM template.
    Functions saves the connection string of the storage account in appSettings, so if we recover from the template, it always fails because of the lack of storage account information.
    (Deployment would be successful, but newly created Functions never works well.)

    Do you have a plan to fix this?
    I know some template samples in Github can create Dynamic Functions successfully, but Azure Portal can't generate…

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add info on a resource of who created the resource

    The Property pane of a resource contains today the date the resource was created, but there is no information about who created it. Often we find resources that was created a long time ago, but nobody know who created it so it is close to impossible to know if the resource is still in use or not. The audit log can give us some clue, but it only go back 90 days. Would be great that the resource have the account info on the property page that show who created the resource.

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add official support for API Management Service in ARM Templates

    I would like to deploy an API Management Service using ARM Template. I managed to get it working but since the service takes about 30 min to activate the deployment, for some reason, will never change to "Succeeded" and the deployment script never finish.

    9 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 →
  19. ARM Template - Automate Azure Function Event Grid Subscription

    Presently using ARM I can automate the creation of an Azure Function Subscriber that has a HTTP trigger.

    "properties": {
    "destination": {
    "endpointType": "WebHook",
    "properties": {
    "endpointUrl": "[listsecrets(resourceId('Microsoft.Web/sites/functions', parameters('azurefunctions_name'), parameters('azurefunctions_loadTcsItemSubscription')),'2015-08-01').trigger_url]"
    }
    },
    "filter": {
    "includedEventTypes": [
    "All"
    ]
    }
    },

    I am however unable to do the same for an Azure Function Event Grid trigger, there seems to be no way of accessing the master key. Can this be added to an upcoming release. please.

    Many Thanks

    Paul

    8 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 →
  20. Resource Policy: dynamic values in policy parameters or conditions

    Policy parameters or conditions values are limited to strings or arrays. In environments where change is a constant, those strings and arrays need to be updated regularly. Instead of having to update the policy, it would be great if we had some way of having dynamic values, for example coming from an HTTP request or from some other external source.

    Consider a scenario in which you have dozens of applications each with multiple resources. Each application has a different owner (product owner). You want to apply a tagging enforcement policy that states that every resource must have a "owner" tag…

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

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Azure Resource Manager

Categories

Feedback and Knowledge Base