Scheduling a Runbook multiple times with different parameters
It would be nice, if one runbook could be sceduled multiple times. Its need with runbooks are parameterized (eg, delete resources with this tag at this time and with that tag once a week).
Unfortunately there are not resources to work on this request, so we are closing it to give you heads up. We appreciate your feedback and ask you to keep providing it.
Rakesh Tripathi commented
It is a very primitive restriction where you have to create different schedules just because you have to pass different parameters. Come on Automation Team, not having resources is just a pathetic reason to close this improvement suggestion!
This in incredibly restrictive to not allow this. Why should I create multiple schedules if that are the same just to link a runbook with different parameters?
It would be nice to have the same schedule but with different parameters, instead of being forced to create multiple identical schedules.
It is a pity that this idea has been closed, because indeed what Joost says: it is a MUST.
This is a must! I have one script to up or downscale a single database. I want to execute this script for all my databases... and NOT create a separate schedule for each one!
Robert Aspinall commented
+1 for this. We should be able to associate a given runbook with the same schedule multiple times, using different parameters.
+3 for this! It is weird that we have to create multiple schedules for the same run book when we could use the same schedule for different runbooks.
Harris Spivack commented
+1 for this! I have a runbook that will change the size of a VM, with the VM Name and new size passed in as parameters. I need to increase the size of a few different VMs prior to core warehouse hours, then size them back down at the end of the day. It sounds like what I have to do is have multiple schedules, one for each VM, that all run at the exact same time.
As a workaround, I guess I can probably use a webhook for the runbook that does the sizing, then have a separate runbook that runs on the schedule that does the web request to kick off the other runbook. This seems like it should be unnecessary
Webber,Michael T. commented
Having the ability to add the same runbook to the same schedule multiple times with different parameters would be ideal. An example scenario would be a runbook that performs standard database maintenance tasks. The runbook parameters include the database to execute against. The runbook needs to run against many databases at the same time. To handle this scenario currently, a duplicate schedule needs to be created for each database. Having the ability to add the same runbook to a single schedule with different parameters, would allow a significant reduction in the number of schedules required. This would make it easier to manage.
Agreed with every comment below. I have a runbook that will start a VM, I want to start 9 VM's at the same time. This means creating 9 identical schedules with different parameters. Would be much simpler to have a single schedule that I configure with different parameters. FYI, I'm only starting a subset of VMs within the same group hence why I can't use Resource Group as a single parameter.
Robin P. Blanchard commented
three years later....
we still can't associate a single schedule to multiple runs (with different parameters) ?
Mark Pointon commented
I have to agree with all. I'm a Senior DBA and I've created an azure Reindex\CheckDB process so I can call it on a single schedule with multiple Jobs having parameters for each of my Azure SQL Endpoints. I was disappointed to see once I started on the second endpoint the published runbook switched to edited.
John O commented
Any update on this. Or, is there a different approach that we are all missing? Having to create multiple schedules (all exactly the same apart from the parameters) cannot be what was intended. Please advice.
Dominic St-Jacques commented
I use it for database maintenance and would like to just change the DB name, so linking the same schedule with different parameters would be great!
John O commented
I have hit this problem too. I have one runbook, it is generic, used to process ssas tabular models. It has one parameter; the name of the model. I simply want to run this runbook multiple times, once for each of my models. I want the processing of each of these models to occur at the same time, e.g. one schedule, but with differing parameters. Am I approaching this in the wrong way?
Adam Levitt commented
I also would like to just reschedule the same runbook with different parameters. It's tedious to set this up multiple times.
I am also needing to run the same runbook hourly but with different parameters, having to create identical schedules for the same times on the same runbook is a bit of a struggle to explain to folks.
I have the same feature request from multiple customers. For example they want to execute commands for multiple VMs at same schedule. Currently 100 schedules are required for 100 VMs. When the request become available, all they need is a single schedule and maintenance will become so simple which is just linking a schedule to a runbook with different parameters.
Carlos Mendes commented
It is already possible to use the same schedule more than once, with different parameters?
I would like to have this as well. Essentially I want to start all VMs in a resource group, then start all VMs in a second resource group 15 minutes later. It's far simpler for me to write a single script with a parameter for the resource group and schedule it for different times. That's fine and works now.
The problem comes when I want to start multiple RG's worth of VMs at the same time, as I can't use the same schedule with different parameters.
As well as this, it would be great to see the parameters in the schedule list.