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. Right sentance of Remove-HybridRunbookWorker

    In this case for remove a VM from gybrid group"Remove-HybridRunbookWorker -url <URL> -key <PrimaryAccessKey> -machineName <ComputerName>" You must use a FQDN full name of VM

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  2. Organize runbooks with a folder like structure in the runbooks view

    Add the ability to organize runbooks into folder / categories in the Runbooks view under automation accounts.

    1 vote
    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 →
  3. Add Support for Newtonsoft.Json.dll v10 or higher

    Currently, Azure Automation requires v6 of Newtonsoft.Json.dll. Certain Powershell modules used in automation (in this case, VMWare's PowerCLI) utilize newer versions of Newtonsoft.Json.dll. In this scenario, the cmdlets which rely on this newer version of the .dll will fail to execute when ran under AA due to AA requiring the older version. Similar issues are outlined in Azure SDK feedback on Github here:

    https://github.com/Azure/azure-sdk-for-net/issues/4380#issuecomment-415025767

    An Azure support ticket was created for this issue:119103124005441

    PowerCLI specific error:
    Get-ContentLibraryItem Could not load file or assembly 'Newtonsoft.Json, Version=10.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The system cannot find the file specified.

    6 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 →
  4. Support expirationDate alias for Microsoft.Automation/automationAccounts/certificates in Policy

    It would be great if you could expose an alias for expirationDate for the Microsoft.Automation/automationAccounts/certificates resource type through Azure Policy. Some example use cases:
    1. Create a policy that audits when a cert is less than X days from expiring
    2. Create a policy requiring certificates be only valid for 30 days (for example, to require consistent rotation)
    3. Create a policy requiring certificates to be valid for at least 2 year (if an org requires longer cert lifetimes)

    Microsoft.Web/certificates exposes this already through the expirationDate alias.

    2 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 →
  5. Add VMSS to start/stop VMs in off hours

    Can we add functionality to start/stop whole VMSSes?
    At present only regular VMs can be started/stopped, this would be useful for example for test AKS clusters which are backed with VMSS rather than VMAS.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Start / Stop VM  ·  Flag idea as inappropriate…  ·  Admin →
  6. update modules to latest in python 2 runbook

    The modules in automation account - python2 runbook are not latest.
    Tried with ComputeManagementClient.virtualmachines.apiversion it returns "2016-04-30-preview", which latest version is "2019-07-01" as your document.
    Please upgrade modules ASAP.

    1 vote
    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. Fix dependencies automatically during modules import

    During Az modules import I have to fix all dependencies manually.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Gallery  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add Authentication Key to Webhooks for secuirity.

    Automation webhooks can be called without any sort of authentication.

    If there was an option on each runbook for a key (Azure generated or user input), that would be great for security.

    We have to consider that anyone in the world can attempt to run our webhooks, and we add a significant amount of verification to ensure the webhook was executed it was from a legitimate source.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  9. HRW will not actually operate at an Elevated Level

    There is a “Known Issue” where the HRW will not actually operate at an Elevated Level and can get caught by UAC. Delegating explicit permissions from the credential resolves the issue.

    1 vote
    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 →
  10. 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 →
  11. AZURE Auto Run Book certificate annual renewal user notification and alert

    please provide 30-day advance notification to renew run book certification to the user so the run book script won't fail otherwise the user has any way of knowing and the certificate will expire; therefore, the script will fail to run thus generates more compute hours which will result in more charges to the user.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Resource Health for Azure Automation

    Azure Automation does not have Resource Health like as Virtual Machine.
    In Oct 25 to Oct 28, huge issue for Automation has occurred. 'Service Health alert' generated after Oct 28.
    If there is Resource Health for Azure Automation, we can know the issue happens in Azure Automation.
    Do you have a plan for using Resource Health?

    0 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 →
  13. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Linux support  ·  Flag idea as inappropriate…  ·  Admin →
  14. azure automation after renewing certificate old cert is kept for 90 days which if exported provides persistence and a security vulnerability

    azure automation after renewing a certificate the old cert is kept for 90 days which if it was exported before the renewal can still be used to authenticate as the security principal this provides persistence and a security vulnerability. It's retention is described under https://docs.microsoft.com/en-us/azure/automation/automation-managing-data#data-retention Please enable the deletion of renewed certificates before the 90 day retention period

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Authorize emails Send from an Azure Automation runbook (Direct Send)

    Emails sent using either PS Send-EmailMessage (Direct send no credentials) are landing in spam folder, we need a way to authenticate/authorize them properly to ensure we can leverage automation for notifications purposes

    https://docs.microsoft.com/en-us/exchange/mail-flow-best-practices/how-to-set-up-a-multifunction-device-or-application-to-send-email-using-office-3#option-2-send-mail-directly-from-your-printer-or-application-to-office-365-direct-send

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Update script to create runas account using Az module

    Script "New-RunAsAccount.ps1" from: "https://docs.microsoft.com/en-us/azure/automation/manage-runas-account#prerequisites", stay using AzureRM modules, and when I tried to change cmd-let it's didn't work.
    Here the erros i got:
    First one:
    Import-Module Az.Profile
    + CategoryInfo : ResourceUnavailable: (Az.Profile:String) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

    Another error:
    .\New-RunAsAccount.ps1 -ResourceGroup $RGAutomationName -AutomationAc ...
    + CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-RunAsAccount.ps1

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add SupportsShouldProcess (WhatIf) Support

    Currently there is no way to utilize the CmdletBinding(SupportsShouldProcess) functionality in runbooks. The current way to add this type of functionality is to create your own [bool]$WhatIf parameter and use if/else statements.

    This means that existing scripts must be re-written (going a step backwards), and it adds increased complexity to runbooks.

    Please automatically add the WhatIf and Confirm parameters when CmdletBinding(SupportsShouldProcess=$True).

    https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/aboutfunctionscmdletbindingattribute?view=powershell-6#supportsshouldprocess

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell cmdlets  ·  Flag idea as inappropriate…  ·  Admin →
  18. Issues scrolling with mouse wheel in runbook editor

    I'm currently having issues using the mouse wheel to scroll, in firefox, while editing a PowerShell-based runbook. I've not tried it with any other runbook types, but I presume the issue would persist.

    3 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 →
  19. Restrict Azure RanAs account permissions to a specific Resource Group and/or Subscription

    Restrict Azure RanAs account permissions to target just one subscription and/or resource group. This account can impact servers across all subscriptions with running sensitive Runbooks.

    3 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 →
  20. Setup DevOps SourceControl sync as a AzureADApp service principle

    I would like to list two issues and possibly can be addressed by one implementation.


    1. Would like to setup sync between Azure Automation Account and DevOps as an Azure AD APP service principle and/or managed identity of automation account, rather than a person or on-prem service account.


    2. Would like to access files from DevOps Repository (e.g latest ARM templates) as a REST call using managed identity/service principle.


    Above is very important as people leave organisations and can leave broken process behind and the worst is, the organisations would not know until something drastic happens.

    Please see the issues below in…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 21 22
  • Don't see your idea?

Feedback and Knowledge Base