Simplifying Data Ingestion with Copy job – Multiple Scheduler support
Copy Job is the go-to solution in Microsoft Fabric Data Factory for simplified data movement. With native support for multiple delivery styles, including bulk copy, incremental copy, and change data capture (CDC) replication, Copy job offers the flexibility to handle a wide range of scenarios—all through an intuitive, easy-to-use experience.
In this update, we’re excited to announce a powerful new enhancement: multiple scheduler support. This gives you even greater control over when your data moves.
Now, a single Copy job can be triggered at different intervals—for example, one scheduler runs daily at 6 AM, while another runs weekly on Sundays. In the past, achieving this required creating multiple Copy jobs with each schedule. With this update, you can configure all your schedules directly within the same Copy job, making orchestration simpler, cleaner, and more efficient.
As you expected, the multiple schedulers can be deployed alongside the Copy job via Git, Deployment Pipelines, or public APIs. You can refer to more details in Unlocking Flexibility in Fabric: Introducing Multiple Scheduler and CI/CD Support | Microsoft Fabric Blog | Microsoft Fabric
Additional Resources
To learn more, explore our Microsoft Fabric Copy Job Documentation.
Submit your feedback on Fabric Ideas and join the conversation on the Fabric Community.
To get into the technical details, head over to the Fabric documentation.
Have any questions or feedback? Leave a comment below!
