Deployment pipelines troubleshooting (preview)
Use this article to troubleshoot issues in deployment pipelines.
What's deployment pipelines in Power BI
To understand what's deployment pipelines in Power BI, refer to the deployment pipelines overview.
How do I get started with deployment pipelines?
Get started with deployment pipelines using the get started instructions.
Why can't I see the deployment pipelines button?
If the following conditions are not met, you'll not be able to see the deployment pipelines button.
You're a Power BI Pro user
You belong to an organization that has Premium capacity
A workspace can only be assigned to a single pipeline
You're an admin of a new workspace
What licenses are needed to work with deployment pipelines?
What type of capacity can I assign to a workspace in a pipeline?
All workspaces in a deployment pipeline must reside within a dedicated capacity for the pipeline to be functional. However, you can use different capacities for different workspaces in a pipeline. You can also use different capacity types for different workspaces in the same pipeline.
For development and testing, you can use A or EM capacity alongside a Pro Power BI account for each user.
For production workspaces, you need a P capacity. If you're an ISV distributing content through embedded applications, you can also use A or EM capacities for production.
Why can't I see all my workspaces when I try to assign a workspace to a pipeline?
To assign a workspace to a pipeline, the following conditions must be met:
The workspace is a new workspace experience
You're an admin of the workspace
The workspace is not assigned to any other pipeline
The workspace resides on a premium capacity
Workspaces that don't meet these conditions, are not displayed in the list of workspaces you can select from.
How can I assign workspaces to all the stages in a pipeline?
You can assign one workspace per pipeline. Once a workspace is assigned to a pipeline, you can deploy it to the next pipeline stages. During first time deployment, a new workspace is created with copies of the items in the source stage. The relationships of the copied items are kept. For more information, see how to assign a workspace to a deployment pipeline.
Why did my first deployment fail?
Your first deployment may have failed due to a number of reasons. Some of these reasons are listed in the table below.
|You don't have premium capacity permissions.||To get premium capacity permissions, ask a capacity admin to add your workspace to a capacity, or ask for assignment permissions for the capacity. After the workspace is in a capacity, redeploy.|
|You don't have workspace permissions.||To deploy you need to be a workspace member. Ask your workspace admin to grant you the appropriate permissions.|
|Your Power BI admin disabled the creation of workspaces.||Contact your Power BI admin for support.|
|Your workspace isn't a new workspace experience.||Create your content in the new workspace experience. If you have content in a classic workspace, you can upgrade it to a new workspace experience.|
|Your using selective deployment and are not selecting your content's dataset.||Do one of the following: Unselect the content that is linked to your dataset. Your unselected content (such as reports or dashboards) will not be copied to the next stage. Select the dataset that's linked to the selected content. Your dataset will be copied to the next stage.|
I'm getting a warning that I have 'unsupported artifacts' in my workspace when I'm trying to deploy. How can I know which artifacts are not supported?
For a comprehensive list of items and artifacts that are not supported in deployment pipelines, see the following sections:
Why did my deployment fail due to broken rules?
If your deployment was previously successful, and is suddenly failing with broken rules, it may be due to a dataset being republished. The following changes to the source dataset, result in a failed deployment:
A removed parameter
A changed parameter name
Data source rules
Your dataset rules are missing values. This may have happened if your dataset changed.
When a previously successful deployment fails due to broken links, a warning is displayed. You can click Configure rules to navigate to the deployment settings pane, where the failed dataset is marked. When you click the dataset, the broken rules are marked.
To deploy successfully, fix or remove the broken rules, and redeploy.
How can I change the data source in the pipeline stages?
You can’t change the data source connection in Power BI service.
I fixed a bug in production, but now I can't click the 'deploy to previous stage' button. Why is it greyed out?
You can only deploy backwards to an empty stage. If you have content in the test stage, you will not be able to deploy backwards from production.
After creating the pipeline, use the development stage to develop your content, and the test stages to review and test it. You can fix bugs in these stages, and then deploy the fixed environment to the production stage.
Does deployment pipelines support multi-geo?
Multi-geo is supported. It may take longer to deploy content between stages in different geos.
What is the deployment pipelines permissions model?
The deployment pipelines permissions model is described the permissions section.
Who can deploy content between stages?
Content can be deployed to an empty stage or to a stage that contains content. The content must reside on a premium capacity.
Deploying to an empty stage - Any Pro user that's a member or admin in the source workspace.
Deploying to a stage with content - Any Pro user who's a member or admin of both workspaces in the source and target deployment stages.
Overriding a dataset - Deployment overrides each dataset that is included in the target stage, even if the dataset wasn't changed. The user must be the owner of all the target stage datasets specified in the deployment.
Which permissions do I need to configure dataset rules?
To configure dataset rules in deployment pipelines, you must be the dataset owner.
Why can't I see workspaces in the pipeline?
Pipeline and workspace permissions are managed separately. You may have pipeline permissions, but not workspace permissions. For more information, review the permissions section.