Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Did you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now

Tzvia

Unifying “Analyze data with” analytics across Fabric (Preview)

As Microsoft Fabric continues to converge analytics experiences across workloads, one of the most important steps forward is reducing friction in how users move from raw data to insights. With the latest integrations, the Eventhouse Endpoint is now deeply embedded into the “Analyze data with” entry points across Lakehouse, Data Warehouse, and Eventhouse, bringing a consistent, discoverable, and powerful way to analyze data using SQL Endpoint and Notebooks, both new and existing.

Lakehouse_with_the_newe_Analyze_data_withLakehouse_with_the_newe_Analyze_data_with

Figure: Lakehouse with the updated Analyze data with entry point, providing consistent access to analytics experiences.

Analyze_data_with_has_new_options_of_Notebook_and_Eventhouse_EndpointAnalyze_data_with_has_new_options_of_Notebook_and_Eventhouse_Endpoint

Figure: The Analyze data with menu now includes Notebook and Eventhouse Endpoint, enabling quick SQL and Spark-based analysis

Why this integration matters

Historically, Fabric users had multiple ways to analyze data, but those options were often scattered across different menus and experiences. This was especially challenging for new users, who had to understand not only which analytics engines were available, but also where to find them. Internal UX and PM discussions consistently highlighted the need for a single, predictable starting point for analysis, regardless of whether the data lives in a Lakehouse, Data Warehouse, or Eventhouse.

The introduction of “Analyze data with” as a first-class action across these experiences addresses that gap by consolidating all analytical entry points into one consistent menu, making it clear how to move from data to insights, while preserving the flexibility power users expect.

Eventhouse Endpoint in Lakehouse and Data Warehouse main pages

Eventhouse Endpoint is designed to provide an Eventhouse-powered query experience directly on top of Lakehouse and Data Warehouse data, without data duplication or manual synchronization. When enabled, an Eventhouse and a KQL Database are automatically created as child artifacts of the source Lakehouse or Warehouse, with schema synchronization handled automatically in the backend.

With the new integration:

  • Analyze data using SQL Endpoint.
  • Analyze data using Notebooks, including both new and existing notebooks.
  • Lakehouse and Data Warehouse main pages now include Eventhouse Endpoint as part of “Analyze data with.”
  • Users can open Eventhouse directly from the source data experience, without navigating to a separate workload.
  • The endpoint always reflects the current schema of the source data, enabling near-real-time analytical access.
This integration makes Eventhouse a natural extension of the data source, rather than a separate system users must explicitly wire up and manage.

“Analyze data with” in Eventhouse: one menu, multiple engines

The same “Analyze data with” concept is now applied directly within Eventhouse itself. A new unified action menu appears at the database level, consolidating all supported analytics tools in one place.

From Eventhouse Capabilities:

  • Analyze data using SQL Endpoint (when OneLake availability and sync are enabled).
  • Analyze data using Notebooks, including both new and existing notebooks.
  • Launch analysis actions from a single, predictable location next to Share, rather than hunting through the ribbon.
This design reinforces a consistent mental model: no matter where you start, Lakehouse, Warehouse, or Eventhouse, the way you analyze data looks and feels the same.

Notebook support: new and existing, everywhere

Notebook integration is a core part of the “Analyze data with” experience across workloads. From both Lakehouse/Data Warehouse and Eventhouse entry points, users can seamlessly open new or existing notebooks and immediately start analyzing data.

Notable capabilities include:

  • Opening a notebook directly from a KQL Database or Eventhouse, with the database automatically added to the notebook environment.
  • Consistent behavior across Spark notebooks, regardless of whether the starting point is Lakehouse, Warehouse, or Eventhouse.
  • A single integration model that avoids special cases or duplicated flows.
This enables users to fluidly move between exploratory analysis, advanced transformations, and experimentation, without switching contexts or reconfiguring access.

A consistent experience across Fabric workloads

From internal PM and UX discussions, one theme was clear: consistency matters as much as capability. By integrating Eventhouse Endpoint into “Analyze data with” across all relevant main pages, Fabric delivers:
  • A unified entry point for analytics.
  • Clear discoverability for Eventhouse, SQL Endpoint, and Notebooks.
  • Reduced onboarding friction for new users.
  • A scalable model that allows additional workloads and tools to plug into the same pattern over time.
Rather than forcing users to learn different interaction models per workload, Fabric now offers a single, repeatable way to analyze data, powered by Eventhouse, wherever the data lives.

The integration of Eventhouse Endpoint into “Analyze data with” is not just a UI change, it’s a foundational step toward a more cohesive Fabric analytics experience. By aligning Lakehouse, Data Warehouse, and Eventhouse around the same analysis entry points, Fabric makes it easier for users to focus on what matters most: deriving insights from their data, fast.

Learn more: Eventhouse Endpoint for Lakehouse and Data Warehouse (Preview)