Weekly Fabric

What shipped

• Use built-in Fabric data protection to get your data AI-ready: Every organization wants to put AI to work on its data. Copilot, agents, and generative AI promise faster insight , but they raise a hard question for security teams: If AI can reach all our data, what stops… (26 Jun)
• Faster Spark History Server loading: Running large-scale data engineering workloads in Apache Spark often means dealing with expensive shuffle operations. (25 Jun)
• Using Bulk Copy API for faster ingestion in Fabric Data Warehouse: The BCP API provides a client-side ingestion path for scenarios where data is produced within application code and needs to be written directly to warehouse tables without intermediate staging. (25 Jun)
• On-premises data gateway June 2026 release: The June 2026 release of the on-premises data gateway is version 3000.322. This new version (3000.322) continues our focus on improving gateway manageability, operational visibility, and enterprise governance… (25 Jun)
• Fabric Influencers Spotlight: June 2026: A monthly post to shine a bright light on Microsoft MVPs & Fabric Super Users (25 Jun)
• Faster Spark History Server loading: A new built-in stored procedure for the SQL analytics endpoint in Microsoft Fabric; sp_get_table_health_metric. (24 Jun)
• Rayfin shareable sites: We’re halfway through 2026, and Microsoft SQL has not slowed down. Since SQLCon/FabCon in March (where we released a ton of things, and those updates can be found in the What's New in Microsoft SQL at… (24 Jun)
• Billing for Microsoft Fabric Planning: A business-first approach to economics on Microsoft Fabric Enterprise planning is evolving across industries - from an isolated finance exercise to a cross-functional capability that spans finance,… (24 Jun)
• ADF-to-Fabric migration flow: Multi Cloud Data integration and transformation made easy and painless by Fabric Data Factory. (23 Jun)
• Improve performance for Python UDFs and complex data types in Microsoft Fabric’s Native Execution Engine: Where this matters: A concrete example For example, you have a data pipeline (extract, transform, load—ETL) that ingests JSON telemetry events, each containing nested arrays of user actions. (22 Jun)
• Event-Driven Copy Job Execution with Fabric Activator: Introduction Modern data platforms are increasingly moving toward event-driven architectures where data flows react to events or changes instead of running on rigid schedules. (22 Jun)

Why it matters

• Use built-in Fabric data protection to get your data AI-ready: Every organization wants to put AI to work on its data. Copilot, agents, and generative AI promise faster insight , but they raise a hard question for security teams: If AI can reach all our data, what stops it from…
• Faster Spark History Server loading: Snapshot-based loading makes large Spark job metrics usable much faster, especially for high-volume batch and streaming workloads.
• Using Bulk Copy API for faster ingestion in Fabric Data Warehouse: The BCP API provides a client-side ingestion path for scenarios where data is produced within application code and needs to be written directly to warehouse tables without intermediate staging.
• On-premises data gateway June 2026 release: The June 2026 release of the on-premises data gateway is version 3000.322. This new version (3000.322) continues our focus on improving gateway manageability, operational visibility, and enterprise governance while…
• Fabric Influencers Spotlight: June 2026: A monthly post to shine a bright light on Microsoft MVPs & Fabric Super Users
• Faster Spark History Server loading: Snapshot-based loading makes large Spark job metrics usable much faster, especially for high-volume batch and streaming workloads.
• Rayfin shareable sites: Fabric-adjacent AI/markdown workflows gain a more shareable presentation layer.
• Billing for Microsoft Fabric Planning: A business-first approach to economics on Microsoft Fabric Enterprise planning is evolving across industries - from an isolated finance exercise to a cross-functional capability that spans finance, operations, supply…
• ADF-to-Fabric migration flow: Migration work can start directly from the Fabric workspace rather than forcing a portal handoff.
• Improve performance for Python UDFs and complex data types in Microsoft Fabric’s Native Execution Engine: Where this matters: A concrete example For example, you have a data pipeline (extract, transform, load—ETL) that ingests JSON telemetry events, each containing nested arrays of user actions.
• Event-Driven Copy Job Execution with Fabric Activator: Introduction Modern data platforms are increasingly moving toward event-driven architectures where data flows react to events or changes instead of running on rigid schedules.

How analytics teams could use it

• Use built-in Fabric data protection to get your data AI-ready: Assess whether it removes data movement, debugging time, dashboard friction or governance gaps in the current analytics stack.
• Faster Spark History Server loading: Platform teams can inspect executions, tune performance and support long-running jobs without waiting on huge event logs to render.
• Using Bulk Copy API for faster ingestion in Fabric Data Warehouse: Assess whether it removes data movement, debugging time, dashboard friction or governance gaps in the current analytics stack.
• On-premises data gateway June 2026 release: Assess whether it removes data movement, debugging time, dashboard friction or governance gaps in the current analytics stack.
• Fabric Influencers Spotlight: June 2026: Assess whether it removes data movement, debugging time, dashboard friction or governance gaps in the current analytics stack.
• Faster Spark History Server loading: Platform teams can inspect executions, tune performance and support long-running jobs without waiting on huge event logs to render.
• Rayfin shareable sites: Teams can package analysis outputs for stakeholders without turning every insight into a custom app or slide deck.
• Billing for Microsoft Fabric Planning: Assess whether it removes data movement, debugging time, dashboard friction or governance gaps in the current analytics stack.
• ADF-to-Fabric migration flow: Data teams modernising orchestration can assess and move legacy Azure Data Factory pipelines with fewer context switches.
• Improve performance for Python UDFs and complex data types in Microsoft Fabric’s Native Execution Engine: Assess whether it removes data movement, debugging time, dashboard friction or governance gaps in the current analytics stack.
• Event-Driven Copy Job Execution with Fabric Activator: Assess whether it removes data movement, debugging time, dashboard friction or governance gaps in the current analytics stack.

Editorial read

Fabric is continuing to push OneLake as the connective tissue: less copy-and-paste data engineering, more open-table interoperability, and more operational workflows that can consume governed analytical data directly. For teams building analytics products, the practical angle is to look for places where Fabric now removes a separate platform, manual troubleshooting step, or bespoke dashboard layer.