Running notebooks in Data Pipelines just got a major upgrade! You can now establish connections using Service Principal (SPN) or Workspace Identity, making authentication more secure and flexible. Before: When executing notebooks through Data Pipelines, there was no option to configure connections directly. Now: With the latest Microsoft Fabric update, you can choose between. Service Principal (SPN): Ideal for automation scenarios where you want a dedicated identity with controlled permissions. Workspace Identity: Leverages the Fabric workspace identity for seamless integration and simplified management. For More information. https://blog.fabric.microsoft.com/en-us/blog/run-notebooks-in-pipelines-with-service-principal-or-workspace-identity?ft=All

I can see more into Engineering Side. The product team has published the latest roadmap updates for covering the upcoming two quarters. This roadmap highlights new features, enhancements, and planned capabilities that will shape the future of data integration and orchestration in Fabric. It’s a great opportunity to prepare for adoption. Explore the full roadmap here. https://roadmap.fabric.microsoft.com/?product=datafactory

First update. We can create shortcut to EventHouse tables. With the Eventhouse endpoint option, we can quickly shortcut to EventHouse tables. Second update. It is easy to check now whether a Dataflow Gen2 is in a running state or has completed successfully. A simple but powerful way to monitor status without digging through logs.

Enabled Lakehouse tables to be read directly from SSMS. This means: You can connect SSMS to the SQL endpoint of a Lakehouse. Query Lakehouse tables with familiar T-SQL syntax inside SSMS. Leverage SSMS features like query plans, execution statistics, and integration with existing SQL workflows. Note: Before Lakehouse tables were accessible only from Warehouse.

Copy Job Activity is now Generally Available in Data Pipeline. Capacity Metrics via Event Streams Monitor Fabric Capacity Consumption through Event Streams Event Streams now expose capacity consumption metrics for Fabric workloads. Metrics include eventstream per hour, data traffic per GB, and processor usage per hour, reported in capacity units (CU hours). These metrics are high-level summaries, not transaction-level details. Functionally, this is close to Capacity Metrics and Chargeback apps but currently limited to aggregated consumption views. Additional information is available through the links below. https://blog.fabric.microsoft.com/en-us/blog/announcing-copy-job-activity-now-general-available-in-data-factory-pipeline/ https://learn.microsoft.com/en-us/fabric/data-factory/copy-job-activity https://learn.microsoft.com/en-us/fabric/real-time-intelligence/event-streams/monitor-capacity-consumption