Allow scheduler configuration with variable libraries
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
- zhaya
Microsoft Employee
Status changed:NewtoUnder Review - hedeencharles
Advocate I
zhaya Tom_Fosterbi This would be a very useful feature! - zhaya
Microsoft Employee
Status changed:Under ReviewtoPlannedWe 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!
- hedeencharles
Advocate I
Thank you for the update zhaya ! - Tom_FosterbiRegular Visitorzhaya is there an update on the ETA of this
- SjoerdW
Advocate I
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. - SjoerdW
Advocate I
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. - DanielSDavisFrequent VisitorSjoerdW 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
Recent ideas
Expose Power Query as a Standalone Runtime and Command-Line Interface (CLI)
Summary Power Query has evolved into one of Microsoft's most powerful data transformation technologies and is now used across Excel, Power BI, Fabric, Dataflows, Power Platform, and other products. ...juansgr_6 minutes agoNew MemberNew1View0likes0CommentsExpose User Prompt and Agent Response Logs for Fabric Data Agents
Idea: As an engineer responsible for managing and improving Microsoft Fabric Data Agents, I currently have no way to view how users are interacting with the agents I’ve built. While it’s likely that...JoshuaPitzer1 hour agoAdvocate INew1.2KViews26likes2CommentsImprove relationship visualisation in Model View for large semantic models.
When working with complex models containing many fact and dimension tables, relationship lines frequently cross and overlap, making lineage difficult to follow. A useful enhancement would be to allo...jcheeseaos1 hour agoNew MemberNew3Views0likes0CommentsEnable Export and Programmatic Access to Copilot Narrative Text
Copilot Narratives provide valuable AI-generated insights directly within Power BI reports. However, there is currently no straightforward way to export, copy, or programmatically retrieve the exact ...Mario_A_S_13 hours agoNew MemberNew22Views3likes0Comments