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.18 votes
Thanks for the feedback . The Product team has identifed this as one of the enhancements and improvement area in the service. It will be picked up as resourcing allows.
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.7 votes
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?