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.
-
Schedule exclusions
It would be nice to be able to exclude specific dates from schedules. For instance one might want to schedule a runbook every Friday of the month except on Friday 13th or if the Monday of the month is the 1st of that month. (like we could do in Orchestrator)
31 votesThanks for posting this! Moving to “Under Review”.
-
edit parameters of automation job
I would like to edit the parameters of an already scheduled Automation job. Currently (9/21/2020), I can see what those parameters are, and I can always unlink and re-link after typing all those parameters in again. I want to just change one parameter though, not all of them.
Sometimes someone might ask me to make a small change this particular run to the job, expecting me to only have to change one particular parameter. In reality, I'd have to change all of them. Just this past weekend, this re-typing of all parameters caused the whole job to fail, also eroding…
29 votes -
Allow monitoring runbooks like orchestrator
Allow for "monitoring" runbooks like orchestrator does, without minutes charge or provide this only for hybrid workers. It makes no sense in running runbooks 24 hours waiting for a condition before the actual magic starts and being charged for the entire day.
Having this option free of charge on hybrid workers would be a great improvement, since we pay for the computer onprem this makes sense.Without this option it is a half solution where we need to run scripts or on prem solution to monitor for a condition and after this send out the webhook call which than again…
19 votesThanks for this suggestion. We will take it into consideration.
-
Possibility to use the same schedule multiple times with the same runbook with different parameters
And it should be possible to tweak the name of the individual scheduled instances to reflect the parameters used.
15 votes -
Enable scheduling for AKS cluster shutdown.
Customers has confirmed a need to have an option to schedule AKS clusters resources to be shutdown and started.
10 votes -
Yearly schedule interval in Azure Automation
I would like to see a yearly option when going to schedule run books in an Azure automation account.
9 votes -
startup
why not to add "startup" function instad of only "shutdown" in VM manager?
I can use automation, but almost run error. it's too hard to use. I hope new feature of "auto start up" VM for the next times.
Thank you!
8 votesWe are looking at simplifying the automation scripts used for starting and shutting down VMs in your subscription so hopefully that will make it easier to use. We will update with the status here once we have a solution in place.
Thanks for the feedback. -
Fix the Runbook Schedule Unlink User Experience
Linking a runbook schedule is a relatively poor experience. Trying to UNLINK a schedule requires a support ticket to learn how to do it. You MIGHT think that using the "Schedule" menu at the top of a runbook would allow you to link and unlink schedules to the runbook. No.. you can only link. To UNLINK, you have to use the "Schedules" menu at the left and then (get this for obscurity) click the existing schedule, then click "...more" and then the "Unlink" option appears.
Why on earth can't I manage the linking AND unlinking from the same place? Please…
7 votes -
IN VM shedule add both start and shutdown with a recurring week shedule (avoiding more complex runbook use)
The shutdown shedule is easy. Adding startup needs use of runbooks. Why not adding startup and shutdown with a recurring weekly shedule to allow easy cost saving by aligning the server use with the opening hours.
6 votes -
Option to remove onetime schedule when completed
I have a runbook that schedules itself to run again one hour after it completes. It does this by creating a onetime schedule. The reason for doing this rather than using a regular (i.e. not a onetime) schedule is to prevent the runbook from starting while the previous job is still running (I discussed this approach with Joe Levy here: http://social.msdn.microsoft.com/Forums/en-US/06f1b011-1fe2-4a3a-a0a3-88256f83a3ea/can-i-prevent-multiple-instances-of-the-same-runbook-from-running-concurrently?forum=azureautomation)
Unfortunately this means that my Assets screen becomes littered with expired onetime schedules (22 or 23 every day) and there's no simple way to go and clean them all up.
Hence this request is for an option on…
6 votesThat’s an interesting idea – thanks for the feedback. We can look into it.
In the meantime, you could probably work around this. I’m not exactly sure what your runbook looks like, but it might make sense to create the schedule with the same name each time, then when the runbook starts again to delete that schedule, then to create it again at the end.
-
Schedule for Day of the week
Customer wants to configure schedule about Day of the week.
For example, customer wants to set execution at Second Tuesday.Cx will apply Windows Update at Second Wednesday, so before update, they want to execute Runbook.
Is there a plan for this configuration?5 votesThanks 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.
-
Ability to Schedule based on weekday/week of month
It would be really handy to have the ability to schedule Update Management deployment schedules based on the day of the month, i.e. schedule an update on the third Tuesday of the month, recurring monthly, etc.
5 votes -
Possibility to name scheduled instances of a Runbook
It should be possible to name the scheduled instance of a runbook to, for example, reflect the parameters used for that particular schedule
4 votes -
Add the ability to use CUT/UTC in Automation schedules
Azure now forces all time inputs for scheduling to be in a time zone, which adjusts for Daylight Savings time. Automations that target other Azure services that use UTC only for scheduling will change relative times twice a year.
Please add a "UTC" option on the Time Zone dropdown to allow a UTC-based scheduled time with no Daylight.
4 votes -
Decouple the Date and Time for automation schedules
When creating an Automation schedule with the ARM template, startTime take a full date and time as a value. But in time, this value varies. For a runbook that run once each days, only the hour is constant. To keep my template up to date, I need to pass parameter for today and merge whith the hour of execution.
A better approach is like the Scheduler Jobs with his Recurrence parameter. It cover most needs and are more easy to use.
4 votes -
link schedule to runbook via ARM templates
how i can link a schedule to runbook via ARM templates?
Please assist.Thanks
ak3 votes -
Schedule update deployement Recurring
Schedule update deployment schedule setting should have option to stop/suspend for recurring deployments. This is required for scenarios like suspending the deployment for specific month and continue it for other months.
3 votes -
Schedule patching using OMS for Linux server like list of same patches need to deploy on dev and prod environment in different week
We need to install patches/updates on Linux Server in below scenario:
- we will fetch list of patches on 3rd/4th Monday of every Month on Development server
We need to install only patches we fetched on 3rd or 4th Monday to be installed in Development server
We need to install only patched we fetched on 3rd or 4th Monday to be installed on Production server after 2 weeks of development server patching
3 votes -
Visualise schedules in a calendar view
Display historic runbook executions like a calendar appointment to visualise runbook executions that might occur at the same time. Future executions could be displayed using historic average runtime or default values to illustrate possible future scheduling conflicts.
3 votesThanks for the feedback. This would be a nice addition.
-
1 vote
- Don't see your idea?