Fabric Plan evolves into a Native Planning Engine by supporting OneLake as its application database (AppDB) to store plan item metadata. This enables new capabilities and several performance improvements.
This article describes the new capabilities, benefits, and performance improvements available with OneLake storage in the Native Planning Engine. It also explains how to enable OneLake storage for new plan items and migrate existing items to OneLake.
By default, Plan uses a Fabric SQL database (__fabric_plan_sys)to store plan item metadata and support viewer collaboration and sharing.

With OneLake storage enabled, new plan items can use OneLake instead of this Fabric SQL database for the following storage purposes:
You can also migrate existing plan item metadata from the current application database (a Fabric SQL database) to OneLake.
As a native planning engine with OneLake support, you no longer need to configure a separate database connection for viewer collaboration or sharing of plan items. Access to shared plan items is governed by workspace rules and user roles in Fabric Planning.

In addition to simplifying storage and collaboration, OneLake adoption brings several performance enhancements and enables new capabilities.
The change applies only to the storage used for Plan artifact metadata (AppDB). It doesn't automatically change where planning sheet's writeback data is stored.
If you use a Fabric SQL database as the writeback destination for planning sheet data, you still need a Fabric SQL database connection to support writeback.
Similarly, for PowerTable, you need to configure a Fabric SQL database connection to connect to the database used for storing table data.
| Data or scenario | Storage |
|---|---|
| Fabric Plan application metadata (AppDB) | OneLake, when the tenant and workspace settings are enabled. |
| Planning sheet writeback data | Fabric SQL database or OneLake, depending on the writeback destination you select. |
| PowerTable sheet data | Fabric SQL database, as configured during PowerTable sheet creation. |
New capabilities, such as Snapshots and Audit cell history, are supported only with the Native Planning Engine. We recommend enabling and migrating to OneLake for AppDB so you're ready to adopt these capabilities.
OneLake adoption also brings performance enhancements planned across multiple phases. These enhancements are designed to make Fabric Plan faster and more responsive, including:
OneLake storage also simplifies the storage architecture by eliminating the need for a dedicated application database for plan metadata. It offers lower capacity consumption and cost compared to Fabric SQL databases, along with faster plan item creation and cell allocation. OneLake can support more than 10 million cells with improved allocation performance.
You need to enable the following tenant and workspace settings to start using OneLake as storage.
To set OneLake as the default storage source for new plan items, an administrator must first enable the corresponding OneLake setting in Fabric tenant settings.
In Admin portal > Tenant settings, under Plan settings, enable Store new Plan items in OneLake.
This setting applies to the entire organization.

A workspace admin must also enable the Store new Plan items in OneLake setting. When enabled, OneLake is used as the default application database (AppDB) storage destination for metadata associated with all new plan items created in that workspace.
This setting is available at Workspace settings > Delegated Settings > Plan settings.

After enabling both these settings:
Use the following steps to migrate an existing plan item's storage to OneLake.
After you migrate an existing Plan item to OneLake, you can't migrate it back to Fabric SQL database storage. Back-migration to Fabric SQL isn't supported.
To use Fabric SQL database storage again, you must disable the setting and can only create a new Plan item.



After migration, you can't change the storage to Fabric SQL for this plan item.
The migration takes a few minutes. The plan artifact metadata is migrated to OneLake successfully.

The Manage Connection option is disabled after the migration. All metadata and other artifact details are stored in OneLake going forward. The Set up connection banner also disappears.

Do not delete the Fabric SQL database until all Plan items in the workspace have been migrated to OneLake. Items that haven't been migrated continue to depend on the Fabric SQL database for metadata storage. Deleting the database before completing the migration breaks these items.
After an existing plan item is migrated to OneLake, its app metadata is stored in OneLake. You can then use capabilities such as Snapshots and audit cell history, along with the performance improvements offered by OneLake storage.
Migrating plan item metadata doesn't change how Fabric SQL databases are used for other purposes, such as storing writeback data. For example, if a plan item uses a Fabric SQL database as its writeback destination, that configuration remains unchanged, and writeback data continues to be stored in that database. Similarly, PowerTable continues to use its Fabric SQL database to store sheet data.
To use OneLake as your writeback destination, you need to select it while configuring the writeback destination. To learn more, see Configure writeback destinations.
