Back to Blogs

Write Back Planning Data to OneLake, Up to 13× Faster

Lumel
Nov 2026

On this page

Write back Fabric Plan results as Delta Parquet, use them in Direct Lake semantic models, and reuse them across Fabric.

This is Part 2 of our three-part Native Planning Engine series. Part 1 introduces the Native Planning Engine, and Part 3 covers the performance improvements across Fabric Plan.

Alongside the brand new Native Planning Engine, now in Public Preview (Part 1), Fabric Plan now supports writeback to OneLake as a new writeback destination, in Delta Parquet format.

Writeback outputs land as Delta tables in OneLake. You can add them to a semantic model in Direct Lake mode and reuse them across Fabric through lakehouse shortcuts, without another copy of the data. Fabric SQL remains a fully supported writeback destination.

This post assumes your Plan items run on the Native Planning Engine. If they don’t yet, turn it on first (Part 1).

In this article:

Choose Your Writeback Destination

Choose OneLake to write back as Delta Parquet. File-based writes are about 5–6× faster than SQL-based writes at typical volumes, rising to 13× at 12M cells, and are tested up to 50 million cells per writeback instance. Fabric SQL remains fully supported and is a great fit for writeback up to 2.4 million cells and for SQL-based workflows.

Writeback capability with the Native Planning EngineWriteback destination: Fabric SQLDirect writeback to OneLake
Destination supportFabric SQL (fully supported)OneLake (direct writeback)
Cells per writeback instance2.4M recommended50M tested
Writeback speed3 mins30 sec (about 6× faster)
Output formatSQL tablesDelta Parquet in OneLake
Writeback scale and speed on the Native Planning Engine, by destination

Writeback speed measured at 2.4M cells. See Writeback performance for every volume tested. Actual speed depends on data volume, workload and capacity.

Writeback Performance

Approximately 5–6× faster at typical customer volumes. Most customers write back 1.2M–2.4M cells; those volumes are marked as typical below. The gap widens as volume grows, reaching 13× at 12M cells, because of the write approach: SQL-based writes versus file-based Delta Parquet writes.

Volume (cells)Writeback to Fabric SQL (SQL-based writes)Direct writeback to OneLake (file-based Delta Parquet writes)Approx. speedup
120K13 sec6 sec2× faster
480K30 sec9 sec3× faster
1.2M (typical)1 min 09 sec15 sec5× faster
2.4M (typical)2 min 54 sec30 sec6× faster
4.8M10 min 11 sec52 sec12× faster
12M22 min 29 sec1 min 40 sec13× faster
30MNot tested4 min 15 secN/A
50MNot tested9 min 05 secN/A
Writeback time by volume: Fabric SQL versus direct writeback to OneLake

Speedup = SQL-based writeback time ÷ file-based OneLake writeback time, rounded to the nearest whole number. SQL-based writeback was not tested at 30M and 50M cells. Actual times depend on workload, model design and capacity. Writeback volume is counted per writeback instance and is separate from the interactive planning grid, which supports up to 12 million cells in aggregate on the Native Planning Engine (see Part 1). On our roadmap, OneLake writeback will extend to support 120 million cells and beyond, matching the planning grid roadmap in Part 1.

How to Set Up Writeback to OneLake

The workflow: Plan → OneLake (Delta Parquet) → Direct Lake semantic model.

1. Add a Writeback Destination

Open the Plan’s Writeback tab and select Add destination.

Plan Writeback ribbon with Add destination.
Start from the Writeback ribbon.

2. Choose OneLake and Name the Table

In Create Destination, select OneLake. Enter the Schema, Table Name, and Decimal Precision, then select Add.

The example uses dbo, variance_drivers_usd_forecast, and two decimal places. The dialog notes that decimal precision cannot be changed later.

Create Destination dialog: OneLake selected, schema dbo, table variance_drivers_usd_forecast, decimal precision 2, and Add button.
OneLake is the selected storage type.

3. Run the Writeback

Select Writeback. When the operation finishes, the Plan displays Writeback completed.

Enabled Writeback command in the Plan ribbon.
Run the writeback operation.
A green check with the message Writeback completed.
The completion message confirms the operation finished.

4. Verify the OneLake Destination

Open Logs and confirm Destination Type: OneLake and Status: Success.

Writeback Logs row showing Destination Type OneLake, Duration 7 Secs, and Status Success.
The duration shown is from this example run; it is not a benchmark for large-volume writeback.

Add the Writeback Tables to a Semantic Model

Plan items are now a supported source in the OneLake catalog. Each Plan item can contain multiple writeback tables; choose the ones your semantic model needs.

5. Find the Plan in the OneLake Catalog

In the semantic model editor, select OneLake catalog. Open the top-right Filter, choose Type → Plan, select the Plan item, and select Connect.

Semantic model OneLake catalog with the Filter menu open and Plan listed as a supported source type; Plan items and the Connect button are visible.
Filter by Plan, select the Plan item, then connect.

6. Select the Writeback Tables

The Add Data Source dialog lists the available writeback tables in the selected Plan. Expand the schema, select one or more tables, and select Confirm.

Add Data Source dialog listing dbo and the variance_drivers_usd_forecast writeback table, with Confirm at the bottom.
This example Plan exposes one table; a Plan can expose multiple writeback tables.

7. Confirm Direct Lake Mode

The selected table is added to the semantic model in Direct Lake mode. Hover over the table to inspect its details: Storage mode shows Direct Lake, and Data source type shows Planning.

Added writeback table with a tooltip confirming Storage mode Direct Lake and Data source type Planning.
The Plan writeback table is now part of the semantic model.

Use the Same Output Across Fabric

Bring It into a Lakehouse Through a Shortcut

Create a shortcut in the lakehouse’s Tables area that points to the Plan’s Delta table in OneLake. The lakehouse can use the table without another copy of the output. About OneLake shortcuts

Connect the Lakehouse Data to an Ontology

With the writeback table available through the lakehouse, bind it to the relevant entity types and properties in Fabric ontology. This brings planning outputs into the business relationships used by that ontology. Ontology data binding

The reuse path: OneLake writeback table → Lakehouse shortcut → Ontology.

To start pipelines, refreshes or alerts automatically after each writeback, see Writeback that sets work in motion.

The screenshots show the writeback and semantic-model workflow; observed run times are examples, not performance guarantees.

Share on:

Comments

0

Leave a Reply

More from the blog

Microsoft, Azure, Copilot, Excel, Fabric IQ, Microsoft Entra, Microsoft Fabric, Microsoft Teams, OneLake, Outlook, Power Automate, Power BI and SharePoint are trademarks of the Microsoft group of companies. IBCS is a registered trademark of IBCS Association. All other trademarks are the property of their respective owners.

This community is operated independently by Lumel. Nothing on this site constitutes a representation or warranty by Microsoft.
arrow-left