Azure Resource Manager

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Restrict use of spaces in tag names

    Currently spaces are allowed in tags. This causes issues with tag governance, as a common occurrence for policy compliance failures is a leading or trailing space in a tag name. Please restrict the use of spaces in tag names, or strip spaces from the input.

    19 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 →
  2. Block peering across tenant

    We have a feature to allow VNET peering across different tenants. However some cx need to disable this feature.

    Please consider having a check box for cx to choose if they want to enable/ disable this feature. Or other workaround to help block this when they want to.

    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 →
  3. Automatically update available sub in global subscription filter option

    We have a global subscription filter feature which can be used to select frequently one in azure portal. In this scenario, we need to manually select one subscription to see available resources even though cx has owner permission. Actually, sometimes cx will forget this step.

    Please consider disable this feature and automatically updated in azure portal if cx already has owner role.

    6 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 →
  4. Nested template calling API multiple times

    Hi,

    I make a call to a function api via nested arm template but it calls api multiple times eventhough it is supposed to be called only once.

    I did monitor my API, most of the times it gets called twice but sometimes even more.

    Could you please look into it and let me know please?

    {"$schema":"https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#","contentVersion":"1.0.0.0","parameters":{},"variables":{"apiVersionDeploy":"2017-05-10","funcionUrl":"http://...","environmentFunctionKey":"xxxx",},"resources":[{"type":"Microsoft.Resources/deployments","apiVersion":"[variables('apiVersionDeploy')]","name":"test","dependsOn":[],"properties":{"templateLink":{"uri":"[concat(variables('funcionUrl'), '?code=', variables('environmentFunctionKey'))]"},"mode":"Incremental"}}],"outputs":{}}

    7 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 →
  5. Enabling static website from ARM template

    Currently ,it's not possible to enable static website from ARM template .I understand management API for storage account does not have static website data-plane property.
    However it's not convenient for users and it should be able to enable static website from ARM template.

    6 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 →
  6. Introduce function to check whether a resource exists

    Currently, the reference() function throws an error at runtime when the resource doesn't exist. I'd like to either have this result a null object instead, or alternatively I'd like a new function such as "exists(resourceName or resourceIdentifier)" returning a boolean. The function should be useable in a "condition" statement.

    I'd like to use this function to work around scenarios where some Azure resources are dependent on each other to be deployed.

    Example: use an ARM template to create a Front Door with a custom domain and an Azure DNS alias record pointing to the Front Door.

    Currently, this is not…

    150 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 →

    Thanks 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.

  7. Remove https://management.azure.com Azure Lighthouse limitation

    Currently Azure Lighthouse can only delegate permission on ressources reachabled from https://management.azure.com (Azure Resource Manager).

    In case of some Azure products, like Azure Data Factories, with Lighthouse, we canno't fully manage the resource because it can be accross others Azure API, https://adf.azure.com

    Could you integrate other dedicated API with Lighthouse to allow a full support of Azure resources ?

    Thanks.

    2 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 →
  8. 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.

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

    We’ll send you updates on this idea

    7 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.

  9. Enable CreateUIDefinition support for “Deploy to Azure” via publicly shared ARM templates

    When using the ability to “Deploy to Azure” via a publicly shared deployments, users are taken to their Azure Portal and presented with a long flat list of fields, with no way to organize them, limited validation, etc..

    Managed Applications and Solution Templates in the Azure Marketplace support a CreateUIDefinition.json, which provide a much more sophisticated user experience, with tabs, validation, and much more dynamic capabilities to productize the experience of using the ARM template. It would be great if you could use the UI Definition capabilities to improve the deployment experience for publicly shared deployments (i.e. "Deploy to Azure")…

    6 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 →
  10. set email for backup alerts in RecoveryServiceVault via ARM

    Need the ability to set the backup alerts on a RecoveryServiceVault via ARM templates.

    Currently this is only available via the portal as per https://docs.microsoft.com/en-us/azure/backup/backup-azure-monitoring-built-in-monitor#notification-for-backup-alerts)

    2 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 →
  11. Deploy to Azure button should obey Azure Portal last visited directory

    The Azure portal has a setting for Sign in to your last visited directory. It appears that when using the Deploy to Azure button (https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-to-azure-button) this last visited directory setting is not followed. This can lead to confusion when you go to deploy and you don't see the Azure subscriptions that you were just looking at in the portal and that you expected to deploy to.

    For more information, please see the following GitHub issue: https://github.com/Azure/azure-quickstart-templates/issues/8680.

    1 vote
    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 →
  12. Built in functions should enable returning seconds since the epoch

    The built in utcNow and dateTimeAdd functions currently can only format to date/time strings using dotnet format strings so can't output seconds since the epoch. This is a problem because the KeyVault secret expiry only accepts seconds since the epoch (https://docs.microsoft.com/en-us/azure/templates/microsoft.keyvault/vaults/secrets) so there's no way to set this value from a template.

    Please add the ability to get seconds since the epoch from date functions. This could be done by overloading the built in "int" function or by adding an additional option to the format string (perhaps detect the new special character and follow a different code path…

    1 vote
    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 →
  13. Possible to use the same template link relative path twice

    Hi !
    I face a limitation with my nested template where I need to generate 2 EventHub (with other resources). I put the EH template in a nested one and wanted to use it two times in the main template but I've got this error message :
    BadRequestError: TemplateSpecVersionInvalidArtifactPath: The artifact path 'eventhub.nest.json' is not supported. An artifact path should be unique and not contain any expressions.

    Of course when I try with one call it works perfectly !
    At the moment is there a solution to do that in the purpose to reuse an existing nested template ?

    thx

    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 →
  14. 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
    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 →
  15. Enable Templates To Utilize HTTP Resources

    Create a function to use an HTTP resource inside of a template.

    Using the schema reference such as httpResource('Microsoft.Cache/Redis#definitions.Sku', '2019-07-01').name.oneOf[0].enum or a URL such as httpResource("https://schema.management.azure.com/schemas/2019-07-01/Microsoft.Cache.json#definitions.Sku.properties.name.oneOf[0].enum") - would allow the "allowedValues" in a great number of templates to be filled with the values directly out of the schema.

    This will greatly reduce copy/pasting of information already available in JSON schemas into templates and ensure correct options are provided by templates by matching versions.

    For example the available schema for Microsoft.Cache/Redis - https://schema.management.azure.com/schemas/2019-07-01/Microsoft.Cache.json - has the property name, possible property values, and description already available to create a Redis…

    4 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. Unable to list FrontendEndpoints in Front Door instance with many endpoints

    Front Door supports up to 500 FrontendEndpoint objects according to the documentation: https://github.com/MicrosoftDocs/azure-docs/blob/master/includes/front-door-limits.md

    However, past around 60-70 FrontendEndpoints, the following api request is timing out with a 504 error:

    https://resources.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/RESOURCEGROUP/providers/Microsoft.Network/frontDoors/FRONTDOORNAME/frontendEndpoints

    Note: This timeout also occurs with the az cli and Azure PowerShell.

    If I delete a couple of endpoints, the api requests will start working again, but as soon as I add them back, this request starts erroring out with 504s again.

    Current Workaround: It appears the "full" endpoint continues to work correctly with many FrontEndEndpoints, so it seems you can select the frontendEndpoints object out of this:

    https://resources.azure.com/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/RESOURCEGROUP/providers/Microsoft.Network/frontDoors/FRONTDOORNAME

    2 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 →
  17. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Azure Deployment Manager  ·  Flag idea as inappropriate…  ·  Admin →
  18. please update Microsoft.Resources/deploymentScripts documentation on that limitations

    Azure AD authentication is not support for the SQL Servers in the Containers right now. It's something that is in development.” please update Microsoft.Resources/deploymentScripts documentation on that limitations , it will help to make crucial decision about architecture.

    2 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 →
  19. Wrong error message while tagging

    After applying tagging policy to Azure resources, if we are adding any wrong tags on any resource so wrong error message is showing. Error should be related to policy and it should say tag names are not compatible/not matching with policy defined.

    Instead, error is coming as Could not save the tags. Access unauthorized.

    There is no issue with access here.

    2 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 →
  20. Send emails to directory roles regardless of PIM elevation status

    Currently alerts sent to directory roles (e.g. Identity Protection alerts that get sent to Global Admins or Security Admins) are only sent to those people if they happen to be elevated in PIM at that time. Just because someone is not elevated does not mean they should not receive those alerts; alerts like these should be sent to the people with the directory role regardless of their elevation status in PIM.

    2 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 →
← Previous 1 3 4 5 27 28
  • Don't see your idea?

Azure Resource Manager

Categories

Feedback and Knowledge Base