PowerTable turns your Fabric data into a no-code app. Teams can edit, track, approve and govern their data, right where it lives. From master and reference data to products, projects, tasks, timesheets and budgets, every team gets one secure place to work. No exporting to spreadsheets, and no waiting on IT. New to PowerTable? Start with What are PowerTable sheets in planning? on Microsoft Learn.

The PowerTable November 2026 release brings exciting enhancements across data management, analytics, project management, and automation. We’ve strengthened Security & Governance, enhanced Microsoft Teams integration across approvals and automations for more proactive tracking, and introduced JSON data type support to expand unstructured data capabilities. Crosstab gets richer pivot functionality, while Kanban brings improvements for easier data updates and tracking. We’re also introducing Earned Value Management metrics in Gantt to help monitor project and task health.

1. Security & Governance

PowerTable security now lets you control who sees and changes each column, and who manages the security settings themselves.

1.1 Column Access

Column Access, in Security, sets Read, Insert and Update permissions for each column of a table, per role. Read shows or hides the column. Insert controls whether a user can enter a value in a new row. Update controls whether a user can change a value in an existing row. Settings apply to all roles or to specific roles. When a user has several roles, an access is granted if any of those roles grant it.

Set Read, Insert and Update for each column, shown here for the Warehouse Manager role on the Employees table.
Set Read, Insert and Update for each column, shown here for the Warehouse Manager role on the Employees table.

Use case: An HR team shares one employee table with the whole business. Managers can see salaries for their reports but can’t change them, while HR administrators keep them up to date. For everyone else, the salary column simply isn’t there, so one table serves every team with no oversharing.

For a full walkthrough, see Column Access: Column-Level Security for PowerTable.

1.2 Control Which Contributors Manage Security Settings

The new Security access page sets whether Workspace Contributors can edit security and governance settings. Choose Yes for all Contributors, No for none, or Specific Contributors only for the Contributors you add to a list. The item owner, Workspace Admins and Workspace Members always have full edit access. The setting covers roles, user attributes, policies, approvals, row and column access, and creating and deleting sheets. It does not affect editing table or planning data. The same page also links to OneLake security, where you control who can access writeback data in OneLake.

Choose which Contributors can edit security and governance settings on the Security access page.
Choose which Contributors can edit security and governance settings on the Security access page.

Use case: A finance team works in a shared budgeting workspace where every member is a Contributor. Everyone can update budget data, but only the two team leads are on the list of Contributors who can change approval rules and column access. The team moves fast, and the controls stay in trusted hands.

How to Set Up Security & Governance

Where to find it: Open Security at the top right of the sheet. Column Access: Security › Column Access. Security access: Security › General › Security access.

Sheet toolbar with the Security button highlighted at the top right
Security opens from the top right of the sheet.

Column Access

  1. Open Security and select Column Access.
  2. Select the table you want to secure.
  3. Choose All Roles, or Specific Roles and add the roles to configure.
  4. Turn Read, Insert and Update on or off for each column.
  5. Select Save Changes.

Security access

  1. In Security, open Security access under General.
  2. Choose Yes, No or Specific Contributors only.
  3. If you chose specific Contributors, add them to the list.

2. Teams Channel Notifications

Automations and approvals can now post messages to Microsoft Teams channels.

2.1 Automations

Send a message in a channel is now available as an action in PowerTable automations. It works with Update, Insert, Delete, Insert using Forms and Button triggers. Write the message, then connect to Microsoft Teams and choose the team and channel to post to. Messages can include dynamic content. Insert fields from the record that triggered the automation, such as a task’s name or start date. Or add predefined values, such as the current date and time. Messages are sent with the permissions of the user who triggers the automation.

A Teams message for new high-priority tasks, with fields from the task inserted as dynamic content.
A Teams message for new high-priority tasks, with fields from the task inserted as dynamic content.

Use case: A high-priority task is created, and the delivery team’s channel hears about it in seconds: “New high-priority task Payment Gateway Integration starts on November 25, 2026.” No one has to refresh a grid or forward an update to keep everyone in the loop.

2.2 Approvals

Approvals can now notify Teams channels in addition to the approvers. In Approvals Configuration, under Notifications, add one or more Teams channels. Each channel is listed with its team and the person who added it, and can be removed at any time.

Use case: A regional manager submits a budget change late in the quarter. The request shows up right away in the finance approvers’ Teams channel, where they’re already working together. Approvals keep moving without anyone digging through an inbox.

Approvals Configuration with Microsoft Teams channels under Notifications
Add Teams channels under Notifications in Approvals Configuration. Approvers still receive email by default.

How to Set Up Teams Notifications

Where to find it: Automations: Setup › Automations. Approvals: PowerTable › Approvals.

Automations

Setup tab with Automations highlighted
Automations sits on the Setup tab.
  1. Open the automation and set its trigger: Update, Insert, Delete, Insert using Forms or Button.
  2. Select Add Action and choose Send a message in a channel as the Action Type.
  3. Write the message. Select + to insert fields from the record or predefined values.
  4. Under Configure Channels, select Add Channel, connect to Microsoft Teams, and choose the team and channel.
  5. Save the automation.

