Deployment Pipelines and Content Lifecycle

Quick Answer: Deployment pipelines move Power BI content through Development → Test → Production stages. Parameter rules configure different server/database connections per stage. The comparison view shows what changed between stages before deploying. This prevents accidental production changes and enables proper testing.

Pipeline Architecture

Three Stages

Each stage is a separate Power BI workspace. Changes are promoted forward through the pipeline.

Creating a Pipeline

Deployment Pipelines → Create a pipeline → Name it
→ Assign workspaces to each stage (or create new ones)

Deployment Process

1. Develop content in the Development workspace
2. Compare Development vs. Test — review differences
3. Deploy to Test — content is copied to the Test workspace
4. Validate in the Test environment with stakeholders
5. Compare Test vs. Production — review differences
6. Deploy to Production — content goes live

Parameter Rules

Parameter rules automatically adjust parameters when deploying between stages:

Pipeline → Deployment Rules → Add Rule
→ Select parameter → Set value per stage

This means one report works across all three environments without manual changes.

Dataset Rules

Beyond parameters, you can configure:

• Data source rules — different connection strings per stage
• Semantic model rules — rebind reports to different datasets per stage

Comparison View

Before deploying, compare stages to see what changed:

Selective Deployment

You can choose to deploy:

• All items — everything from the source stage
• Selected items — only specific reports or datasets
• Backward deployment — rarely used but possible (production → test)

Best Practices

1. Never edit directly in Production — always work in Development
2. Use parameter rules for all environment-specific settings
3. Validate thoroughly in Test before promoting to Production
4. Use security groups for workspace access per stage
5. Document deployments — track what changed and why
6. Schedule deployments during low-usage periods
7. Roll back by redeploying the previous version from Test if issues arise

Content Lifecycle Patterns

Git Integration (Preview)

Power BI now supports connecting workspaces to Git repositories:

• Track .pbip files in source control
• Enable branch-based development
• Code review pull requests for Power BI changes
• Automated deployment via CI/CD pipelines

Versioning Strategy

On the Exam

The PL-300 frequently tests:

• Understanding the three deployment pipeline stages and their purposes
• Configuring parameter rules for environment-specific settings
• Knowing which changes require redeployment vs. automatic updates
• Understanding the comparison view before deploying
• Recognizing the capacity requirements for deployment pipelines