This article by the Microsoft Fabric Blog details the new Multiple Scheduler and CI/CD support in Fabric, highlighting key enhancements for scheduling and deployment workflows.

Multiple Scheduler: A Game-Changer for Complex Scheduling Needs

In modern data environments, flexibility is essential. Until recently, Microsoft Fabric only allowed one scheduler per item. This limitation forced users to duplicate pipelines, manually configure jobs, or create fragile workarounds to meet real-life scheduling requirements.

This limitation has now been removed.

Introducing Multiple Scheduler Support

Microsoft Fabric now supports Multiple Scheduler, allowing users to configure up to 20 schedulers per item, each with its own timetable.

Multiple Scheduler Interface

Why Multiple Scheduler Matters

This was a top ask (P0) from enterprise customers and repeatedly surfaced in Customer Advisory Team (CAT) surveys. It eliminates a longstanding flexibility gap that blocked migrations from other platforms like Azure Data Factory (ADF) and Synapse Analytics.

Real-World Scenarios Now Addressed:

  • Multiple Schedules for the Same Item: For example, a pipeline used by multiple dashboards can now be triggered daily at 6 AM and weekly on Sundays—no duplication needed.
  • Different Job Types on the Same Item: Items supporting several job types (such as refresh and publish) can now have separate schedulers for each, managed through API (with UI support forthcoming).

Scheduler CI/CD: Deploy with Confidence

With added flexibility comes operational complexity—multiple schedulers mean more configuration and potential for deployment errors. To address this, Microsoft introduces comprehensive Scheduler CI/CD support:

New Capabilities

  • Schedulers are deployed alongside each item through Git, Deployment Pipelines, or public APIs.
  • Configuration changes are tracked, versioned, and validated, just like any part of your item.

Deployment Scenarios Now Supported:

  • Git Integration: Scheduler configurations live as .json files in the item directory and are reflected in Git status/diffs.

    Scheduler JSON Example

  • Deployment Pipeline Support: Changes are visible within deployment history and comparison tooling.
  • Public API: Scheduler definitions are embedded, enabling full create/read/update/delete (CRUD) operations and version control.

What’s Available Now

  • Multiple Scheduler API Support: Create, read, update, or delete up to 20 schedulers per item.
  • UI Support for Default Job Types: Users can manage multiple schedulers directly from the Fabric UI.
  • CI/CD Integration: Scheduler configurations are deployed, tracked, and validated with Git and pipelines.
  • Monitoring: Job histories are separated per scheduler and error reporting is clear.

Roadmap: What’s Coming Next

Microsoft Fabric plans to extend these capabilities further by:

  • Adding full UI CRUD support for all job types
  • More granular job history separation in the Monitor hub
  • Enabling scheduler reuse across items
  • Enhanced validation and better naming support

For in-depth guidance, consult the Choose the best Fabric CI/CD workflow option for you in the Microsoft documentation.

This post appeared first on “Microsoft Fabric Blog”. Read the entire article here