Approvals

PowerTable tab with Approvals highlighted
Approvals sits on the PowerTable tab.
  1. Open Approvals Configuration.
  2. Under Notifications, select Add Channel and choose the team and channel.
  3. Select Save.

3. JSON Data Type

The JSON data type lets you store key-value pairs, nested objects and arrays in a single column, and edit them like any other field.

Use cases: Not all business data fits neatly into fixed columns. Now it doesn’t have to. JSON opens PowerTable to semi-structured data in every industry:

Configuring a Strict JSON column with field names, input types and display names
Define a Strict JSON column field by field, with an input type and display name for each.
Editing a Strict JSON cell in a side panel with controls for each field
Selecting a JSON cell opens a side panel with the right control for every field.

How it works:

How to Set Up a JSON Column

Where to find it: For a new column, PowerTable › Insert Column › Database Column. For an existing table, Setup › Columns.

  1. Upload a file, connect an existing table, or add a new column.
  2. Set the column’s data type to JSON.
  3. Choose the input type: Keys Only or Strict.
  4. For a Strict column, add each field with its name, input type and display name, and mark the mandatory ones.
  5. Save the table configuration.

4. Crosstab: A Complete Planning Canvas

Crosstab displays table data as a pivot. Dimensions sit in Rows and Columns, and the values in the cells are editable. Every change is written back to the source table.

Crosstab now lets you generate the grid you need, enter data at any level of detail, and decide how every value is summarized.

4.1 Generate the Planning Matrix Automatically

Generation Strategy sets which rows and columns Crosstab creates:

Use case: Picture a sales team planning by product, region and salesperson. Pair a product-region map with a region-salesperson map, and the planning grid builds itself. Every valid combination is ready to fill, and nothing that doesn’t belong gets in the way.

Under Generation Strategy, choose Valid Combinations and select the validity tables to generate from.
Under Generation Strategy, choose Valid Combinations and select the validity tables to generate from.
The generated Crosstab. Valid combinations are open for entry, and all others are shaded and read-only.
The generated Crosstab. Valid combinations are open for entry, and all others are shaded and read-only.

4.2 Multiple Column Dimensions

The Columns field accepts multiple dimensions, such as Region, Salesperson and Month. Their order sets the header hierarchy. Date, single-select and lookup fields can be combined.

Use case: A sales director reviews targets across the whole organization. With Region, Salesperson and Month stacked in Columns, every salesperson in every region appears side by side, month by month, in one view. No more stitching reports together to see how the team is tracking.

Region, year and month stacked in Columns, in the order you set.
Region, year and month stacked in Columns, in the order you set.

4.3 Dates in Rows

Date fields can now be added to Rows. They use the same Time Interval, Date Range and Date Hierarchy settings as in Columns. Crosstab generates a row for each period in the range, and can add Year and Quarter columns from the hierarchy.

Use case: A product planner builds a monthly forecast with months down the side and regions across the top. The year and quarter stay in view next to every month, so seasonal patterns are easy to spot. Forecasting feels as easy as a spreadsheet, with every number saved straight to the source.

Product, Year and Month in Rows, with a row generated for every month in the range.
Product, Year and Month in Rows, with a row generated for every month in the range.

4.4 Row-Only Layouts

A Crosstab can be configured with only Rows and Values, without a Column dimension. Generation, aggregation and subtotals work the same way.

A row-only Crosstab with Salesperson and Region in Rows and Sales Quantity as the value.
A row-only Crosstab with Salesperson and Region in Rows and Sales Quantity as the value.

Use case: A finance team collects budget lines by department and cost center. A row-only Crosstab gives them a clean list to fill in, with subtotals for each department rolling up on their own. No extra columns and no manual totals.

4.5 Drilldown

With Drilldown on, selecting a cell opens a detail view of the values behind it. Drill by field, such as Task under Project. Or drill by time, such as Week or Day under Month. Values entered in the detail view are written to the matching record and date. With Drilldown off, a Period Reference Date sets which date each summary value is read from and written to. Choose First Day, Last Day or a specific day.

Use case: A project manager reviews logged hours by project and month. When a month looks light, they open the cell and enter hours week by week, task by task. The big picture and the fine detail stay one click apart, and every value lands on the right record and date.

A March cell for one salesperson and region opened with Drilldown, ready for entry by product, week by week.
A March cell for one salesperson and region opened with Drilldown, ready for entry by product, week by week.

4.6 Value Aggregation

Each field in Values has its own aggregation, set from its ellipsis menu. Number fields support Sum, Average, Minimum, Maximum, Count and Count Distinct. Text and date fields support First, Last, Count and Count Distinct. Binary fields support Count and Count Distinct. The aggregation applies to subtotals, grand totals, drilldowns and collapsed column groups.

