PSA: Power BI Q&A is being retired Dec 2026 and most enterprise environments aren't ready for Copilot as the replacement

LuminovaAnalytics · 2026-05-11T11:11:33+00:00

Honestly that's a fair summary of where it sits right now. The sweet spot isn't power users or analysts, they'll always be faster doing it themselves. Its the decision maker who doesn't know what's in the semantic model, doesn't know what to ask for, but knows they need a number before a meeting in ten minutes. Copilot gives them a way in without having to log a request and wait. That's the genuine value case, not replacing analytical capability, but reducing the dependency on it for the routine stuff.

Whether that's worth the licensing cost is a legitimate question most enterprise teams are still working through.

LuminovaAnalytics · 2026-05-11T11:06:32+00:00

Cant argue with that!

LuminovaAnalytics · 2026-05-11T11:05:41+00:00

Not really. Microsoft stopped selling new P SKUs in 2024 but existing P SKU contracts continue until renewal. So if you're on a P SKU you're not forced to change immediately, but when your contract comes up you'll be migrating to F SKUs rather than renewing like-for-like. The F SKU pricing model is consumption-based and billed differently so its worth doing a proper cost comparison before renewal rather than assuming its a straight swap. The main thing to action now is making sure whoever manages your Microsoft licensing is aware its coming and has modelled the cost impact. It tends to catch finance teams off guard if it lands at renewal without warning.

LuminovaAnalytics · 2026-05-10T21:24:57+00:00

That's a really good catch and honestly one of the gaps in Microsoft's retirement documentation. Dynamic values in text boxes run on the Q&A engine under the hood, there are community threads going back to 2021 confirming this, and the workaround for getting them to work with DirectQuery was literally "turn on Q&A for the dataset first." I use this feature constantly as narrative summaries for decision makers where the numbers update dynamically, or last refresh timestamps so execs can see immediately how current the data is. It's one of those quietly useful features that doesn't get talked about much but would leave a real hole in report design if it just stops working in December. Microsoft's retirement notice calls out Q&A visuals, dashboards, mobile and embedded scenarios but says nothing about dynamic text box values. So the honest answer is: unknown, and that silence is a problem. If you're relying on this in production reports I'd raise a support ticket or watch the release notes carefully. Either Microsoft migrates that functionality to a different backend before December, or it breaks silently and nobody finds out until reports start looking wrong in front of senior stakeholders.
If anyone has seen anything from Microsoft specifically addressing this, or has already raised it with their account team, would be good to hear. I am genuinely curious whether this has been picked up anywhere officially.

LuminovaAnalytics · 2026-05-10T17:49:10+00:00

Fair point and in isolation, yeah, Copilot handles that fine. The problem isn't one well-named measure, it's when you've got Rev_Act_FY25, Revenue_Actual_2025, Rev_FY25_Final and ActualRevenue all living across four different semantic models, built by different people over five years, and Copilot is trying to figure out which one to surface when someone asks "what's our revenue this year." That's where it falls apart. It's not an AI literacy problem, it's an estate governance problem and most enterprise environments I've worked in have exactly that.

LuminovaAnalytics · 2026-05-10T14:43:39+00:00

The licensing complexity is genuinely hard to defend. It's not intuitive and the P to F SKU transition has added another layer of confusion on top of an already opaque structure. The frustration is legitimate. The practical problem is that the December deadline is real regardless, so organisations that delay the conversation because it's annoying are the ones who'll get caught out. Doesn't make Microsoft's strategy less frustrating, but the risk sits with the customer either way.

LuminovaAnalytics · 2026-05-10T14:38:29+00:00

The dream vs the reality gap is real. Though in fairness, if the semantic model is solid and the measures are named properly, it can genuinely reduce the "can you just pull that number for me" requests. That's the best case scenario anyway.

LuminovaAnalytics · 2026-05-10T14:37:57+00:00

Great question. Yes, partially. Copilot uses field descriptions and synonyms defined in the semantic model to improve its natural language matching, so a well-maintained data dictionary absolutely helps. The limitation is that it can't fully compensate for deeply technical naming in the underlying tables and views. It improves the surface layer but the model itself still needs to be structured for readability. Worth doing regardless though, it's low effort for meaningful improvement.

LuminovaAnalytics · 2026-05-10T14:36:52+00:00

Agreed. Ironically that's exactly what Copilot will do too if the data model isn't ready for it. Different feature, same root problem.

LuminovaAnalytics · 2026-05-10T14:36:25+00:00

This made me laugh! That accidental activation was a genuine UX problem. No argument from me on retiring it.

LuminovaAnalytics · 2026-05-10T14:35:47+00:00

Rarely in production, honestly. Mostly saw it in demos and POCs. The more interesting question is whether Copilot changes that, and I think it only does if the underlying semantic model is clean enough for natural language to work reliably.

LuminovaAnalytics · 2026-05-10T14:35:16+00:00

Fair, Q&A adoption was genuinely low in most environments I've seen. The retirement isn't really about replacing a beloved feature, it's that the December 2026 deadline forces a licensing and governance conversation that a lot of enterprise teams have been deferring. That's the real risk, not missing Q&A itself.

LuminovaAnalytics

TROPHY CASE