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. PowerSTIG Module Import in Azure Automation

    The PowerSTIG module is unable to be imported using the Azure Automation blade inside the Azure Portal. I would like to have the ability to import the PowerSTIG module and all required dependencies via the Azure Portal. Currently, to get this to work all required dependencies have to be imported using PowerShell.

    73 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  ·  Flag idea as inappropriate…  ·  Admin →
  2. Create an IP to report on DSC drifts / compliance

    PowerShell DSC is currently poor in reporting on configuration drifts and compliance levels. Collect this data in Ops Insight to answer questions like:
    - which systems are experiencing a configuration drifts and for which DSC policies?
    - which is the compliance level for this specific DSC policy / setting?

    72 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add native support for job concurrency control

    Certain runbooks must not have more than one concurrent job instance running at any time. Although we have some workarounds using helper runbooks / job queue tables, including this natively as we had it in SCORCH would really help, as the workarounds do not guarantee the behavior 100%

    68 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    67 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 →
  5. 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.

    63 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  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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!

    63 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 →
  7. 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…

    62 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  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  8. 61 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  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    59 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  ·  PowerShell authoring  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.

    58 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  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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…

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

    We are bringing in support for Managed identity in Azure Automation which would be the recommended way going forward for authentication & get over the issues\overhead associated with managing RunAs cert.
    ETA :March-End\Early April CY21.

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

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

    54 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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.

    54 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  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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.

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

    53 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  ·  User Experience  ·  Flag idea as inappropriate…  ·  Admin →
  17. Assign dedicated IP address(es) to Azure Automation Accounts/Runbooks and Functions

    Currently, network connections opened in a runbook have the source IP address anywhere in the address space of a particular datacenter. If the destination of the network connection is protected by a firewall, such as for example on an Azure SQL Database server or an SFTP server, it requires opening the firewall to allow connections from the entire datacenter, which is unacceptable for a security conscious Azure tenant.

    For many tenants, this will block the very promising scenario of using Azure Automation runbooks to run scheduled jobs connecting to infrastructures that are protected in such a way.

    The request is…

    52 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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.

    50 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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.

    49 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  ·  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.

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

    48 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Start / Stop VM  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base