Novedades semanales
- PowerBI:
Power BI November 2026 Feature SummaryIf you haven’t already, read Arun Ulag’s Ignite blog post to learn how Microsoft is bringing together databases, analytics, and intelligent applications across Azure and Microsoft Fabric.
________________________________
Welcome to the November 2026 Power BI feature summary! We're sharing this month's updates ahead of the Power BI Desktop release, which will follow the week of November 23, 2026.
This month’s updates make it easier to build, customize, manage, and share experiences across Power BI and Microsoft Fabric. Highlights include expanded ways to work with Microsoft Copilot, new reporting and visualization capabilities, enhancements to org apps, and updates that simplify data connectivity and semantic model deployment.
Read on to explore the latest features and see how they can help you create more consistent, interactive, and accessible experiences with your data.
Table of Contents
- Events and Announcements
- General
- Reporting
- Power BI Integration with OneDrive and SharePoint (Generally Available)
- Card visual trend charts
- Add to style presets (Generally Available)
- List slicer with multi-line selection box and dropdown (Generally Available)
- Gantt chart updates (Preview)
- Table and matrix filtering from action buttons within visual title (Preview)
- Slicer mode (date picker, dropdown, list) can be set using custom theme (Generally Available)
- Default slicer mode for dates is now “date picker” (Generally Available)
- Icons visibility improvements for high contrast mode (Generally Available)
- Blank reports in the web communicate better next steps (Generally Available)
- Azure Maps support for sovereign clouds (Generally Available)
- Plot area background color and transparency (Generally Available)
- Drag and drop navigation ordering in Org Apps
- Multi-tasking support for Org Apps
- Convert existing Org Apps to use audiences
- Apps page updates coming soon; now available in Fabric
- Modeling
- Data connectivity
- Power BI Mobile
- Embedded Analytics
- Third-party custom visuals
- That’s a wrap!
- Monthly Video: Power BI Update - November 2026
- Download November Power BI Desktop after November 23, 2026.
- Publishing: 11/23/2026
Events and Announcements
FabCon + SQLCon Atlanta is back, March 8–12, 2027
Join data, analytics, BI and AI professionals from around the world at the Georgia World Congress Center. You get two co-located conferences with one registration, 100+ expert-led sessions, and keynotes, breakouts and hands-on learning across Fabric, SQL and Azure AI. You'll leave with practical takeaways you can use right away.
Save $200 with code MSCMTY, register now.
New in 2027: FabCon + SQLCon is going Down Under!
FabCon runs April 6–9, 2027 in Sydney, Australia. Save AUD$250 with code MSCUST, register now.
Data Days: AI Work is live (Nov 2 – Dec 15)
Your Power BI reports are just the start. Data Days: AI Work brings real people, real projects and real AI on Fabric, SQL and Power BI. See Fabric IQ and Fabric Apps turn insights into action, learn how analysts use Copilot at work, join dataviz and Fabric apps contests, and prep for PL-300 and DP-600.
Explore Data Days: https://aka.ms/datadays
The Power BI DataViz World Championships are on!
Think your reports have what it takes? Round 1 is open through November 18, and Round 2 runs November 25 – December 9. Two winners from each round go head to head live on stage at FabCon + SQLCon Atlanta for the World Champion title.
Learn more about the DataViz World Championships.
General
Retiring standalone Power BI Copilot experiences in favor of Microsoft Copilot (Preview)
The next chapter for Microsoft Copilot in Power BI and Fabric. We're expanding Microsoft Copilot in Power BI and Fabric to users without a Copilot Premium license. This is the next step toward replacing standalone Power BI Copilot with Microsoft Copilot.
Figure: The Microsoft Chat experience in Power BI; available capabilities depend on your license and entitlements.
The path from standalone Power BI Copilot. We plan to end support for standalone Power BI Copilot on the web, including Home, and in Teams and Power BI mobile by the end of January 2027. These experiences remain available during the transition. Official deprecation, end-of-support, and retirement dates have not been announced; we will share dates and guidance separately. Microsoft Copilot is the planned replacement, with capabilities based on each user's license and entitlements. Report Copilot remains available and supported in the Power BI service, Power BI Desktop, and Power BI mobile. Copilot in web modeling and DAX query view also remains available and supported.
An upgraded experience built around your Fabric data. Power BI and Fabric users without an M365 Copilot Premium license will be able to use Fabric IQ in Microsoft Copilot in the Power BI service even with just a Basic license, subject to their content permissions and licensed access.
Refer to the licensing and eligibility requirements for the applicable access conditions.
With Fabric IQ in the Basic experiences, users can:
- Find and reference supported reports by name, link, or attachment.
- Ask questions grounded in Power BI semantic models and explore results through follow-up questions.
- Return to conversation history across supported Copilot experiences.
Basic licenses include Fabric IQ, but not Work IQ. Premium adds Work IQ for organizational Microsoft 365 emails, meetings, chats, and documents, plus features such as advanced model access.
For more information on the breakdown, refer to the Copilot in Power BI and Microsoft Fabric (Preview) documentation.
Updated Copilot defaults on December 8, 2026. Microsoft Copilot is currently off by default; administrators can enable it in the Fabric admin portal. Admins can manage access with the "Users can access Microsoft Copilot in Power BI and Microsoft Fabric" tenant setting in the Fabric admin portal.
On December 8, 2026, Microsoft Copilot will default to on and standalone Power BI Copilot will default to off. Existing administrator choices will be preserved. This changes tenant-setting defaults only; it is not a deprecation, end-of-support, or retirement date.
Figure: Visual of the Microsoft Copilot tenant setting in the Fabric Admin portal.
Get started
Explore the current preview and administrator requirements in Copilot in Power BI and Microsoft Fabric. For more about how Copilot answers questions using Power BI data, refer to Fabric IQ in Copilot Chat.
Retiring app-scoped Copilot (Preview) in Power BI workspace apps
We're retiring app-scoped Copilot (Preview) in Power BI workspace apps. The experience and the workspace app setup setting used to enable it will be removed in January 2027.
Figure: App-scoped Copilot entry point in a Power BI workspace app navigation menu.
Your app content, audiences, and permissions will remain unchanged. You can continue using Copilot within eligible reports, including reports opened in a workspace app, to ask questions about your data and get summaries.
Power BI Desktop for Apps (Preview)
We're building a new way to turn your Power BI data into interactive Fabric apps.
Power BI Desktop for Apps combines your semantic model with an AI-assisted app-authoring experience. Start with your data, describe the experience you want to create, and work with the built-in agent to build and iterate on your app. You can then preview your app locally and continue refining it yourself.
As you build, a live connection to your semantic model in the Power BI service gives the agent context about your data. You can also edit text directly and use the Design pane to adjust fonts, colors, themes, and other visual properties.
Power BI Desktop for Apps is being prepared for preview and is coming soon.
Reporting
Power BI Integration with OneDrive and SharePoint (Generally Available)
First introduced in 2023, in preview, the Power BI integration with OneDrive and SharePoint has reached general availability.
Many report authors already use OneDrive and SharePoint to store and collaborate on their Power BI files before publishing them. With this release, both the web viewing experience and the open, save, and share capabilities in Power BI Desktop are ready for production use, so your reports can live where the rest of your Microsoft 365 work already does.
View Power BI files right in OneDrive and SharePoint
Quickly view Power BI files stored in OneDrive and SharePoint directly in your browser, with no need to install Power BI Desktop or download the file. Just select a .pbix file in your OneDrive or SharePoint library and the report opens in the browser, where you can interact with visuals, explore the data, use bookmarks, switch page views, and apply high-contrast colors.
- Share with confidence: share a link using the familiar Microsoft 365 share dialog, which respects your OneDrive and SharePoint permissions and policies.
- Built-in version history: track changes and restore earlier versions of a report with Microsoft 365 version history.
- Governed by default: sensitivity labels are respected, and admins have visibility through Microsoft 365 audit logs and the Power BI activity log.
Figure: Power BI reports can be viewed directly in SharePoint or OneDrive.
Open, save, and share from Power BI Desktop
Power BI Desktop works seamlessly with OneDrive and SharePoint. Open reports straight from your OneDrive or SharePoint sites, save new or existing reports directly to a cloud location, and share a link with colleagues using the Share button at the top right of Power BI Desktop. Storing your files in OneDrive and SharePoint gives you file versioning, easier co-authoring, and a backup that's always in the cloud.
Figure: Open Power BI files from OneDrive, SharePoint, or your recent files in Power BI Desktop.
Getting started
- Viewing in the browser is on by default. Admins can manage it under Tenant settings > Integration settings in the admin portal: “Users can view Power BI files saved in OneDrive and SharePoint”.
- Open, save, and share in Power BI Desktop are on by default in the November release of Power BI Desktop. Admins can manage it under Tenant settings > Integration settings in the admin portal: “Users can share links to Power BI files stored in OneDrive and SharePoint through Power BI Desktop”.
- To view reports in the browser, you need a Power BI Pro, Premium Per User, or E5 license and at least read access to the file.
Try the Power BI integration with OneDrive and SharePoint and learn more about it in our documentation: View Power BI files in OneDrive and SharePoint and Power BI Desktop OneDrive and SharePoint integration.
Card visual trend charts
Show trends or regional patterns alongside your key metrics in the Card visual. Use a line, bar, or column chart to show changes over time, or a shape map to show regional patterns. To get started, add a field to Trend axis (Preview) in the Build pane. Add measures to compare performance and a legend to identify them. Customize data labels, markers, axes, and other formatting options; tooltips show the data point and axis values.
Figure: The Card visual supports line, column, bar, and shape map charts, with chart and formatting options visible in the Format pane.
Learn more about Card visual trend charts in the Create a card visual in Power BI documentation.
Add to style presets (Generally Available)
Visual style presets let you format a visual once and reuse that formatting for every visual of the same type in your report. Instead of repeating the same changes on each chart, format one visual in the Format visual pane, and then save it as a named style preset or add it to the base visual style.
Figure: Save a visual’s current formatting as a named style preset to reuse across visuals of the same type.
The preset then appears in the Style presets dropdown for every visual of that type, so you can apply the same look with a single selection. You can also make any preset the default for its visual type, and visuals that use the default style update to match. Style presets are saved in your report's theme. To reuse them in other reports, download the theme and import it there.
After saving a style preset, use Reset all style settings to default to remove manual formatting overrides and let the visual use its preset. This new option appears alongside Reset all settings to default and removes only formatting set in the Format visual pane. It preserves conditional formatting, actions, and data-bound elements, such as reference labels.
Figure: Reset formatting overrides to use the visual’s style preset without removing conditional formatting, actions, or data bindings.
Learn more about creating, updating, and sharing presets in the Use visual style presets in Power BI reports documentation.
List slicer with multi-line selection box and dropdown (Generally Available)
The list slicer helps you save space on your report page with a customizable dropdown. Format items with pictures, labels, and conditional formatting, and keep that formatting in dropdown mode. Adjust the dropdown size to fit your report. Selections appear as pills that readers can review and remove. To show more selections before they're grouped into a count pill, turn off Single line under Selection box > Layout.
Figure: WithSingle lineturned off, the selection box fills the visual and shows more selections before they're grouped into a count pill.
Use show selected first to list selected items at the top, making them easier to find in long lists. This option works in the list slicer with or without dropdown mode and is also available in the button slicer.
Learn more about creating and using a list slicer.
Gantt chart updates (Preview)
Make overall progress and individual task progress easier to see in the Gantt visual with column totals and data labels. Configure totals under Columns > Totals and data labels under Rows > Data labels in the Format visual pane. This release also fixes progress bar formatting and keyboard navigation issues and increases default column widths to give task details more room.
Figure: Show overall progress with column totals and display progress percentages beside task bars using data labels in the Gantt visual.
Learn more about using the Gantt visual in Power BI.
Table and matrix filtering from action buttons within visual title (Preview)
Bring filtering to where report viewers are working with the new Filter action button for table and matrix visuals. Adjust visual-level filters directly on the visual, with the same experience and filter card formatting as the Filters pane. The Filter action button also shows the number of visual-level filters applied to the visual.
To enable it, turn on Action buttons under General in the Format visual pane. Position the button within the title, above, or below, and customize its icons, text, and styling to fit your report. The overlay shows only Filters on this visual; page and report filters are still adjusted in the Filters pane.
Figure: Add a Filter action button so readers can adjust visual-level filters directly from a table or matrix without opening the Filters pane.
For now, this is limited to table and matrix visuals, and we plan to bring it to other visuals in a future release. Action buttons are planned to expand with a Sort button in a future release too.
Learn more about adding action buttons to Power BI visuals.
Slicer mode (date picker, dropdown, list) can be set using custom theme (Generally Available)
Set the slicer mode in a custom report theme to apply a consistent default without configuring each slicer individually. Save the setting in your theme file, then reuse the theme in other reports to keep your preferred slicer experience consistent. If the specified mode isn't compatible with the slicer's column, Power BI automatically switches to a compatible mode.
Learn more about setting visual properties in custom report themes.
Default slicer mode for dates is now “date picker” (Generally Available)
When you add a date column to the Slicer visual, it now starts in Date picker mode, so you can offer flexible date filtering without changing the style first. Readers can choose a specific date or range using the calendar or slider, or use relative selections anchored to today, the first date, or the last date in your data. You can still choose another style under Slicer settings > Options > Style in the Format pane.
Learn more about using the Date picker slicer.
Icons visibility improvements for high contrast mode (Generally Available)
Conditional formatting icons now adjust to display correctly in high contrast mode, making it easier to distinguish status indicators and interpret your data when using high contrast settings.
Figure: Conditional formatting icons now adapt to high contrast mode, including in the icon picker.
Learn more about using high contrast colors in Power BI reports.
Blank reports in the web communicate better next steps (Generally Available)
When you edit a blank report on the web, you now see the same getting-started experience as in Power BI Desktop.
Figure: The blank report canvas on the web now shows the same getting-started guidance as Power BI Desktop, helping authors build visuals from their data.
If a report is intentionally blank with no visuals, viewers see a banner explaining that it's empty, so they don't mistake the blank canvas for content that's still loading.
Figure: A banner lets report viewers know when a report is empty and suggests adding visuals or contacting the report owner.
Learn more about viewing and editing reports in the Power BI service.
Azure Maps support for sovereign clouds (Generally Available)
Azure Maps in Power BI is now supported in Azure Government, including GCC and GCC High.
Government customers can use the Azure Maps visual to bring location-based data to life with interactive map visualizations, making it easier to explore geographic patterns and insights within their government cloud environment.
Learn how to get started with the Azure Maps visual in Power BI.
Plot area background color and transparency (Generally Available)
Match your visuals to your report's design with plot area background color and transparency settings, now available in this release of Power BI Desktop following their announcement in the previous release. Set a background color and adjust its transparency. You can also use conditional formatting and URLs for plot area background images.
Figure: Bar chart with the Plot area background formatting pane open, showing the new Background color and Transparency options.
Learn more about customizing visualization background color and transparency.
Drag and drop navigation ordering in Org Apps
Put your org app's most important content where readers can find it. In edit mode, drag navigation items to reorder them. For example, move a newly added item or link from the bottom of the navigation to the position you want.
Figure: Reorder an org app’s navigation by dragging an item to a new position.
To learn more, refer to the org apps documentation.
Multi-tasking support for Org Apps
You can now switch from editing an org app to another item, such as a Real-Time Dashboard, without being prompted to save or discard your changes. This helps you find and review content to include in the app while you're still building it. An indicator shows when the org app has unsaved changes, as it does for other items.
Figure: A dot beside the org app indicates unsaved changes.
To learn more, refer to the org apps documentation.
Convert existing Org Apps to use audiences
If you created an Org App before audiences were available and don't want to recreate the app entirely, you can now convert it to use audiences. Organize content for different groups within a single app and tailor what each audience sees, rather than creating separate apps for each group.
Figure: Use the Upgrade option to convert an existing org app to use audiences.
To learn more about audiences, refer to the Org Apps (Generally Available) announcement blog post, and the audiences’ conversion documentation.
Apps page updates coming soon; now available in Fabric
The updated Apps page is rolling out progressively and brings Fabric Apps into the browsing experience, along with updated app names, refined sorting, and new pivots. These changes make it easier to browse your apps and find the one you need.
Figure: Org apps, workspace apps, and Fabric apps together on the updated Apps page.
The Apps page is now available in Fabric. To learn more, refer to the updated Apps page documentation.
Modeling
Semantic views (Preview)
Define your business metrics once, next to your data in OneLake, and use them everywhere. Semantic views let you describe tables, relationships, and business metrics separately from the engines and tools that consume them. For example, define revenue once and reuse the same definition across teams, Power BI reports, and Fabric data agents.
Wherever practical, semantic views are defined in Apache Ossie (incubating) format, a community-led effort to establish a vendor-neutral standard for exchanging semantic metadata across analytics, AI, and BI platforms. Where that is not yet practical, we are working with the community to expand coverage.
With OneLake shortcuts, you can reuse a centrally maintained semantic view across lakehouses without copying it. For example, a regional sales team can use a central revenue definition while keeping its data in its own lakehouse.
In this preview, publishing a semantic view creates a managed, read-only Direct Lake on OneLake semantic model for use in AI and BI experiences. The semantic view remains the source of truth.
To get started, open your lakehouse, select New semantic view, complete the starter YAML or upload your own files, and then select Publish from the semantic view folder.
Use semantic views for definitions shared across tools. Use Power BI semantic models for advanced modeling capabilities.
Figure: Author a semantic view from a Fabric lakehouse.
To learn more, refer to the semantic views documentation.
M parameter support for Direct Lake on OneLake models (Preview)
M parameter support makes it easier to deploy Direct Lake on OneLake semantic models across development, test, and production environments. Use parameter rules in deployment pipelines to point each stage to the appropriate OneLake source without manually updating source expressions in the model after deployment.
You can add parameters through TMDL view, or through Power Query in composite models. Parameterize the workspace and lakehouse IDs separately or use a single parameter for the complete OneLake URI. Then configure stage-specific values using Parameter rules in your deployment pipeline.
This lets you maintain the same semantic model across deployment stages while keeping its OneLake source configuration specific to each environment.
Figure: Define workspace and lakehouse M parameters in TMDL view.
Figure: Configure stage-specific M parameter values using Parameter rules in a deployment pipeline.
Learn more in Create deployment rules for Fabric's ALM and Develop Direct Lake semantic models.
Data connectivity
Switch Power Query experiences from Get Data (Preview)
It’s now easier to try the New Power Query Experience (Preview) in Power BI Desktop. You can turn it on or off directly from the Get Data dropdown, without opening Settings.
On the Home ribbon, open the Get Data dropdown and select New Power Query Experience under Get Data (Preview). A check mark shows that it’s enabled. The next time you use Get Data, the new experience opens; no restart required.
Figure: Comparison showing how selecting or clearing New Power Query Experience in Power BI Desktop’s Get Data menu switches between the new and legacy experiences, with no restart required.
Give it a try as you connect to your next data source. You can switch back to the legacy experience by selecting the option again, and Desktop remembers your choice across sessions.
Power BI Mobile
Open Fabric Apps directly in Power BI Mobile (Coming soon)
Fabric apps are now available directly in the Power BI Mobile app, bringing purpose-built, interactive data experiences to phones and tablets. Users can open a Fabric app without leaving the mobile experience, making it easier to review data, monitor business insights, and act while on the go.
Fabric apps are integrated into the familiar Power BI Mobile discovery experience. Users can find them from the Apps, Workspaces pages and inside OrgApp navigation, and they can also appear in search, recent items, and favorites.
After opening a Fabric app, users can use familiar mobile actions, including full-screen viewing, sharing and deep links, in-app search, favorites, and Siri on iOS.
Figure: Fabric apps can be discovered, opened, and configured for quick access in Power BI Mobile.
For even faster access, users can configure a Fabric app as their launch item. The selected app then opens automatically whenever Power BI Mobile starts, providing one-tap access to a frequently used operational or analytical experience.
Embedded Analytics
Embed workspace apps in SharePoint Online (Coming soon)
Power BI Workspace Apps can now be directly embedded into SharePoint Online pages and sites. Previously, you could embed only individual reports and visuals in SharePoint. With this update, you can embed the complete workspace app, including its navigation, sections, and content. Readers get the same experience they would get in Power BI, right on your SharePoint page.
Figure: Embedding a workspace app into a SharePoint Site via a URL.
Two easy ways to add your workspace app
- Paste the workspace app URL - Open a workspace app in the Power BI Service. On the File menu, select Embed report > SharePoint Online. When embedding a workspace app, you can decide if you want to embed the full app, or just the current report before exporting the URL. Copy the report URL from the dialog box and paste it into the SharePoint content menu.
- Choose from the workspace picker - If you don't have the link handy, use the workspace picker in the Power BI web part to browse the workspaces you can access and select the workspace app you want. You don't need to copy or paste a URL.
Whichever way you choose, the embedded workspace app keeps its existing Power BI permissions. Viewers see only content they already have access to, including any audiences you've set up in the app. Your security and governance settings stay in place.
This update supports workspace apps only; support for org apps is planned. Learn how to enable embedding in the Embed a report web part in SharePoint Online documentation.
Third-party custom visuals
Need more visual options for your report? Power BI reports support custom visuals built to fit your exact needs. Browse hundreds of options in AppSource, also available directly from Power BI Desktop, or develop your own and add it to a single report, share it across your organization, or publish it to AppSource for the community. You can even develop a custom visual tailored to your specific requirements with AI coding tools like GitHub Copilot Free.
The following are some updates from the community-based custom visuals you can use in your reports today.
Stacked and Layered Waterfall in Zebra BI Charts
Revenue is 2.1M above plan, and the CFO asks: where did that come from? A waterfall shows how much changed, not which segments drive it, so the review stalls while someone switches pages.
With Stacked and Layered Waterfall in Zebra BI Charts, one of our most requested features, the total and its drivers sit in one chart. Get the full update.
Stacked waterfall builds the segments into each column: EMEA +3.2M and Americas +1.4M above the connector, APAC -2.5M below it. Ideal for two or three segments.
Figure: Stacked waterfall: each monthly variance to plan is broken down by region inside one column.
Layered waterfall gives each segment its own row, with the totals still connected, so the region that broke the quarter can't hide. Ideal for price-volume-mix or cost bridges, where drivers pull in opposite directions.
Figure: Layered view: each region gets its own row, with the plan and actual totals connected across all rows.
What you gain:
- Faster reviews: the conversation moves from "where did this come from?" to "what do we do about APAC?"
- Board-ready exports: the breakdown lives in the bars, so it survives PDF and PowerPoint. Nothing to rebuild by hand.
- No extra work: drag a dimension into Groups and switch views with a click. No DAX, no extra measures, and mixed directions split automatically so bar heights stay honest.
Try it out in Zebra BI Charts.
Drill Down Line PRO by ZoomCharts
Make line charts easier to read and explore with Drill Down Line PRO. Series Labels show each series name beside the chart, with a connector pointing to its line. Users can see which line is which without checking the legend. This helps when comparing sales by region, product results, or actual sales against a budget.
Figure: The top image showcases the new customizable series labels feature introduced in the Drill Down Line PRO visual. The bottom image demonstrates how to drill down to the next level by selecting a category directly on the chart.
Figure: The customization and interactive features of Drill Down Line PRO, including the ability to combine up to 25 data series in a single chart, customize line styles (solid, dashed, dotted, or stepped), highlight key values, and display targets or benchmarks directly on the chart. Interactive navigation allows users to focus on specific chart areas for deeper analysis.
Key features:
- Series Labels: Customize fonts, colors, backgrounds, markers, and connectors to fit your report. Available when the second Y-axis is turned off.
- Click to drill down: Move from a broad view into more detail, such as from regions to individual stores.
- Cross-chart filtering: Select data points to filter other visuals and explore related results.
- Zoom and pan: Focus on the part of the chart you want to explore.
- Up to 25 series: Compare several measures in one chart and style each line separately.
- Flexible line styles: Choose solid, dashed, dotted, or stepped lines.
- Color rules and thresholds: Highlight key values and show targets or benchmarks directly on the chart.
Threadseer: See How Work Really Flows
Your dashboards show what happened. But can they show how it happened? An order took 12 days to complete. A claim was processed three times. A service request missed its deadline. Traditional dashboards can highlight these outcomes, but understanding the actual sequence of events behind them often requires a different kind of analysis.
Threadseer brings a comprehensive process mining platform directly into Power BI, turning event-level data into interactive maps of how work really flows through an organization.
Discover the most common process paths, pinpoint bottlenecks and rework, compare variations, investigate deviations from expected workflows, and drill into individual cases to understand what happened. Whether you're analyzing healthcare claims, manufacturing orders, financial operations, or service requests, Threadseer helps you move from reporting results to investigating the processes behind them. It runs within the Power BI visual, without requiring a separate process mining platform or sending your event data to an external service. Get started with the free Community edition and discover what your existing data can reveal.
Figure: Process Map – Threadseer process mining visualization in Power BI showing a healthcare claims workflow with branching process paths, common variants, rework loops, and activity-level metrics.
Figure: Variant Comparison – Threadseer comparing two healthcare claims process variants in Power BI, highlighting differences in workflow steps and median cycle time.
Explore Threadseer on Microsoft Marketplace
That’s a wrap!
From new ways to build AI-assisted apps and work with Microsoft Copilot to greater flexibility across reporting, modeling, connectivity, and embedded analytics, this month’s updates are designed to help you get more from Power BI.
Try the features that are most relevant to your work, explore the linked documentation to learn more, and let us know what you think. We’ll be back next month with more Power BI updates.
We're sharing this month's updates ahead of the Power BI Desktop release, which will follow the week of November 23, 2026.
- Monthly Video: Power BI Update - November 2026
- Download November Power BI Desktop after November 23, 2026.
- Publishing: 11/23/2026
Wednesday 18th November 2026, 7.12pm
- PowerBI:
Power BI at Ignite: Building on the momentumIf you haven't already, read Bogdan Crivat's Microsoft Fabric Ignite blog post for a complete look at our Ignite announcements across Microsoft Fabric.
Coming out of FabCon/SQLCon in Barcelona and the Power Platform Community Conference, I'm more excited than ever about what's ahead for Power BI. It's been inspiring to see the community explore new AI-powered experiences and rethink how we interact with data, uncover insights, and make decisions.
At FabCon, I shared that Power BI is entering its next chapter. Your ideas, enthusiasm, and feedback since then have helped shape what we're delivering this week. At Ignite, two key parts of that chapter are ready for you to try: Power BI Desktop for Apps and semantic views, both now in public preview.
Power BI Desktop for Apps: Build apps where you already build reports
In Barcelona, we gave you an early look at a new app-building experience in Power BI Desktop, powered by Fabric apps. This week, it arrives in preview as Power BI Desktop for Apps.
It starts where Power BI always has with a semantic model you already trust. Choose a published semantic model, describe the app you want in natural language, and an agent builds it and iterates with you. Refine the result with direct edits and a design pane, preview it locally, and publish it to Microsoft Fabric when it's ready.
Because these are apps, they can do more than display data. They can accept inputs, preserve shared state, and support operational workflows. That makes room for everything from a focused portal for a team's reports to a planning app where people enter targets, approve them, and comment in context, all built on the definitions your organization already trusts.
Reports aren't going anywhere; they remain the fastest way to explore and share insights. Apps extend what you can build on the same semantic model when people need to act on what they see.
This experience isn't limited to Fabric capacity customers. Apps in Power BI are available to Power BI Pro customers in the coming weeks, with support for Premium Per User coming in the months ahead. Fabric apps, the technology underneath, is also now generally available.
Figure: Creating an app with the new experience in Power BI Desktop.
The apps you build with Power BI Desktop for apps come with a new set of visuals made for Fabric apps. Charts, maps, KPI cards, slicers and data grids share consistent typography, color and spacing, so an app looks cohesive without requiring you to hand-tune every visual. They work in light and dark themes and adapt to your app's own colors.
They also behave the way Power BI users expect. With the Fabric visuals packages you get familiar Power BI capabilities like tooltips, cross-filtering and cross-highlighting, so selecting a point in one visual focuses the rest of the page. They support keyboard navigation and screen readers too.
To learn more about how we're designing visuals for people and agents alike, refer to the blogpost on Data visualization in the agentic era.
Figure: Examples of Fabric visuals capabilities.
Semantic views: an open semantic layer, built on Apache Ossie
The semantic layer is an organization's most strategic asset. With more than 22 million Power BI semantic models in use every day, Power BI is the world's most widely adopted semantic layer, and the business meaning in those models increasingly grounds agents, apps, and Microsoft Copilot.
Today, semantic views enter public preview as the first semantic layer based on Apache Ossie (incubating) open standards, with the unparalleled modeling power of Power BI behind it. You define governed business metrics and semantics directly where your data lives in OneLake, in an open format designed for interoperability. Measures can be written in DAX, so a definition like Total Sales can carry year-over-year and rolling-period logic, not just a simple sum. Define a metric once and reuse it across reports, apps, and AI, within Fabric and, through Apache Ossie, with platforms such as Snowflake and other partners over time.
Semantic models remain the heart of Power BI and Fabric IQ. Semantic views complement them by separating business definitions from compute, so the definitions your teams agree on can move across engines and ecosystems without being rebuilt. We'll keep advancing Apache Ossie with Snowflake and the broader community, including establishing DAX as an Ossie-recognized query language.
Figure: Defining governed business metrics in a semantic view.
What's ahead
If you're ready to take the next step and want to learn how to build apps for your teams and organization, we invite you to join Data Days: AI Work to learn from practitioners through real projects, working demos, and follow-along sessions. Whether you want to understand the possibilities, find a pattern to try, or share what you build, explore the sessions and find your next step at aka.ms/DataDays.
Register for our upcoming Fabric and SQL Community Conferences: Atlanta | Sydney—use code MSCUST to save.
Thank you for building with us and for continuing to challenge us to imagine what comes next. I can't wait to see what you create.
Tuesday 17th November 2026, 6.30pm
- PowerBI:
Announcing the retirement of R and Python visuals in Power BIThe built-in R and Python visuals in Power BI will retire in May 2027.
What changes
This retirement applies only to R and Python visuals in interactive Power BI reports. Python scripts used in Power Query to populate tables are not affected.
- Power BI service: At retirement, all R and Python visuals will stop working in published reports, including those published before retirement.
- R-powered custom visuals: Custom visuals that use R will also no longer work at retirement.
- Older versions of Power BI Desktop: These visuals will continue to work locally using R and Python installed on your machine.
- Future versions of Power BI Desktop: After retirement, R and Python visuals will be removed, so you won't be able to add them to reports.
What you need to do
No migration within your report will recreate your exact R or Python visual. You must replace it with a different visualization before retirement.
Start reviewing your reports for R and Python visuals and communicate within your organization that reports using them will be impacted. Preserve their scripts and dependencies.
If you use Power BI project (PBIP) format and Git-integrated workspaces, search your report definitions in source control to find these visuals across multiple reports. Look for the visualType values pythonVisual for Python visuals and scriptVisual for R visuals.
Keep the visualization in your report. Rebuild it with a built-in Power BI visual or an existing custom visual. AI coding tools can also help you create a visual with the Power BI custom visuals software development kit (SDK).
The Power BI roadmap includes planned HTML and Vega core visuals for more flexible report visualizations. Check the roadmap for planned availability.
Recreate the analysis or visualization outside the report. Explore these alternatives:
- Fabric notebooks: Recreate the analysis and visualization in a notebook. Scripts may need changes for supported languages, libraries, and data access.
- Fabric Apps: Explore this option for visualizations that can't be recreated in a Power BI report.
Both Fabric notebooks and Fabric Apps can be added to Organizational Apps to share them with your audience.
Next steps
Test your replacement and let report consumers know what's changing before retirement. If you view an affected report but don't own it, contact the report owner.
Learn more in the R visuals documentation and Python visuals documentation. Share feedback on this retirement in the comments.
Monday 09th November 2026, 7.00pm
- PowerBI:
Power BI reports support OAP exceptions for semantic models in separate workspaces (Preview)Workspace outbound access protection (OAP) helps you control where data in a Microsoft Fabric workspace can flow. The initial preview for Power BI reports, launched in June, required a report in an OAP-protected workspace to use a semantic model in that same workspace. Customer feedback highlighted that this was too restrictive. With this improvement, a report can now query a semantic model in another workspace provided a workspace administrator explicitly allowed that destination through an OAP exception policy.
Apply exception policies to allow report-to-model connections
OAP continues to block outbound report-to-model connections by default. When a report opens, Power BI evaluates the report workspace policy before it renders the report in the browser. If the destination workspace is covered by an applicable exception, the report can connect to its semantic model. Otherwise, Power BI blocks the connection, and the report does not open.
The report honors the policy that a workspace admin configured for the semantic model destination. You don't configure an exception on each report, and you don't need to move the report and semantic model into the same workspace. The OAP exception policy supports a common Power BI architecture: a central team manages shared semantic models in one workspace, while business teams build reports in separate workspaces. You can preserve that separation of ownership without removing the outbound boundary from the report workspace.
See the improvement in action
The following example shows a report stored in an OAP-protected workspace, and its semantic model is stored in another workspace. First, the report does not have an applicable exception policy. Power BI blocks the cross-workspace connection and displays the following error because the report can't access its semantic model.
Figure: OAP continues to block outbound report-to-model connections by default.
Next, a workspace admin creates an exception policy for the semantic model workspace. In the workspace settings under Outbound networking, select Add new cloud connection rule, select Power BI Semantic Model as the Connection Kind, and select the desired semantic model workspace under Workspace exception, as in the following screenshot. Select Add, and then select Save to save the Data Connection rules.
Figure: An OAP exception policy to allow report-to-model connections.
After the policy takes effect, the same report loads and its visuals render successfully. The report binding doesn't change. The OAP policy determines whether the cross-workspace connection is allowed. The semantic model remains subject to its own OAP controls. Connections from the semantic model to cloud databases, on-premises systems through gateways, lakehouses, warehouses, and other sources are still evaluated against the semantic model workspace's data connection rules. Make sure you enable OAP for both, the report workspace as well as for the semantic model workspace.
Next steps
Work with your workspace admin to confirm that your report workspace meets the OAP prerequisites and that OAP is enabled. Then create an exception policy for each approved semantic model destination. Policy changes can take about 15 minutes to propagate.
For configuration details, refer to the Workspace outbound access protection for Power BI reports documentation. To understand downstream enforcement, refer to Workspace outbound access protection for semantic models.
Thursday 05th November 2026, 10.00pm
- PowerBI:
Power Query Corner: Finding and connecting to data in the new experience (Preview)About this series
This is the first in a six-part Power Query Corner series exploring the new Power Query experience. Each post takes a closer look at a different part of the experience, including what’s changing, why it matters, and how you can put it to work. Getting data doesn't always begin with a connector name. You might know which database to use, recognize a team-maintained Fabric item, want to return to a source from yesterday, or already have the query logic you need.
A connector list is useful once you've decided how to connect. But choosing the right data often comes before that decision. We moved to a module-based approach so Get data can support those different starting points, rather than making every task begin with the same connector picker.
The idea is simple: start with what you know, then follow the route that fits the task. Modules organize discovery, reconnection, and authoring around that idea. They don't remove the need to authenticate, select the right objects, inspect a preview, or maintain the query afterward.
This first Power Query Corner issue follows a sales-report scenario in the new Power BI Desktop experience. It also uses clearly labeled Power Query Online examples to explain the wider design, then looks at the five most frequently reported Get Data problems and the work addressing them. The customer-feedback analysis draws on publicly available reports in our community forum thread, where we track feedback on the new Power Query experience.
Choose a Get data route that matches your task
Priya is preparing a regional sales review. A colleague offers a spreadsheet export, but the team also maintains sales data in Fabric. Before choosing Excel or another connector, she needs to decide whether to reuse that maintained item, return to a known source, or establish a new connection.
A module is a task-focused view inside Get data. Home brings the available routes together; the other modules give each task room for its own search, context, and actions. In Desktop, that includes New, Recent data, OneLake catalog, Blank table, and Blank query. The names and choices offered depend on the product hosting Power Query.
Figure: Home brings different starting points into one Get data experience. View more opens the corresponding full module; a source shortcut starts that source's connection flow. Official Desktop documentation screenshot. Source: Microsoft Learn
Know the source? Keep the direct route.
If Priya already has the required server, file location, or service URL, New remains the straightforward route: search for the connector or browse its category, then supply the required settings. Home can provide a shortcut without first opening the full list. Selecting a connector starts the connection workflow; it doesn't immediately load data.
This matters for familiar work. The module-based approach isn't an instruction to browse every module before choosing a CSV file. It should preserve a direct path for someone who already knows the source.
Know the business data? Discover the item first.
If Priya knows the team maintains sales data but doesn't know its endpoint, OneLake catalog gives her a different starting point. She can find an item by its business context, then review its type, owner, location, and available endorsement or sensitivity information before deciding to connect.
Imagine two items, both named Sales: one is in the team's maintained reporting location, while the other belongs to a personal test project. The name alone isn't enough. Catalog context helps Priya ask the right questions before she commits the report to a source. Endorsement is a useful signal, not a guarantee of suitability, and discovering an item does not grant permission to read it.
The benefit is not merely another way to open the same dialog: it lets Priya choose an appropriate existing data item before looking up connection details or creating another export.
To learn more, refer to the OneLake catalog overview for the catalog's broader discovery, governance, and security roles.
Used it before, or need a small starting table?
Recent data is the route back to a source Priya already recognizes. It avoids starting the decision again at the connector list, but a recent entry isn't a snapshot of the data or a guarantee that its location and permissions are unchanged.
Blank table and Blank query answer a different question: what if the starting point isn't an external source? Priya might enter a small RegionCode-to-RegionName mapping in Blank table or paste a self-contained M expression into Blank query. M is Power Query's formula language. Entered values become part of the query; pasting a spreadsheet's values does not create a refreshable connection to that spreadsheet.
Power Query Online examples, not Desktop capabilities
The broader module design also accommodates finding a source by browsing the place where it lives. Recognizing an Azure resource or a SharePoint site is different from knowing its server address or file URL. Where those source-browsing experiences are offered, they can carry the user from a recognizable location to the contents they want. Browsing into a location and selecting it for a connection are different actions, and a file's contents are different from a folder's file list.
Browse Azure, SharePoint browsing, and Upload is not currently available as modules in Power BI Desktop. They are part of Dataflow Gen2, and some are also available in Power BI web modeling; the available modules vary by host. There is no committed release date for these modules in Power BI Desktop. This module distinction should not be confused with the availability of individual Azure or SharePoint connectors through New. Search scope, filters, previews, and available actions depend on the browser and host. The useful principle is to support recognition and navigation where appropriate while retaining direct connector configuration.
Dataflow Gen2 illustrates another distinction: reusing data is not the same as reusing query logic. OneLake catalog helps find a data item; My Queries holds personal M scripts; Shared queries (Preview) let authors import logic shared by others. For example, Priya could reuse an existing region-cleanup script in a dataflow instead of recreating those transformations. Importing shared logic creates an independent copy, not a live link to its original, and does not transfer credentials or destinations.
To learn more, refer to the My Queries or Shared Queries documentation.
Figure: Dataflow Gen2 example, not Power BI Desktop: My Queries is a personal library of query logic, distinct from recent sources and from the separate Shared queries module. This published Dataflow Gen2 screenshot illustrates why different tasks need different entry points. Source: Microsoft Learn
Modules can also support tasks such as describing transformations with Copilot in Dataflow Gen2, subject to that feature's requirements. That does not make every Power Query Online module a Desktop capability. Use Get Data in Dataflow Gen2 for its supported entry points and Data sources in Power BI Desktop for Desktop.
Try it: Choose and preview a sales source in Power BI Desktop or web modeling
You can use the October 2026 release of Power BI Desktop or try Power BI web modeling today with an authorized source in a nonproduction report. In Desktop, enable the preview: navigate to File > Options and settings > Options > Preview features, select New Power Query experience, and select OK. The exercise below is a workflow, not a supplied sample dataset.
For the documented preview prerequisite, refer to the Data sources in Power BI Desktopdocumentation. Power BI web modeling uses Power Query Online, not this Desktop toggle.
Define the decision: Priya needs sales by region for the intended reporting period. In Desktop or Power BI web modeling, choose a maintained item in OneLake catalog, a known source through New, or an appropriate Recent data connection; the available routes vary by host.
Connect with context: compare the item’s owner, type, and location, or provide the connector’s settings, then authenticate with your authorized account. Catalog visibility does not grant data access.
Preview before committing where Navigator is offered, select the intended object and check its columns and level of detail. In the new Desktop Navigator, use Transform data in the Load dropdown when shaping is needed; follow the web modeling controls for that host.
Check the outcome in the editor: confirm the selected query and its Source step and explain which source the report now depends on. Use the linked Microsoft Learn guidance for detailed connection steps and host-specific options.
Figure: The selected item's type determines its available actions and subsequent connection path. This Desktop documentation screenshot shows Connect and Edit, not an Import/DirectQuery selector. It does not imply the same actions for every catalog item. Source: Microsoft Learn
The route changes how you find the source; it does not skip the source-specific connection and preview stages. Some connectors provide a table preview rather than Navigator.
For those patterns and host distinctions, refer to the Getting Data Overview. documentation.
In the Power BI service, use Create > Get Data for a new semantic model, or Get data in an existing model's ribbon, with the required editing permissions. A semantic model contains the tables, relationships, and calculations used for analysis. This route is not a Dataflow Gen2 destination workflow.
Refer to the Edit semantic models in the Power BI service. documentation to learn more.
Compare the decision, not just the dialog layout
The legacy Desktop Get Data dialog is organized around connector categories: choose the source type, then connect. That remains an effective mental model when you already know the source. Legacy Desktop also has recent-source and Fabric-data entry points; the point is not that these ideas never existed before.
The new experience brings different starting points into an organized Get data surface. New starts with the connector; OneLake catalog starts with an existing data item and its context; Recent data starts with previous work; Blank table and Blank query start with values or code. Home helps choose among the available routes instead of acting as the only place where everything must fit.
That changes Priya's first decision from “Which connector should I pick?” to “What am I trying to reuse or create?” For a maintained Fabric source, she can investigate the item before configuring a new source connection. For a known CSV file, she should still be able to take the direct route. In supported Power Query Online hosts, query-library and source-browsing modules extend the same principle to other tasks.
A common organizing pattern does not mean identical behavior. Power BI Desktop and Power Query Online differ in how connection settings, authentication, and load or save actions work. In the new Desktop Navigator, Transform data is inside the Load dropdown; the documented legacy flow has a separate Transform Data button. Choose the transformation route when the data needs inspection or shaping before loading.
For host-specific gaps and workarounds, refer to the New Power Query experience known limitations and workarounds documentatin. Some Desktop workflows still use a legacy interface while preview is enabled.
The design is useful only if those routes remain practical. Discovering the right data should not come at the expense of an established SQL-editing workflow, required Web options, a reliable Combine action, or prompt access to a familiar connector. That is why the feedback below matters: it tests the intended benefits against the work people need to finish.
State of the new UI
Status summary
The new Get data experience remains in preview. Alongside making sources easier to discover, an important part of this work is preserving the connection workflows people already depend on in the legacy experience.
We've addressed the missing native-SQL input when creating connections with supported connectors. A native SQL statement is a database query supplied directly to the source, rather than a sequence authored entirely through Power Query's transformation controls.
Entering that statement when first connecting and reopening it later are different workflows. Coverage for reopening connection settings through the Source step's gear icon is still partial for native SQL and other extension-based connectors. We're continuing work on the underlying connection dialog to support these editing scenarios more consistently.
For the maintained reference to current gaps and workarounds, refer to the New Power Query experience known limitations and workarounds documentation.
What we're hearing
For this first issue, we reviewed the discussion from its beginning on May 11 through October 26, 2026: the opening post and all 386 replies available at the review cutoff. The five themes below were selected by the number of distinct contributors explicitly reporting each problem, not the number of posts or likes. A person is counted once per issue and can appear in more than one theme. These counts describe the discussion, not the proportion of all customers affected.
Because this is a full-history review, the ranking includes the initial native-SQL gap that has since been addressed. We keep it separate from later editing problems so progress on one is not mistaken for completion of the other.
- Entering native SQL is an essential part of connecting
-
- Twenty-four distinct contributors in the first-run feedback review.
- For some teams, connecting to a database starts with an existing SQL statement, not simply selecting a table. That statement defines the dataset they want to bring into the report and lets them reuse a familiar database-querying workflow.
- One Amazon Redshift user reported that the custom SQL input was missing from Advanced options. Another explained that their BI group primarily used Redshift and disabled the preview after discovering the missing native-query field.
- In their established connection workflow, entering SQL was part of getting started. Removing that input meant the new dialog could not accommodate how their team already prepared report data. This was a workflow blocker, not simply a preference about the dialog's layout.
- We've addressed the missing input for supported connectors. That change concerns creating the connection; maintaining its SQL afterward requires separate attention.
Figure: Legacy Desktop Amazon Redshift connection dialog from Microsoft Learn. Advanced options is shown collapsed; the connector documentation lists SQL statement among its advanced capabilities. This is a legacy workflow reference, not a screenshot of the preview fix. Source: Microsoft Learn
- Creating a query is only the beginning: people need to edit it later
-
- Sixteen distinct contributors in the first-run feedback review.
- In the legacy experience, users could return to a query's Source step, select its gear icon, and reopen the connection dialog to change the SQL statement. The gear icon is the shortcut for editing settings associated with that step.
- An Azure Databricks contributor described the difference between creating and maintaining a query: the SQL input was available when creating a connection but disappeared when reopening its settings. They relied on that dialog for quick updates to existing reports, saving time and transformation steps, and reverted to the legacy experience when it was unavailable.
- There is also a broader productivity concern. One detailed example explains how a team moves parameterized SQL between Power Query and DBeaver. They use reporting-period parameters so business users can change dates without rewriting SQL. Their editing workflow depends on extracting readable SQL; copying it from the Advanced Editor instead introduces M-specific quotation marks and escape sequences that must be cleaned up before it can run in the external tool.
- These examples show why the gear-icon workflow matters. It provides access to an editable connection form instead of requiring users to reconstruct or modify the surrounding M expression. Coverage remains partial, and we're continuing work on reopening settings for native SQL and other extension-based connectors. The parameterized-query example is a distinct scenario, not a claim that every variation is already covered.
- Get data needs to become usable quickly
-
- Eight distinct contributors in the first-run feedback review.
- For a familiar source, users often already know exactly what they want to connect to. They expect to select the connector and proceed without waiting for the rest of the discovery experience.
- One contributor compared their CSV workflow directly: previously, they selected CSV and chose a file; in the new flow, they waited for the interface and then selected Browse before choosing the file. Another reported delay before the connector options were even visible.
- The concern is therefore not only total loading time. It is how quickly someone can act on a choice they have already made. A discovery page should help someone exploring an unfamiliar source without slowing down someone returning to a familiar one. Improvements to Get Data startup and loading are expected in the December 2026 Power BI Desktop release.
- Advanced Web settings can determine whether a connection is possible
-
- Five distinct contributors in the first-run feedback review.
- Advanced connection settings are not necessarily optional refinements. A web service may require a particular request header before it will return data, or a connection may need a URL assembled from several parts. A request header is additional information sent with the request, such as a service's required authentication header.
- One contributor described using an X-API-Key header for a read-only service account. That configuration worked in the classic dialog, but the new dialog provided no way to enter the header. Other feedback distinguished missing custom-header configuration from the missing API-key authentication option. These are related concerns, but restoring a header input is not the same as implementing every authentication method or secure credential-storage scenario.
- In the legacy From Web experience, Advanced options exposed URL parts, timeout or page-wait controls, and request-header inputs where applicable. For people relying on these settings, a simpler dialog that omits a required input cannot replace the existing connection workflow.
We're working on the Web API and Web Page connectors' advanced configuration to restore the missing settings. The two connectors have different purposes and applicable options, so this is not a promise that every setting belongs in both dialogs.
Figure: Legacy Desktop from Web Advanced settings from Microsoft Learn. This reference shows the kinds of controls discussed in the feedback; applicability differs between Web API and Web Page. It does not show the current preview or a completed fix. Source: Microsoft Learn
- Combine Files needs to produce the combined contents people expect
-
- Five distinct contributors in the first-run feedback review.
- Folder and SharePoint Folder workflows commonly bring similarly structured files together into one table, such as monthly exports for a reporting period. The file list and the combined data are different results: the list describes the files, while the combined table contains the rows read from inside them.
- In the documented legacy Desktop Folder workflow, Combine & Transform Data combines file contents and opens the result in the editor. Transform Data alone opens the file list as-is. That distinction lets users choose whether to combine immediately or filter the list before combining.
- One report described receiving file metadata even though the preview showed file contents. Another required a second Combine Files action from the ribbon, while a SharePoint Folder report described output containing the processed files' headers rather than the expected combined data.
- These are different symptoms, but they interrupt the same task: turning a collection of files into a usable dataset. The expected output is the files' combined contents, not a list that still requires the user to repeat the operation or repair the result manually. We're continuing to address the reported Combine Files issues.
Figure: Legacy Desktop Folder preview from Microsoft Learn. The rows shown are file metadata, not the contents of the CSV files. The Combine action begins the workflow that reads and combines those contents. This is a reference image, not a screenshot of a reported failure. Source: Microsoft Learn
Beyond these five themes, contributors also raised concerns about authentication choices, catalog and Navigator completeness, recent-source behavior, custom-connector compatibility, localization, and the visibility of Load and Transform actions. We acknowledge those reports as well; appearing less frequently in this discussion does not make their impact unimportant.
What you can expect
The missing native-SQL input at initial connection has been addressed for supported connectors. Our ongoing work includes improving how existing connection settings reopen through the gear icon, restoring missing advanced settings in Web API and Web Page connections, and addressing Combine Files failures.
For startup and loading performance, improvements are expected in the December 2026 Power BI Desktop release. That expectation applies specifically to startup and loading; we are not announcing the same release timing for every issue discussed here.
Connector and workflow coverage can differ while this work progresses. An improvement to initial connection does not automatically resolve an editing problem, and progress on one Combine Files failure does not establish that every reported symptom is fixed.
For current limitations and available workarounds, including when returning to the legacy Desktop experience is appropriate, see New Power Query experience known limitations and workarounds. In Desktop, you can clear the New Power Query experience preview checkbox without restarting. That fallback does not switch Power Query Online in web modeling to a legacy interface.
Share your feedback
Discuss your experience and share feedback in the forum: Share your thoughts on the new Power Query experience in Power BI.
Propose feature ideas or vote on existing suggestions in the Fabric Ideas portal.
Continue the Power Query Corner series
This post is part of our six-part Power Query Corner series on the new Power Query experience. Explore the other posts in the series:
- Finding and connecting to data in the new experience (Preview)
- Understand how your Power Query query runs (Preview)
- Understanding query relationships with Diagram View (Preview)
- Review wide tables with Schema View (Preview)
- Read the whole recipe in Query Script View (Preview)
- Cluster supplier labels and rank results (Preview)
Links will be added as each post is published.
Thursday 05th November 2026, 5.00pm
- PowerBI:
Microsoft & Snowflake’s Commitment to Apache OssieIf you haven't already, check out FabCon and SQLCon 2026 in Barcelona: Building the data foundation for Microsoft Copilot and Agents for a complete look at all of our FabCon Europe announcements across Fabric and Microsoft Databases.
Advancing an open, interoperable semantic foundation for AI-powered analytics
Today, Microsoft is pleased to affirm our commitment to Apache Ossie (incubating), a community-led effort to establish a vendor-neutral standard for exchanging semantic metadata across analytics, AI, and BI platforms. This has been a close collaboration with Snowflake, who helped found Ossie.
We have heard loud and clear that customers want to enable platform-agnostic agentic experiences. Shared semantic context must be defined once and reused across platforms, enabling agentic consumption at scale, maximizing the reach of AI-powered analytics, and empowering users to leverage the best agent for the job.
Power BI semantic models are key enablers of AI-powered analysis, providing humans and AI agents with governed semantic context to answer data questions quickly and confidently. Power BI semantic models have more than 38 million monthly active users and are adopted by 94% of Fortune 500 companies. Microsoft was also recognized as a Leader and Outperformer in the GigaOm’s radar for semantic layers & metric stores in 2025. We’re now bringing this wealth of experience to Apache Ossie, and we are excited to work with Snowflake and other partners to help make the project successful.
Why Apache Ossie matters
Until now, semantic definitions were often recreated across platforms, introducing complexity, inconsistency, and management overhead. Apache Ossie addresses this with a common specification that tools can read and write. Its goal is straightforward but consequential: define a semantic layer once and make it portable across the data and AI ecosystem, while preserving semantic meaning and governance for agentic consumption.
Collaboration with Snowflake
Snowflake and Microsoft serve many of the same customers, but customers don't want to choose between ecosystems. They want their data and analytics investments to work together. That makes interoperability between, for example, Snowflake Semantic Views and Power BI semantic models a shared responsibility. This layers on top of the integration work we have already done with Snowflake for writing Iceberg tables from Snowflake to OneLake, Mirrored Databases from Snowflake, using Iceberg tables with OneLake, Catalog Integration for OneLake, Power Query Snowflake connector and much more.
As discussed in the Snowflake blog post and the message below from Carl Perry, VP of Analytics at Snowflake, our collaboration is currently focused on using Apache Ossie as a vehicle for cross-platform semantic-layer conversion without moving or duplicating the underlying data. Looking ahead, we’re committed to advancing the open standard by building on our deep expertise in semantic modeling by, including helping establish DAX as an Ossie-recognized query language. We also plan to help advance Ossie support for ontologies so customers can extend the business logic in semantic models beyond agentic analysis and into platform-agnostic operational intelligence.
Ultimately our goal is simple: enable customers to define once, and reuse anywhere.
Today, we are highlighting the following new integration scenario: converting an Ossie document into both a Snowflake Semantic View and a Power BI semantic model. This enables customers to define shared semantic context once, then reuse it across Snowflake and Fabric while retaining the agentic experiences and capabilities of each platform. Refer to Apache Ossie Microsoft Converter for more information.
Building together
We look forward to working with the Apache community, Snowflake, and others across the industry to create a more open and connected future for AI-powered analytics, delivering more choice and flexibility for customers.
Get involved: Visit the Apache Ossie project website and repository to explore the specification and community contribution channels. Share your thoughts and feedback with us.
Apache Ossie is undergoing incubation at the Apache Software Foundation. Incubation indicates that the project is working toward the governance, infrastructure, and community practices expected of established Apache projects.
Monday 26th October 2026, 6.44pm
- PowerBI:
Power BI October 2026 Feature SummaryLast month, we shared a packed September update alongside the European Microsoft Fabric + SQL Community Conference. Even so, the Power BI team has continued delivering new capabilities, and we didn't want to wait another month to share them.
This update includes enhancements across Copilot and AI, reporting, and semantic models, helping users create richer reports, streamline workflows, and get more value from their data.
Table of Contents
Copilot and AI
Create Power BI reports with custom visuals using skills for Fabric (Generally Available)
The Power BI Report Authoring skill now extends natural-language report authoring to custom visuals, helping teams create reports that meet specialized business and design requirements with less manual configuration. Ask the agent to add a visual, bind it to report data, apply formatting, and validate the visualization.
The skill can use supported custom visuals already added to a report, including visuals imported from a file, and it can help identify an AppSource visual when the report needs a capability that core visuals don’t provide. This reduces time spent finding visual identifiers, editing report files, and troubleshooting field mappings, so report authors can focus on selecting the right presentation for the business question.
Learn more in the Power BI Report Authoring skill overview and Install Skills for Fabric guidance.
Reporting
Gantt chart (Preview)
The Gantt visual is a new core visual for Power BI reports that lets you show tasks and progress on a time-based axis. Use it to plan projects, track schedules, or compare activities across categories directly in your report.
Figure: Gantt visual showing a project schedule grouped by Planning, Development, Testing, and Deployment phases from January to April 2025, with the Format visual pane open to the Visual tab.
The visual includes:
- Plotting of bars showing the duration of each row with progress formatting and milestones to mark key -dates.
- Axis with custom formatting and range controls, so you can set the start and end dates, adjust the date and time format, and choose the units that appear on the axis.
- Bar colors cascade naturally by category, which keeps related tasks visually grouped without extra configuration.
- You can add more columns next to the task list to show fields such as owner, status, or duration.
- A zoom axis lets report readers focus on a specific window of time and then return to the full range.
To try the Gantt visual, enable it in Power BI Desktop under File > Options and settings > Options > Preview features, and then restart Power BI Desktop.
To learn more and try it in your reports, refer to the Gantt visual documentation.
List slicer with dropdown option (Preview)
The list slicer now includes a dropdown mode that makes long lists easier to navigate and active filters easier to review. Enable Show selected first to pin current selections to the top of the dropdown, eliminating the need to scroll through every item to confirm what is filtered. The button slicer also supports Show selected first, providing the same quick view of active selections in either slicer style.
Figure: List slicer in dropdown mode showing selected values as dismissible pills and the Show selected first option.
The dropdown carries over the formatting you've already applied to the list slicer items, and you can now customize the height and width of the dropdown drawer to fit your report layout. The search box also has more formatting options, so you can match the slicer to the look you want across background, border, and text styles.
Each selection appears as a pill outside the dropdown that shows the item name and a dismiss button, so report readers can remove a value with one click. When selections exceed the available space, a count pill shows how many more values are selected, so you can see the total without opening the dropdown.
When you use Select all and then clear one or more items, the slicer makes the resulting filter state explicit. Cleared values appear as Not (item) pills, showing that Power BI is excluding those values rather than including every remaining item individually. If you do not clear any items, Select all behaves like no selection and does not filter other visuals.
To learn more, refer to the Slicers in Power BI documentation.
Chart plot area background color (Generally Available)
The plot area of bar, column, line, area, combo, ribbon, waterfall, and scatter charts now supports a single fill color and conditional formatting in addition to the existing background options. A solid color can improve visual separation, while conditional formatting can use a measure or field value to make changes in the data easier to recognize.
Figure: Bar chart with the Plot area background formatting pane open, showing the new Background color and Transparency options.
To learn more, refer to the Customize visualizations in a Power BI report documentation.
Auto-expand hierarchy axis with field parameter support (Generally Available)
Bar, column, and line charts now support auto-expand for the hierarchy axis when you add more than one column to the axis, and the hierarchy axis now works with field parameters.
Figure: Column chart using a field parameter on the axis with Auto expand turned on in the X-axis formatting pane.
This matches the existing auto-expand behavior in the slicer and matrix visuals, so hierarchy interactions stay consistent across your report. Add a field parameter to the axis so you can quickly switch between a single column and any combination of columns as the hierarchy, without rebuilding the visual.
Report viewers can drill up, drill down, or move across hierarchy levels from a slicer, allowing them to explore the data based on the question they want to answer. The same behavior is available when viewers use Personalize this visual to change the chart’s axis fields.
Figure: Selecting a field in the Category parameter slicer updates the column chart axis and the matrix hierarchy at the same time.
The animation shows a report page with a Category parameter slicer, a column chart, and a matrix. When you select Country in the slicer, the column chart updates to show Sales by Country with one bar per country, and the matrix updates to show the Country level of the hierarchy. Selecting Segment or Product instead swaps the chart axis and matrix hierarchy to that field. When you make multiple selections, the hierarchy expands automatically, so a single slicer controls the fields used across both visuals without requiring other changes to the report.
To learn more, refer to the Customize X-axis and Y-axis properties, Drill mode in the Power BI service and Create field parameters documentation.
Personal bookmarks keep column widths (Generally Available)
Personal bookmarks now preserve visual column widths, so you can return to the exact table or matrix layout you saved instead of resizing columns again. This includes reordered and resized columns, helping you maintain a consistent personal view each time you apply the bookmark.
Figure: Save a personal bookmark to preserve your report’s table column widths.
To learn more, refer to the Personal bookmarks in Power BI documentation.
Semantic models
More accurate surge protection with semantic models
Semantic models now report capacity unit (CU) usage continuously during long-running background operations instead of reporting most usage when an operation finishes. This gives surge protection a more current view of in-progress consumption, so configured rejection and recovery thresholds respond more closely to actual capacity usage. The improvement is automatic and requires no settings changes.
Actual capacity measurements from August 2026, when continuous CU reporting was first enabled, show that capacity intervention shifted earlier in the process. Compared with the period before enablement, proactive surge-protection rejections increased from 5% to 12%, and operations that were delayed but ultimately accepted increased from 11% to 16%. Late-stage Fabric throttling rejections decreased from 23% to 13%. These observed changes correspond to a 145% increase in proactive surge-protection rejections, a 52% increase in delayed but accepted work, and a 41% reduction in late-stage Fabric throttling rejections.
Figure: Continuous CU reporting shifts capacity intervention toward proactive surge-protection rejections and accepted delays, based on actual measurements from August 2026.
Continuous CU reporting exposes consumption sooner, allowing surge protection to reject more new background operations proactively and delay more on-demand work without rejecting it. As a result, fewer operations reach deeper Fabric Throttling rejection states.
To learn more, refer to the Surge protection documentation.
That’s a wrap!
The momentum from last month continues with new capabilities that make Power BI more flexible, efficient, and powerful for both report authors and consumers. We encourage you to explore the features highlighted in this post and review the accompanying documentation to start taking advantage of them in your own solutions.
We'll be back next month with more updates and innovations from across Power BI.
Thursday 15th October 2026, 9.25pm
- PowerBI:
Power BI September 2026 Feature SummaryAs the Power BI, Microsoft Fabric, data, and analytics community gathers in Barcelona for the European Microsoft Fabric + SQL Community Conference, this month is packed with news. From new Copilot and AI experiences to reporting, modeling, data connectivity, developer enhancements, and mobile updates, we're sharing the latest innovations designed to help you build, analyze, and act on your data more effectively. Whether you're joining us in person or following along from afar, this roundup is your guide to everything new across Power BI this month.
Table of Contents
- General
- Copilot and AI
- Power BI Agentic Experiences (Generally Available)
- Microsoft 365 Copilot is coming to Power BI (Preview)
- Power BI data answers in Microsoft Copilot Chat (Generally Available)
- Fabric IQ Plugin in Microsoft 365 Copilot Cowork (Generally Available)
- Build Fabric Apps more easily in GitHub Copilot App (Preview)
- Enhanced Report Consumption Copilot with Fabric IQ
- New control for Copilot access to semantic models
- Remote Power BI Authoring MCP Server (Preview)
- Reporting
- New Report Ribbon on the web (Preview)
- Live Visual Sharing in Outlook on the web (Preview)
- More control and context in Power BI Home (Generally Available)
- Set and reset column widths in table and matrix (Generally Available)
- Visual calculations for small multiples (Generally Available)
- Design ribbon for Power BI reports (Generally Available)
- Slider color options for Slicer visual (Generally Available)
- Translytical task flows show user date function (UDF) information in button action (Generally Available)
- Format pane headers stay visible as you scroll (Generally Available)
- Pick the axis initial scroll position (Generally Available)
- Azure Maps geocoding improvements (Generally Available)
- On-object interaction improvements (Preview)
- Support for Fabric Apps in Org apps (Coming Soon)
- Changes to Power BI subscription email delivery
- Increased Export to Excel row limits (Coming Soon)
- Value selection in Narrative visual
- Modeling
- Data connectivity
- Mobile
- Developers and APIs
- Other
- Third-party custom visuals
- That’s a wrap!
General
Deprecation of Old File Picker experience in Power BI Desktop
In April we deprecated the old file picker experience in Power BI Desktop. Starting in October, users using versions of Power BI Desktop from March 2026 or earlier will no longer be able to save and share Power BI files to OneDrive and SharePoint. Please ensure you update Power BI Desktop to keep using this functionality.
Copilot and AI
Power BI Agentic Experiences (Generally Available)
Agentic development in Power BI is real, and it is already delivering value: whether you are starting from scratch with greenfield projects or building upon existing solutions in brownfield scenarios, BI developers can delegate the work to an agent, review the result, and refine it rather than starting from scratch every time.
What makes this work is tools and context. Through Work IQ and Fabric IQ, the agent grounds its work in your business context—your data, your semantics, and the way your organization operates. Through skills—published by Microsoft in skills-for-fabric, shared by the community, or personalized by your own team—it also picks up your development context: the modeling and reporting practices, conventions, and workflows your team expects.
Through tools such as the Power BI Authoring MCP server and the Power BI Desktop Bridge CLI, the agent can act on that context: reading and changing semantic models and reports directly, reloading its edits in Power BI tools, and reviewing its own work. Point an agent at a requirements document or a screenshot of the layout you want, describe what you need, and the agent can help accelerate the initial authoring pass, which you can then review and refine.
Figure: Animated GIF showing the creation of a Power BI report based on a remote semantic model using Modeling MCP, the Modeling skill, and report authoring skills.
What's available today
- The powerbi-authoring plugin in microsoft/skills-for-fabric bundling the semantic modeling and reporting agent skills and tools. It was recently updated to support report authoring for remote semantic models in Power BI service and an expanded range of supported report visuals, including custom visuals.
- To learn more, refer to the Power BI skills documentation.
- The local Power BI Authoring MCP server allows the agent to edit semantic models in Power BI Desktop.
- To learn more, refer to the Power BI Authoring MCP documentation.
- Power BI Desktop Bridge lets an agent reload changes in a running instance of Power BI Desktop and capture screenshots to check its own work.
- To learn more, refer to the Power BI Desktop Bridge documentation.
- Browser-based validation for remote report editing, so the agent can validate a report using a headless browser (an automated browser that runs without a visible user interface). Removing the local Power BI Desktop dependency allows the full authoring loop to run without Power BI Desktop, extending the agentic experience to Mac users and others who do not rely on a local installation.
To learn more and get started, refer to the Power BI agentic documentation.
Microsoft 365 Copilot is coming to Power BI (Preview)
Copilot experiences have emerged across the applications people use every day, bringing AI closer to the work happening in each product. But this can also feel fragmented, with different entry points, separate conversations, and uncertainty about which Copilot agent to use.
Our goal is to create a consistent Copilot experience that is available wherever people work. People should not have to leave the application they are using to find it. Microsoft 365 Copilot should be available within their experience, carry relevant context across experiences, and connect to the specialized intelligence of each product.
We’re taking an important step toward that goal with a preview of Microsoft 365 Copilot integrated directly into Power BI and Microsoft Fabric.
This integration gives users a familiar place to bring together business context and trusted data. Shared conversation history lets them continue a discussion as they move between Microsoft 365 Copilot experiences instead of starting over in each application.
Figure:Screenshot of Copilot Chat integrated into the Power BI experience, including integration with Work IQ.
In Power BI, a question no longer has to stop with the numbers in a report. A sales leader could use Fabric IQ to identify which regions are behind plan, then use Work IQ to connect the results with customer emails, meetings, account plans, and documents. They could summarize the complete picture and even kick off actions and tasks in Cowork, all from inside Power BI. This work context and ability to move directly from insight to action were not available in the standalone Power BI Copilot experience.
Figure:Screenshot of the Cowork integration into the Power BI experience, highlighting the full Microsoft 365 experience embedded into Power BI.
A new setting in the Fabric admin portal will determine whether this integration is available by enabling or disabling its entry point in the navigation pane. It will be off by default, giving administrators time to evaluate the experience before introducing it to their organization. Administrators can enable it when they are ready and disable it if they need to pause access.
This setting is independent of the existing setting for standalone Power BI Copilot. If both settings are enabled, users with a Microsoft 365 Copilot license will see entry points for both experiences, and standalone Power BI Copilot will continue to appear on Home. If standalone Power BI Copilot is disabled and Microsoft 365 Copilot is enabled, users will see only the Microsoft 365 Copilot entry point.
During the initial preview, the integrated experience is available only to users with a Microsoft 365 Copilot license. These users receive the full Copilot Chat experience in Power BI and Fabric, bringing together Fabric data through Fabric IQ and relevant Microsoft 365 context through Work IQ. Existing permissions and governance controls continue to determine which content each user can access.
Support for a broader Fabric audience will follow. This expansion will give Fabric users without a Microsoft 365 Copilot license access to an integrated Copilot experience tailored to their available capabilities. The experience may differ from the full licensed offering, but it will extend Fabric IQ and conversational data experiences to more types of Fabric users.
The preview will roll out with the setting turned off by default, with administrators choosing when to enable it for their organization.
This is an important step toward one Copilot that meets people wherever they work, connecting the context surrounding each decision with trusted business data.
To learn more, refer to the Copilot in Power BI documentation.
Power BI data answers in Microsoft Copilot Chat (Generally Available)
Users can find and ask questions about Power BI reports and semantic models directly from Microsoft 365 Copilot. They can search for relevant Power BI content, attach a report or provide a link, and ask questions in natural language.
Figure: Microsoft Copilot Chat featuring a data answer coming from a Power BI report, cited.
Powered by Fabric IQ, the experience uses the data, measures, relationships, and business logic already defined in Power BI to provide grounded answers. Users can also bring Power BI insights into conversations that include their Microsoft 365 work context, such as emails, meetings, and documents.
Microsoft 365 Copilot now supports Microsoft Purview Data Loss Prevention (DLP) policies and information protection controls for this experience. This helps organizations adopt conversational analytics while applying their existing policies for identifying, classifying, and protecting sensitive data. The experience continues to respect existing Power BI permissions and Microsoft 365 governance controls. Users can only access Power BI content they are authorized to view, and administrators retain control over whether Fabric data is available in Microsoft 365 Copilot.
Organizations can use Power BI data answering in Microsoft 365 Copilot with production support and service commitments. This milestone makes it easier for users to bring trusted business data into the flow of work without leaving Microsoft 365 Copilot or creating a separate agent.
To learn more, refer to the Fabric IQ in Microsoft 365 Copilot Chat (Frontier) documentation.
Fabric IQ Plugin in Microsoft 365 Copilot Cowork (Generally Available)
Power BI data is available where multi-step work happens, so a business question, the analysis behind it, and the follow-up it triggers stay in one place.
To ground a task in Power BI, users can search for relevant content, attach a report, or paste a link to a report or semantic model. Questions are answered using the data, measures, relationships, and business logic already defined in the semantic model. Coverage now extends to reports published through organizational apps, with improvements to content discovery, large model handling, schema selection, Verified Answers, and row-level value search.
The plugin also carries forward the governance controls organizations rely on in Power BI:
- Existing access controls: Power BI permissions and row-level security determine which reports and semantic models each user can reach.
- Citations and sensitivity labels: Responses cite the Power BI content behind an answer and surface the Microsoft Purview Information Protection label applied to it, so users can see where a number came from and how it is classified.
- From insight to action: With Fabric IQ, users can analyze Power BI reports using natural language, uncover key findings, and put those findings to work right away in Cowork. Whether they are summarizing business performance, investigating a trend, or answering a data question, Fabric IQ turns trusted organizational data into outcomes.
To learn more about supported scenarios, setup, and current considerations, refer to the Fabric IQ in Microsoft 365 Copilot Cowork documentation.
For licensing and pricing information, refer to Microsoft 365 Copilot plans and pricing.
Build Fabric Apps more easily in GitHub Copilot App (Preview)
Fabric Apps were introduced in June as an AI-first way to build custom web apps with Microsoft Fabric as the backend. This month we’re excited to share that building these Fabric Apps on your governed data has become even easier with the GitHub Copilot App, which gives you a natural language chat interface instead of a command-line interface.
Figure: GitHub Copilot App chat interface.
To try it out, start by downloading the GitHub Copilot App. Then navigate to Customize > Plugins > Rayfin, and select Install to enable our dedicated plugin:
Figure: Installing Rayfin plugin in GitHub Copilot App.
Once the plugin is enabled, simply start a new chat and work with Copilot to help plan your Fabric data app. After you review and approve the plan, ask the agent to execute it and specify the workspace where you want to deploy the app.
Figure: Example New York Taxi app.
We look forward to seeing the amazing apps you build! Check out our community gallery for inspiration.
Enhanced Report Consumption Copilot with Fabric IQ
When viewing a Power BI report, you can enable Fabric IQ from the Copilot pane to better answer complex questions about your data. This enhancement merges existing Fabric IQ capabilities into Power BI Copilot report viewing mode, allowing Copilot to use a multi-step approach to evaluate data in the semantic model and refine its approach when generating a response.
Figure: Fabric IQ enabled in Power BI Copilot report pane (viewing mode) to answer a data question with a supporting textual answer and visualization.
With Fabric IQ enabled, Copilot can:
- Provide better answers to questions about your data based on detailed reasoning capabilities directly into the report viewing experience.
- Show reasoning steps to help you understand how Copilot provided an answer.
- Generate Fabric visuals to help you further analyze your data. Answers can include column, bar, stacked, line, area, pie, donut, scatter visuals.
- Provide the underlying DAX query and data table used to generate a response.
Figure: GIF illustrating how to enable Fabric IQ in Power BI Copilot report pane (viewing mode) to answer data questions.
To learn more, refer to the Ask Copilot questions about your data documentation.
New control for Copilot access to semantic models
Power BI now provides semantic model editors with greater control over how Copilot can be used with their data. Users with write permissions can block read-only users from accessing a semantic model through Copilot and Microsoft’s remote MCP tools, supporting governance, compliance, and access-control requirements.
The setting applies across Copilot experiences that query the semantic model, including Power BI Copilot experiences; Microsoft 365 Copilot Chat and Cowork; and data agents, remote Fabric MCP servers, and Power BI MCP servers. When disabled, users with read-only access won't be able to access that semantic model through these experiences. By default, the setting remains enabled to preserve the current behavior.
This setting appears in the Copilot section with the following description: “Allow any person with read-only access to use AI (i.e. Copilot, Microsoft’s MCP tools) on the model and its related reports.”
Figure: Setting that allows people with read-only permission to use AI experiences with the semantic model and its related reports.
This update gives organizations a clear and enforceable way to control AI access to semantic model data while maintaining flexibility for semantic model editors.
To learn more, refer to the Use Copilot with Semantic Models in Power BI documentation.
Remote Power BI Authoring MCP Server (Preview)
The Power BI Authoring MCP enables AI applications to create and modify semantic models in Fabric workspaces, without installing or maintaining anything local. This release also unblocks Mac users that want to use the Power BI Authoring MCP, because the server runs remotely and does not require local binaries.
Use the following endpoint in AI applications such as GitHub Copilot App:
https://api.fabric.microsoft.com/v1/mcp/powerbi/authoring
Figure: Power BI Remote MCP Server configuration in GitHub Copilot App.
The local Power BI Authoring MCP server, released in November 2025, remains generally available. It remains an option when an agent needs to work with Power BI Desktop, Power BI Project (PBIP) or TMDL files on disk. The local and remote servers support the same authoring capabilities.
We recommend using the remote server when local development is not required, such as when creating a Direct Lake semantic model in a Fabric workspace.
In the following example, the AI agent uses one tool call to create a Direct Lake semantic model connected to a Fabric Lakehouse:
Figure: Using Power BI Remote MCP to create a Direct Lake semantic model.
To learn more, refer to the Power BI Authoring MCP server documentation.
Reporting
New Report Ribbon on the web (Preview)
The Report ribbon is now available on the web, providing a consistent experience for report consumption and authoring that more closely matches Power BI Desktop. The ribbon organizes commands into clear, easy-to-navigate tabs, making it easier for users to discover features, interact with reports, and complete editing and authoring tasks directly in the browser. It also introduces the new Design ribbon and additional capabilities that were previously unavailable on the web, such as Format Painter.
This milestone brings greater consistency to Power BI report-authoring experiences and marks an important step toward a seamless, end-to-end reporting workflow on the web. As web authoring capabilities continue to expand, users will be able to accomplish more of their reporting tasks directly in the browser, enabling a more streamlined, productive workflow.
Figure: New report ribbon on the web.
Enable the Try the new ribbon (preview) at the top of the page to explore the new experience. You can disable the setting to return to the previous ribbon.
To learn more, refer to the Report Ribbon on the web documentation.
Live Visual Sharing in Outlook on the web (Preview)
For years, sharing data through email has been stagnant. You could send a screenshot, but it immediately became stale. You could attach a report link, but recipients had to leave their workflow to find the context they needed. And every follow-up question often meant another screenshot, another export, or another email thread.
Now, we're bringing a new way to share Power BI insights directly in the flow of work with Live Visual Sharing in Outlook. With Live Visual Sharing, you can insert a Power BI visual into Outlook on the web and share it as a live, interactive experience. Recipients can view and interact with the visual directly in Outlook while staying connected to the latest underlying data.
Figure: A live Power BI visual in Outlook on the web.
When a live visual is shared, Outlook renders an interactive version of the Power BI visual. Rather than embedding a static image, the experience remains connected to the source report and retrieves current data when viewed.
Recipients can:
- Interact with the visual directly in Outlook on the web.
- Access tooltips and explore data points.
- See filters and slicers applied at the time of sharing.
- View refresh information and data context.
- Navigate back to the source report when deeper analysis is needed.
The result is a richer conversation around data, directly within Outlook.
Sharing a live visual is simple:
- Open a Power BI report in the service.
- Select a visual to share, then select More options in the upper-right corner.
- Select Share.
Figure: Share option in Power BI.
- Select Link to this visual.
Figure: Link to this visual as part of the share dialog.
- A pop-up will appear asking if you want to use the current view (apply existing filters and slicers) or not.
- After selecting Create Link, the link is copied to your clipboard.
Figure: Before copying the link, you can configure the view in this dialog.
- Open Outlook on the web. This experience is not available in the Outlook desktop app. Create a new email.
- Paste the link in the email. The visual renders in loop after a few seconds! You can also share the same link in a Loop page, and the visual will also be rendered.
Figure: An unfurled Power BI visual in Outlook on the web.
By combining Power BI, Outlook, and Loop-powered experiences, we're bringing data closer to where collaboration happens. Live Visual Sharing can support more informed, data-driven conversations in Outlook.
To learn more about Live Visual Sharing in Outlook, refer to the Share live Power BI visuals documentation.
More control and context in Power BI Home (Generally Available)
Power BI Home now provides additional context and personalization options to help users discover the right content more efficiently. With new freshness indicators and customizable list views, you can quickly identify the most relevant reports and semantic models, prioritize the metadata that matters most, and tailor the experience to fit your workflow.
Find the right content more easily
Discover the right content more easily with new Data Refreshed and Modified Date columns in Power BI Home. By bringing the freshness signals already familiar from workspace list views into Home, users can more easily spot recently updated reports and semantic models, distinguish between similar items, and quickly find the content that matters most. Whether you're checking for the latest business updates or deciding which refreshed report to open, you can navigate with greater confidence and less guesswork.
Figure: Power BI Home showing two new columns for Data refreshed and Modified date.
Customize your Home list view
Not every user, team, or organization relies on the same signals to discover content. With Column Options, you can show or hide metadata, drag and reorder columns to prioritize the information you use most, and reset to the default view at any time. Whether you rely on freshness signals, endorsements, sensitivity labels, or location information, you can tailor Home to match your workflow.
Figure: Power BI Home showing new column options dropdown.
To learn more, refer to the Power BI Home documentation.
Set and reset column widths in table and matrix (Generally Available)
You can now right-click a column header in a table or matrix and select Set column width to specify its width in pixels. This option helps report viewers improve readability and fit the information they need within the available space, without changing the report author’s design or affecting other viewers. Changes made by viewers last only for the current viewing session. To restore the width defined by the report author, right-click the column header and select Reset column width.
Figure: Set or reset the width of an individual table or matrix column from its context menu.
To learn more, refer to the Adjust column width in Power BI tables documentation.
Visual calculations for small multiples (Generally Available)
You can now use visual calculations in visuals with small multiples. Create calculations such as moving averages and compare trends across categories without adding separate measures to the semantic model. In the visual matrix, the field in the small multiples field well appears on the ROWPAGES axis. You can select ROWPAGES by itself or combine them with ROWS and COLUMNS to control how the calculation moves through the visual.
Figure: Create a moving average visual calculation for a line chart divided into small multiples by country.
To learn more, refer to the Visual calculations overview documentation.
Design ribbon for Power BI reports (Generally Available)
The new Design ribbon brings report styling tools together in one location. Apply a built-in or organizational theme, open the Theme pane to customize report-wide defaults, or import and download theme files directly from the ribbon. You can also quickly open Page size, Page background, and Wallpaper settings for the current page.
Figure: The Design ribbon provides theme controls and shortcuts to page formatting settings in Power BI Desktop.
Two new built-in themes, Dark and Soft dark, use the new Versa color palette and styling that closely follows the Fluent 2 base theme. These themes let you design against a dark report canvas and return to the default light theme before publishing if needed.
Figure: Apply the Dark built-in theme from the Themes gallery on the Design ribbon.
To learn more, refer to the Use the Design ribbon in Power BI documentation.
Slider color options for Slicer visual (Generally Available)
Match your slicer's slider to your report design. The Slicer visual's Between, Before, After, and Date picker settings include a Slider format section where you can turn the slider on or off, set the handle style, and choose colors for the handles, selected range, and track.
Handle options adjust based on the Responsive layout toggle (General > Properties > Advanced options). When Responsive is on, handles appear as circles with Fill color, Border, and Size.
Figure: Slider formatting options for a date range slicer with Responsive layout turned on.
When Responsive is off, handles appear as rectangular bars with Border, Width, and Height.
Figure: Slider formatting options for a date range slicer with Responsive layout turned off.
To learn more, refer to the Slicer visual in Power BI documentation.
Translytical task flows show user date function (UDF) information in button action (Generally Available)
The formatting pane now displays the Workspace, Function set, and Data function assigned to a data function button. These read-only details help you confirm that the button references the intended function without reopening the OneLake catalog. This information is especially useful when you review or troubleshoot reports that use several functions or connect to functions across multiple workspaces.
Figure: View the workspace, function set, and data function assigned to a button in the formatting pane.
To learn how to configure data function buttons, refer to Create a data function button in Power BI.
Format pane headers stay visible as you scroll (Generally Available)
Expanded section headers now remain visible at the top of the Format visual pane as you scroll through their settings. This update helps you keep track of the section you’re editing, especially when a section contains many formatting options. For example, when you scroll through color settings, the Colors and Data colors headers remain visible for context.
Figure: Expanded section headers remain visible while you scroll through formatting settings.
To learn more about formatting visuals, refer to Get started formatting report visualizations.
Pick the axis initial scroll position (Generally Available)
Categorical axes—like month, year, or product name—show a scrollbar when there are more categories than fit in the visual. Until now, the scrollbar always started at the beginning of the data, so the oldest values displayed first. This month, you can set Initial scroll position to End on the axis Layout section, and the visual loads with the most recent data in view. Users can still scroll back to see earlier history. The option is available on stacked, clustered, and 100% stacked bar and column charts; line, area, stacked area, and 100% stacked area charts; line and stacked column and line and clustered column charts; ribbon, waterfall, and scatter charts with a categorical X-axis.
Figure: Line chart withInitial scroll positionset toEndon the X-axis. The scrollbar is positioned on the right, showing the most recent months first.
To learn more, refer to the Customize x-axis and y-axis properties documentation.
Azure Maps geocoding improvements (Generally Available)
Large reference layers now render correctly when you filter your report. Reference layers add geographic context using points, lines, and polygons, such as locations, routes, postal codes, sales territories, and administrative regions. The Azure Maps visual renders up to 30,000 reference-layer features at a time. Previously, when a reference layer exceeded this limit, features excluded from the initial view could remain missing even after a report filter narrowed the data to a smaller area.
Figure: Azure Maps visual displaying an all-up view of a US ZIP Code reference layer containing more than 30,000 polygons. Some ZIP Code boundaries are not displayed because the reference layer exceeds the rendering limit.
Figure: Azure Maps visual showing the previous behavior after the report is filtered to Washington. Only ZIP Code polygons included in the initial feature set are displayed, resulting in an incomplete view of the state.
Figure: Azure Maps visual showing the new behavior after the report is filtered to Washington. The full reference layer is re-evaluated, displaying all relevant ZIP Code boundaries for the state.
Now, Azure Maps re-evaluates the reference-layer features whenever report filters are applied. The unfiltered view is still limited to 30,000 features, but a filtered view accurately displays the relevant features, up to that limit.
On-object interaction improvements (Preview)
Based on your feedback during preview, we're introducing the first in a series of on-object interaction improvements, designed to make quick edits to your visuals easier. This month we're refining how you add data and manage some visual elements.
The Build flyout now opens only when you select Add data, helping you stay focused when dragging and dropping data directly onto a visual or into the Build pane.
We’ve also separated Title and Subtitle in the Add to your visual flyout, so you can manage them independently. In addition, title and subtitle are now turned off by default for matrix, table, and card visuals in reports that use the latest base theme. New reports automatically use the latest base theme. For existing reports, select Update theme in the Theme pane to apply this change. You can turn either element back on when needed.
Figure: On the left, select Add data to open the Build flyout. On the right, manage Title and Subtitle independently from the Add to your visual menu.
To learn more, refer to the using on-object interaction with visuals and updating to the latest base theme documentation.
Support for Fabric Apps in Org apps (Coming Soon)
Soon, users will be able to include generative Fabric Apps alongside the reports, dashboards, notebooks, and other content in your Org Apps.
For example, imagine you want people to rate the content in an Org App and share feedback about what would make it more useful. You can create a Fabric App for that experience and add it directly to the Org App.
Figure: Adding a Fabric App item for rating an experience into an Org App and then viewing that rating experience from within the Org App.
Whether you’re helping people explore what could happen next, act on an insight, or complete a specialized workflow, Fabric Apps give you a flexible new way to build for your audience without sending them somewhere else. Together, organizational apps and Fabric Apps provide a way to bring enterprise reporting, content, and tailored experiences together for your organization.
Learn more about org apps and item types supported, including Fabric Apps.
Changes to Power BI subscription email delivery
Power BI is updating the platform used to deliver subscription emails as part of ongoing improvements to delivery reliability and long-term service health.
As eligible subscriptions move to the updated platform, customers may notice changes to the sender identity and email formatting. Each subscription transfers automatically when it moves. Customers do not need to recreate it or change its schedule or recipients.
Figure: After selecting Subscribe for an item, an information icon identifies a subscription that has moved to the updated email delivery platform.
Learn more about changes to Power BI subscription emails.
Increased Export to Excel row limits (Coming Soon)
Many users export Power BI data to Excel for further analysis. This month, we're increasing the maximum number of rows that can be exported from table visuals using Data with current layout from 150,000 to 500,000. This increase helps you analyze larger datasets in Excel with fewer export operations.
Figure: Export data from a table visual to Excel using Data with current layout, supporting up to 500,000 rows.
To learn more about exporting data from Power BI visuals, refer to Export data from a Power BI visualization.
Value selection in Narrative visual
We are replacing the Q&A natural language experience for creating dynamic values in the Narrative visual and text box with a more deterministic UI. This is due to the ongoing deprecation of the Q&A tool, and also based on feedback that it was hard to deterministically pick exact values through the Q&A experience.
Authors can now create and edit custom values through a direct, deterministic UI: select a column or measure, apply any valid summarization, and add any type of filter.
Auto-generated values are unchanged, and values previously authored with Q&A remain available as read-only.
Figure: The new value selection options in the Narrative visual.
To learn more, refer to the Create Smart Narrative documentation.
Modeling
Create and edit DirectQuery semantic models in the Power BI service
DirectQuery semantic models can now be created and edited directly in the Power BI service, eliminating the need to download and use Power BI Desktop.
Previously, building models that query data sources in real time meant downloading Desktop, authoring the model, and publishing it to the web. Now, web-based modeling gives your team the freedom to:
- Work from any device: Mac, Linux and Windows users can now author DirectQuery models straight from the browser.
- Collaborate in real time: Multiple team members can work on the same semantic model simultaneously.
- Ditch the desktop loop: Skip the download-edit-republish cycle and update your models instantly in the service.
Capabilities on the web
Start from scratch: Connect to a supported data source and choose DirectQuery mode.
Figure: Power Query interface displaying data source connection settings, with DirectQuery selected as the data connectivity mode.
Full modeling control: Open existing DirectQuery models to manage relationships, write DAX and tweak table/column properties.
Figure: Model View in Power BI Service showing tables, relationships, and the properties panel for editing a DirectQuery semantic model.
Flexible storage modes: Easily switch table storage modes from DirectQuery to Import or Dual if needed.
Figure: Properties pane that allows user to switch table storage modes from DirectQuery to Import or Dual.
Thanks to this new capability, composite models are also available on the web! Head to the Power BI service and open one of your DirectQuery semantic models or create a brand-new one. We'd love to hear what you think!
Learn more in the DirectQuery documentation.
Approximate Distinct Count comes to Import and Direct Lake (Preview)
Distinct count is one of the most resource-intensive operations in any analytical engine. As data cardinality grows, so do CPU and memory usage, often slowing down your interactive reports.
APPROXIMATEDISTINCTCOUNT already offered a faster alternative for DirectQuery sources such as Azure SQL, Synapse, BigQuery, Databricks, and Snowflake. This month we're extending support to Import, Direct Lake on OneLake, and Direct Lake on SQL semantic models.
DAX = APPROXIMATEDISTINCTCOUNT(<columnName>)
Figure: Model View in Power BI Service showing tables, relationships, and the properties panel for editing a DirectQuery semantic model.
How it works and when to use it
Instead of scanning every single unique value, APPROXIMATEDISTINCTCOUNT calculates a highly accurate estimate of unique values with a standard error rate of ~1.6%. In return, you get faster query execution times.
- Best for high-cardinality columns: Use it on columns with millions of unique values (such as transaction IDs, user IDs, or timestamps) where an approximate result can reduce the resources required to calculate distinct values.
- Keep standard DISTINCTCOUNT for low-cardinality data: Stick to exact counts for smaller attributes like Country, Category, or Status, where standard calculation is already fast, or for financial metrics where absolute precision is required.
Swap APPROXIMATEDISTINCTCOUNT into your heaviest measures today and let us know how much speed you gain on your models!
Learn more in the APPROXIMATEDISTINCTCOUNT documentation.
Accelerate text searches in your semantic models with String Indexing (Preview)
String Indexing for Power BI semantic models is coming soon! If your reports rely heavily on text fields, such as product names, customer comments, or long descriptions, you’ve likely faced slow performance when users search or filter on large semantic models. String Indexing is designed to improve text-search performance in supported semantic models.
Why String Indexing?
Common text operations like DAX functions (SEARCH(), CONTAINSSTRING()) and advanced text slicers in reports traditionally scan data row-by-row. As datasets grow, these scans slow down query times.
String Indexing builds specialized indexes so the engine can locate matching text more efficiently, which can improve report responsiveness for both Import and Direct Lake semantic models.
Indexing modes
You can configure String Indexing via model metadata to fit your workload needs:
- Auto Mode: Automatically builds the index on the first query execution for a qualifying column. The index does not persist in storage; it remains in memory only while the column is loaded and will be rebuilt on subsequent queries if evicted. Ideal for smaller models.
- Full Mode: Builds and persists the index during scheduled data refreshes. While refresh times and model size may slightly increase, users enjoy consistently fast query performance right out of the box.
Get started
String Indexing requires a semantic model running at 1707 compatibility level. During this initial preview phase, indexing can be configured through TMDL on the web or XMLA metadata. Desktop support and a dedicated UI experience within Power BI are planned for a future release to simplify setup.
Figure: Setting up the “stringIndexingbehavior” property to full in TMDL view in the web.
Check out the String Indexing documentation for setting up instructions, prerequisites, and guidance on choosing the right indexing mode for your models.
We look forward to seeing how this feature helps make text-heavy reporting experiences faster and more responsive!
Introducing Full-Text Search in Power BI Semantic Models (Preview)
Full-Text Indexing for Power BI semantic models is coming soon! While traditional string searches look for exact character matches, Full-Text Indexing enables a more intelligent search experience based on the meaning of words and natural language concepts. This capability powers two new DAX functions, TEXTCONTAINS() and TEXTSIMILARITY(), making it easier than ever to analyze large volumes of textual data directly in your semantic models.
Why Full-Text Indexing?
Business data increasingly contains rich text content such as customer feedback, support tickets, product descriptions, incident summaries, and knowledge articles. Searching this data using traditional string matching often requires exact matches and can miss relevant results due to differences in spelling, word forms, or phrasing.
Full-Text Indexing builds a specialized search index at the column level, allowing semantic models to understand words rather than just character sequences. This enables advanced search experiences such as:
- Finding related words through linguistic analysis (for example, run, running, and runs)
- Matching singular and plural variations automatically
- Ignoring common stop words such as "the" or "and"
- Supporting phrase-based searches
- Tolerating minor spelling mistakes through fuzzy matching
- Enabling semantic similarity search scenarios
Getting Started
FTS Indexing requires a semantic model running at 1708 compatibility level. During this initial preview phase, indexing can be configured through TMDL on the web or XMLA metadata. Desktop support and a dedicated UI experience within Power BI are planned for a future release to simplify setup.
Figure: Setting up the “fullTextIndexingbehavior” property to full in TMDL view in the web.
New DAX functions
Full-Text Indexing is required for two new DAX functions:
- TEXTCONTAINS()
- Returns TRUE when a text value matches a search expression using full-text search semantics rather than simple substring matching. It supports multiple search modes, including keyword matching, phrase matching, and fuzzy matching for typo tolerance
- TextContains(<WithinTextColumn>, <SearchText>, [MatchMode])
- Example: "Show me all reviews that mention spa." The review either matches or it doesn't.
Figure: Example of the new TEXTCONTAINS() DAX function in DAX query view.
- TEXTSIMILARITY()
- Returns a relevance score indicating how well the text in <WithinTextColumn> matches <SearchText>. It enables similarity-based text comparisons, helping identify records that are semantically related even when they do not contain the exact same words.
- TextSimilarity(<WithinTextColumn>, <SearchText> [, <MatchMode>])
- Example: "Show me the 10 reviews most relevant to 'good breakfast'." Reviews mentioning both terms prominently rank higher than reviews that only partially match.
Figure: Example of the new TEXTSIMILARITY() DAX function in DAX query view.
Learn more about these two new DAX functions (TEXTCONTAINS, TEXTSIMILARITY) in our documentation.
Full-Text Indexing is supported for both Import and Direct Lake models, with Full mode recommended (during Preview) for the best out-of-the-box performance and user experience.
Refer to the Full Text Indexing documentation to learn more about prerequisites, configuration options, and setup instructions.
Data connectivity
New Power Query editor (Preview)
Since May of this year, the modern Get Data experience has been available in preview inside Power BI Desktop; the feedback we've gathered from that rollout has directly shaped what comes next. Your reports of friction points, missing capabilities, and rough edges between the legacy and modern interfaces went straight into the backlog, and this month that work pays off: the full modern Power Query Editor experience moves into preview.
Figure: Screenshot of the new Power Query editor using the light theme.
It's the same trusted engine, wrapped in a completely refreshed editing surface — and we're still closing the remaining gaps with the legacy UI as we go.
Let's explore six key reasons to enable and try this feature.
- Modern Get Data - The same connector browsing and search experience you already know from Fabric Dataflow Gen2 — now in Desktop. Searchable, categorized, and designed to make connectors easier to find and navigate than the legacy dialog.
- Try it: Connect to a new data source and browse the OneLake catalog.
Figure: Screenshot of the Modern Power Query Get Data experience inside of Power BI Desktop.
To learn more, refer to the Data sources in Power BI Desktop documentation.
-
Dark theme, end to end - No more jarring light-mode panes breaking your flow. The legacy editor only partially supported dark theme. The modern editor applies it consistently across the preview grid, dialogs, and other parts of the editing surface.
Figure: Screenshot of the Power Query editor using the Power BI dark theme.
- Folding visibility - Stop guessing whether your query folds. Step folding indicators mark each step as folding or not, and the new query plan shows exactly how the engine intends to evaluate your query — and where folding breaks down.
- Try it: Open the query plan on a query with several steps and find where folding stops.
Figure: Screenshot of the Query Plan dialog inside of the new Power Query editor.
To learn more, refer to the Understanding Query Evaluation and Query Folding in Power Query documentation.
- Diagram view - See how your queries relate to each other visually, instead of reverse-engineering it from names. A gamechanger for files you've inherited or models with long reference/merge chains.
- Try it: Open a file with referenced queries and trace a merge visually.
Figure: Screenshot of the Diagram View inside of the new Power Query editor experience.
To learn more, refer to the Diagram view documentation.
- New capabilities, now on Desktop - Features that used to live only on the web are now here: rank column, cluster values, schema view, query script view, plus upgrades to transforms you already use daily.
- Try it: Add a rank column or cluster values on a messy text column.
Figure: Screenshot of the Schema view available in the new Power Query editor.
To learn more, refer to the Rank column and Use Schema View documentation.
- Export a Power Query template - Capture your solution at a point in time and take it with you. Export a template from Desktop and import it straight into a Dataflow Gen2 — queries, steps, and structure intact.
- Try it: Export a template from a multi-query file and import it into a Dataflow Gen2 to compare.
Figure: Screenshot of the Export template experience in the Power Query editor.
To learn more, refer to the Power Query template documentation.
Ready to try it?
Enabling the modern Power Query experience takes just a few seconds — no restart required:
- Open Power BI Desktop.
- Locate: File > Options and settings > Options.
- Under Preview features, check New Power Query experience.
- Open (or reopen) the Power Query Editor — you're now in the modern experience.
Once you've had a chance to explore this new user interface and its experiences, we want to hear from you.
Share your thoughts on the new Power Query experience in the Fabric Community — what's working, what's missing, and what would make it a compelling alternative from the legacy editor. Every comment helps shape what ships next.
Microsoft Outlook Mail connector (Preview)
We're introducing the new Microsoft Outlook Mail connector (Preview) for Power BI Desktop. Built on the Microsoft Graph API, it lets you read your mailbox data — folders, messages, and attachments — using an organizational account. This is the first in a set of new connectors we'll be releasing as a modern alternative to the Exchange Online connector.
The initial preview is scoped to Mail in Power BI Desktop. Additional connectors for Calendar Events, Contacts, and Tasks are on the roadmap, along with Excel and Power BI service / Fabric Dataflows Gen2 support.
Scheduled refresh isn't supported yet — this applies to both the Power BI service and refreshes routed through the on-premises data gateway.
To try it, enable the Microsoft Outlook Mail preview feature under Options in Power BI Desktop, then open Get Data → Online Services → Microsoft Outlook Mail and sign in with your organizational account.
Figure: Microsoft Outlook Mail connector with the Preview badge in the Power BI Desktop Get Data experience.
Figure: Microsoft Outlook Mail listed among Online Services in the Power BI Desktop Get Data pane.
To learn more, refer to the Microsoft Outlook Mail connector documentation.
More flexible Data Privacy Firewall query patterns in Power BI Desktop (Preview)
Power BI Desktop now allows Data Privacy Firewall partitions that reference other partitions also access data sources when the privacy levels of the involved data sources are compatible. Introduced in the July 2026 release and enabled by default, this preview setting aligns Power BI Desktop with Power Query Online, gateways, and the Power BI service.
This change supports common query patterns in which one query returns a value that another query uses to build a web request, SQL statement, file path, or other data source request. These patterns can now run without refactoring queries or duplicating logic solely to satisfy the previous partition restriction.
The Data Privacy Firewall remains active. Power Query continues to evaluate the privacy levels of the involved data sources before combining data, helping authors use more flexible query designs while preserving privacy protections.
Figure: The new Power BI Desktop preview setting allows compatible cross-partition query patterns while the Data Privacy Firewall remains active.
To learn more, refer to the Allow data privacy firewall partitions that reference other partitions to also access data sources documentation.
Mobile
Mobile page indicator (Generally Available)
Know immediately which report pages are mobile-ready, without clicking through them. Each page that has a mobile layout shows an icon on its page tab in the footer, so you can spot your mobile coverage instantly. Pages without a mobile layout stay unmarked, making it easy to see what's left to optimize.
The icon is coming soon to both Power BI Desktop and the Power BI service. In Power BI Desktop, it appears in both desktop layout view and mobile layout view, so you can track mobile coverage right where you work. In the Power BI service, it appears in mobile layout view.
Figure: Page tabs marked with an icon to show which pages have a mobile layout.
To learn how to build mobile-optimized reports, refer to the Mobile-optimized Power BI reports overview documentation.
Contact details in Info drawer (Generally Available)
We’re making it easier to connect with the right people from the Power BI Mobile app. You can now find contact details in the Info drawer for reports, apps, and dashboards, and email the relevant contact directly from your phone.
Figure: Two Power BI Mobile screens showing the Contoso Sales workspace and the report’s Info drawer with a clickable contact name for sending an email.
To learn more about Power BI in mobile, refer to the What Are the Power BI Mobile Apps? documentation.
Developers and APIs
Power BI Projects (PBIP) (Generally Available)
Since entering preview in 2023, PBIP has changed how developers build and manage Power BI content. It stores report and semantic model definitions as human-readable text files, turning a Power BI solution into a codebase.
Developers can search these files, track changes in Git, review diffs in pull requests, automate updates with scripts and pipelines, and use AI agents to work with models and reports. Changes remain visible and reversible, which makes team development easier and safer.
Recent improvements have made the workflow more practical. These include opening a project directly in Visual Studio Code and detecting external file changes in Power BI Desktop.
Figure: Open Visual Studio Code entry point in Power BI Desktop.
New underlying formats capabilities:
- Tabular Model Definition Language (TMDL) for semantic models.
- Power BI Enhanced Report Format (PBIR) for reports. PBIR is now the default report format for PBIX and PBIP files. New reports use it from the start. When you edit a report that uses the legacy format, Power BI tools automatically convert it to PBIR.
To learn more, refer to the Power BI Projects documentation.
New Purge Data option for Fabric APIs
The new Purge Data option for Fabric APIs gives developers and administrators greater control over programmatic semantic model deployments. This capability allows users to explicitly approve deployments that may require removing existing data, helping unblock scenarios such as schema or data type changes that previously failed validation checks.
Designed with both safety and automation in mind, purgeData keeps data protection safeguards enabled by default while giving developers the flexibility they need to manage complex deployment scenarios at scale.
To learn more, refer to the Purge Data documentation.
Other
Data updated and sensitivity fields of Power BI report in Microsoft Teams preview card (Coming Soon)
Power BI report previews in Microsoft Teams will soon surface the report's last refresh date and sensitivity label. These additional signals will help users quickly assess the freshness, relevance, and classification of a report before opening it.
Figure: Power BI report preview card in Microsoft Teams chat showing report metadata, including the last refresh date and sensitivity label.
To learn how Power BI content is displayed in Microsoft Teams, refer to the Link preview cards in Microsoft Teams chats and channels documentation.
Artifact info header for Power BI tabs in Microsoft Teams (Generally Available)
Power BI content in Microsoft Teams tabs now includes the artifact info header, giving users the context they need without leaving their flow of work. Available for reports, apps, organizational apps, dashboards, and scorecards, the header brings key artifact information and actions together in one place.
The new header displays the artifact name and sensitivity label and provides an entry point to artifact metadata. You can open the artifact in the Power BI personal app in Teams, open it in a browser, and refresh the tab.
Tab owners can control their experience with the new Show info header setting on the tab settings page. The setting is 'on’ by default and can be turned off when a more compact tab experience is preferred.
Figure: Power BI report in a Microsoft Teams tab with the artifact header open, displaying report metadata.
Figure: Power BI report in a Microsoft Teams tab, with the setting dialog open.
To learn how to add Power BI content as a tab in Microsoft Teams, refer to the Embed Power BI reports in Microsoft Teams documentation.
Third-party custom visuals
graphomate matrix
The graphomate chartrix is a brand-new charting visual, and it offers various improvements over graphomate charts. First and probably most obvious is the new interactive user interface which enables users to define most elements of the chart layout directly on the visual. To keep this interface effective and uncluttered it focuses on the most important parameters of your chart.
Users can now create combination charts which were simply not possible before. There are also new chart types like the variance waterfall, which automatically renders from one measure and two dimensions. Of course, the graphomate chartrix is IBCS® certified. With the latest release an XFL editor has been introduced, which helps you write scripts to format the chartrix far beyond the possibilities of the regular option set. XFL scripts also provide a way to conditionally format the visualization, dynamically changing properties in relation to the actual data.
This new visual is provided free of charge to existing customers of the graphomate charts. All development efforts will be focused on making the graphomate chartrix the best IBCS® charting visual there is.
- Video Link: graphomate chartrix for Microsoft Power BI
- AppSource Link: graphomate chartrix
- Sample Report Link
Drill Down Bubble PRO by ZoomCharts
Drill Down Bubble PRO is a Power BI visual designed for exploring relationships, trends, and outliers across multiple dimensions of data. It adds richer exploration, selection, and analytical capabilities directly inside the visual.
Key features include:
- Multi-level drill down to explore data hierarchies from a high-level overview to detailed insights.
- Pan and zoom controls to navigate dense datasets and focus on specific clusters or individual data points.
- Area and lasso selection to quickly isolate groups of bubbles and use selections for interactive analysis and filtering.
- Dynamic regression lines that recalculate as the displayed data changes, making trends and relationships easier to identify.
- Line and area thresholds to highlight targets, ranges, exceptions, or other important business benchmarks.
- Area shading to visually group and compare selected segments of data.
- 200+ formatting settings to tailor the chart to different reporting and branding needs.
Figure: Drill Down Bubble PRO demonstrates multi-level drill down, panning, and zoom controls for exploring data from high-level patterns to detailed points.
These capabilities make Drill Down Bubble PRO especially useful for customer segmentation, sales analysis, portfolio analysis, performance monitoring, and other scenarios where users need to actively explore patterns rather than simply display them.
Commenting in view mode: introducing Zebra BI Tables+ & Charts+
It's month-end. A regional manager opens the report, spots a variance in their region, and knows exactly why it happened. But the report isn't theirs to edit, so the explanation ends up where it always does: a screenshot pasted into PowerPoint, emailed around, detached from the number that prompted it.
That's the collaboration gap. Your report shows what happened; the why and the what next leave the report and get lost.
Meet Zebra BI Tables+ and Charts+: two new visuals that keep everything existing Zebra BI Tables and Charts offer and add a built-in collaboration layer. Report viewers can add comments directly on a data point, in view mode, with no Power BI edit access. Each comment is anchored to the exact figure and stored in your own SharePoint file. Zebra BI stores nothing.
Figure: Zebra BI Tables+ and Charts+ enable report viewers to add contextual comments to individual data points, attach supporting files from SharePoint, and collaborate directly in view mode.
So instead of screenshotting insights into PowerPoint or maintaining a custom workaround, the whole team explains and decides right on the report. Instead of slides or emails, the next steps can be defined directly on the spot.
Stop losing good decisions to a missing context. Start making them on the report. Try Zebra BI Tables+ and Charts+ free for 14 days on AppSource.
Network Graph by Powerviz
The Powerviz Network Graph is a visual representation of Nodes and the relationships or connections between them. Its primary purpose is to illustrate how different entities are related or interact with one another.
Key Features
- Line Options: Customise node links with different styles and colors.
- Node Shape: Choose from various shapes, icons, or upload your own.
- Labels: Display categories, values, and percentage labels.
- Data Colors: Access 30+ color palettes, including color-blind-safe options.
- Fill Patterns: Highlight nodes with patterns or upload your own.
- Conditional Formatting: Highlight outliers based on measures or category rules.
- Clusters: Group related nodes to reveal patterns.
- Relationships: Analyze node connections at a glance.
- Animation: Add pop-ups and highlight effects.
- Import/Export: Save and reuse themes easily.
- Toolbars: Gain advanced control over the graph.
Other features included are Sorting, Ranking, Lasso / Reverse Lasso, Grid View and more.
Business Use Cases
Customer Relationship Management (CRM), Supply Chain Optimization, Social Network Analysis (SNA).
Figure: Customize every connection, cluster, and node to build a Network Graph that truly fits your data.
Figure: Go beyond connections with powerful colors, patterns, labels, formatting, and interactive controls.
Resources
- Try Network Graph visual for FREE from AppSource
- Check out all features of the visual
- Step-by-step instructions
- YouTube Video
- Learn more about visuals
- Follow Powerviz on LinkedIn
Hierarchical Bar Chart
New, exciting changes were made to Hierarchical Bar Chart.
- Bubble Matrix for stacks - The visual now provides the option to show stacks as bubbles below the bars.
Figure: Hierarchical Bar Chart transforms stacked period values into bar-and-bubble matrix layouts for clearer comparison of category totals and component contributions.
- Display Stacks as Clustered Columns - From the format pane settings, you can choose to display stacks as clustered column chart.
Figure: Hierarchical Bar Chart displayed as clustered columns, with period targets and variance indicators configured from the Format visual pane.
- Filter using legends - You can click on a stack legend to filter out other stacks. On mouse hover relevant stack gets highlighted.
- Stack ribbons and %age of total - You can now choose to connect stacks with ribbon and show percentage of total for each stack.
Resources
- Check out the Hierarchical Bar Chart Update YouTube video.
- Download the visual from APPSOURCE
- Download a sample pbix file
- For more information refer to Hierarchical Bar Chart or contact us.
That’s a wrap!
The European Microsoft Fabric + SQL Community Conference is just getting started, and there's never been a more exciting time to be part of the Power BI community. We hope these updates help you discover new capabilities, streamline your workflows, and get even more value from your data. Be sure to explore the links throughout this post for deeper technical guidance and follow along with the latest announcements and sessions from Barcelona.
Thursday 15th October 2026, 9.06pm
- PowerBI:
Databricks ADBC connector for Power BI and Microsoft Fabric (Generally Available)This release is part of the broader ODBC-to-ADBC transition for Power Query connectors described in the Transition from ODBC to ADBC drivers in Power BI and Microsoft Fabric documentation.
What’s new
Existing connections in your semantic models, dataflows, and paginated reports continue to work unchanged — the migration path is currently opt-in per connection, per workspace, or per tenant.
Highlights:
- Improved security - ADBC drivers incorporate security enhancements, such as memory safety and garbage collection.
- No changes to existing behavior - This transition moves away from the embedded ODBC drivers that ship with Power BI. It does not change behavior for the ODBC connector when you use a separately installed ODBC driver.
- Efficient large dataset support - ADBC provides a set of standard interfaces for interacting with Arrow data, which is especially efficient at fetching large datasets with minimal overhead and no serialization or copying.
- Supported authentication - Databricks ADBC supports OAuth (user), OAuth (M2M / Client Credentials), and Microsoft Entra ID.
Connectors covered by this release
Connector Previous driver New driver (GA) Databricks Simba Spark ODBC Databricks ADBC Azure Databricks Simba Spark ODBC Databricks ADBC How to try it
You can test the ADBC driver now. We suggest you start soon to help ensure the eventual deprecation of ODBC and migration to ADBC runs smoothly. There are three ways to begin validating ADBC, ordered by how much control you want.
1. Opt in per connection using Implementation="2.0"
The fastest way to compare ADBC and ODBC for a specific report or dataset. Add the
Implementation="2.0"option to the source step in your Power Query expression:Source = Databricks.Catalogs("adb-1234567890.1.azuredatabricks.net", "/sql/1.0/warehouses/<warehouse-id>", [Implementation="2.0"])Refresh the dataset and compare row counts, column types, and totals against your production baseline. If you want to force a side-by-side comparison against ODBC, use
Implementation="1.0".2. Override the default for a validation workspace
If you want to validate several reports together, a workspace admin can turn ADBC on for a single workspace while the rest of the tenant continues to use the legacy driver. Publish the reports you want to test into that workspace and run your normal refresh schedule.
3. Enable ADBC by default at the tenant level
When you’re confident with the results, the tenant admin can enable Users can connect to data sources by using Apache Arrow database connectivity (ADBC) in the Admin portal. New connections across the tenant will use the ADBC driver by default, and Desktop and the service stay aligned on the same driver.
What to expect during validation
The ADBC driver is designed as a compatibility-preserving replacement for the Simba Spark ODBC driver. Validate your key reports in Desktop before enabling ADBC at the tenant level and report any regressions to adbcmigration@microsoft.com.
Explore Transition from ODBC to ADBC drivers in Power BI and Microsoft Fabric for more information.
What’s next
The Power BI service will move from ODBC to ADBC through the first quarter of 2027. We recommend that you start validating today, so the tenant-level move is a non-event when it lands.
We’d love your feedback
Try the new Databricks ADBC driver. If anything looks different from what you'd expect — a refresh that fails, a total that changed, a performance regression — send the tenant ID, connector, M expression, and what you observed to adbcmigration@microsoft.com.
Get started this week:
- Read the Databricks connector documentation.
- Install the latest Power BI Desktop.
- Pick one production report on Databricks and add
Implementation="2.0"to its source step. - Compare row counts, column data types, and key totals against your production baseline.
- Report anything unexpected to adbcmigration@microsoft.com.
Thursday 15th October 2026, 5.00pm
- PowerBI:
Power BI’s next chapter: The evolution of business intelligenceIf you haven't already, check out FabCon and SQLCon 2026 in Barcelona: Building the data foundation for Microsoft Copilot and Agents for a complete look at all of our FabCon Europe announcements across Fabric and Microsoft Databases.
More than a decade ago, I watched Power BI change the way users work, analyze and take action on their data. Since then, I have had the privilege of seeing it grow alongside our customers—from a tool for building reports into a platform used by millions of people to understand their businesses and make decisions every day. Now, Power BI is entering its next chapter.
Introducing the next generation of report development
We’re introducing a new app building experience in Power BI Desktop, powered by apps in Fabric, that enables users to create data applications using natural language. Starting from a trusted semantic model, users can generate, preview, edit, and publish purpose-built applications to Microsoft Fabric. These applications can accept inputs, write back data, preserve shared state, and support operational workflows, helping users move from insight to action. This experience will be available for Power BI Desktop users in the coming months.
Importantly, this experience isn’t limited to Microsoft Fabric capacity customers. Apps in Power BI will be available in preview to Power BI Pro and Premium Per User customers, as well as Microsoft Fabric capacity customers. Pro and Premium Per User customers will also have access to Fabric Database capabilities, enabling them to build applications that support both analytical and transactional scenarios. This brings AI-assisted app creation to Power BI users through their existing licensing options.
Our community is already bringing some creative ideas to life. Explore some examples from Microsoft and the community in the Fabric apps gallery today.
Figure: Creating an app using natural language in Power BI Desktop.
Figure: A community created app by Jon Sandman that shows football statistics and match replays for coaches.
Expanding the semantic layer
The semantic layer is an organization's most strategic asset. More than 22 million Power BI semantic models are in use every day, making Power BI the world’s most widely adopted semantic layer. Increasingly, it also grounds agents, applications, and Microsoft Copilot in that same business meaning.
At FabCon Barcelona, we are sharing an early look at semantic views, allowing users to define governed business metrics and semantics directly where data lives in OneLake and reuse them across and beyond Fabric. Our goal is to bring semantics closer to where the data lives while making it open, reusable, and interoperable.
We are also pleased to affirm our commitment to Apache Ossie (incubating), a community-led effort to establish a vendor-neutral standard for exchanging semantic metadata across analytics, AI, and BI platforms. Working with Snowflake and the broader industry, we’re helping customers define semantic context once and reuse it across ecosystems without duplicating data or business logic. Our collaboration with Snowflake currently focuses on cross-platform semantic-layer conversion. Looking ahead, we’re committed to advancing Apache Ossie through our deep semantic-modeling expertise, establishing DAX as an Ossie-recognized query language and expanding support for ontologies, enabling platform-agnostic operational intelligence.
Figure: Semantic views provide governed business context across analytics, applications, and AI experiences.
Bringing semantic models into M365 Copilot
Fabric IQ in Microsoft Copilot Cowork and Microsoft Copilot Chat are now generally available. Users can ask business questions in Copilot Chat and receive trusted answers grounded in governed Power BI reports and semantic models, with Copilot inferring which report or model is right for the question. In Cowork, Power BI content participates directly in long running and asynchronous tasks.
The same Microsoft Copilot experience is also coming directly to Copilot in Power BI, allowing you to use your M365 data for richer responses. Fabric IQ MCP is entering general availability, so creators can use the same conversational analytics in their own development environments and external MCP clients. You can read more details about this update in our Fabric IQ in Microsoft 365 Copilot Cowork documentation.
Looking ahead
Power BI’s evolution has always been shaped by the community and the millions of creators, analysts, developers, and business users who build with it every day. Your ideas, feedback, and ingenuity have pushed us to make business intelligence more accessible, trusted, and connected to the decisions that matter. Thank you for building this community—and for continuing to challenge us to imagine what comes next.
You can catch all our announcements in detail in the Power BI September 2026 monthly roll-up blog. We invite you to help shape this next chapter—share your feedback with us, shape our roadmap, and meet us in person at Fabric Community Conference and Ignite!
Tuesday 29th September 2026, 6.30am