Azure Resource Manager
-
Show Azure Storage <StaticWebsite> setting when query in Azure Resource Graph
It's not possible to query Storage <StaticWebsite> setting in Azure Resource Graph to see which accounts have this feature enabled or not. I understand ARG is based on ARM properties returned by management API, and it seems the ARM response for storage account does not have this data-plane property.
However I think it should be included in the response as it's a general property for StorageV2 accounts. It's not convenient for users and we need to get this info from Storage API - https://docs.microsoft.com/en-us/rest/api/storageservices/get-blob-service-properties)5 votes -
Azure REST API to update Azure AD User's Authentication Info
We are having our Web Application which Creates User in Azure AD using Graph API and stores its details in Database including Email and Phone. Our requirement is to update the Azure AD User's Authentication Info, that is used for Self Service Password Reset and Multi-Factor Authentication, via back end using Azure REST API.
So we want to have an Azure REST API to update the Azure AD User's Authentication info.1 vote -
ARM template parameter validation
It should be possible to validate and restrict ARM template parameters using a regex.
This would greatly reduce the change for parameter value errors causing a template deployment to fail.
This would also make ARM templates a more competitive alternative to AZ CLI and Azure PowerShell.
1 voteThanks 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
-
The REST api for 'Policy States - List Query Results For Management Group' is taking more time to show the correct compliance status
Currently when we are assigning a policy with a not scope field, The REST api for 'Policy States - List Query Results For Management Group', shows incorrect compliance status for resources which are included in the not scope field. As this is a design limitation, which sometimes takes a while for a change like exclusions to take effect.
It would be really great if we can prioritize this issue.
5 votes -
provide an ability to query metrics APIS by resource groups and tags
This ability is required to restrict the response to a particular resource group or tag on a set of resources.
This could be required when integrating Azure with an APM like Dynatrace or other tools.Currently, all metrics are returned irrespective of the resource group or the custom tag in the query, polluting one environment with data from the others that are hosted in the same subscription.
1 vote -
Allow us to Stop an entire Resource Group
I'd like to be able to stop (and start) all resources in a resource group where resources can be stopped with a single button in the portal.
The use-case is development stuff, things I'm learning. It'd be nice to just turn it off and feel safe that I am not inadvertently consuming resources.
1 voteThanks 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
-
Better error handling, reporting
When deploying linked ARM templates, the user gets below error:
"status": {
"value": "Failed",
"localizedValue": "Failed"
},
"subStatus": {
"value": "InternalServerError",
"localizedValue": "Internal Server Error (HTTP Status Code: 500)"
},On further investigation, found that 2 parameters were not being substituted with values. Once those 2 parameters were addressed, the deployment went successful.
Can we please have a more verbose error description displayed instead of plain "Internal Server Error"?
Thank you!
1 voteThanks 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
-
“created date” and “created by” should be default attributes for every azure resource
By default every azure resource should have "Created Date" and "Created By" metadata.
1 voteThanks 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
-
Cancel resource movement
Currently, once you start moving a resource between resource groups, you cannot cancel it.
In some cases, it takes a long time to move, and if the event described on the left occurs, it will interfere with the work, so we strongly hope to change the function so that you can cancel the movement.1 voteThanks 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.
-
About resource locking when moving resources between resource groups
Currently, when moving a resource between resource groups, the resources in the source and destination resource groups are locked.
We strongly recommend that you change the function so that resources that are not related to the movement are not locked when moving between resource groups.1 voteThanks 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.
-
Make it easy to hide/filter events in Activity Log
It would be much easier to find important events if I could hide certain event types not just on severity.
For example 'Microsoft Azure Policy Insights' is spamming resources with warning events every few minutes and the only way to hide is by deselecting "Warning" severity, which potentially hides important information.
If could deselect by operation names, for example "Audit", life would be much better :)
An alternative approach would be to bundle all events of the same type and list as 1 entry that you can expand/collapse.
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.
-
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…
1 voteThanks 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.
-
Automatically delete old deployments as DeploymentQuotaExceeded error occurs
We are often hitting the DeploymentQuotaExceeded error, exceeding the quota of 800 deployments. This happens because old deployments are never deleted, no matter how old they are. We would like to request as a feature a rolling behavior where, as the quota is reached, the oldest deployment is automatically deleted.
20 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.
-
to make Custom ARM Template available in the Deployment Section of the Resource Group even if the Subscription get suspended
As the subscription get suspended, in the deployment section of the resource group the Template gets unavailable or unresponsive without any error just the Template shows "Generating Template..." and also the redeploy option get unresponsive. All of the options are responsive like "Overview", "Input", "Output" but "Template" shows "Generating Template...". Further "Redeploy" option should work because as in Custom Template there is an option to change the Subscription but it gets Unresponse. Although the template is just a CODE a static content what it would be charging?
1 voteThanks 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.
-
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.7 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.
-
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…
5 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.
-
Please make a function that converts string to securestring
Please make a function that converts string to securestring
1 voteThanks 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
-
More informative error response code for Azure REST API
We are using Azure Resource Manager to automate the creation of Azure Subscription, assign some user after the creation, deploy some resource to the Subscription, etc.
The issue is, sometimes the API response returned is not very informative and often misleading. For example, directly after creating the Subscription using ARM, if we try to assign a user to the Subscription using ARM, sometimes the API would return 403 response. Is it a permission problem with our client? No, after we add some logic to retry the API call whenever the response returned 403, eventually the API would return 200 response.
…
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.
-
Automated Destruction of Resource, planned on deployment
It would be cool if i can give a date on deployment when a certain resource i deploy is automatically destroyed again. Either after a certain amount of time or with a certain date. i could do this myself with a account/vm which manages the rest of the resources, but give a date with azure cli on creation would be much nicer :)
1 voteThanks 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.
-
YAML/YML support for ARM
Can we have YAML support for ARM just like AWS cloudformation
2 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.
- Don't see your idea?