Use case: A delivery lead tracks hours and status for every task in one Crosstab. Hours are summed for each period, while Status shows the latest value, so effort and progress sit side by side. Every number tells the story it should.

Sales Quantity totals and the latest Status side by side, with totals by year and region.
Sales Quantity totals and the latest Status side by side, with totals by year and region.

How to Set Up Crosstab

Where to find it: PowerTable › Layout › Crosstab. To change an existing Crosstab, PowerTable › Layout › Manage Layout.

Layout menu with Crosstab highlighted
Switch to Crosstab from the Layout menu on the PowerTable tab.
  1. Open the Crosstab layout configuration.
  2. Assign dimensions to Rows and Columns. Add several dimensions to Columns, add a date field to Rows, or leave Columns empty for a row-only layout.
  3. Add fields to Values, and choose each field’s aggregation from its ellipsis menu.
  4. Under Generation Strategy, choose None, All Combinations or Valid Combinations. For Valid Combinations, select one or more validity tables, then set the interval and generation range.
  5. Turn on Drilldown and choose a drilldown field or time interval. Or leave it off and set a Period Reference Date.
  6. Save the layout.

5. Kanban: Keep Work Flowing

Kanban groups table rows into stacks by a status column. Moving a card to another stack updates its status.

Kanban now lets you set a limit on each stage and add new stages without leaving the board.

5.1 Stack Limits

Stack Limit, in each stack’s menu, sets the maximum number of cards a stack can hold. It works for any stack, whether the board is grouped by stage, owner, priority or any other column. The header shows the current count against the limit. A red Max marker appears when the count goes over it. Each stack can have its own limit, or none.

Use case: A development team caps its Review stack at six cards. When a seventh card lands, the Max marker appears on the header, and the team knows it’s time to finish reviews before starting anything new. Bottlenecks show up before they become problems.

Set the limit from the stack menu. The header shows the card count, and the Max marker flags a stack that’s over its limit.
Set the limit from the stack menu. The header shows the card count, and the Max marker flags a stack that’s over its limit.

5.2 Add a Stage from the Board

The + Add Stack button sits after the last stack. The name is added as a new value of the status column. Cards moved into the stack take that value when saved.

Use case: Work on an integration stalls while the team waits on a vendor. The team lead adds a Blocked stage straight from the board and moves the affected cards into it. Everyone can see what’s stuck, and the board stays an honest picture of the work.

The + Add Stack button after the last stack on the board
Add Stack sits right after the last stage on the board.

How to Set Up Kanban Limits and Stages

Where to find it: PowerTable › Layout › Kanban.

Layout menu with Kanban highlighted
Switch to Kanban from the Layout menu on the PowerTable tab.

Stack limits

  1. Open a stack’s menu and select Stack Limit.
  2. Enter the maximum number of cards for that stack.

New stages

  1. Select + Add Stack after the last stack.
  2. Type a name and press Enter.
  3. Move cards into the new stack and select Save to Database.

6. Earned Value Management

Earned Value Management lets you see whether a project is on schedule and on budget, in the same plan your team works in.

Earned Value Management (EVM) is the standard project control method for tracking schedule and cost together. It complements your Gantt schedule by showing whether spending is in line with progress. EVM compares three figures against an approved baseline. These are the budgeted value of work planned to date, the budgeted value of work completed, and the actual cost so far.

Add EVM metrics as derived columns in the Gantt layout, right beside the schedule.
Add EVM metrics as derived columns in the Gantt layout, right beside the schedule.

PowerTable now calculates EVM on your project plans. Inputs from your task, resource and time-entry tables are mapped once in Layout Configuration. PowerTable then calculates Budget at Completion, which is locked when you save a baseline. It also calculates Planned Value, Earned Value, Actual Cost, Schedule Variance, Cost Variance, Schedule Performance Index (SPI) and Cost Performance Index (CPI). Variances show how far ahead or behind a project is in money terms. An SPI or CPI below 1.0 means the project is behind schedule or over budget.

Use case: Take a $100K project with an SPI of 0.88 and a CPI of 0.78. An SPI of 0.88 means the team has completed 12% less work than scheduled so far. A CPI of 0.78 means every dollar spent is earning 78 cents of budgeted work. Your PMO knows while there’s still time to act.

How to Set Up Earned Value Management

Where to find it: On a Gantt layout, PowerTable › Insert Column › Visual Column › Add Derived Column.

Insert Column menu with Add Derived Column highlighted under Visual Column
Add Derived Column sits under Insert Column › Visual Column on the PowerTable tab.
  1. In the Gantt layout configuration, map your task, resource and time-entry columns, such as dates, effort, progress, rates and costs.
  2. Save a baseline to lock in Budget at Completion.
  3. Select Add Derived Column, expand Earned Value Management, and select the metrics to show.
  4. Select Apply.

Try the PowerTable November 2026 Updates Today

This release helps teams spend less time wrangling data and more time acting on it. Because it all runs on your Fabric data, everything stays in one governed place.

