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

Hi Corujo ,

I agree, the deployment pipeline comparison in Fabric does include scheduling details such as triggers as part of the pipeline definition. That’s why you’re noticing differences between DEV (no schedule) and PROD (daily trigger). Until environment specific deployment rules are available, you might consider documenting the expected schedule differences in your deployment checklist or workspace documentation to make reviews and comparisons easier. Alternatively, you can automate trigger setup after deployment, for example, if you’re using the API or PowerShell, include a step to re-enable or update the PROD trigger once deployment is complete. This helps keep environments consistent while ensuring that the production schedule continues to run as intended.

It would also be helpful to share this feedback through Microsoft’s official feedback channels, such as Microsoft Fabric Ideas -

https://community.fabric.microsoft.com/t5/Fabric-Ideas/idb-p/fbc_ideas/ideas/search-ideas

Feedback submitted through these channels is frequently reviewed by the product teams and can contribute to meaningful improvements.

Best regards,
Sreeteja