A plan rarely stops when the numbers are submitted. With writeback event triggers, a writeback can refresh reports, feed downstream systems and alert the right people, configured from the planning UI with no code. The loop from plan to action closes entirely within Fabric.

Writeback Event Triggers at a Glance

Writeback event triggers at a glance: three events (starts, succeeds, fails), Fabric actions from pipelines to stored procedures, and writeback parameters passed to each action.

In this article:

Why It Matters

Before Event Triggers, the steps after a writeback were manual or needed external plumbing: someone refreshed the report, re-ran a pipeline or called an API from an Azure Function. Now the plan starts that work itself, the moment the data lands, using the Fabric items your data team already runs.

The result: reports show approved numbers within minutes, downstream systems get the plan without a hand-off, and failures reach someone who can fix them.

Events and the Actions They Can Run

When a writeback…Typical actionsExample
StartsStored procedure, Teams or Outlook notificationSnapshot the current destination table before it changes, or tell data owners a load is under way
SucceedsSemantic model refresh, pipeline, notebook, Dataflow Gen2, stored procedure, notificationRefresh the variance report, push the approved budget to the ERP, or recalculate a downstream allocation
FailsTeams or Outlook notification, stored procedureAlert the plan administrator with the error details and log the failed run
What to run at each writeback event

You can configure several triggers on one planning sheet, so different automation paths run for different events, and run actions in sequence, such as a stored procedure followed by a semantic model refresh.

Watch It Work

Trigger Fabric Actions After Writeback in Fabric Plan

Demo, about 3 minutes: set up a trigger that runs a pipeline after a successful writeback, pass the execution ID as a parameter, chain a stored procedure with a semantic model refresh, and check each run in the trigger logs. Also on the Fabric Plan community.

Four Recipes to Start With

Each one replaces a manual step that usually follows a planning cycle.

1. Close the Loop to Reports

On succeeds, refresh the semantic model that holds plan versus actuals, so the variance report shows the new plan without waiting for the next scheduled refresh. See it end to end in Planning Decision to Business Action.

2. Feed the Approved Budget Downstream

Once the plan clears approvals and is written back, run a Fabric pipeline on succeeds that copies the approved version to the ERP or a finance data mart, passing the scenario and version as parameters.

3. Recalculate Dependent Data

On succeeds, run a stored procedure or notebook that rebuilds allocations, aggregates or derived tables that depend on the plan, then refresh the semantic model that reports on them.

4. Never Miss a Failure

On fails, send a Teams or Outlook message to the plan administrator with the writeback details, so issues are fixed before the deadline.

Set Up Writeback Event Triggers

Event Triggers are configured on the planning sheet, after a writeback destination exists.

Step 1: Configure the Writeback Destination

Set up writeback to Fabric SQL or OneLake for the planning sheet. See writeback to OneLake and the Planning 103 – Writeback video.

Step 2: Add an Event Trigger

From the planning UI, add a trigger and choose the event: when the writeback starts, succeeds or fails.

Step 3: Choose the Action

Pick the Fabric item to run and its connection, such as a pipeline, notebook, Dataflow Gen2, semantic model refresh or stored procedure, or a Teams or Outlook notification.

Step 4: Map Parameters

Pass writeback details and execution metadata, such as the execution ID, to the action, so it processes only what changed.

Step 5: Test with a Dry Run

Run a writeback on a test version and confirm each action ran in the trigger logs, then add more triggers for other paths.

PowerTable too. PowerTable Automations can run stored procedures from a Fabric SQL database, passing values from the record that triggered them, alongside no-code create, update and find-record actions. Watch Execute Stored Procedure Action in PowerTable Automations and Setting Up Automations in PowerTable.

Good Practices

Learn More on the Community

Automate the Step Your Team Does by Hand

Pick the one task that always follows a writeback today, usually a report refresh, and make it an Event Trigger. Add the failure alert at the same time.

Sources

Feature details reflect published Fabric Plan updates at the time of writing.

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.

