Difference in pipeline scheduling between DEV and PROD causes confusion during deployment

[Corujo]

Hi everyone,

I’m currently implementing a data pipeline that is deployed from a DEV workspace to a PROD workspace in Microsoft Fabric.

In my setup, I want the pipeline to run daily only in PROD, but not in DEV (since DEV is used just for testing and development). However, when I set up the daily schedule in the PROD environment, this creates a difference between the DEV and PROD versions of the pipeline.

As a result, when I compare or deploy changes, Fabric shows differences in the pipeline configuration, which makes it confusing — it looks like the pipelines are out of sync, even though the only intended difference is the scheduling configuration.

Has anyone else faced this situation?

How do you handle environment-specific configurations like pipeline triggers or schedules between DEV and PROD in Fabric?

Thanks in advance for your insights!

Best regards,

Carlo

[v-sshirivolu]

Hi @Corujo ,

This is a common scenario when managing Microsoft Fabric pipelines across different environments. It’s best to handle scheduling as environment-specific, rather than embedding it in the pipeline itself. You can keep the pipeline design consistent in both DEV and PROD, but manage the schedule separately in each workspace.

For your situation, consider removing the daily schedule from the DEV pipeline and only setting it up in the PROD workspace after deployment. This keeps the pipeline design in sync across environments, with scheduling as the only difference. You can do this manually or automate it using PowerShell or the Fabric API.

Alternatively, you could create a small orchestrator pipeline in PROD to run the main pipeline on a schedule, while in DEV you run it manually for testing. If you’re using Deployment Pipelines, you can set rules to keep schedules disabled in DEV and active in PROD. In general, separating schedules from the main pipeline helps keep DEV and PROD aligned and avoids confusion during deployment.