The new scheduler is a great idea (Unlocking Flexibility in Fabric: Introducing Multiple Scheduler and CI/CD Support | Microsoft Fabric Blog | Microsoft Fabric)
However, the fact that we cannot control this using variable libraries means that if you have scheduled refreshed disabled in dev and test then after every prod deployment you have to renable the refresh.
There is also no way to turn off this new scheduler and go back to the old scheduler which did not move across environments.
Please either enable us to control the scheduler via depoyment pipelines ASAP or give us a tenant switch to disable this till this feature is supported.
8 Comments
- Status changed:NewtoUnder Review
- zhaya Tom_Fosterbi This would be a very useful feature!
- Status changed:Under ReviewtoPlanned
We are planning for a work to allow users control the Scheudler On/Off state with variable library. The ETA would be March 2026. Thank you all for your feedback!
- Thank you for the update zhaya !
- zhaya is there an update on the ETA of this
- This would also be useful for pipelines with multiple schedules. Instead of only controlling a single scheduler on/off state, it would be great if the activation state of each schedule could be configured through Variable Libraries. That would allow organizations to define separate DEV, TEST and PROD schedules (for example 06:00, 05:30 and 05:00) and activate only the appropriate schedule in each environment.
- Variable Libraries would become even more powerful if they could control the activation state of individual schedules instead of only a single scheduler. A pipeline can already have multiple schedules. We use: DEV schedule (06:00) TEST schedule (05:30) PROD schedule (05:00) During deployment, only the appropriate schedule should be enabled for the target environment. This avoids manual changes after deployment and eliminates the need to parameterize schedule times. This would fit naturally with Variable Libraries and Deployment Pipelines.
- SjoerdW It looks like Microsoft snuck that feature in on us. I can't find a single thread on it, but it's in the Fabric UI
