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

    345 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 →
  2. Creation of Run As accounts using ARM Template

    Creation of Run As accounts using ARM Template

    307 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  Integration with other products  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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 .

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

    az command cannot be found when using in a runbook

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

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

    129 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    triaged  ·  9 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  7. Python 3

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

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

    69 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 →
  9. 55 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 →
  10. CSP Subscription cannot create Azure Classic Run as Account

    When creating Automation Account in Azure portal, if we use CSP subscription, creating Classic Run as Account is failure.

    Because CSP can access ARM resource only.
    But error message is very unclear.

    - Message
    Azure Classic Run As account creation error

    An error occurred while creating the Azure Classic Run As account for account 'AutomationTest'. Error details: ForbiddenError: The server failed to authenticate the request. Verify that the certificate is valid and is associated with this subscription..

    <Request>
    For resources not available in CSP, please output error including CSP string.

    53 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 →
  11. 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.

    53 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 →
  12. 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%

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

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

    44 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 →
  15. 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…

    44 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Source control integration  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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.

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Debugging and troubleshooting  ·  Flag idea as inappropriate…  ·  Admin →
  17. Extension for VSCode

    Provide a VSCode extension similar to the ISE Addon

    40 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 →
  18. 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…

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  User Experience  ·  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. Signed runbooks for Azure cloud platform worker

    Please add support to run only signed Runbooks so that we can be sure that no modifications are made for our runbooks.
    It should work not only on Hybrid worker as it is now, but also on Azure cloud platform worker.
    We should be able to provide our certificates for signature checks (better via KeyVault integration).

    29 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 →
  20. Start-AzAutomationSourceControlSyncJob Add SyncType parameter to invoke 'Incremental' syncs

    The Start-AzAutomationSourceControlSyncJob function only triggers a FullSync from a connected Azure DevOps Repo, which can sometimes take a long time if you have lots of runbooks in a repo. Can we add a pramater to this to trigger an optional incremental sync?

    Use Case
    The Azure Automation account has this option as a feature toggle but not something that can be triggered ad-hoc after a full sync outside of Azure Automation. We don't want to use the AutoSync feature as we want to control the upload of runbooks via Azure DevOps pipelines with approvals etc. then trigger a sync job…

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Source control integration  ·  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

← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base