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. 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 →
  2. Move "Run on" to runbook settings

    It doesn't make sense to have "Run on" dynamically selecteable. Please move it to "Runbook settings" so that we can do a one-time configuration of whether a runbook should run using hybrid workers or cloud-based workers.

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

    22 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 →
  4. Hybrid Worker Maintenance

    It would be very helpful to have the ability to "pause" a hybrid worker so that it can complete any running jobs without accepting new jobs. This would allow the worker to become passive for maintenance/patching.

    We could then automate the rolling maintenance between hybrid workers to ensure availability and zero runbook downtime.

    14 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  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  5. The Automation Operator account should also have permission to read Hybrid Worker Groups

    Having the Automation Operator see what machines are in each group would help him figure out where to start the jobs.

    7 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  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  6. Register-AzureAutomationScheduledRunbook does not support assigning to hybrid worker

    Register-AzureAutomationScheduledRunbook does not support assigning to hybrid worker. it is only possible via the GUI and ARM.

    6 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  ·  0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  7. Provide a change log for agent updates to Hybrid Runbook Workers

    Agent updates is being pushed regularly to Hybrid Runbook Workers, but customers have no insights into how often this occurs and what the changes are. After being bitten by a bug related to downloading Assets to a Hybrid Runbook Worker, we can see the need for having insights into agent updates in order to possibly correlate them to issues such as the one we ran into. Ideas for ways to provide this information can be an RSS feed and/or a PowerShell cmdlet in the HybridRegistration or AzureRM.Automation modules.

    3 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  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for this suggestion and sorry that you were affected by a bug. Right now, we are posting any major updates to Service Updates announcements so that is a good place to look. This wouldn’t contain every single update though, so we will take this suggestion into consideration.

  8. HybridWorker servername in logs

    Seeing that the new functionality of importing Azure Automation logs directly to OMS, it would be nice if the logs contained the name of the HybridWorker is has been running on.

    Our environment consists of 4 HybridWorkers as of now - and to be able to troubleshoot, we need to know exactly what server a runbook has been executed on.

    Right now, we use on-prem logging besides the OMS part - with some custom way to fetch the servername.
    If we can get servername in the OMS logs too, we can totally skip our on-prem logging.

    2 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  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  9. Testing on Hybrid Worker - Run Settings does not remember run location

    In the testing console, the inputs are remembered when the testing console is opened again, but the Run Settings already reset to "Azure" even if it had been tested on "hybrid worker" the last time it was open

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for this suggestion! We will investigate remembering the last run on setting for hybrid.

  • Don't see your idea?

Feedback and Knowledge Base