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.
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:
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.
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.
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.
Last updated
Was this helpful?