A native Gantt chart, a dropdown list slicer, custom visuals via Copilot, and a change to how models report capacity use. What to adopt, and what to wait for.
A small release with one big footnote
October's Power BI update is short. Three visual changes, one Copilot change, and a paragraph about semantic models that most people will scroll past. In keeping with how we read a Power BI release, here is what we would switch on, what we would leave in preview, and the one item we would read twice.
Adopt: the dropdown list slicer
The list slicer gains a dropdown mode in preview, with a show selected first option, selection pills, a count of what is selected, and a Not label when you clear items from a select all. That last one is the useful bit. A filter that reads Not Cancelled is clearer to a reader than a list of nineteen ticked statuses, and it removes the question we hear most from report users: what have I actually got selected here. The button slicer gets the same show selected first behaviour. Both are preview but low risk, since the worst case is a slicer that looks slightly different. We would turn it on for any report with more than a handful of filters.
Adopt: plot area background and hierarchy axes
Two general availability items that sound cosmetic and are not. Plot area background colour, with conditional formatting, lets you shade the target zone on a line chart or mark a period on a bar chart without a hack involving a second series. Auto expanding hierarchy axes now work with field parameters, which removes a reason we used to tell clients not to use field parameters on bar and column charts. Microsoft's own comments under the post say the plot area change slipped by a few weeks, so check your Desktop version before you promise it to anyone.
Wait: the Gantt chart
A native Gantt visual, in preview, plots tasks, progress and milestones on a time axis with zoom and extra columns. People have wanted this for years and have been using AppSource visuals to get it. Our advice is to wait one release. First previews of core visuals tend to be missing the formatting options that the AppSource equivalents have, and swapping a project team's visual twice in two months is worse than swapping it once. Build a test page, show the project office, and plan the move for when it is stable. The reason to move at all is governance: a core visual has no third party licence, no separate update cycle, and no question about where the data goes.
Adopt carefully: custom visuals through Copilot
The Report Authoring skill can now add, bind, format and validate custom visuals from a natural language request, including AppSource visuals, and it is generally available. It is a real time saver for people building reports with agents, which is now part of how we work, as our post on the Power BI agentic tooling explains. The discipline is the same as ever: an agent that can add an AppSource visual can add one your tenant has not approved. Keep the organisational visuals allow list tight and this is a productivity gain. Leave it open and it is a new way to sprawl.
Read twice: surge protection is now more accurate
The item that matters most is the one with no screenshot. Semantic models now report their capacity unit usage continuously during long running operations, such as refreshes, rather than in one lump at the end. Microsoft switched this on in August and published the effect for one region: proactive surge protection rejections rose from 5% to 12%, delayed but accepted operations rose from 11% to 16%, and late stage throttling rejections fell from 23% to 13%.
In plain terms, the capacity now sees a big refresh coming and acts earlier, rather than letting it run and then throttling everyone at the end. That is better behaviour, and it is also a change in what you will observe. If a refresh that used to complete now gets rejected or delayed by surge protection, nothing is broken; the system is doing what it was meant to do, earlier. The fix is the usual one: look at the refresh in the Capacity Metrics app, move it to a quieter window, and check whether the model is carrying measures and columns it does not need. With Fabric overage billing now charging three times the pay-as-you-go rate for excess use, as covered in our capacity guide, earlier rejection is also cheaper rejection.
What to do this month
Turn on the dropdown slicer preview for busy reports. Use plot area backgrounds once your Desktop has them. Put the Gantt chart on a test page and leave production alone. Review the custom visuals allow list before anyone points an agent at it. And if a scheduled refresh starts being delayed, read the surge protection paragraph before you raise a ticket. If you would like us to look at a report estate with this in mind, our Power BI team starts with a free audit.
Related reading
What is worth adopting from a Power BI release, and what to ignore
Why your Power BI report is slow, and the five things to fix first
What unused measures and columns are quietly costing you
Microsoft's new Power BI agentic tooling is less about AI and more about discipline
Maisie Hudson
Analytics Consultant
Part of the Hopton Analytics team, delivering governed analytics programmes for UK mid-market organisations.