Enable Partial Updates for Power BI Apps

Power BI doesn’t support “partial” app updates. When you select Update app, all included artifacts are re-published with their latest workspace versions. The service UX doesn’t provide an item-level publish toggle. See Microsoft docs: Publish an app in Power BI.

What this means for your scenario (A, B, C with only B approved)

If A and B were both edited in the workspace, pressing Update app will push the new versions of both A and B to the app. There isn’t a built-in way to push only B while keeping A’s previous app version.

Safe, enterprise-friendly workarounds

1. Deployment Pipelines with Selective Deploy

   • How it helps: Move only approved items (e.g., B) from Test → Prod. A remains on the old version in Prod, so updating the Prod app won’t include A’s unapproved changes.
   • How to implement:
   • Use a pipeline (Dev/Test/Prod) and build your app from the Prod workspace.
     •  
   • When A and B change in Test, deploy only B to Prod using the UI or REST API /pipelines/{pipelineId}/deploy.
     •  
   • Open the Prod app → Update app. Only B has changed in Prod, so the app picks up B’s new version while A stays as-is.
   •  
2. Notes / Docs: Pipeline automation • Selective Deploy API
3. “Stable vs Preview” Report Copies + Audiences

• How it helps: Keep a “Report A (Stable)” for end users and a “Report A (Preview)” only visible to QA/Owners. You can continue to update A (Preview) without exposing it.
• How to implement:
  1. Duplicate A to create A (Stable) and A (Preview) (both can point to the same semantic model).
  2. In the App, use Audiences to include A (Stable) for users and A (Preview) for approvers only.
  3. Publish app updates freely; users never see A (Preview) until it’s approved and swapped in.
• Notes / Docs: Apps & audiences improvements • Apps with multiple audiences

• Use “Include in app” and Navigation

  1. How it helps: Temporarily exclude A (Preview) from the app to avoid exposing unapproved content while still allowing editors to iterate in the workspace.
  2. How to implement:
     1. On the app’s Content tab, untick items you don’t want to surface.
     2. Publish the app; only the selected items are visible to audiences.
  3. Notes / Docs: Manage included items & navigation

  4. Keep dataset stable; ship report-only changes

     • How it helps: If A’s risk is tied to model changes, isolate model edits to a separate branch/workspace. Ship B’s report-only changes while keeping the Prod semantic model unchanged.
     • How to implement:
       1. Land model changes in Test only.
       2. Move B’s visual/layout changes to Prod.
       3. App update reflects B; A continues to use the stable Prod model.
  5. Notes / Docs: CI/CD patterns with pipelines: Pipeline automation

     Why true “partial app update” is tricky

     • The app is essentially a view over the workspace’s current artifact versions. Item-level version pinning inside the app isn’t exposed today in the service UX.
• Microsoft’s guidance focuses on controlling when the app is updated and who sees what (audiences), not pinning per-item versions.

  Recommended release workflow (practical template)

  1. Standardize on Pipelines: Dev → Test → Prod; build the app from Prod.
  2. Isolate work: Use separate copies (Stable/Preview) for risky reports; expose Preview only to approvers via audiences.
  3. Selective Deploy: When only B is approved, deploy only B to Prod (skip A). Then perform a single Update app.

Governance: Tag Stable items (e.g., name suffix “(Stable)”), document the swap procedure, and audit app changes via change log.

Optional automation (for advanced teams)

You can script “deploy-only-these-items” then “update app owners” notifications with REST APIs/DevOps:

POST https://api.powerbi.com/v1.0/myorg/pipelines/{pipelineId}/deploy
Body: {
  "sourceStageId": "...",
  "targetStageId": "...",
  "options": {
    "allArtifacts": false,
    "artifacts": [
      { "id": "<ReportBId>", "type": "Report" }
    ]
  }
}

Docs: Selective Deploy (REST) • Pipeline automation

Wrap-up