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. 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…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make securestring a supported input type for runbooks

    As of right now you can´t secure the runbook input. Using a string works fine but it leaves the password for example in the input as plain text. If we could write the password as a secure string instead, that would be great and solutions to reset passwords etc. would be safe to implement in production.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  PowerShell authoring  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow VMs to communicate with DSC without public Internet connection

    Can we allow Azure VMs to somehow communicate with Automation Accounts in the same subscription in order to implement DSC without requiring the VM to have an Internet connection? Since the IP address of the automation account changes so readily, I cannot create a specific NSG rule for automation accounts, though I would love to be able to use Azure DSC for our VMs. Today, I cannot due to the inabaility for me to lock down generic Internet traffic on internal-only VMs.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  4. Git (Stash) Source Control Support or TFS On-Prem

    Would be good if we could connect to our Stash server rather than having to use GitHub. Alternatively we have an on-prem TFS setup that we could also use. Data sovereignty issues prevent the use of GitHub/VSO at this time.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for your feedback on this! We are definitively interested in private/on-prem scenarios for source control.
    As we start to do more development in this area, our team will follow up to get more details about your specific needs.

  5. Email after runbook job

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

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  6. Desired State Configuration Source Control

    Provide the ability to sync DSC Configurations with remote GitHub Repo's. Similar to how the Runbook integration works. When a push to a Git Repo is made, synchronise it with the Azure Automation Account.

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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!

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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.

  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.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  10. Surface runbook errors in the Automation account overview page like runbook exceptions are surfaced

    Currently if my runbook is having issues and I look at the overview page, I can only see exceptions of the runbook. The runbook may hit errors during execution, which do not show up on this page.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  11. Open up for HelpMessage and Validation to be supported in Automation runbooks input parameters.

    Ability to describe and validate required parameters in more detail, in the Test Pane. Instead of starting a runbook that will fail due to wrong inputs, users will have to correct these wrong typings before initiation of the runbook.

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Fixed IP for Automation PowerShell sandbox in order to fit ACL requirements for public endpoints

    If VM has external endpoints (WinRM, SSH) protected by ACL, the Azure Automation doesn't able to connect for such VMs.

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  13. authenticate source control fails

    We use VSTS + Git for change control. When asked to authenticate there is a failure with 0 additional information. Our source control is part of the same AD tenant.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
  14. Delete subscriptions without first removing RBAC role definitions /assignable scopes

    We have a custom RBAC role definition that we link to new subscriptions. If we delete a subscription without first removing the link with the RBAC role definition, we are unable to link this role definition to new subscriptions. This is blocking our environment, because we are not able to adapt our current role and rights model.

    So, it should be possible to remove subscriptions without first removing the link(s) with role definitions /assignable scopes.

    See ticket 117020815287840 for more information.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Role Based Access Control  ·  Flag idea as inappropriate…  ·  Admin →
  15. Adding a "Create New" button in Graphical Runbook configuration when adding input parameters

    when configuring input parameters for a cmdlet in the graphical runbook canvas, if there are no inputs configured, you'll get an "No item to display" message and you have to go back and add input parameters. However, you will lose unsaved changes if you go back. To make it more user friendly, would it be better if there's a "Create New" button next to the "No item to display" message so users can create input parameters without having to go back and lose unsaved changes.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Graphical authoring  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for voting for this suggestion. We will look into adding functionality that makes adding input parameters from cmdlet configuration easier.

  16. Show the line number when an exception is raised

    I tend to use ErrorActionPreference = 'STOP' in my Runbooks (and my Powershell scripts) because if I haven't handled an exception, I want to know. While in Powershell this gives me a useful trace to go back and figure out what went wrong, in Azure Automation I am presented with only the exception name, ie "An error occurred while sending the request.". This makes it really hard to find out what happened.

    As a work around, I can put a whole bunch of Write-Verbose statements in my Runbook, but this is tedious. It would be great if Azure Automation could…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Debugging and troubleshooting  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Can you provide more detail on what you mean by useful? Do you want to know where in the code the error occurred? Can you provide an example of what you find useful for debugging PS in the ISE?

    You may want to try using ErrorRecord.InvocationInfo for non-terminating errors since on non-terminating errors, we currently save this data in the Error stream.

    On terminating errors (exceptions), this data is currently lost. But we can investigate storing this information to present it for debugging. I would like to make sure that this is the info that you are looking for though, so please confirm.

    As a workaround for now, you could write a global try/catch block in the runbook (which will also catch exceptions thrown because of $ErrorActionPreference = ‘Stop’) and write $_.ErrorRecord.InvocationInfo to a stream.

  17. 21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Edit the name of assets and runbooks

    To be able to edit name/description or asset/runbook

    [Beth Cooper]: Updating this request to only include updating the names of runbook/assets because you can currently edit the description

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    You can currently edit the description on runbooks and assets. To do this for runbooks, go to the Configuration page.

    On the names, would the ability to add a friendly name (that you can edit at any time) be sufficient or are you hoping to change the workflow name as well?

  19. Move "Run on" to runbook settings

    It doesn't make sense to have "Run on" dynamically selecteable. Please move it to "Runbook settings" so that we can do a one-time configuration of whether a runbook should run using hybrid workers or cloud-based workers.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  20. Migrate runbook with assets to another Automation Account

    It would be nice to have the option to migrate a runbook to another Automation Account. With a user action, on whether or not assets and stuff, associated to the runbook, should be moved too.

    I see it useful in a Test / Prod environment. We want multiple users to be able to develop runbooks, but only in a controlled environment. And then move it to our production Automation Account when done.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for posting this suggestion. We do have integration with source control which would easily enable you to sync your runbooks from a dev to prod account easily. https://azure.microsoft.com/en-us/blog/azure-automation-source-control-13/

    Are you asking to be able to pick a runbook and supporting assets and then move them to another account? Would being able to group them together and export them as an ARM template work as a potential solution or is your preference to have a tool in the UX to do this?

  • Don't see your idea?

Feedback and Knowledge Base