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 a "premium" SKU for Automation Accounts without/increased limits

    It would be very useful to have an automation account with either dedicated sandboxes and/or sandboxes with increased maximum limits, especially for memory and network sockets.
    Furthermore, the current way of assigning jobs to a sandbox is unpredictable, resulting in jobs to randomly fail.
    Using Hybrid Workers requires maintaining VM(s), which a lot of customers are trying to avoid when migrating their infrastructure to Azure.

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

  2. Remove the 400Mb limit or provide payed option with larger limit

    Our runbooks crash because of the 400Mb RAM limit in Azure Automation. They do not crash when Running on a Hybrid Runbook Worker. The problem with the Hybrid Runbook worker is that it's not a Serverless model with pay per use. It would be good if we could:

    1) Runbooks in Azure Automation that will not crash because of the 400 Mb limit
    2) We can somehow remove the default PS Modules in an Automation Account which we don't need to lower the memory consumption. At the moment these modules cannot be removed.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Performance  ·  Flag idea as inappropriate…  ·  Admin →
  3. How about making test runs faster than what I could do in the frickin' '70's on vacuum tubes?

    How about making test runs faster than what I could do in the frickin' '70's on vacuum tubes? This "Queueing" BS isn't going to get it. Sonn, there will be an ENTIRE generation people- starting with the "Millennials", who will have NO CLUE what high performance computing is.

    "Queuing". That is a FRICKING laugh.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Performance  ·  Flag idea as inappropriate…  ·  Admin →
  4. priority option for powershell workflow

    It isn't reliable enough to know, that a workflow will start some time after it is triggered.
    For example: a Workflow triggered by a webhook starts in between two or ten minutes. So one can not calculate with the result of the runbook.

    Please add a option to start a workflow immidiatelly (and charge it double for example) or with extra power so we can count on it.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Performance  ·  Flag idea as inappropriate…  ·  Admin →
  5. Test Pane Output is really slow

    The output area of the test pane is terribly slow:

    Testing scenario: I created a code block setting VerbosePreference to "Continue" and then calling "import-module ConfigurationManager", that code is then run on a HybridWorker on premise. That import-module command produces about 900 lines of output (various import- and export messages)

    Result:

    - Without verbose messages it takes 2 seconds
    - With verbose messages it take 8 minutes
    - Opening the test pane (which shows the old test output) takes multiple minutes as well

    I think there is some room for improvement here ...

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Performance  ·  Flag idea as inappropriate…  ·  Admin →
  6. Show Minutes for each runbook to complete

    Each runbook should show how many minutes it took to complete. This is what we are being billed for. It should be the top and center for every runbook. There should also be average and a forecast based on current schedule.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Performance  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Beth Cooper responded

    Thanks for this suggestion. You can calculate it based on job start and job end times, but makes sense for us to show the calculated runtime in the portal as well.

  • Don't see your idea?

Feedback and Knowledge Base