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. Enable option to hide or mask input parameters for runbook job

    When running job in runbook, input parameters (Input Name and Value) are displayed in job windows.

    I can imagine there can be use cases such as multiple users using one runbook and the job input parameters are displayed to every users.

    As a workaround, currently there are Runbook assets , variable which can encrypt the values, but these are made for automation account level.
    I believe there should be straight forward way to hide or mask input parameters for runbook job from runbook itself.

    29 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  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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

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

    We're glad you're here

    Please sign in to leave feedback

    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.

  4. Azure Automation should support managed identities

    Azure Automation should support managed identities for authentication. This would eliminate the need for RunAs accounts, key rotation, etc.

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    started  ·  0 comments  ·  Integration with other products  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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.

    26 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 →
  6. 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.

    26 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
  7. Sync in both directions

    I find that a possibility to sync to repos would be useful as that would enable creation of already existing runbook files in the repo, also the graphical runbooks (if any) could be exported that way.

    26 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  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
  8. edit parameters of automation job

    I would like to edit the parameters of an already scheduled Automation job. Currently (9/21/2020), I can see what those parameters are, and I can always unlink and re-link after typing all those parameters in again. I want to just change one parameter though, not all of them.

    Sometimes someone might ask me to make a small change this particular run to the job, expecting me to only have to change one particular parameter. In reality, I'd have to change all of them. Just this past weekend, this re-typing of all parameters caused the whole job to fail, also eroding…

    26 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  ·  Scheduling  ·  Flag idea as inappropriate…  ·  Admin →
  9. 25 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  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow Custom Module sync / link from AzureDevOps Artifacts (or other external repository)

    We have multiple custom powershell modules. All are in CI/CD in Azure Devops.
    I now have created a workaround to keep modules in Azure Automation up-to-date.
    Publishing our modules to the PowerShell Gallery is not an option.

    Please provide a way to link PowerShell modules to Azure DevOps Artifacts using a service connection / webhook / whatever, or to any other private repository for that matter.

    25 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  ·  Integration with other products  ·  Flag idea as inappropriate…  ·  Admin →
  11. Display Powershell 5 information stream in runbook output

    Anything written to the new Powershell 5 information stream (stream 6) doesn't appear in the job output if $InformationPreference is set to 'Continue'.

    25 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 →
  12. More robust viewing and management of Hybrid Runbook Workers

    Hybrid runbook workers should have management offered through the Azure Portal and via PowerShell cmdlets.

    User story 1: As a user I should be able to see which hybrid runbook worker a particular job ran on, not just the hybrid worker group (which I should see as well). The Azure Portal UI should show me the specific hybrid worker and I should also see the specific hybrid worker as output when executing Get-AzureRmAutomationJob (again, in addition to the Hybrid Worker Group).

    User story 2: As a user I should be able to configure individual hybrid workers to be available/unavailable to…

    25 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  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  13. Interactive Console

    It would be great if the test pane offered a true interactive REPL. This would allow better testing and debugging of code before publishing. Right now there always seems to be a bit of guesswork involved in getting a script runbook working correctly and being able to debug the script would be really beneficial. I am a big fan of the ISE add-on for Azure Automation, but this doesn't really offer true debugging features.

    I know this is a tall order and may not be possible, but it's definitely on my wish list!

    25 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  ·  Debugging and troubleshooting  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for posting this suggestion! You are right that this is a larger work item, but something that could really help with debugging. Having your & the community vote for it helps our team prioritize the work though, so even if its a tall order its great for us to get the feedback.

  14. Pause a published runbook to prevent it accepting new jobs

    Today once you publish a runbook there is no way to put it in maintenance mode and prevent new jobs from being accepted. You only choices seem to be to delete the runbook so it is not shown as published (which loses all job history), or comment out the runbook code and publish that version so it basically does nothing. Would like to see a new menu option to Pause or Disable/Enable a published runbook.

    24 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  ·  Debugging and troubleshooting  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  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…

    24 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  ·  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. Remove the 400Mb limit or provide payed option with larger limit

    Our runbooks crash because of the 400Mb RAM limit in Azure Automation. They do not crash when Running on a Hybrid Runbook Worker. The problem with the Hybrid Runbook worker is that it's not a Serverless model with pay per use. It would be good if we could:

    1) Runbooks in Azure Automation that will not crash because of the 400 Mb limit
    2) We can somehow remove the default PS Modules in an Automation Account which we don't need to lower the memory consumption. At the moment these modules cannot be removed.

    23 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  ·  Performance  ·  Flag idea as inappropriate…  ·  Admin →
  18. Start/Stop VM solution for automation accounts should contain Weekday scheduling as an optoin

    At the moment Start Stop VM only supports daily startup/shut down. Whats the point if the work week consist of 5 days . I dont need to fire up the VM's on Saturday and Sunday just to shut them down again.

    23 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  ·  Start / Stop VM  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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

    We're glad you're here

    Please sign in to leave feedback

    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.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Role Based Access Control  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base