Start with the update closest to a challenge your team has today: a sensitive column, a product table full of empty cells, or a board that’s always overloaded. Turn it on, and see what changes.

Secure data, flexible structure and plans that build themselves, all in the place your teams already work.

Feature details reflect Fabric Plan at the time of writing.

The Native Planning Engine stores planning data and application metadata as files in OneLake. That one architectural shift, together with optimizations across the product, makes Fabric Plan faster from the first click to the final writeback.

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

Covered in Parts 1 and 2: 10× more scale (12M cells), 10× faster calculation and up to 13× faster writeback.

Fabric Plan performance improvements: up to 79% faster adding a Planning sheet, 53% faster creating a Plan item, 60% faster catalog loading, about 50% faster filter lists, up to 80% faster Intelligence Sheets, and an app download less than a third the size.

Figures come from our testing. Performance varies with workload, model design, data size and capacity.

One Architecture Change, Felt Across the Product

With the Native Planning Engine, planning data and application metadata are stored as files in OneLake, and Plan items no longer need a separate system database. The benefits go well beyond the calculation and scale gains in Part 1 and the writeback gains in Part 2: creating and opening Plan items, adding Planning sheets and returning to views you use often are all faster too.

We also optimized start-up, the catalog, filters and Intelligence Sheets. Some of these improvements reach every Plan item; the full set comes with the Native Planning Engine and OneLake.

In this article:

Fabric Plan Performance Improvements, Before and After

The same everyday tasks, from launch to writeback, before and after the Native Planning Engine and OneLake.

What you doBeforeAfterChange
Launch Fabric PlanA large application to download firstA compact package that loads quickly, even on slower networksLess than ⅓ the size
Create a Plan itemSet-up took about twice as longReady for planning in about half the timeUp to 53% faster
Open a Plan itemSlower to openOpens up to a third soonerUp to 33% faster
Add a Planning sheetAdding a sheet took up to five times as longNew sheets are ready in a fraction of the timeUp to 79% faster
Browse the catalogThe full catalog loaded up frontEach section loads as you open itUp to 60% faster
Open a filterLong member lists took time to appearLists appear with only the members you needAbout 50% faster
Plan at scaleUp to 1.2 million cells in aggregateUp to 12 million cells in aggregate (Part 1)10× more scale
Calculate the planCalculations on the previous planning engineIn-memory calculation on the Native Planning Engine (Part 1)10× faster
Load an Intelligence SheetVisuals competed for shared resources while loadingVisuals load side by side without waiting on each otherUp to 80% faster
Return to a view you use oftenData was fetched again each timeA fast local copy is used firstFaster repeat visits
Write back resultsSQL-based writesFile-based Delta Parquet writes directly to OneLake (Part 2)Up to 13× faster
Your planning experience, before and after

What it means for your team: less waiting during planning sessions, more scenarios tested before a deadline, and a tool that more people keep using.

Four Ways to Get the Most from These Improvements

Some of the result depends on how your environment is set up. These four steps make the biggest difference.

1. Migrate to OneLake

The file-based architecture is what unlocks the full set of improvements in this blog. Plan items still on the previous planning engine miss many of them.

Turn on Store new Plan items in OneLake at the tenant and workspace levels, start with new Plan items, then migrate your existing ones gradually. Part 1 walks through each step.

2. Write Back to OneLake

Saving planning results to OneLake makes everything above even more effective. Your plans, forecasts and assumptions sit in one governed place, and reporting across Fabric reads them directly.

File-based Delta Parquet writes to OneLake are about 5–6× faster than SQL-based writes at typical volumes and up to 13× faster at 12M cells. Fabric SQL remains a fully supported writeback destination. Part 2 shows how to set it up.

3. Keep Your Semantic Model in Good Shape

Fabric Plan reads data from your semantic model, and how long that takes depends on how well the model performs.

Outside Fabric Plan’s scope. The improvements in this blog cover what happens inside Fabric Plan. They do not change how quickly your semantic model loads. If you want data to arrive faster, work with your semantic model owner to keep the model well designed and efficient.

4. Bring In Only the Data You Need

The more detail a planning sheet holds, the more work it has to do. Detail that nobody plans against makes the sheet slower without adding value.

  1. Plan at the level your decisions need. If a team plans by region and month, there is no need to load every product and day.
  2. Use filters and RLS to focus each user on the part of the plan they own. With these set up properly, most teams won’t need more than 2.4 million cells in a planning grid.
  3. If your use cases still need more than 12 million cells, consider multidimensional cube modeling, or dimension partitioning with consolidation through InfoBridge or PowerTable–Planning integration (see Part 1).

For scaling techniques such as context filtering, dimension partitioning, cubes and PowerTable, see Key Considerations for Planning at Scale with Microsoft Fabric Plan.

Complete Your OneLake Migration

Move your Plan items to the Native Planning Engine, write back to OneLake, and keep your data model and sheets lean. You get faster planning everywhere, from the first click to the final writeback.

Start with Part 1: turn on the Native Planning Engine, then Part 2: write back to OneLake.

