Power BI 2026 年 8 月：改变报表构建、治理与共享方式的更新

Power BI Desktop Gets a Real VS Code Bridge — Edit Outside, Reload Without Restarting

What changed

• Power BI Desktop now has a built-in entry point that opens the current .pbip project directly in Visual Studio Code — no manually hunting for the project folder.
• Edit project files such as the semantic-model TMDL and report-definition files in VS Code; Power BI Desktop detects external file changes and prompts you to apply them without restarting the application.
• This workflow requires Power BI Projects (.pbip), not a traditional single-file .pbix report: File > Save As > Power BI project.

Why it matters

This is the clearest day-to-day productivity improvement in the release for teams using source control. A bulk rename, a reviewed TMDL change, or a small report-definition edit no longer needs the close-edit-reopen cycle. Move active team projects to PBIP first; do not convert one-off reports simply because VS Code is available.

Direct Lake Gains Three Important Controls — but Two Are Still Preview

What changed

• The Power BI service now separates Refresh schema and data, Sync schema only, and Refresh data only. You can also choose the same action at table level instead of refreshing an entire semantic model.
• Direct Lake on OneLake tables can be converted individually to Import storage mode in web modeling to create a mixed-storage model. This capability is preview and rolling out over the following weeks.
• Direct Lake calculated columns are also preview. They are authored in DAX in web modeling or Desktop without changing storage mode or modifying data upstream.
• These columns are evaluated at query time, respect RLS and OLS, support user-context-aware DAX functions such as USERCULTURE(), and cannot be used in relationships because they do not materialize.

Before

-- Before: a report-specific label normally had to be created upstream
-- (for example in a Lakehouse SQL view) or replaced with a measure.
-- That adds deployment ownership for a small semantic-model need.

After

-- Preview: define the user-aware display label in the Direct Lake model
Orders[Viewer Month Name] =
FORMAT ( Orders[OrderDate], "MMMM", USERCULTURE() )

-- Keep it out of relationships: Direct Lake calculated columns are
-- evaluated at query time and are not materialized.

Why it matters

The refresh split is the immediately useful operational change: a Direct Lake schema change no longer has to travel with every data refresh. The two Direct Lake modeling features are promising, but both are preview. Test calculated columns for report-facing, user-aware labels and test targeted Import conversion for exceptions; do not use either as a reason to move durable joins, shared business logic, or high-volume transformations out of the lakehouse.

The August Authoring Bundle Is Bigger Than the Matrix Fix

What changed

• Modern visual defaults and the theme-formatting experience are generally available. New reports start with the Fluent 2 base theme, and the Theme pane can set colors, typography, visual properties, page settings, and filter-pane styling across a report.
• Font overrides were removed from the base theme, so a change in the Theme pane Text settings can now update titles, callouts, labels, and general text across existing and future visuals.
• The Date picker for the Slicer visual is generally available and adds Single date selection plus a header action to clear a selection.
• Matrix visuals can now expand and collapse column headers, with configurable +/- icon size and color, when more than one field is in the Columns well.
• Reports in org apps now support comments with @mentions and report context. Smaller additions include a donut center value, default freezing for matrix row headers, OneLake file URLs for visuals and maps, chart outer padding, Azure Map refinements, and more slicer formatting controls.

Why it matters

Adopt the theme controls as a report-starting standard, not as end-of-project polish: one controlled font and visual-default decision is cheaper than reformatting dozens of visuals later. The matrix capability is a direct replacement for workaround pages or flattened period columns, while org-app comments turn review feedback into report-context collaboration instead of screenshot threads.

Copilot Sees Bookmark-Revealed Visuals; Fabric Apps Move Toward Least Privilege

What changed

• Copilot Summary and the Copilot Narrative visual can now consider visuals that are hidden by default and revealed by display-only bookmarks triggered through a bookmark button or navigator.
• Copilot reads those visuals in place without changing bookmark state, while existing row-level security and object-level security stay enforced.
• Microsoft also announced an upcoming Fabric App permission change: in early September, consumers of a data app template will need Read permission on the underlying semantic model instead of Build permission. App authors will still need Build.

Why it matters

Bookmark-based tabs are common in polished executive reports, so this removes a blind spot where a Copilot summary could omit content the reader could reveal. Treat the Fabric App permission item as a rollout notice, not an August behavior change: inventory apps that currently grant Build solely for consumption, then retest them when the September change reaches your tenant.

Power Query Dark Mode Gets Practical Accessibility Improvements

What changed

• The August data-connectivity update improves contrast and readability across the light and dark Power Query themes.
• Transparent connector icons now receive a white background in Dark Mode so they remain identifiable in the Get Data experience.

Why it matters

This is not a model feature, but it matters to people who spend hours choosing, diagnosing, and switching data sources. There is no migration to plan; make sure teams using the newer Power Query experience know that the dark-mode connector visibility issue has been addressed before they work around it with an unnecessary theme change.

Consumption Gets More Practical on Phones and in SharePoint

What changed

• Power BI Mobile for iOS and Android is rolling out a Rotate view button in the report footer, giving users a wider report view even if the phone is locked in portrait orientation.
• Users can now export the data behind a report visual to Excel from the mobile app. The export reflects the current filters, slicers, drill state, permissions, and row-level security.
• The new SharePoint Online embed experience lets users browse accessible workspaces and reports rather than pasting a full URL, and it can embed a single visual as well as a report or report page.

Why it matters

Mobile export is the operationally important item: business users can take an approved, security-trimmed visual extract into Excel without first moving to the service. For SharePoint owners, test a single-visual embed on a real intranet page; it is often a clearer alternative to embedding an entire report when the page needs one governed KPI.