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

    47 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 →
  2. CORS support for Azure Automation Webhooks

    It would be great to have the ability to enable CORS on Azure Automation Webhooks to enable quick testing from client-side javascript code. At present, client-side javascript will not be able to make a valid POST call to an Azure Automation Webhook due to the call being across origins. This would also allow lightweight apps to be developed without server-side code, for non-technical interfaces that could front-end complex Azure Automation workflows.

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  3. Please allow for versioned configurations in Azure Automation

    It would be great to have multiple versions of DSC configurations compiled into Azure Automation, simultaneously.

    Currently, a server, or other resource, could be provisioned with one version of a configuration, but if an updated version is compiled during pipeline transitions, they could receive a different configuration than tested in a lower environment, invalidating their tests.

    This would allow someone to target a v1.1.0 configuration, even though the latest is v1.1.3 in Azure Automation, for example.

    It would be doubly nice if this could be derived from Git tags or other versioning mechanism in TFS/VSTS, as well.

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

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

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

    43 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. Outgoing WebHooks

    It would be nice if it was possible to register callbacks for events like "Runbook Status Changed".
    This would allow people to execute runbooks using your existing WebHooks concept (HTTP POST), store the jobid and consume the result of the runbook through the callback once completed.

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  9. Enable Auto-Renew for Automation Run As Account certificates

    Enable Auto-Renew for Automation Run As Account certificates. Right now they expire 1 year after creation and cannot be set to automatically renew.

    43 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 →
  10. Extension for VSCode

    Provide a VSCode extension similar to the ISE Addon

    42 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 →
  11. 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.

    41 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 →
  12. 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.

    40 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 →
  13. 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.

  14. 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),…

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

  15. 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…

    37 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 →
  16. 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.

  17. Make Automation an Azure Trusted Service

    the Azure automation ip range should be added as an Azure trusted service so when I use vnet endpoints on storage accounts, etc and tell it to allow azure trusted services automation works.

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

    36 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 →
  19. 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.

    36 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 →
  20. 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…

    35 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 →
  • Don't see your idea?

Feedback and Knowledge Base