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.

How can we improve Azure Automation service?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • 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

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

    236 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

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

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

    110 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 →
  7. 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.

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

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

    66 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 →
  10. 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.

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

    56 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 →
  12. 55 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 →
  13. 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.

    50 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 →
  14. Python 3

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

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

    46 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 →
  16. Support populating and displaying arrays for account-level Variables

    While it's possible to set arrays with Set-AutomationVariable, they cannot be displayed or edited from UI.
    It makes them a bit inconvenient - if I have a job that I need to execute against a set of something, I need to have separate jobs to validate and change that set.

    45 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 →
  17. Please allow for versioned configurations in Azure Automation

    It would be great to have multiple versions of DSC configurations compiled into Azure Automation, simultaneously.

    Currently, a server, or other resource, could be provisioned with one version of a configuration, but if an updated version is compiled during pipeline transitions, they could receive a different configuration than tested in a lower environment, invalidating their tests.

    This would allow someone to target a v1.1.0 configuration, even though the latest is v1.1.3 in Azure Automation, for example.

    It would be doubly nice if this could be derived from Git tags or other versioning mechanism in TFS/VSTS, as well.

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Desired State Configuration  ·  Flag idea as inappropriate…  ·  Admin →
  18. Outgoing WebHooks

    It would be nice if it was possible to register callbacks for events like "Runbook Status Changed".
    This would allow people to execute runbooks using your existing WebHooks concept (HTTP POST), store the jobid and consume the result of the runbook through the callback once completed.

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

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Webhooks  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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 →
← Previous 1 3 4 5 19 20
  • Don't see your idea?

Feedback and Knowledge Base