Learn more in the Fabric Plan documentation and on Microsoft Learn.

Appendix: How Each Improvement Works

For readers who want to know what changed behind the scenes at each step.

Improvements are described as “up to” or approximate figures, and results vary with workload, model design, data size and capacity.

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.

Intelligence Sheets turns your Fabric data into reports people can read, analyze, and act on. Teams build variance reports, dashboards, and analysis on the same semantic model, security, and backend as the rest of Fabric Plan, with standard IBCS® notation and their plans in the same place. New to Intelligence Sheets? Start with What are intelligence sheets in planning? on Microsoft Learn.

Here’s what’s new in Intelligence Sheets for November 2026. This release brings enhancements across visuals for performance, integrated planning and reporting, security, and authoring experiences:

1. Performance

We have made significant improvements to performance and usability across building, reading, and sharing reports. You’ll notice the difference in how quickly reports load, how they respond as you work, and how comments behave during collaboration. These build on the platform-wide gains described in Part 3 of the Native Planning Engine series, including up to 80% faster loading for Intelligence Sheets with many visuals.

2. Embedded Planning and PowerTable Sheets

Embedded Planning Sheets in Intelligence Sheets now include the full Planning Sheet toolbar. Apply filters with Super Filters on the canvas and adjust formatting and customization at the same time, without leaving the report. The same options are available in reading view.

Revenue and profitability planning report in Intelligence Sheets with an embedded Planning Sheet selected and the full Planning toolbar
An embedded Planning Sheet in an Intelligence Sheets report, with the full Planning toolbar available alongside KPIs, a product master table, and a revenue chart.

2.1 PowerTable Quick Measure Support in Intelligence Sheets

Quick Measure in PowerTable sheets now includes time intelligence. Add prior-period values, period-over-period change, and YTD, QTD, or MTD totals without writing date logic. PowerTable quick measures are also supported in Intelligence Sheets and can be used in any visual via From Sheets in the Data pane.

3. Organization Tree Visual

The new Organization Tree visual displays employee or cost center hierarchies from your semantic model as an interactive org chart.

To add it, select Tree in the Visualizations pane, then choose Organization Tree under Tree Types.

Organization Tree brings the hierarchy and organizational performance use cases of the xViz Performance Flow visual natively into Intelligence Sheets.

Organization Tree in sparkline view with four reporting levels and sample data
Organization Tree in sparkline view. Illustrative, with sample data.

Organization Tree also supports a left-to-right layout for performance hierarchies, with the value, variance, and trend on every node.

Organization Tree in a left-to-right layout showing Sum of Sales by region, segment, and category, with variance and column sparklines on each node
Organization Tree showing Sum of Sales by region, then segment, then category, with variance and a trend on every node.

4. Decomposition Visual

The new Decomposition visual breaks a measure down level by level, across dimensions and hierarchy levels, in the order you choose. Each level shows which branch contributes most.

To add it, select Tree in the Visualizations pane, then choose Decomposition Tree under Tree Types.

Decomposition visual breaking Sum of Sales down by category and Furniture subcategory
Decomposition visual showing Sum of Sales by category, then by Furniture subcategory. Each node shows the actual, the comparison, and the variance. Illustrative, with sample data.

5. Chart and Table Updates

New options for matrices, tables, and charts:

5.1 Matrix and Table Enhancements

Visible Rounding

Matrix and Table visuals have a new aggregation type, Visible Rounding. It calculates totals from the rounded values displayed, using the visual’s display precision and rounding rules, so totals match the visible values. Source data is unchanged, and other aggregation types work as before.

Current assetsValue ($M)Displayed, no decimals
Cash and cash equivalents14.414
Accounts receivable2.32
Inventory15.215
Other receivables1.62
Total, standard aggregation33.534
Total, Visible Rounding33.533

Example: current assets on a balance sheet, shown without decimals. Standard aggregation rounds the actual total, 33.5, up to 34, but the lines a reader sees add up to 33. Visible Rounding adds the displayed values (14 + 2 + 15 + 2 = 33), so the balance sheet ties on screen.

5.2 Chart Enhancements

Conditional Formatting on Line, Area, and Marker Charts

Apply conditional formatting by rule, measure type, or custom measure, for example to flag missed targets, distinguish actuals from forecast, or mark thresholds. It’s ideal for multi-scenario forecasting and budget planning, where each scenario can be formatted differently so scenarios are easy to compare.

Forecast revision line chart with dashed budget lines beside a Manage rules panel with one rule per series
Conditional formatting rules for each series of a line chart, managed in one panel. Illustrative, with sample data.

Valid Points on Line Charts

Line charts can plot only valid periods, so forecast and partial-year series don’t drop to zero. With Use valid points turned on in Format › Data label, the end label anchors to the last period with data instead of the last category.

Before and after: a line chart data label on the last category shows nothing, and with Use valid points on it anchors to September, the last month with an actual
With Use valid points turned on, the end label moves from the empty last category to the last month with data. Illustrative, with sample data.

