Forum Discussion
Fabric Deployment Pipeline Query
- 10 months ago
Hello StitoTheGreat,
You currently:
Use Power BI Premium capacity (P SKU) with existing Deployment Pipelines.
Plan to migrate to Microsoft Fabric capacities (F SKUs), possibly:
F16 → for Dev/Test (pay as you go)
F64 → for Production (reserved instance)
Your goal: use Deployment Pipelines across these workspaces, which would reside in different Fabric capacities — still within the same tenant.
Yes, it is possible to include workspaces hosted on different Fabric capacities in the same Deployment Pipeline, as long as all capacities belong to the same tenant.
Microsoft explicitly supports cross-capacity deployment within a tenant under these conditions:
All capacities (e.g., F16, F64) are under the same tenant and region.
All workspaces are Fabric-enabled (i.e., not legacy shared capacity).
You have Contributor/Admin permissions on all target workspaces.
Source :
- Fabric Deployment Pipelines – Workspace requirements
- https://learn.microsoft.com/en-us/fabric/cicd/cicd-overview
- https://learn.microsoft.com/en-us/fabric/admin/capacity-settings?tabs=power-bi-premium
Hope it can help you !
Best regards,
Antoine
- 10 months ago
Exactly, it’s considered best practice to host your different environments (Dev, Test, Prod) on separate Fabric capacities.
That way, any heavy or unstable development workloads can’t impact your production performance or consume shared compute.You can monitor and tune usage on your Dev capacity using the Fabric Capacity Metrics App, and once everything is validated and optimized, you can safely promote and deploy the content to the Production capacity through your deployment pipeline.
Hello StitoTheGreat,
You currently:
Use Power BI Premium capacity (P SKU) with existing Deployment Pipelines.
Plan to migrate to Microsoft Fabric capacities (F SKUs), possibly:
F16 → for Dev/Test (pay as you go)
F64 → for Production (reserved instance)
Your goal: use Deployment Pipelines across these workspaces, which would reside in different Fabric capacities — still within the same tenant.
Yes, it is possible to include workspaces hosted on different Fabric capacities in the same Deployment Pipeline, as long as all capacities belong to the same tenant.
Microsoft explicitly supports cross-capacity deployment within a tenant under these conditions:
All capacities (e.g., F16, F64) are under the same tenant and region.
All workspaces are Fabric-enabled (i.e., not legacy shared capacity).
You have Contributor/Admin permissions on all target workspaces.
Source :
- Fabric Deployment Pipelines – Workspace requirements
- https://learn.microsoft.com/en-us/fabric/cicd/cicd-overview
- https://learn.microsoft.com/en-us/fabric/admin/capacity-settings?tabs=power-bi-premium
Hope it can help you !
Best regards,
Antoine