Power BI March 2026 Update: What Changed in PBIR

TL;DR: The Power BI March 2026 update bumped seven PBIR schema files to new versions and added a 1920x1080 "16:9 HD" page size option. If you're building tools against PBIR or managing reports in Git, you need to know which schemas changed and what the new versions expect. This post covers every change and what it means for your workflow.

The Update That's Easy to Miss

Microsoft's Power BI feature summaries are dense. The March 2026 update includes dozens of changes across Desktop, Service, Mobile, and the developer platform. Most of the attention goes to the headline features.

But if you work with PBIR files directly (through Fabric Git integration, CI/CD pipelines, or any tool that reads or writes the report JSON), the schema version changes matter more than anything else in the release notes. Mismatched schema references can cause validation failures when Power BI Desktop tries to open a report, and those failures are often silent. The report opens, but something is off.

Here's what changed.

Seven Schema Version Bumps

The March 2026 update touched seven schema files simultaneously. Three are top-level schemas that define the core structure of a PBIR report. Four are supporting schemas referenced by the top-level files.

The visualContainer jump from 2.5.0 to 2.7.0 is the largest. That schema defines the structure of every visual on a report page: position, dimensions, type identifier, data bindings, formatting. A two-minor-version jump signals meaningful structural additions, not just documentation changes.

The page and report schemas each moved one minor version. The page schema now supports the new HD page size option (more on that below). The report schema updated its reportVersionAtImport object to reference the new visual and page versions.

The four supporting schemas all bumped by one minor version. These are referenced by the top-level schemas through $ref pointers. If you validate PBIR JSON against the schemas (which you should, if you're generating or modifying it programmatically), your validator needs the matching versions or the $ref chain breaks.

New Page Size: 16:9 HD (1920x1080)

The March update also added a new page size preset. Previously, "16:9" in Power BI meant 1280x720. Now there are two options:

• 16:9 at 1280x720 (unchanged, still the default)
• 16:9 HD at 1920x1080 (new)

The default for new reports remains 1280x720. The HD option is available for teams that want higher-resolution report layouts, particularly for large-format displays or embedded scenarios where the extra pixel density matters.

If you're generating PBIR files, the page dimensions live in page.json under the width and height properties. Adding 1920x1080 as a valid combination is straightforward, but you'll want to update any validation logic that checks page dimensions against a known set of presets.

Why This Matters for PBIR Tooling

Every tool that reads or writes PBIR files has a $schema reference at the top of each JSON file. That reference points to a specific version of the schema on developer.microsoft.com. When Power BI Desktop opens a PBIR report, it checks these references.

If your tool generates a visualContainer.json file with a $schema pointing to version 2.5.0, but Desktop expects 2.7.0, one of two things happens:

1. Desktop silently upgrades the schema reference on save (best case).
2. Desktop throws a validation warning or produces unexpected behavior (worse case).

Neither outcome is ideal if you're maintaining reports in Git. Silent upgrades create noisy diffs. Validation warnings erode trust in the tool.

The fix is simple: update your schema references to the March 2026 versions. But you have to know the update happened first. Microsoft does not send a notification when schema versions change. You find out by reading the release notes carefully, diffing the schema files yourself, or discovering the mismatch when something breaks.

The Bigger Signal

Seven schema files bumping simultaneously tells you something about Microsoft's investment in PBIR. This is not a format sitting on a shelf. The version cadence is consistent (December 2025, February 2026, March 2026 all included schema updates), and the changes span the full depth of the format. Microsoft is actively iterating.

For anyone evaluating whether to invest time in PBIR tooling or Git-based report management, this cadence is encouraging. The format is being maintained. The schemas are being extended. Building against PBIR is building on a foundation that Microsoft is actively developing.

If you want a deeper understanding of the PBIR format itself, how the folder structure works, and why Microsoft made this change, start with our guide to PBIR.

How Draft BI Handles This

I updated Draft BI's PBIR export pipeline to the March 2026 schemas the same week the update shipped. When you design a report layout in Wireframe Studio and export it as PBIR, the generated JSON references the correct March 2026 schema versions across all seven files. The new 16:9 HD page size is also available as a canvas preset.

This is one of the advantages of PBIR being an open, structured format. When schemas change, the update is mechanical: point the $schema references to the new URLs, validate the generated JSON against the new schemas, run the test suite. No reverse engineering required.

If you're working with PBIR files and want to skip the manual schema tracking, Draft BI stays current so you don't have to.

Tony Thomas

Founder of Draft BI, building the design-first companion for Power BI report development. Writing about PBIR, WCAG accessibility, DAX measures, and the workflows that help Power BI developers and analysts deliver better reports faster.