Azure Resource Manager
-
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.110 votesThanks 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.
-
Increase Keyvault Reference Limit in Parameters from 29 to 60+
As of right now, the communicated limit for keyvault references in a parameters file is "30", but is actually in practice 29 (appears to be a bug?).
This limitation is quite low for mature systems. Take, for example, the following potential data points:
- Multiple SQL ids/passwords, storage account keys, AI instrumentation, Redis cache credentials, etc. for connection strings
- App to app communication creds/API keys
- Programmatically created dynamically named/numbered resources
- References to signing keys for different purposes
Many of the clients I work with are struggling with this issue, which seems easily fixable by increasing the limit to a larger number.…
36 votesThanks 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. Since this request came out of an escalation, I’ve engaged the feature owner to take a look and suggest next best step to validate and resolve the reported bug.
-
Identity function for Azure Resource Manager Templates to know who submitted the deployment
It would be good to be able to have a something that returned the user that requested the deployment, either the UPN or the AAD object Id. This can then be used to
Tag the resource with the details of who created/last updated.
This would be great to avoid the masss of resources created without anyone knowing who created them. Thus helping audit and manageability.
If its a function it could be used in policy and thus enforced tagging.Add permissions based on the user doing the deploy.
The last one is useful for the developer scenario where the you…
21 votes -
Add role assignment of AzureAD roles
Currenlty, ARM templates ("Microsoft.Authorization/roleAssignments") does not support assigning AzureAD roles like 'Application Administrator', 'Cloud Application Administrator' or 'Directory Readers'.
Assigning AzureAD roles are needed for "app registration" in AzureAD
13 votes -
expose the "eventName" property
We need a property we can use to identify the different events from a deployment, which currently looks completely identical with the only difference not being usable to identify the correct events automatically
11 votes -
Ability to add functional extensions to templates
I find myself often writing the same boilerplate code in my templates. Particularly in the functions section (name formatting and such). It would be nice to be able to import functions into templates and maintain common functions in a single place.
Example in the attachment
8 votes -
Add a retry mechnanism when parallel deployments fail due to any kind of "Conflict" error
Scenario:
- multiple ARM deployments running in parallel
- all contain a deployment task targeting the same resource group / resource e.g. add a KeyVault access policy/a secret
- all except one deployment fail with a "Conflict" error and need to be restarted manuallyExpected behaviour:
Azure retries automatically when such a "Conflict" occursAnalysis from the KeyVault team:
"Based on the investigation performed, we were able to conclude the existing conflicts (409) when trying to run parallel deployments where due to the fact that the deployments were trying to write new access policies to the Key Vault.Since Key…
6 votes -
YAML/YML support for ARM
Can we have YAML support for ARM just like AWS cloudformation
6 votesThanks for bringing this to our attention. 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.
-
Support Rename Resources (VMs, Resource Groups, VNets)
Azure subscriptions can be renamed because the subscription GUID is actually used inside the system to determine the instance of the subscription.
Azure resources can also be moved between resource groups or subscriptions. After the move, the resource URI will change, causing the script to be modified.
In addition, VM and other resources also have resource IDs inside.In this case, why not provide the function of resource renaming? This is very MUST HAVE, and many customers are requesting this feature!!!!!
5 votes -
Allow usage of function arrays in the dependsOn section
The dependsOn section needs an array of strings, and each string added can call some functions like resourceId, parameters, and variables. But it does not accept a parameter or variable that contains an array of strings. It also doesn't allow the use of copy.
Allowing this would make it much easier (actually make it possible) to dynamically generate a list of dependencies based on parameters.
For instance, creating alerts links to action group resources. It is very likely that the action groups to use are given as a parameter (array of strings). Converting those strings to resourceIds (multiple) is easy…
5 votesThanks 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.
-
Assign resources in ARM templates a simple unique reference ID
The dependsOn array (for example) uses a horrible syntax to refer to resources within the same ARM template. I don't know why since they're all objects in the same "memory space" so when the template is run, they could have simple IDs and a simple way to refer to them.
Imagine if we were able to assign our own GUID or other unique surrogate ID to each resource, it could be used to refer to resources in the same template without the nightmare addressing syntax you have.
The deployment manager can maintain a memory structure containing the ID and the…
4 votesThanks 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.
-
CopyIndex - add staged length for count
Add CopyIndex function to allow a numerical length to count. Enterprise may have their naming standards end with "01", "02", "03", etc. CopyIndex currently will only count logically from 0. "1" "2" "3", etc.
Suggested framework:
CopyIndex(loopName, offset, stagedlength)Suggest framework example:
CopyIndex('VM',1,000)Results would be:
VM001
VM002
VM003
VM0044 votesThanks 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.
-
Add the ability to deploy On-Premise Data Gateways via automated deployment
We're trying to fully automate our deployments via ARM templates with Azure DevOps, but have been unable to deploy On-Premise Data Gateways with a service principle connection. Investigating the situation with Microsoft revealed that you must use a personal or service account with Azure CLI.
3 votes -
Allow actual output of type "securestring"
When defining ARM outputs, "securestring" is a valid type, but nothing is actually outputted. This raises the question as to why it's a valid type, if it serves no purpose.
The "securestring" should be returned for further processing. (Alternately, there should be a schema error for specifying a type that can't work.)
Additional discussion at https://github.com/MicrosoftDocs/azure-docs/issues/32931.
3 votesThanks 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.
-
Microsoft.Resources/deploymentScripts should also have a windows container image
Microsoft.Resources/deploymentScripts is a great and needed addition ARM templates.
Still, limiting it to linux container images is not ideal, at least for our case where we have PowerShell scripts that need to run and they are not PSCore. The migration for them is not that straight forward.
2 votes -
Restrict deploying 3rd party service using Azure policy or Subscription function.
Currently, There are no way to restrict deploying 3rd party service. This is essential suggestion for solving customer’s pain point like below.
In the point of view of the CSP subscription user, the price of the third party service displayed on the Azure portal differs from the amount charged by the Customer. It mean there are possibilities that CSP subscription user can notice the customer's profit margin .
2 votes -
Exported template should be easily deployable in all scenarios
Exported template should be made deployable even when they include PrincipalID and KeyVault properties. Currently, if we have a resource with SystemManagedKey, we need to remove these from the exported template before deploying: keyvaultproperties, PrincipalID and TenantID. This takes additional time and effort. Thanks.
2 votes -
Complete mode should display / return deletion operations
When running a deployment in Complete mode, operations for deleting resources in the resource group that do not exist in the current deployment template are not shown in the deployment summary, or in the DeploymentOperations object using the .NET SDK.
The operations for deleting existing resources when running a deployment in Complete mode should be displayed / retrievable on the new deployment.
2 votes -
Allow manual / ad-hoc deployment rollback
When creating or updating a deployment, there are options to rollback on failure to either the last successful deployment, or a specific deployment (OnErrorDeployment).
There should be a way to rollback to the last successful deployment or a specific deployment without a deployment creation or update failing.
This would be useful in cases where we want to roll back to the previous successful deployment after a cancelled deployment leaves a resource group in an unwanted state, or if we want to bring a resource group back to a previous state for any reason, but we don't want to export the…
2 votes -
Allow the contributor role to set and remove locks
At the moment the contributor can not set or delete roles because it has no Microsoft.Authorization permissions.
But the contribute to the project and sometimes need to delete resources they can do that no when lock is set but we set locks to prevent unintended deletion of resources.
But to do this now we have to make everybody owner which is strange. I get that the Contributor role do not have Microsoft.Authorization/ permissions but not why they do not have Microsoft.Authorization/locks/ permissions
2 votes
- Don't see your idea?