Skip to content
datastudyguides

DP-600 · 2.1.5 · Prepare data

OneLake integration

Implement OneLake integration for Eventhouse and semantic models

Expose or Import data as in so other Fabric engines can reuse one copy.

The core idea

OneLake integration showing Eventhouse and Import semantic model data exposed as Delta tables in OneLake for reuse by other Fabric engines.

integration lets other Fabric engines reuse data without building another movement pipeline.

For , exposes or table data as read-only . Writes are batched, so the OneLake copy can lag behind ingestion.

For , OneLake integration exports Import tables after model refresh. and tables are not exported.

Key points

  • : exports data as
  • : Import tables export after refresh
  • Reuse: other Fabric engines access the same data
  • Latency: Eventhouse exports batch; model exports follow refresh

Click an underlined term for a one-line explanation, or see them all in the glossary .

Exam trap

Neither feature is instant. An batches its writes, so the copy can lag behind ingestion, and a exports only after a refresh.

Sources · 2 Microsoft Learn pages Show ▾

Checked on October 4, 2026. Report a problem

Go deeper on Microsoft Learn

Checked against Microsoft Learn on October 4, 2026. Report a problem with this card

How well do you know this?