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. az cli support in runbooks

    az command cannot be found when using in a runbook

    440 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    22 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  2. Creation of Run As accounts using ARM Template

    Creation of Run As accounts using ARM Template

    429 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    23 comments  ·  Integration with other products  ·  Flag idea as inappropriate…  ·  Admin →
  3. Provide more control of how runbooks are allocated to a sandbox

    There are several scenarios that cause sandboxes to crash or runbooks to fail in both hybrid workers or in Azure.
    1) Sandboxes fail with out of memory randomly. If the wrong combination of runbooks get executed in a sandbox the the sandbox can crash intermittently. If there was a way to control how many jobs run in a sandbox, or flag particular runbox to run by themselves and not share a runbook this problem could be mitigated.
    2) If runbooks land in a sandbox that require different subscriptions one of the runbooks will fail. Someway of preventing this so that…

    358 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 →
  4. 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.

    320 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Hybrid  ·  Flag idea as inappropriate…  ·  Admin →
  5. Bring Azure Automation and DSC to Azure Stack

    Please bring Azure Automation and DSC to on-premises to Azure Stack . This is an important part of the hybrid cloud story.

    This is a copy from here: https://feedback.azure.com/forums/344565-azure-stack/suggestions/11632959-where-is-sma-in-microsoft-azure-stack .

    280 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Integration with other products  ·  Flag idea as inappropriate…  ·  Admin →
  6. Redeploying jobSchedule resource from ARM template

    Currently Microsoft.Automation/automationAccounts/jobSchedules resources cannot be redeployed from ARM template if there are existing jobSchedules pointing to the same runbook and schedule. The deployment would return:

    "A job schedule for the specified runbook and schedule already exists"

    Same issue even deploying with a different name (GUID) for the jobSchedule.

    Currently the workaround is deleting the existing resource and redeploy, which is a very cumbersome approach for automation.

    213 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  8 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  7. Python 3

    Why on Earth was this new functionality introduced using the outdated Python 2?

    176 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  8. Support PowerShell Core as Runbook Type

    I develop on OSX and so use PowerShell Core heavily.

    It's frustrating when Azure Automation Runbooks don't work the same way as they do locally because they run PowerShell 5.

    For example, Invoke-RestMethod in PowerShell Core supports the following parameter:
    -Authentication

    166 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  9. Webhooks ARM Template

    Webhooks from ARM Template still don't work.
    I've seen the schema you're providing: https://docs.microsoft.com/en-us/azure/templates/microsoft.automation/automationaccounts/webhooks
    The PowerShell commandlets first request to generate a token before it is apply in the template.
    When I run the ARM Template with your schema I cannot provide the URI and i get the error: "Invalid uri"

    I know it's a duplicate of https://feedback.azure.com/forums/246290-automation/suggestions/13227531-webhooks-arm-template
    but you've closed the item and it is still not working.

    162 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  10. PowerShell cmdlet to get Runbook context.

    It would be great if you could use in runbook code something like Get-RunbookContext to retrieve the current ResourceGroup and/or Automation Account the runbook is executing in. Then it would be much easier to locate Automation Account Assets like connections and variables without the need to hard-code them into your Runbook. The PowerShell commands available to retrieve and use assets require you to specify the ResourceGroup and Automation Account the asset is stored under.

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

    100 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add possibility to end a test job when it hangs.

    Sometimes when running code in a PS runbook something seems to hang. I'm getting the following error although the job probably finished long time ago:
    "BadRequest: Test job is already running."
    I would like to have the opportunity to clear any running test jobs to bypass this bug.

    98 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support a service tag which denotes the IP address space for Azure Automation

    Currently, we don't support a service tag which denotes the IP address space for Azure Automation service. There are scenarios where a customer would like to allow only the inbound traffic from Azure Automation service by using NSG when a runbook send a HTTP request to a VM. Such customers are requires to whitelist all IP addresses of Azure datacenter. However the customers need to update the settings of NSG every week because there's a possibility that the Azure IP ranges are changed once a week. This requires complicated procedures and high-maintenance. So, it would be great if the service…

    93 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ability to remove jobs from the Jobs history

    The list of jobs quickly gets long and if you play around with some configurations etc and the job fails it will mess up the statistics (and potentially scare some people). So I suggest an option to remove jobs from that list.

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
  15. WebHook Job Monitoring

    Allow people to use the same WebHook Url used for triggering a runbook for querying job status.
    Instead of doing a HTTP POST (used for triggering) you could allow a HTTP GET with the JobId as parameter. This would be a lightweight alternative for consuming runbook results no matter client and platform.
    Note: Using the same url means same access token which leads to monitoring being possible for the lifetime of the access token.

    74 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support Update Management in North Europe

    Log Analytics in North Europe currently cannot be linked to an Automation Account in the same region. In order to deliver update management, VMs will need to register with a Log Analytics workspace in a region where linking to an automation account is supported.
    https://protect-eu.mimecast.com/s/pEoSCxO1iLlov9C8VEom?domain=docs.microsoft.com
    Please could support be added for North Europe?

    65 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  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.

  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.

    65 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. 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%

    62 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Other  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 24 25
  • Don't see your idea?

Feedback and Knowledge Base