Marimekko Scale and Limit

Marimekko charts can now show column width as a percentage of the total, together with category labels on the x-axis.

Marimekko chart of total sales and orders by region, split by product category
Marimekko chart: column width shows total orders by region, and segment height shows the sales mix by category. Illustrative, with sample data.

Dynamic Bands on Gauges

On angular and linear gauges, band start and end values follow the current selection or filter.

Angular gauge with red, amber, and green bands whose boundaries come from the measures Sum of B1 and Sum of B2
Angular gauge with band boundaries set by measures in the Primary bands field. Illustrative, with sample data.

6. Gantt Visual

The Gantt visual supports the complete functionality of the xViz Gantt chart. New in this update:

Gantt visual with the column width menu open showing Fit to Header, Fit to Content, and Manual Column Width
Column width options in the Gantt toolbar: Fit to Header, Fit to Content, and Manual Column Width.

7. Authoring Experience

Line chart selected on a report, with the new outer toolbar across the top and the Settings side panel open
The outer toolbar for a selected line chart, with the Settings side panel open.

8. Governance: Roles and Security

Administrators can now configure reading view settings for each role in Security › Roles › Reading View Customization.

Roles settings for the Viewer role: reading access by sheet and reading view controls by visual type
Reading View Customization for a Viewer role: reading access by sheet, and available controls by visual type. Illustrative, with sample data.

9. Storytelling: Notes, Marker Mode, and Comments

Matrix of AC vs PY by product category with notes pinned to cells and an All notes panel
Notes pinned to Matrix cells and listed in the All notes panel. Illustrative, with sample data.
Overlapped column chart with its comment thread open in the Visual level tab of the All comments pane
Visual-level comments: each visual keeps its own thread, listed in the Visual level tab of All comments. Illustrative, with sample data.

10. IBCS® Certification

Fabric Plan is IBCS® certified, aligned with ISO 24896:2026. IBCS® notation, automatic AC, PL, PY, and FC scenarios, and themes are available across 100+ charts and templates.

  • The IBCS® theme is now available across all three sheet types: Planning, PowerTable, and Intelligence.
IBCS® certification seal: Certified Charts + Tables, + ISO 24896, Microsoft Fabric Planning, 2026 | 04

Try the Intelligence Sheets November 2026 Updates Today

Intelligence Sheets has seen major improvements in performance, UI, and capability. Business users can build financial, management, variance, and paginated reports, executive scorecards, and ad hoc analysis without code.

Reports can draw on semantic models, on Planning sheets with budgets, forecasts, and scenarios, on PowerTable sheets and queries, and on data from platforms such as Snowflake, Databricks, and SAP through shortcuts and mirroring. Combine the sources that best fit each analysis, blend measures across them, and plan, analyze, and update in one place.

New visuals, role-based reading views, and planning inside your reports, all in the place your teams already work.

Planning to retire legacy BI tools such as Tableau, Qlik, or Cognos? Try Intelligence Sheets in Fabric Plan, a full BI suite on the Power BI semantic model.

Legacy BI tools for visual analytics, enterprise reporting, board packs, and exploration redirected to Intelligence on Microsoft Fabric
Consolidating visual analytics, enterprise reporting, board packs, and exploration on Intelligence Sheets in Microsoft Fabric.

Resources

Feature details reflect Fabric Plan at the time of writing.

Fabric Planning was announced at FabCon Atlanta in March 2026 to bring planning, analytics and decision-making together in one place. Finance and business teams often plan in one tool, report in another, and explain the numbers in slide decks and email threads. Each switch takes time, and the context behind the numbers gets lost.

The Intelligence Sheet brings management reporting into the same Plan item where planning happens. Teams connect to their semantic model, build planning models, create budgets and forecasts, and deliver reports in one place.

This release adds IBCS® certification, embedded planning, Intelligence Sheets in organizational apps alongside Power BI, and data-linked annotations, along with enhancements that make reports faster to build and easier to read.

Overview: The Intelligence Sheet interface

IBCS® certified reporting

Microsoft Fabric Planning is IBCS® CERTIFIED Charts+Tables (International Business Communication Standards). It is also certified to ISO 24896:2026, Notation for business reporting: the certification confirms that business charts and tables in the Intelligence Sheet are designed to the ISO standard. Finance users get a standard visual language they recognize on sight.

IBCS certified charts and tables in the Intelligence Sheet

Demo: Build IBCS reports in Microsoft Fabric

Embedded Planning grids, PowerTable grids and Forms

Planning grids, PowerTable grids and Forms can now be embedded directly in an Intelligence Sheet, alongside charts, KPIs, and Gantt, Resource, Kanban and Calendar views.

A PowerTable form, PowerTable grid and planning grid embedded beside KPIs and a chart

What this changes for planning teams

The report is no longer only the last step in the planning cycle. It is where teams analyze, decide and act.

Demo: Planning integration in the Intelligence Sheet
Demo: PowerTable integration in the Intelligence Sheet

