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. Continuous Deployment of runbooks

    I have runbooks that are stored in source control which then get deployed to Azure Automation. The process of deploying them is rather cumbersome (basically a bunch of hand crafted Powershell scripts that call the Azure Automation cmdlets). It seems to me that there are going to be lots of people crafting the same kind of scripts - that's a lot of wheel-reinvention going on.
    I'd like to see some features introduced that support quick and easy Continuous Deployment of runbooks (i.e. I check them into source control and they automatically get deployed to Azure Automation).

    Some ideas:
    -Support Continuous…

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add bitbucket support to Azure Automation

    Add bitbucket as a supported source for Azure automation under the 'source control' pane. Currently only TFS and GitHub are supported.

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

    41 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 →
  4. Provide better exception messages in Azure Automation

    Exceptions are currently only surfaced by the exception message string. Please give us richer exception messages for Powershell-based runbooks, such as file name, line number, etc. Ideally I'd like to get a "regular" exception object back using Azure Powershell.

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Debugging and troubleshooting  ·  Flag idea as inappropriate…  ·  Admin →
  5. Extension for VSCode

    Provide a VSCode extension similar to the ISE Addon

    40 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 →
  6. Start/Stop VMs during off-hours for CSP Azure Subscription

    The latest scripts are working fine for CSP Azure Subscriptions (as of 2018-06-10)

    But each job run throws lot of job errors with message content like:

    Get-AzureVM : ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and
    is associated with this subscription.
    At line:168 char:16
    + $currentVM = Get-AzureVM | where Name -Like $filtervm.Trim() ...
    + ~~~~~~~~~~~
    + CategoryInfo : CloseError: (:) [Get-AzureVM], ComputeCloudException
    + FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.GetAzureVMCommand

    Job: ScheduledStartStop_Parent

    CSP based Azure subscriptions have no ASM functionality

    39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  7. Allow DSC Reports to include ResourcesNotInDesiredState that were corrected during a consistency check

    Currently if a node is set to ApplyAndAutoCorrect, when the report is sent back to the report server, there is no reference to any resources that were non-compliant at the time of the consistency check. DSC will auto correct without reporting what it did. For compliance reasons, we would like to be able to query the report server to see if any resources had to be put back into desired state. We would like DSC to report non-compliance like it does when using ApplyandMonitor mode prior to auto correct.

    Here is the link to the same request on the PowerShell…

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

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

  9. Add VSTS Integration for Azure Automation

    Activate the VSTS (and TFS) Integration at source control in Azure Automation.

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

    35 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 →
  11. Azure Automation should support using pre-existing Service Principals for RunAs connections

    Currently the only *supported* method for adding a RunAs connection to an Azure Automation account is to create a new Service Principal. By default the SP is created with Contributor access to the entire subscription.

    This is not ideal for several reasons:
    * Contributor access to a subscription is a relatively high level of access. I would like to ensure that my automation accounts are more tightly constrained.
    * The auto-generated name for the SP can cause problems in accounts that have applied a naming standard/governance model to SP accounts.
    * Since we are unable to reuse our existing SPs…

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Role Based Access Control  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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),…

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

  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.

    34 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. multiple powershell module versions in automation module

    We can't have multiple version of a powershell module in automation.

    We develop some DSC resources and we using in different configuration of project but sometime we havnt the same version in each configuration. Like old configuration for project1 with xPSDesiredStateConfiguration with 4.0.0.0 and new configuration for project2 with xPSDesiredStateConfiguration version 6.2.0.0 .
    So each time we want to compile we need to upload the old or new version. It's not working like a nugget server keeping old version.

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
  15. start/Stop VMs during off-hours

    Current start/Stop VMs solution in preview seems not so flexible due to the current limitaion/restriction and the use of the asset variables. Example:

    1) Not allow to create multiple schedules to stop and start for different servers at different timezone in the same automation account. The Resource group and servers exclusion lists are all defined in the variables. Correct me if I’m wrong, in order to have the above solution in place, we need to have multiple automation account in place.

    2) Not possible to set any specific date to exclude the job being triggered. For example we need the…

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Start / Stop VM  ·  Flag idea as inappropriate…  ·  Admin →
  16. Create a native SCSM Azure Automation connector

    System Center Service Manager (SCSM) only has connectors to SMA and Orchestrator. To be able to shift to Azure Automation for all our automations there have to be an Azure Automation SCSM connector. Please add this soon!

    32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Integration with other products  ·  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…

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow description/instructions of parameters to be seen by person starting a runbook

    I have a PowerShell runbook that requires input for several parameters. I'd like to customize the text here when someone starts the runbook. For example, to let the automation operator know that this input is required to be less than 10 characters, or must have numbers, etc. This looks similar to these:
    1) https://feedback.azure.com/forums/246290-automation/suggestions/6560476-display-parameter-help-messages-in-ui
    2) https://feedback.azure.com/forums/246290-automation/suggestions/10921377-open-up-for-helpmessage-and-validation-to-be-suppo

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  PowerShell authoring  ·  Flag idea as inappropriate…  ·  Admin →
  19. Schedule exclusions

    It would be nice to be able to exclude specific dates from schedules. For instance one might want to schedule a runbook every Friday of the month except on Friday 13th or if the Monday of the month is the 1st of that month. (like we could do in Orchestrator)

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Scheduling  ·  Flag idea as inappropriate…  ·  Admin →
  20. Support other mainstream, cross-platform scripting language like Python and Ruby

    Other cross-platform languages like Python and Ruby have served as automation and orchestration scripting languages of choice for much longer than PowerShell. A large community of users already know and use Python on Windows, Linux, and Mac systems. Its okay to invent something new with Powershell, although it would be even better to embrace and support existing languages like Python for IT Automation.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell authoring  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base