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. Verbose output missing when using Invoke-Command on a Hybrid Worker

    From a PowerShell script in a runbook on a Hybrid Worker verbose output gets dropped when calling Invoke-Command.

    For example, my script could be:

    Write-Verbose "Hello from the Hybrid Worker computer" -Verbose

    Invoke-Command -ComputerName remoteServer -ScriptBlock {
    Write-Verbose "Hello from [$(hostname)]" -Verbose
    }

    In the example above the first verbose message is seen but the second is not.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  2. Utilize the same Automation hybrid runbook workers across multiple Automation accounts under the same subscription.

    Utilize the same Automation hybrid runbook workers across multiple Automation accounts under the same subscription. Currently its a 1to1 link between an automation account and a runbook worker. This means I have to create a new runbook worker for each automation account.

    197 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  3. Is it possible for RunBooks to always run hybrids from a schedule?

    I do not see in the documentation how I can configure a runbook to always run hybrid

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the valid suggestion. Your feedback is now open for the user community to upvote which 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. Import-PSSession is not working for Enable-RemoteMailBox. Example : $Session = New-PSSession -ConfigurationName Microsoft.Exchange -Connecti

    Import-PSSession is not working for Enable-RemoteMailBox.
    Example :

    $Cred2 = Get-AutomationPSCredential -Name 'Credentials'

    $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://OnPrem-ExchangeServerURL/PowerShell/ -Authentication Kerberos -Credential $Cred2

    Import-PSSession $Session -AllowClobber

    Enable-RemoteMailbox -Identity $Email -RemoteRoutingAddress $SamAccountName@tenantname.mail.onmicrosoft.com

    This commands fails to start the session - It stays into loop and does import the session.

    Eventually, I want to import session in exchange server and change the mailbox to Remote via Enable-RemoteMailBox

    Error Message:
    The names of some imported commands from the module 'tmp_yd05zbqm.wbf' include unapproved verbs that might make them
    less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with…

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

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

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

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

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  9. Increase maximum amount of concurrent jobs on a Hybrid worker

    It would be nice if it is possible to increase the amount of concurrent azure automation jobs on a single hybrid worken. At this moment the limit is 50 jobs.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  10. Ability to specify a default hybrid worker group

    The Automation Administrator should be able to specify a default hybrid worker group for all runbooks as well as a per-runbook default hybrid worker group.

    16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  11. Hybrid Workers should not require WoW64-Support

    Hybrid Runbook Workers require WoW64-Support to function.

    Worse still, there appear to be absolutely no errors reported anywhere regarding why runbook jobs won't start.

    Event a simple "Hello World!" job remains in Queued and quietly transitions to Suspended. There are zero logs shown in the Automation/Runbook blades and zero logs shown on the hybrid worker.

    Re-adding WoW64-Support feature allows runbooks to start again.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  12. Runbook Execution and MMA Proxy settings

    Runbook Execution on the hybrid runbook worker currently uses the MMA Proxy settings. This should be an option that can be enabled or disabled.

    You can use New-WebServiceProxy to connect to an internal server with the proxy configured in the MMA to reproduce this issue.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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.

  17. hybrid worker should use configured proxy

    Currently the hybrid worker doesn't use proxy settings from MMA, this forces the hybrid worker to be NATted, and slows deployments in certain security sensitive environments. For some calls it doesn't use the specified credentials for others doesn't use the proxy at all (for example all the communications to port 30004)

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

    Proxy support is now available for PowerShell script runbooks. PowerShell Workflow Runbooks will be targeted next.

  18. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    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