Every month the Power BI team ships a long list. Most of it is noise for a business team; a couple of items change how the report looks or how fast the model answers. October 2026 has both, and one of them — the native Gantt chart — was the most requested visual on the Power BI ideas forum for years.
This is the tour we would give a client: what is native now, what is still preview, and what to test before you roll it out on a real report.
The Gantt chart is finally native (preview)
Until now, a Gantt chart in Power BI meant a custom visual from AppSource, or a matrix with a wall of DAX behind it. Neither was something you wanted to hand off to a colleague.
October 2026 ships a core Gantt chart visual, in preview. It is built into Power BI Desktop and the service, so it renders with the rest of the report and does not depend on a third-party visual staying maintained.
What it does:
- Bars show task duration, with progress formatting and milestones on the same axis.
- The time axis is configurable — start and end dates, date/time format and axis units — so you can scope a project without a second date table hack.
- Bar colors cascade by category by default, so a status field (on track, at risk, blocked) drives the color instead of a manual rule each time.
- You can put extra columns next to the task list: owner, status, duration, percent complete.
- A zoom control focuses on a time window and returns to the full range without re-filtering the page.
The catch is that it is preview. To use it you turn it on in File > Options and settings > Options > Preview features and restart Desktop. If your reports are consumed through the service, preview visuals are fine to publish, but expect behavior to change before GA.
For project tracking specifically, this replaces an entire category of "we keep the real plan in Excel and paste a screenshot into the report" workarounds. The plan and the report can finally be the same object.
The list slicer grew a dropdown
The other visual change is smaller but shows up on almost every report: the list slicer now has a dropdown mode, in preview.
- It keeps the item formatting of the existing list slicer, so nothing looks foreign.
- "Show selected first" pins what the user already picked to the top of the list.
- Selections appear as pills outside the dropdown with a dismiss button, and a count pill handles the overflow once you select more than fits.
- The search box gets its own formatting controls — background, border, text styles.
- Clearing items after a "Select all" produces explicit
Not (item)pills, so the report states exactly what is excluded rather than leaving it to memory.
The pattern this fixes is a real one: a slicer with 40 customers eats a third of the canvas. A dropdown keeps the page for the chart, which is what the audience came for.
Chart and axis improvements that are already GA
Two reporting changes in October are generally available and need no preview toggle:
- Chart plot area background color — a single fill or conditional formatting, now supported on bar, column, line, area, combo, ribbon, waterfall and scatter charts. Conditional formatting here is genuinely useful: it lets a reference line or an out-of-range band be part of the chart, not an annotation someone has to maintain.
- Auto-expand hierarchy axis with field parameter support — bar, column and line charts now auto-expand a hierarchy axis the way slicers and matrices already did, and it respects field parameters. If you build a dynamic "choose the dimension" report, the axis finally behaves.
Neither one changes the model. Both change how much explaining the report needs.
What we would test this week
- Turn on preview features in a copy of Desktop, not the one you use daily. Preview visuals and preview toggles can affect file format behavior; keep the daily driver clean until you have published a test report.
- Take one real project schedule and rebuild it as a Gantt. Check the progress formatting against how your team actually reports percent complete — that is where most Gantt rollouts stall.
- Check the dropdown slicer against your long-value slicers. If a report page has three slicers with 30+ items each, that page is the benchmark for whether the dropdown pays off.
- Verify conditional plot area formatting on the charts you already ship. It is GA, so it is low risk, but re-check how the format holds in dark themes and in the mobile layout.
- Audit Desktop versions across the team. From October 2026, Power BI Desktop builds from March 2026 or earlier can no longer save to OneDrive and SharePoint. Anyone on an old build will find out at the worst possible moment.
Where this fits the bigger picture
A feature summary is easy to read and hard to act on. The filter we use is simple: does this reduce the number of manual steps between a business process and the report that measures it?
The Gantt chart does — it removes the custom visual and the Excel screenshot. The dropdown slicer does — it gives the canvas back to the chart. The plot area formatting does — the chart carries its own context.
That is the same principle behind the model work we do every week. If your reports still run on a pile of custom visuals and manual formatting because "Power BI cannot do it", part of that list just got shorter — see our Power BI consulting page.
Sources
- Power BI October 2026 Feature Summary — Microsoft Fabric Community
- Power BI Weekly Issue #377 (2 October 2026) — roundup of FabCon Europe 2026 and the September 2026 feature wave
- Announcements from the Microsoft Fabric Community Conference — Barcelona 2026 — James Serra