Before deploying Microsoft Fabric items from Development to Test or Production, Deployment Pipelines should automatically perform a detailed impact analysis.
The validation should identify:
• Downstream reports, semantic models, notebooks, pipelines, and other dependent items that may be affected
• Breaking schema changes, including removed columns or changed data types
• Operations that could delete, truncate, or overwrite existing data
• Missing connections, permissions, dependencies, or deployment rules
• Configuration differences between source and target environments
The results should be displayed with severity levels such as Information, Warning, and Critical. Administrators should be able to block deployments containing critical changes or require manual approval before proceeding.
This feature would prevent broken reports, failed refreshes, and accidental data loss, making Fabric deployments safer and easier to manage.