A brand new in-memory engine for planning in Microsoft Fabric, with 10x+ improvements in both performance and scale. No separate system database is required anymore.

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

Native Planning Engine highlights: 10× more scalable, up to 12M cells in aggregate (up from 1.2M), and 10× faster writeback and calculation.

The scale figure compares the Native Planning Engine’s 12M-cell aggregate limit with 1.2M cells on the previous planning engine. The calculation figure is compared with the March preview; for writeback, the full benchmark in Part 2 shows up to 13× at 12M cells. Performance varies with semantic model design and capacity. For every user-facing improvement, see Part 3.

You can now enable the Native Planning Engine in Tenant settings as a Public Preview capability, as announced on our roadmap at FabCon Barcelona. Planning inputs are stored in OneLake as Apache Arrow files and loaded in memory for planning, so Plan items no longer need a separate system database.

We are also excited to share that you can now write back directly to OneLake as a new writeback destination, in Delta Parquet format. We cover that in Part 2: Writeback to OneLake.

In this article:

Turn On the Native Planning Engine

The Native Planning Engine is turned on by the Store new Plan items in OneLake setting. Once it is on, planning inputs are persisted in OneLake, and business output tables can write directly to OneLake as Delta Parquet. Turn the setting on at two levels.

1. Tenant Level

Your Fabric administrator opens the Admin portal, goes to Tenant settings, turns on Store new Plan items in OneLake, and selects Apply.

Fabric Admin portal, Tenant settings: the Store new Plan items in OneLake setting is expanded with its toggle set to Enabled and the Apply button highlighted.
Admin portal → Tenant settings: turn on Store new Plan items in OneLake, then select Apply.

2. Workspace Level

In the workspace that holds your Plan items, open Workspace settings, go to Plan settings under Delegated Settings, and turn on Store new Plan items in OneLake.

Workspace settings showing Plan settings with the Store new Plan items in OneLake toggle turned on
Workspace settings → Plan settings: turn on Store new Plan items in OneLake.

What to Expect After You Turn On the Setting

  1. New items use the new engine. All new Plan items are created in Native Planning Engine mode.
  2. Start with new items. Create new Plan items first and experience the better performance and scale.
  3. Move existing items when you’re ready. Follow the migration plan below.

At general availability, every remaining Plan item moves automatically. GA is planned in the next few weeks. Plan items still on the previous planning engine will be migrated to the Native Planning Engine, so we recommend moving and checking your key items during the preview.

Massive Scale and Performance with the In-Memory, File-Based Native Planning Engine

Fabric Plan now runs on a brand new native, file-based, in-memory planning engine that raises the planning limit tenfold, from 1.2 million to 12 million cells in aggregate. Apache Arrow supports efficient planning data access, while Delta Parquet makes business writeback outputs available across Fabric.

Plan items no longer need their own system database. Planning inputs live in OneLake, so there’s one less item to provision and manage, and storage is billed as part of your Fabric capacity. Fabric SQL remains a fully supported writeback destination, and PowerTable uses it as its writeback database.

Power BI semantic models can be massive, from millions to billions of rows or more. Because Fabric Plan runs directly on top of those semantic models, it can support any number of dimensions, measures and scenarios. That sets it apart from other planning tools, where performance degrades as the number of dimensions, measures or scenarios grows.

Flexible Enough for Every Team, Built for Enterprise Scale

Any planning method, with the controls to run it across every line of business.

Fabric Plan capability map: plan on the data (tabular, measure, multi-country, multidimensional), model the business (row, driver-based, strategic, operational), built-in controls in every plan, powered by Rust and Apache Arrow.

Go deeper: tabular modelling and choosing a planning method, measure models, row models, driver-based planning, operational planning with PowerTable, writeback and automation, and governance with Audit Cell History.

Native Planning Engine: semantic-model queries feed Rust allocation and instant calculation, real-time business outcomes, and OneLake storage with Delta Parquet writeback outputs.
Input, calculation, persistence, and business writeback in one connected planning experience.

