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.

How can we improve Azure Automation service?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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…

    342 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  2. Alert from Azure Automation

    Add the possibility to set up an alert when something goes wrong with the Automation job.

    124 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  3. az cli support in runbooks

    az command cannot be found when using in a runbook

    121 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  4. Remove quid requirement for jobs resource types in ARM templates

    CompilationJob and Job resource types require a guid for the resource name. Because of this PowerShell is needed to prevent inserting a guid manually. Which makes template more complex and prevents template only deployment. (Deploy to Azure button)
    Resource Types
    Microsoft.Automation/AutomationAccounts/jobs
    Microsoft.Automation/AutomationAccounts/Compilationjobs
    Please remove the requirement of the guid in the resource name. The job identifier/name of the underlying job can still be a guid.

    93 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thank you for the feedback. This is something that we are looking at to see if it is feasible.

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

    67 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add native support for job concurrency control

    Certain runbooks must not have more than one concurrent job instance running at any time. Although we have some workarounds using helper runbooks / job queue tables, including this natively as we had it in SCORCH would really help, as the workarounds do not guarantee the behavior 100%

    46 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  7. variables to provide execution context

    Please provide built in variables so that an executing runbook can know stuff about itself. e.g.:
    -CurrentAutomationAccount
    -Me (would return the name of the runbook).

    Here's an example of why this would be useful. I want to call New-AzureAutomationSchedule & Register-AzureAutomationScheduledRunbook so that the current executing runbook can schedule itself to run again after a specified period of time. Unfortunately New-AzureAutomationSchedule has a required parameter "AutomationAccountName". This obviously isn't something that I want to hardcode into the runbook so I need a way to access the containing account. The only way to do this is to deploy a variable that…

    40 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

    33 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  9. CSP Subscription cannot create Azure Classic Run as Account

    When creating Automation Account in Azure portal, if we use CSP subscription, creating Classic Run as Account is failure.

    Because CSP can access ARM resource only.
    But error message is very unclear.

    - Message
    Azure Classic Run As account creation error

    An error occurred while creating the Azure Classic Run As account for account 'AutomationTest'. Error details: ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription..

    <Request>
    For resources not available in CSP, please output error including CSP string.

    31 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  10. Python 3

    Why on Earth was this new functionality introduced using the outdated Python 2?

    31 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow multiple .Net framework versions including the latest 4.6.2

    The current sandbox only supports .Net Framework 4.5.2. Would be better to have a support to run the automation script with at least 3 versions of .Net framework including the latest version of 4.6.x.

    29 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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

    24 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  13. Enable Implicit Remoting

    I don't seem to be able to use implicit remoting to manage things like Exchange Online or the Office 365 Compliance Center, which leverages Exchange as well.

    This is a hurdle for me as I can't migrate some of our important jobs to Azure Automation. Is it possible to enable implicit remoting in the PowerShell environment?

    Thanks!

    21 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for this feedback. We will take a look.

    Also, do you have an example of a command that you are trying to use right now? I’ve heard of other customers managing Exchange & O365 with Automation, so there might be a different way to perform the task you are trying to do.

  14. Link Azure Automation Account to OMS Workspace using Powershell

    I am trying to generate an OMS Solution using Log Analytics and Azure Automation. However, after I create an Azure Automation account i observe that there is no way to link the Azure Automation account to the Log Analytics workspace. It would be great if this option is available.

    20 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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.

    17 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  16. Email after runbook job

    Is it possible to send an email of the azure runbook automation job output ?

    16 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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…

    15 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support for GDI+ on worker

    hi all, I'm developing a runbook that generates mail with graphical content using System.Web.DataVisualization.Chart class. Since the runbook grabs data from OMS Log Analytics it is an ideal solution for an Azure worker, alas when I run the runbook I get "A generic error occurred in GDI+'. Any plan to add support for GDI in the Azure worker?

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow cross-tenant Azure Automation update deployments

    Previously we were able to perform cross-tenant deployments to all of the customers that we support from a centralized automation accounts in our main tenant, however this appears to no longer be the case as we received an email from the product group stating so.

    We would like to continue to use this feature as we have been for several months. Managing multiple Log Analytics and Automation account resources in multiple tenants is not idea for someone who may support multiple tenants.

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  20. Offer a better price on Azure Automation DSC for Azure Stack VMs

    Azure Stack VMs pay the same of an AWS VM to use Azure Automation DSC while VMs on Azure have the service for free.

    A better price for Azure Stack's VMs is a reward for those customers using the hybrid Microsoft's offers.

    10 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base