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. The way updating the certificate for Run As account should be more flexible

    Currently, the self-signed certificate that you created for the Run As account expires one year from the date of creation and the certificate won’t be automatically updated. Although you can set your certificate to expire a very long time by using Azure PowerShell, some users wonder that it will be a security issue if such a long certificate leaks. Such users are required to update the certificate every year before it expired. It would be great if the operations to update a certificate could be flexible as follows so that the uses can omit the troublesome procedure, which is updating…

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  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.

  2. Issues scrolling with mouse wheel in runbook editor

    I'm currently having issues using the mouse wheel to scroll, in firefox, while editing a PowerShell-based runbook. I've not tried it with any other runbook types, but I presume the issue would persist.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  3. Please make the label for each activity display more characters and lines

    In runbook designer, the label for each activity is too small in length, only allows 11-15 characters, could you please make it allow more characters showing. This will help to know what each activity does at a glance in runbook designer.

    Currently the words wrapped and cut off. it is hard to read especially when calling child runbook, we want to know what child runbook name is , but it wrapped and cut off, we will have to click it to display the whole label.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  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

  4. assign a schedule to runbook via ARM templates

    I'm in the middle of automation and deploying runbooks/schedules via ARM templates but couldn't find the option to link schedule to runbook.
    i tried with "type": "Microsoft.Automation/automationAccounts/jobSchedules", but didn't work

    could you please check and provide some suggestions?
    thanks
    ak

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  5. Fix New-AzureRmResourceGroupDeployment module to read the parameter 'name' from json correctly

    In my case i must to change the name of parameter 'name' from template.json and parameters.json.
    I downloaded a Service Plan Automatetion Script and changed the parameter name from 'name' to 'servicePlanName' to make it works, else PowerShell prompt this...
    nameFromTemplate:

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  6. It would be nice to remove the old entries for Update Deployments in update management solution for presentation purposes

    It would be nice to remove the old entries for Update Deployments in update management solution for presentation purposes.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  7. Enable Ctrl + s in powershell editor

    It's nice to have the powershell editor and see how it supports useful capabilities like code comments through keyboard shortcuts. (Ctrl + k c), however, it would be even better if it supports Ctrl + s to save the script (currently it opens a window to save the whole webpage...), that would make the editor even more intuitive.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  8. Assign DCS Multiple Node Configurations to a DCS Node

    Would be nice to be able to assign multiple DCS node configurations to a DCS node, i.e. the same way we can have multiple GPO assigned to an OU.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  9. ctrl+s to save

    When editing a workbook, ctrl s should save the workbook, instead of having to press the save button

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  10. Test Pane should show what's actually happening

    Currently the test pane only shows the output that specific commands write, but if a command isn't writing anything, there's no way to know where in the script the problem is occurring. Similarly with issues, if something is endlessly looping, there's no way to know what or if it's just very slow.
    The test pane should either be a proper step through of the script (highlighting the running command along with the output) or show it like the commands were typed into the PowerShell window itself.

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

    Thanks for posting this suggestion!

    There are a couple of existing features that may get you most of what you are looking for.

    1. While we do not have a debug mode where you can step through your runbook and see output, we do have an Add-On for the ISE and you can debug your runbooks in the ISE. http://www.powershellgallery.com/packages/AzureAutomationAuthoringToolkit/0.2.3.1

    2. If you are using graphical runbooks, there are settings that you can turn on to show exactly what is happening and what command ran with it by turning on additional logging. Select your graphical runbook > Settings > Logging and Tracing > turn on Verbose and change Trace Level to detailed to get the level of detail you are looking for.

    3. For scripts, you can set your verbose preference to continue (instead of silentlycontinue) in your runbook to debug and write to the verbose stream. $VerbosePreference =…

  11. Ability to rerun a job with same parameters of the last job

    The feature I propose is a 'Rerun Command’. I have a ‘crude’ mockup attached. Clicking on Rerun would bring up the Start Runbook blade; but with the parameter values prepopulated with the same values from the previous execution. I can now modify any value, if necessary, or just click OK, to start the job quickly.

    I see myself rerunning my runbook with mostly the same values. When I have many input parameters, I have to be very careful not to mess up any values, and what I do now is open two browser windows. Open the previous job’s Input blade…

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  12. Refresh of Portal Automation Views

    With the ability to author via the ISE add-on, it is easy for the portal to get out of sync quickly with the actual data. Would like to see refresh buttons on all relevant blades or a triggered server-side refresh to keep the portal in sync as changes to underlying runbooks are made externally.

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

    Thanks for this feedback. What are the most important blades or resources to add a refresh button to?

  13. Display Parameter Help Messages in UI

    When using [Cmdletbinding()] along with parameter property Helpmessage and [ValidatePattern()] it would be nice if these messages were fed back to the user interface. Right now the users have to guess what the parameter allows them to input through trial and error.

    For example:

    [code]

    [Cmdletbinding()]
    param (

    [Parameter(Mandatory=$true),HelpMessage='Enter 1 computername']
    [ValidateNotNullOrEmpty()]
    [string] $Computer
    )

    In the console, when referencing a workflow with this parameter set you could enter !? to get the help message.

    37 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

    Thanks for the feedback! We will look at making these modifications to starting a runbook job.

  14. Support populating and displaying arrays for account-level Variables

    While it's possible to set arrays with Set-AutomationVariable, they cannot be displayed or edited from UI.
    It makes them a bit inconvenient - if I have a job that I need to execute against a set of something, I need to have separate jobs to validate and change that set.

    45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  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
    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 →
  16. Provide notification when global modules are changed in the automation account

    Today global modules can be added and updated without any prior notification by the Azure Automation team. In certain scenarios these changes cause issues with existing code used in the account. A simple banner in the automation account indicating which modules were updated would facilitate troubleshooting efforts.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  17. Sorting Filtering Runbook list

    It would be great if there was a way to sort/filter runbooks in the Azure Automation Runbook definition table. I envision being able to sort and filter each column, as well as a table-wide search function.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  18. change tracking "Manage Machines" is grayed out after onboarding

    change tracking "Manage Machines" is grayed out after onboarding.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  19. Increase Custom field limits for Log type AzureDiagnostics

    Currently there is a 500 custom field limit to Log types. Turning on diagnostics for Data factory V2 quickly fills this limit to the maximum on AzureDiagnostics which is used by multiple services / providers.

    Can we have the limit raised, or suffix the log type with the service / provider or resource name to help overcome this. If the limit is reached, critical diagnostic events can be lost.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow adding a message to a change

    When making an edit to a runbook, it would be useful to be able to add a message to that change, e.g. "Fixed bug on line 22"

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base