> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/engine-guide/microsoft-fabric/permissions-and-grants.md).

# Permissions and grants

Provision Fabric and DataOS access before configuring or deploying a Data Product.

## Fabric-side permissions and grants

Provision access before configuring a gateway. Fabric and DataOS authorization are separate.

| Role                     | Scope                           | Required access                                                                            |
| ------------------------ | ------------------------------- | ------------------------------------------------------------------------------------------ |
| Admin role               | Fabric workspace or capacity    | Creates workspaces, assigns capacity, and grants workspace roles.                          |
| Vulcan service principal | Entra app registration          | **Contributor** or higher workspace role. It materializes models through the SQL endpoint. |
| Consumer role            | BI users and endpoint consumers | **Viewer** workspace role and SQL endpoint read access.                                    |

Grant the service principal a workspace role in the Fabric portal. Then verify its SQL-level access:

```sql
SELECT name, type_desc
FROM sys.database_principals
WHERE name = '<service-principal-name>';
```

In the Fabric portal, open **Workspace settings → Manage access → Add people or groups**. Select the app registration and assign **Contributor**. The service principal also needs `db_datareader` and `db_datawriter`-equivalent SQL endpoint access for model materialization.

`connection.database` must exist before `vulcan plan`, unless the Vulcan resource creates it. Warehouse creation uses the Fabric REST API.

## DataOS permissions

Provision these permissions before you create or deploy a Data Product.

| Permission                        | Outcome                                                                                                                                      |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Tenant Access                     | Build and manage Data Products in your tenant.                                                                                               |
| `roles:id:data-dev`               | Create and apply Vulcan resources.                                                                                                           |
| Can Use (Compute, Secrets)        | Every permission can be granted to a tenant Role now- grant it once and the whole team, including future joiners, inherits it automatically. |
| git-sync Secret                   | Pull model code from Git.                                                                                                                    |
| Fabric workspace Contributor role | Authorize the service principal in Fabric.                                                                                                   |

{% hint style="info" %}
Confirm that you can use the service-principal Secret before you start. Request the Secret and its **Can Use** grant together.
{% endhint %}

Resource access is deny-by-default. A role tag alone does not grant resource use. Confirm **Can Use** for both Compute and the service-principal Secret.

### Next step

Configure and validate the gateway in [Connect to Microsoft Fabric](https://v2.dataos.info/references/engine-guide/microsoft-fabric/connect-to-microsoft-fabric.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://v2.dataos.info/references/engine-guide/microsoft-fabric/permissions-and-grants.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