Intelligence Sheets in organizational apps, alongside Power BI

Intelligence Sheet reports and Planning Sheets can now be added as pages in a Power BI or Fabric organizational app, alongside your existing Power BI reports. Intelligence Sheets and Power BI reports co-exist in the same app, so teams keep using the reports they already have and add planning and IBCS reporting next to them.

Demo: Intelligence and Planning content in an organizational app, alongside Power BI reports

Notes, markers and data-linked annotations

Notes, markers and annotations now stay connected to the data and the filter context behind them, so insights can be reviewed, presented and discussed directly in the report.

Notes, marker mode and annotations on a financial performance report

Demo: Collaborative commentary and annotations

Additional enhancements

Matrix enhancements

Row grouping and reordering, sorting, comments and themes, with better support for blended and non-semantic values.

Images

Add images to the report canvas, and use image URLs and SVGs in charts and KPI visuals.

Variables with actions

List, number, date and date-range variables put assumptions in the reader's hands. Variables drive formulas, formatting and actions, and can be bound per environment through Fabric variable libraries, so the same report points at the right values in test and in production.

Demo: Configure an action parameter

Split categories and group measures

Change how data is pivoted in a visual by grouping measures and splitting categories, without changing the source data. For example, show actual, plan and prior year side by side within each period.

Images on the canvas, grouped measures and matrix enhancements

Get started

Explore more updates

Videos

For more, visit the video library.

PowerTable sheets in Fabric Plan, is a no-code data app for managing dimensions, master and reference data, and business entities, stored and governed in Fabric SQL tables. 

Here's a roundup of the latest updates, covering security, automation, data entry, tracking and everyday usability. 

1. Security - Layered Up! 

Protect sensitive data with security that builds in layers. Access starts at the database and narrows further in PowerTable, with flexible rules that adapt to how each organization defines who should see what. 

2. Automation  - Now Doing More! 

Let every change set the next one in motion. New automation actions use the data entered in PowerTable to trigger further updates across Fabric items and databases, keeping connected systems in sync without manual effort: 

3. Data Input - Opened Wider 

More data, more ease to bring it in. PowerTable now provides greater flexibility at the point of entry: 

4. Insights, Upgraded! 

PowerTable now exposes more metrics and perspectives, making effort and workload easier to track: 

5. Quicker Actions 

The most common scheduling and restructuring actions are now right where you work: 

6. Usability Upgrades 

In the pursuit of a more intuitive, personalized and collaborative experience, PowerTable now includes the following updates: 

That's the latest from PowerTable. Grab a table, try something new, and watch this space for what's next. 

Learn more 

Every Fabric Planning update announced at FabCon Europe in Barcelona, with a short demo video for each feature.

At FabCon Europe 2026, Microsoft announced a new set of capabilities for Planning in Microsoft Fabric. The updates make planning simpler to set up, faster at enterprise scale, more tightly connected to Power BI semantic models and the rest of Fabric, and easier to govern as adoption grows.

Microsoft's announcement covers the headline features: Planning in Microsoft Fabric: From insight to action. This post goes through the full list of updates, shows each one in a demo video, and marks which features are in preview or coming soon.

Overview: What's new in Fabric Plan

What's new with Planning

The Planning updates are grouped into five areas, followed by the limitations removed in this release.

1. Start faster

These updates cut down the setup needed before a team can begin working on the numbers.

No-setup connectivity for semantic models

Connecting a plan to a semantic model is now as simple as building a Power BI report: a single click, with the same workspace permissions you already use in Power BI.

Create Plan → choose semantic model → connect → start planning.

Until now, most onboarding effort went into setting up and maintaining the DMTS connection, and into fixing plans when that connection expired. That setup is gone.

BeforeNow
Create and share a DMTS connectionNot needed
Recover plans after a DMTS connection expiresNot needed
Configure a shared cloud connection and service principalNot needed
Turn on tenant settings, including XMLAOn by default
Workspace Admin or Member rights, and Build permission on the semantic modelSame permissions as building a Power BI report

Existing permissions and data access controls continue to apply, so nothing new has to be secured.

Demo: Simpler onboarding, from semantic model to plan

Home Layout

Different teams often work inside the same Plan item but need different information. Home Layout lets you create dedicated landing pages for each role within one Plan item.

Each team lands on what it needs first, with less navigation, and one Plan item can serve every team.

Demo: Home Layout

2. Plan at scale

These updates support detailed, driver-based plans that stay connected to enterprise targets.

Native Planning Engine Preview

The new Native Planning Engine is built on Rust and Apache Arrow with tight OneLake integration. It delivers up to 10x improvements in performance and scale.

Demo: Native Planning Engine

How much scale do you need? Recommendations

Semantic models can hold billions of rows, but a plan usually works with a few dimensions in rows, time in columns and a set of measures. Most plans need no more than 1.2 million cells. With filters and row-level security (RLS) on the semantic model, that is enough scale for most customers.

The Native Planning Engine supports up to 12 million cells in a planning model. Large plans are still limited by two things outside the engine:

Our recommendations:

Multi-driver, multi-measure simulations

You can now test several drivers together and see their combined effect on the measures that matter.

Related demo: Driver-based planning in Tree View, with a P&L at every node

More ways to model and deliver planning

Demo: Lookup columns in PowerTable

3. Put plans to work

These updates move approved plans and forecasts into analysis, agents and downstream workflows.

Semantic model integration

Planners can now write plan data back into the same semantic model the plan is built on, so actuals and plans live in one governed model.

Demo: Add the writeback table to the semantic model

Fabric IQ ontology and Data Agents

Once plan data is in the connected semantic model, Fabric IQ can use plans and forecasts alongside actuals.

Demo: Add the plan table to semantic models and the ontology

Event Triggers

A plan rarely stops when a value is submitted. Event Triggers let planners configure, from the planning UI, what runs when a writeback starts, succeeds or fails.

Demo: Event Triggers

Execute Stored Procedure in PowerTable Automations

PowerTable Automations already provide no-code actions for creating, updating and managing records. Some processes depend on logic that lives in the database. Execute Stored Procedure brings that logic into the same automated workflow.

Demo: Stored procedure execution in PowerTable Automations

OneLake writeback (Coming soon)

Fabric Planning will add OneLake as a native writeback destination, as an alternative to Fabric SQL Database.

4. Reach the business

These updates bring planning into the apps people already use and extend it to the people who know the business.

Planning in organizational apps

Planning Sheets and Intelligence Sheet reports can now be embedded as pages in a Power BI or Fabric organizational app, alongside Power BI reports and related analytics.

Demo: Embed Plan in an organizational app

Planning and PowerTable in the Intelligence Sheet

A planner who builds a detailed planning sheet often also needs KPIs, charts and a management-ready view of the same plan. The Intelligence Sheet can now hold Planning and PowerTable content together in one sheet.

Demo: Planning integration in the Intelligence Sheet
Demo: PowerTable integration in the Intelligence Sheet

Direct sharing of Plan items

A Plan item can now be shared directly with any user, even if they are not a member or viewer of the workspace it lives in.

Microsoft Entra B2B guest access

Guest users invited through Microsoft Entra B2B can now access and collaborate on Plan items in the same way as internal users.

Notes, Marker Mode and Annotation

Report authors can add narrative and context directly around the data, so a report explains itself when it is presented.

Demo: Collaborative commentary and annotations
Demo: Adding notes and using Marker Mode

IBCS® certified reporting

Fabric Planning is IBCS® certified, aligned with ISO 24896:2026.

Demo: Build IBCS reports in Microsoft Fabric

5. Govern growth

These updates give administrators control over access, capacity and permissions as more teams adopt planning.

Tenant-level session upgrade controls

Until now, any user who entered data, wrote back changes or collaborated was upgraded automatically from a Viewer session to a Stakeholder session. Three new Plan tenant settings in the Fabric Admin Portal let administrators decide who can upgrade and see capacity impact before it happens.

Demo: Session types and tenant settings

Capacity throttling

Fabric capacity controls now apply consistently to planning as it reaches a wider audience.

Row-level security for PowerTable

Teams that write back to shared tables rarely need the same access to the same data. Row-level security brings data-driven access control into PowerTable, down to the individual row.

Demo: Roles and policies-based security in PowerTable

Contributor security controls Coming soon

A new setting will let administrators control which Contributors can change security and governance settings in a Plan item.

Fabric Planning supports Microsoft Fabric Private Link at both tenant and workspace level.

PowerTable-only billing

Microsoft recently announced a billing change for non-planning editors. For PowerTable-only data management, editors are billed as Stakeholders and consumers as Viewers, so teams get full data management without a Planner session.

6. From known limitations to known wins

Several limitations from earlier releases have now been removed.

Access and connectivity

FeatureMarch 2026Now
B2B user supportNoYes
Private Link supportNoYes (Preview)
Semantic model connection authenticationOAuth / service principalAll supported authentication methods
Admin/Build permission required on semantic modelRequiredNo
Direct Lake semantic models need extra configurationYesNo

Scale and capacity

FeatureMarch 2026Now
Power BI Pro / PPU / lower-capacity SKUs (no XMLA support)NoYes
Bulk data input limit1M rows10M rows

Workspace, deployment and data security

FeatureMarch 2026Now
CI/CD deployment with a service principalNoYes
Database-level row-level security (RLS)NoYes
DMTS connection recoveryManual rebuild neededYes
Contributor role: create/share cloud connectionsNoNot applicable
Contributor role: Plan items requiring embed tokensNoNot applicable

What comes next

Microsoft's stated next step is an API surface for the planning lifecycle, so an agent can work inside a plan the way a planner does: draft a forecast, run a simulation across drivers, compare scenarios before a commitment is made, write the result back, and start the downstream work it sets in motion.

What's New with Fabric Planning: webinar

We will walk through these updates in a live session, with demos and time for questions: Register now

Learn more

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.