The Inventory Grid and Calculation Paths

The illustration shows 12 million model cells, with 2.4 million cells affected by the bulk input operation.

Inventory scale illustration: 100,000 SKUs × 24 months × 5 measures = 12 million cells, with a 2.4 million-cell lead-time change flowing through dependent calculations.
Illustrative values. Formula dependencies cross periods, measures, and hierarchy totals.

Match Planning Scope and Capacity

Data fetched through XMLA affects capacity and responsiveness. The size of an interactive planning model is distinct from the volume published in a writeback instance. For scaling techniques such as context filtering, dimension partitioning, cubes and PowerTable, see Key Considerations for Planning at Scale with Microsoft Fabric Plan.

Caution: watch your Power BI XMLA query and concurrency limits. Large plans can reach the XMLA query and concurrency limits of your Fabric capacity, which can cause throttling. Limits depend on your capacity size, so consider a larger capacity when you need to fetch more Actuals data per query from the semantic model.

Roadmap: Up to 120 Million Cells in the Planning Grid

With this release, the Native Planning Engine supports up to 12 million cells in aggregate, 10x the 1.2 million cells of the previous engine. That total covers Actuals fetched from your semantic model plus visual forecast and formula measures. Next on our roadmap is support for up to 120 million cells inside the planning grid, 100x the previous limit. At that point, the only limit will be how much data you can fetch efficiently from your semantic models without throttling. Data fetched through XMLA alone will be capped at around 12 to 24 million cells.

This is a forward-looking roadmap item; release timing may change.

Make the Native Planning Engine Your Default

The Native Planning Engine is our default recommendation going forward.

New Capabilities Require the File-Based Engine

Advanced modeling features require OneLake storage. Audit cell history and driver-based modeling are available now, and snapshots (frozen versions) arrive on December 8, 2026. These capabilities are supported only by the Native Planning Engine: they require its file-based architecture and will not be supported by the previous planning engine.

Fabric SQL remains a fully supported writeback destination.

Move Existing Items When Your Team Is Ready

Frequently Asked Questions

Who can turn on the Native Planning Engine?

A Fabric administrator turns on Store new Plan items in OneLake in Tenant settings. The setting can be delegated so that capacity and workspace admins can enable or disable it, and it is then turned on for each workspace in Workspace settings → Plan settings. See Turn on the Native Planning Engine.

Do existing Plan items change when I turn it on?

No. The setting applies to new Plan items. Existing items keep running on the previous planning engine until you migrate them, or until the automatic migration at general availability.

Is Fabric SQL still needed?

Yes, but not as the system database. Planning inputs are now stored in OneLake, which removes the need for a second database. PowerTable continues to use Fabric SQL as its writeback database, and Planning sheets continue to support Fabric SQL as a writeback destination, alongside OneLake writeback.

Does my data come with the item when I migrate?

Migrating an item from Item settings moves that item to the new engine. Copying an item with deployment pipelines creates a new item without its data, which is useful for testing. The recommended path is to smoke test first: copy the item with deployment pipelines, check it on the Native Planning Engine, then migrate the original from Item settings.

Can I move an item back to the previous planning engine?

No. Migration is one-way, so a migrated item can’t be moved back to the previous planning engine. Smoke test a copy first, as described above, before migrating the original.

What happens to the Fabric SQL system database?

Once every Plan item in the workspace has been migrated to OneLake, the Fabric SQL system database (the application database) can be safely deleted. If any Plan items in the workspace haven’t been migrated yet, leave the database in place so their metadata isn’t lost. Keeping it does no harm.

Does the new engine change what I pay?

The pricing model doesn’t change: Fabric Plan is still billed by session type on your Fabric capacity. What changes is the other resources part of the bill. Instead of charges for a Fabric SQL system database, you now incur OneLake storage. See how Fabric Plan pricing works.

Are there limitations during the preview?

No. There are no known limitations during the preview.

Resources and Feedback

The inventory illustration uses fictional data. Performance figures are examples, not performance guarantees.

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.