Deployment Overwrites Production Pipeline Schedule with Development Schedule – Expected Behavior?

Hi AdarshChekodu ,

Thanks for your response. You are correct in Microsoft Fabric, deploying a Data Pipeline using Deployment Pipelines replaces the entire pipeline definition, including schedules and triggers. This is the expected behavior, and currently, there isn’t a built in option to keep environment specific settings like schedule during deployment.

1. This is the current workaround, though it can be tedious. The ARM template model in ADF does provide more flexibility, and this limitation in Fabric has been noted by many users.

2. While these help with dynamic logic within a pipeline, such as changing data sources or filters, they cannot be used to set or manage the schedule. There is no documentation supporting this use at the moment, but I will share any updates if that changes.

3. At present, it is not possible to isolate or exclude the schedule when deploying a pipeline. Deployments are all or nothing, which can be challenging when development and production require different refresh schedules.

I’d recommend raising it on the Fabric Ideas - Microsoft Fabric Community many users have requested more control over environment specific settings like schedules.

Regards,
Yugandhar.