> 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/readme/prerequisites-for-plan.md).

# Prerequisites for Plan

This article lists *all* the required prerequisites, tenant settings, and capacity settings that must be configured to use Plan.

### Tenant settings

[Fabric administrators](https://learn.microsoft.com/en-us/fabric/admin/roles) can grant access to these settings in the [admin portal](https://learn.microsoft.com/en-us/fabric/admin/admin-center) under [tenant settings](https://learn.microsoft.com/en-us/fabric/admin/tenant-settings-index).

1. Enable **Users can create Plan (preview) items**. This setting is required to create plan (preview) items.

<figure><img src="/files/Sa7dNw0cuGtoH2RPrD6M" alt=""><figcaption></figcaption></figure>

2. Under [**Integration settings**](https://learn.microsoft.com/en-us/fabric/admin/tenant-settings-index#integration-settings), enable **Allow XMLA endpoints and Analyze in Excel with on-premises semantic models**.

<figure><img src="/files/xnSaz6Pjlljl2LWzY7qj" alt=""><figcaption></figcaption></figure>

3. Under **Developer settings**, enable [**Embed content in apps**](https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-developer#embed-content-in-apps)**.**
4. For service principal-based authentication, enable [**Service principals can call Fabric public APIs**](https://learn.microsoft.com/en-us/fabric/admin/service-admin-portal-developer#service-principals-can-call-fabric-public-apis) under **Developer settings**.

<figure><img src="/files/zCgo6CRGZq3sD1SKnDj4" alt=""><figcaption></figcaption></figure>

### Capacity settings

1. Semantic models used with Plan must be hosted on supported capacities, such as
   * **Power BI Premium capacities (P1, P2, and higher)**
   * **Microsoft Fabric capacities (F SKUs)**
2. Plan scenarios that rely on XMLA endpoints and embed tokens require supported **Microsoft Fabric capacities (F SKUs)** or **Power BI Premium capacities (P1–P5)**. Power BI Pro and Power BI Premium Per User (PPU) aren't supported for these scenarios. Some lower-capacity SKUs can also have XMLA and memory limitations that prevent supported usage.
3. In the Power BI Admin portal, under **Capacity settings**, ensure that the **XMLA Endpoint** setting is configured as **Read Only** or **Read Write**.

<figure><img src="/files/YhkeI9VPD9BRKiN6A7yX" alt=""><figcaption></figcaption></figure>

### Semantic model connection owner permissions

The shared cloud connection owner, whether a user account or service principal, must have a workspace **Member** or **Admin** role.

### Database connections

#### Optional requirements

These are optional database connections that you can configure for specific scenarios such as collaboration and writeback.

1. Create and share a Fabric SQL database connection with report viewers so they can collaborate on the plan report. To know more, see [Create a database connection for collaboration](/documentation/readme/planning-sheets/how-tos/create-a-database-connection-for-collaboration.md).
2. Create and configure writeback destinations if you want to write back the plan data. See [Configure writeback destinations](/documentation/readme/planning-sheets/how-tos/persist-planning-data-using-writeback/configure-writeback-destinations.md) for more information.

{% hint style="info" %}

### Note

During Plan (preview) item creation, a Fabric SQL database is automatically created in your workspace. This database stores your plan report's metadata.
{% endhint %}


---

# 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/readme/prerequisites-for-plan.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.