Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Automation

Azure Automation allows you to automate the creation, monitoring, deployment, and maintenance of resources in your Azure environment using a highly-available workflow execution engine. Orchestrate time-consuming, error-prone, and frequently repeated tasks against Azure and third party systems to decrease time to value for your cloud operations.

Visit the Automation page to learn more about Automation and how to get started.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. az cli support in runbooks

    az command cannot be found when using in a runbook

    605 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  2. Creation of Run As accounts using ARM Template

    Creation of Run As accounts using ARM Template

    493 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    27 comments  ·  Integration with other products  ·  Flag idea as inappropriate…  ·  Admin →

    The Product Group is coming up with the support of managed identity for Automation to be used instead of Runas account with a tentative ETA of CY21 March-End. All our investments would be towards moving customers to use managed identity rather than RunAs.

  3. Utilize the same Automation hybrid runbook workers across multiple Automation accounts under the same subscription.

    Utilize the same Automation hybrid runbook workers across multiple Automation accounts under the same subscription. Currently its a 1to1 link between an automation account and a runbook worker. This means I have to create a new runbook worker for each automation account.

    385 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  4. Provide more control of how runbooks are allocated to a sandbox

    There are several scenarios that cause sandboxes to crash or runbooks to fail in both hybrid workers or in Azure.
    1) Sandboxes fail with out of memory randomly. If the wrong combination of runbooks get executed in a sandbox the the sandbox can crash intermittently. If there was a way to control how many jobs run in a sandbox, or flag particular runbox to run by themselves and not share a runbook this problem could be mitigated.
    2) If runbooks land in a sandbox that require different subscriptions one of the runbooks will fail. Someway of preventing this so that…

    361 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  5. Bring Azure Automation and DSC to Azure Stack

    Please bring Azure Automation and DSC to on-premises to Azure Stack . This is an important part of the hybrid cloud story.

    This is a copy from here: https://feedback.azure.com/forums/344565-azure-stack/suggestions/11632959-where-is-sma-in-microsoft-azure-stack .

    282 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Integration with other products  ·  Flag idea as inappropriate…  ·  Admin →
  6. Redeploying jobSchedule resource from ARM template

    Currently Microsoft.Automation/automationAccounts/jobSchedules resources cannot be redeployed from ARM template if there are existing jobSchedules pointing to the same runbook and schedule. The deployment would return:

    "A job schedule for the specified runbook and schedule already exists"

    Same issue even deploying with a different name (GUID) for the jobSchedule.

    Currently the workaround is deleting the existing resource and redeploy, which is a very cumbersome approach for automation.

    282 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →

    Redeploying job schedule through ARM template needs a different jobschedule GUID. Even if you delete the job schedule , the GUID is retained in the database , hence a 2nd deployment will succeed only if the GUID is different.

    The scenarios where jobschedule GUID cannot be reused is as follows:

    1) The automation account is deleted before deleting the job schedule. The job schedule entry is soft deleted but is still present in the database.

    2) The automation account is created with the same name again and the same GUID is used for job schedule.

    We have identified as a bug & an improvement task is planned. We will pick this up as resourcing allows since this would need some changes in the architecture. As a workaround to this, pls update the GUID for jobSchedule.

  7. Azure Automation PowerShell version 7.0

    Anyone know if or when this will be released, or if it will be?

    243 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support PowerShell Core as Runbook Type

    I develop on OSX and so use PowerShell Core heavily.

    It's frustrating when Azure Automation Runbooks don't work the same way as they do locally because they run PowerShell 5.

    For example, Invoke-RestMethod in PowerShell Core supports the following parameter:
    -Authentication

    195 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  9. Trigger email notifications or Azure log generation when a certificate is nearing expiration.

    We recently ran into an issue where the AzureRunAs cert expired and caused most automations to fail due to a connectivity error. The client hadn't checked on AA for a bit and didn't see the portal warning.

    Would be nice to have an email alert option to alert admins when certificates stored in AA are nearing expiration, or generate a log we which we can use to build Azure Alerts or feed into OMS. As of now, we had to create an AA runbook that pulls cert info on a schedule and alerts if necessary.

    187 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →

    The Product Group is coming up with the support of managed identity for Automation to be used instead of Runas account with a tentative ETA of CY21 March-End. All our investments would be towards moving customers to use managed identity rather than RunAs. With the support of managed identity , customers would not have to worry about the overhead of certificate management.
    We will , however , prioritize email notification for cert expiry if resourcing allows.

  10. Webhooks ARM Template

    Webhooks from ARM Template still don't work.
    I've seen the schema you're providing: https://docs.microsoft.com/en-us/azure/templates/microsoft.automation/automationaccounts/webhooks
    The PowerShell commandlets first request to generate a token before it is apply in the template.
    When I run the ARM Template with your schema I cannot provide the URI and i get the error: "Invalid uri"

    I know it's a duplicate of https://feedback.azure.com/forums/246290-automation/suggestions/13227531-webhooks-arm-template
    but you've closed the item and it is still not working.

    183 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  11. PowerShell cmdlet to get Runbook context.

    It would be great if you could use in runbook code something like Get-RunbookContext to retrieve the current ResourceGroup and/or Automation Account the runbook is executing in. Then it would be much easier to locate Automation Account Assets like connections and variables without the need to hard-code them into your Runbook. The PowerShell commands available to retrieve and use assets require you to specify the ResourceGroup and Automation Account the asset is stored under.

    137 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support a service tag which denotes the IP address space for Azure Automation

    Currently, we don't support a service tag which denotes the IP address space for Azure Automation service. There are scenarios where a customer would like to allow only the inbound traffic from Azure Automation service by using NSG when a runbook send a HTTP request to a VM. Such customers are requires to whitelist all IP addresses of Azure datacenter. However the customers need to update the settings of NSG every week because there's a possibility that the Azure IP ranges are changed once a week. This requires complicated procedures and high-maintenance. So, it would be great if the service…

    123 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add support for Azure CLI Runbooks in Automation

    This feature is requested at the below item, but it is closed to votes since it was moved from another product. Recreating so it can receive votes to reflect the frequent comments.
    https://feedback.azure.com/forums/246290-automation/suggestions/31482895-add-support-to-automation-for-az-cli

    The ask is to be able to create Runbooks that run Azure CLI commands, not PowerShell, as there is functionality in CLI that is not achieved with PowerShell in some cases.

    118 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add possibility to end a test job when it hangs.

    Sometimes when running code in a PS runbook something seems to hang. I'm getting the following error although the job probably finished long time ago:
    "BadRequest: Test job is already running."
    I would like to have the opportunity to clear any running test jobs to bypass this bug.

    108 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  15. Increase 1MB Size Limit for DSC Node Configurations (MOF files)

    Azure DSC node configuration (MOF files) are currently limited to 1 MB in size. This limitation does not allow for significantly detailed or complex configurations.

    In my specific scenario, we have several IIS websites in a our web farm and we've hit the limit of how many unique websites we can configure per server because the MOF file is larger than 1 MB. The resulting error is that the MOF cannot be encrypted by Azure DSC Automation.

    100 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  16. Ability to remove jobs from the Jobs history

    The list of jobs quickly gets long and if you play around with some configurations etc and the job fails it will mess up the statistics (and potentially scare some people). So I suggest an option to remove jobs from that list.

    88 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  17. Change behavior when sandbox runs out of memory (1MB max to one stream limit)

    There is currently a maximum limit of 1MB when outputting values to the any stream (Serialized size per object in pipeline).
    I understand why this limit is there, but I don't think the current behavior is the right way to go.

    Current behavior is that the runbook restarts, and runs 3 times until it is stopped with the following error:

    Suspended
    The job action 'Activate' cannot be run, because the process stopped unexpectedly. The job action was attempted 3 times.

    If we run it on look at the eventlog on a hybrid worker (this error also happens in Azure workers),…

    78 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for posting this feedback! I’m checking with our team to see if there is anything that we can do about this in the short term. We’ll definitely take this into consideration in our longer term plans.

  18. WebHook Job Monitoring

    Allow people to use the same WebHook Url used for triggering a runbook for querying job status.
    Instead of doing a HTTP POST (used for triggering) you could allow a HTTP GET with the JobId as parameter. This would be a lightweight alternative for consuming runbook results no matter client and platform.
    Note: Using the same url means same access token which leads to monitoring being possible for the lifetime of the access token.

    78 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  19. DSC: Include nodes' Azure resource IDs

    Currently, when viewing a node in Azure Automation DSC, the only identifying information is the node's hostname and IP address. If the node is an Azure VM, it would be helpful to also include the node's resource ID, because in a cloud environment hostnames and IPs can be constantly changing or even overlap.

    Note that Azure VMs onboarded with the DSC extension already send resource ID and other "ExtendedProperties" to Azure Automation DSC, so this information is already being recorded, it's just for internal use only right now and can't be retrieved via the ARM API.

    78 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  20. Make Automation an Azure Trusted Service

    the Azure automation ip range should be added as an Azure trusted service so when I use vnet endpoints on storage accounts, etc and tell it to allow azure trusted services automation works.

    76 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 27 28
  • Don't see your idea?

Feedback and Knowledge Base