What the roadmap item describes
Microsoft AI at Work roadmap item 574113, titled “Dynamics 365 Contact Center: Historical analytics,” describes a move away from heavier, workload-specific Power BI models toward a shared analytics foundation. Its recorded description specifies aligned fact tables, shared dimensions, pre-built aggregations, and common definitions covering conversations, sessions, agents, queues, channels, customer satisfaction (CSAT), handle time, and operational KPIs.
The roadmap record also says customers can continue using the supplied Power BI reports, with extensibility through Microsoft Fabric, Direct Lake, SQL, Spark, and custom lakehouse models. That frames the update as a foundation-and-extensibility change—not a notice to replace every dashboard.
The item’s recorded rollout details identify:
- Products: Dynamics 365 Contact Center and Dynamics 365 Customer Service.
- Platform: Web.
- Status: Rolling out.
- Release ring: General Availability.
- Cloud: Worldwide, Standard Multi-Tenant.
- Estimated general availability: October 2026.
There is an important availability caveat. The accessible live roadmap page did not expose item 574113’s individual details, so its recorded status and scope could not be independently reconfirmed there. Microsoft explicitly describes roadmap dates as estimates subject to change. October 2026 should therefore not be read as proof that every eligible tenant has received the feature.
Historical analytics is not starting from scratch
Microsoft’s existing documentation lists historical dashboards for Summary, Conversation, Queue, Voice, Voicemail, Agent, Bot, Proactive Outbound, Bot-Intent, and Quality Assurance Agent. The last two product-specific examples worth noting are Proactive Outbound and Quality Assurance Agent: Microsoft documents those dashboards as available in Dynamics 365 Contact Center only.
Nor are facts and dimensions themselves new to the product. Microsoft Learn already describes an out-of-box model in which fact tables organize metrics and dimensions provide the attributes used to filter or group them. Its example is analyzing average handle time by queue.
The distinction in the roadmap description is consequently the shared foundation across reporting areas and its additional extension options, rather than the invention of a dimensional data model.
That matters because a familiar chart can sit on top of a substantially different data architecture. Keeping the report experience does not, by itself, establish whether existing custom models, permissions, or refresh arrangements will carry over unchanged.
Why consistent definitions matter
A useful example comes from Microsoft’s documented conversation workflow. A conversation represents the end-to-end customer interaction; a session represents an assignment attempt within a queue. One conversation can therefore contain multiple sessions, including transitions between an AI agent and a service representative. Those counts answer different questions and should not be treated as interchangeable.
The analytical opportunity is straightforward: if the shared foundation consistently preserves those distinctions, reporting teams could have less work reconciling calculations across dashboards and custom analysis. That is an interpretation of the roadmap’s architecture—not a separately verified promise that every discrepancy will disappear.
Metric definitions deserve the same scrutiny. Microsoft’s customization documentation gives an example where default average handle time considers the primary representative’s time, while specialist consultation time is represented separately. An organization may deliberately want a different calculation. A common foundation can provide a baseline, but it does not eliminate the need to explain business-specific measures.
In other words, matching KPI labels are not enough. The arithmetic must match, too.
What administrators should—and should not—change
For organizations with custom Power BI reporting, the most useful immediate step is preparation rather than migration. Consider inventorying:
- Custom measures that duplicate Microsoft’s standard KPIs.
- Reports that combine conversation, session, queue, and representative data.
- Business-specific definitions that intentionally differ from the standard model.
- Dependencies that would need testing before adopting a different data foundation.
This is planning guidance, not a Microsoft deployment procedure for item 574113.
One existing safeguard remains particularly relevant: Microsoft recommends treating the dataset in its managed workspace as read-only, because changes can cause report problems and may be overwritten by subsequent model releases. That guidance concerns the documented customization architecture; the roadmap item does not establish a replacement customization procedure.
Likewise, the named Fabric, Direct Lake, SQL, and Spark options should not be interpreted as automatic access or a complete implementation specification. The roadmap description does not settle licensing, capacity requirements, connection setup, security behavior, refresh frequency, retention, or migration mechanics.
The practical takeaway
The roadmap describes an evolution worth watching: preserve the supplied reporting experience while making its underlying data foundation more consistent and extensible. Its potential value is less about another dashboard and more about reducing the effort required to build trustworthy analysis.
For now, the sensible evaluation question is not simply, “Does our tenant have it?” It is: Can our existing reports and custom measures use the new foundation without changing what their numbers mean? That is the test that will turn an architectural update into an operational benefit.
References
- Dynamics 365 Contact Center: Historical analytics Microsoft 365 Roadmap · 2026-10-28T23:04:31.716623Z
- Understand the analytics data model | Microsoft Learn learn.microsoft.com
- Manage omnichannel historical analytics reports in Customer Service | Microsoft Learn learn.microsoft.com