> For the complete documentation index, see [llms.txt](https://docs.fabricplan.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fabricplan.com/documentation/plan/known-limitations-in-plan-preview.md).

# Known Limitations in Plan (Preview)

Review the following known issues and limitations before you begin working with plan (preview).

### B2B user support

Plan doesn't support Microsoft Entra B2B IDs.

### Private link support

Plan items aren’t supported in workspaces or tenants that use private links.

### Semantic model

* You must have *Admin* or *Build* permissions on the semantic model.
* Semantic models in Direct Lake mode require additional configuration.
* Semantic model connections support only OAuth-based and service principal–based authentication.
* Semantic models published in *My workspace* aren't supported.

### Capacities supported

Power BI Pro and Power BI Premium Per User (PPU) aren't supported for Plan scenarios that use XMLA endpoints and embed tokens. Similarly, lower-capacity SKUs that do not support XMLA endpoints are also unsupported.

### Database-level row-level security (RLS) support <a href="#database-level-row-level-security-rls-support" id="database-level-row-level-security-rls-support"></a>

PowerTable doesn't support user-specific database-level row-level security (RLS) when connecting to Fabric SQL tables through a database connection. As a result, users might see rows that differ from the expected RLS-filtered results. This limitation exists because PowerTable executes all database queries by using the identity associated with the database connection that the user configures during sheet creation, rather than the identity of the signed-in PowerTable user.

### PowerTable DMTS connection recovery <a href="#powertable-dmts-connection-recovery" id="powertable-dmts-connection-recovery"></a>

If you delete the DMTS connection that you configured for a PowerTable sheet, or if it becomes unavailable, you can't open the sheet to update the connection. The connection recovery screen doesn't appear, and you see the message "DMTS connection is deleted or not found."

To recover, create a new PowerTable sheet by using the Existing Table option and configure the same table again.

### Workspace permissions

* Users with the *Contributor* role can't create or share cloud connections.
* Users with lower-level workspace roles, such as *Contributor*, can't create Plan artifacts that require embed token generation.

### Workspace renaming <a href="#workspace-renaming" id="workspace-renaming"></a>

Don't rename a workspace that contains a Plan item. Renaming the workspace breaks the Plan item, and the item no longer opens.

### Bulk data input limit <a href="#bulk-data-input-limit" id="bulk-data-input-limit"></a>

Bulk data input supports a maximum of 1 million rows. Uploading more than 1 million rows from an Excel or CSV file isn't supported and might cause the upload to fail.

### Semantic model renaming <a href="#semantic-model-renaming" id="semantic-model-renaming"></a>

Don't rename a semantic model that's connected to a Plan item. Renaming the semantic model breaks the connection, and the Plan item no longer works with the renamed semantic model.

### Maximum number of sheets per item <a href="#maximum-number-of-sheets-per-item" id="maximum-number-of-sheets-per-item"></a>

A Plan item supports up to 25 sheets. Keep the number of sheets within this limit to avoid problems when working with the item.

### Maximum number of visuals per item <a href="#maximum-number-of-visuals-per-item" id="maximum-number-of-visuals-per-item"></a>

A Plan item supports up to 50 visuals. Keep the number of visuals within this limit to avoid problems when working with the item.

### Infobridge cell limit <a href="#infobridge-cell-limit" id="infobridge-cell-limit"></a>

Each Infobridge query in a Planning sheet supports up to 1.2 million cells. Queries that exceed this limit might fail to load or process.

To work with larger datasets, split the data across multiple Planning sheets and append the queries. This approach supports a consolidated workbook of up to about 5 million cells (for example, across five Planning sheets).

### Writeback cell limit <a href="#writeback-cell-limit" id="writeback-cell-limit"></a>

Writeback supports up to 1.2 million cells per operation. Writeback operations that exceed this limit aren't supported and might fail.

### Disclaimer <a href="#disclaimer" id="disclaimer"></a>

Supported limits might vary depending on client resources, Fabric capacity, and Power BI XMLA query limits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fabricplan.com/documentation/plan/known-limitations-in-plan-preview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.