Unlocking Flexibility in Fabric: Introducing Multiple Scheduler and CI/CD Support
Multiple Scheduler: A Game-Changer for Complex Scheduling Needs
In today’s data environments, one size rarely fits all. Yet until now, Fabric only allowed one scheduler per item, forcing users to duplicate pipelines, manually configure jobs, or build brittle workarounds to meet real-world needs.
That changes today.
We’re excited to announce Multiple Scheduler support in Fabric — a long-awaited capability that allows users to configure up to 20 schedulers per item, each with its own time plan.
Why It Matters
This feature was a P0 ask from many enterprise customers and a top complaint surfaced in CAT team surveys. It directly addresses the flexibility gap that blocked many users from migrating from platforms like ADF and Synapse
Real Scenarios, Now Solved
- Multiple time schedules for the same item
A pipeline used by several dashboards can now be triggered at different intervals — for example, one scheduler runs daily at 6 AM, another weekly on Sundays. Previously, users had to duplicate the pipeline to achieve this. Now, they can configure multiple schedulers directly on the same item. - Different job types on the same item
Some items support more than one job type (e.g., refresh vs. publish). With Multiple Scheduler, users can now create separate schedulers for each job type — even though only the default job type is visible in the UI, all schedulers are fully supported via API. (UI is on the way.)
Scheduler CI/CD: Making It All Deployable
But with great flexibility comes great complexity. More Schedulers mean more configurations, more dependencies, and more chances for deployment errors.
That’s why we’re also announcing Scheduler CI/CD support — a foundational upgrade that makes Multiple Scheduler truly usable at scale.
What’s New
- Schedulers are deployed alongside the item via Git, Deployment Pipelines, or public APIs.
- Configuration changes are tracked, versioned, and validated — just like any other part of your item.
Deployment Scenarios, Solved
- Git integration: Scheduler configurations are stored as
.jsonfiles in the item folder and reflected in Git status and diffs.
- Deployment Pipeline support: Changes are surfaced in deployment history and comparison tools.
- Public API: Scheduler definitions are embedded in item definitions, enabling full CRUD operations and version control.
What’s Available Today
- Multiple Scheduler API support: Create, read, update, and delete up to 20 schedulers per item.
- UI support for default job types: Easily manage multiple schedulers in the Fabric UI.
- CI/CD integration: Scheduler configurations are deployed with the item, tracked in Git, and validated in pipelines.
- Monitoring: Job history is separated per scheduler, and errors are surfaced clearly.
What’s Coming Next
We’re continuing to expand support with:
- Full UI CRUD support for all job types.
- Job history separation by Scheduler in Monitor hub.
- Scheduler reuse across items.
- Enhanced validation and naming support.
For more information, refer to the Choose the best Fabric CI/CD workflow option for you documentation.
