Introduction
Contact centers generate an enormous amount of data. Every call handled, message exchanged, or issue resolved leaves a signal. When these signals are measurable and actionable, organizations are empowered to improve their operations and better serve their customers.
Dynamics 365 Contact Center includes a layered analytics and reporting framework. Supervisors and service managers can begin with the out-of-the-box dashboards available immediately in Copilot Service workspace. Organizations that need custom KPIs, additional data sources, or tailored visualizations can extend those reports using Power BI and Microsoft Fabric. For operations and engineering teams that need conversation-level diagnostics and system health telemetry, Azure Application Insights provides a data pipeline for routing events data.
The analytics layers
Think of the analytics framework as three overlapping layers.
Out-of-the-box dashboards give everyone a starting point: historical and real-time reports across channels, queues, and representatives, ready to use without any Power BI expertise.
Power BI data model customization unlocks the underlying data models. Report authors can add new metrics, bring in custom Dataverse entities or external data sources, build composite models, and embed the results back into Copilot Service workspace. This layer requires Microsoft Fabric licensing and some Power BI authoring skill.
Azure Application Insights connects your Dynamics 365 Contact Center environment to Azure Monitor's telemetry pipeline. It captures conversation lifecycle events like routing decisions, handoffs, and state transitions in a queryable log that developers and operations teams can use for diagnostics, custom dashboards, and integration into broader monitoring platforms.
This module walks through each layer and shows you how to configure them for your organization.
You should be familiar with Copilot Service workspace, the Copilot Service admin center, and basic concepts in Power BI before starting this module. For the Azure Application Insights unit, some familiarity with Azure Monitor and Kusto Query Language (KQL) is helpful but not required.