Dynamics 365 Customer Service: Filter Historical Adherence Reports by Planning Group

Microsoft has addressed that operational blind spot by launching planning group filtering for the adherence historical analytics report in Dynamics 365 Customer Service. Tracked under Microsoft’s AI at Work roadmap ID 576854 (and accompanied by Microsoft 365 Message Center notice MC1456408 ), the capability reached general availability in August 2026 for Worldwide (Standard Multi-Tenant) cloud instances on the web. According to Microsoft’s Customer Service 2026 release wave 1 plan and Microsoft Learn documentation, the update allows supervisors and workforce managers to filter historical adherence analytics by one or more planning groups, recalculating performance metrics specifically for the filtered scope rather than returning a blunt contact-center-wide aggregate.

For IT administrators, Power Platform makers, and contact center leads, this isn't just an extra dropdown menu in a dashboard. It connects historical reporting directly to the foundational unit of Dynamics 365’s Workforce Engagement Management (WEM) architecture. Here is a complete technical breakdown of how the filter works, how the underlying adherence math is calculated, and what administrators need to configure before supervisors can expect any data to populate.

Why Planning Groups Matter in Contact Center Analytics​

To appreciate why this filter is a necessary addition, it helps to look at how Microsoft structures workforce management inside Dynamics 365 Contact Center and Customer Service. According to Microsoft Learn’s documentation on setting up and managing planning groups, a planning group is not a casual tag or an arbitrary list of favorite agents. It is the foundational planning unit in workforce management.

A planning group binds together the specific queue and channel combinations—such as Voice Tier 1 East, Chat Support, or Billing Email—that generate workload for a team. Each group defines:

• Demand Scope: One or more queue-and-channel combinations that determine which interaction volumes are fed into forecasts. Critically, Microsoft enforces a strict one-to-one boundary here: a specific queue-and-channel combination can belong to only one planning group at a time. If an admin tries to assign an already-claimed queue and channel pair to a second planning group, the system throws a validation error upon saving so interaction volumes are never double-counted in forecasts.
• Time Zone: The governing clock for scheduling and forecasting intervals across associated artifacts.
• Service Objectives: Target metrics including Service Level percentage, Target Answer Time in seconds, Shrinkage percentage (scheduled time lost to breaks, training, coaching, meetings, or unplanned absences), Occupancy percentage, and Concurrency (such as 1 for voice, or higher for chat and digital channels).
• Associated WEM Artifacts: Shift plans, forecast scenarios, and capacity plans all inherit the planning group’s shared configuration.

Before planning group support arrived in historical analytics—alongside sibling August 2026 updates for filtering the real-time adherence tracker, associating forecast scenarios, and creating capacity plans by planning group—evaluating past schedule adherence meant looking at the operation without that structural context. If overall adherence dipped on a Tuesday afternoon, was it because a single under-supported voice queue got hammered and kept agents trapped in after-call work, or was there a broad, center-wide scheduling mismatch?

By bringing planning group scope into adherence historical analytics, managers can isolate specific operational units or compare multiple groups across the exact same time window.

• Section Summary: Planning groups act as the structural backbone of Dynamics 365 workforce management, tying specific queue-and-channel combinations to service objectives and shift plans. Adding them to historical analytics lets managers isolate queue-specific adherence dips from broad operational trends.

How the Planning Group Filter Works in Practice​

In the Copilot Service workspace, supervisors access the report by navigating the site map to Workforce management and selecting Adherence historical analytics.

According to Microsoft Learn’s documentation for the adherence history report, the Planning group filter sits alongside the report's existing parameters, allowing managers to combine multiple criteria in a single view. When a user selects one or more planning groups and clicks Apply, the report dynamically recalculates the top-level summary cards and representative grids for just that selected scope.

Combining Report Filters​

Supervisors can layer the planning group filter with four existing report filters documented by Microsoft Learn:

The Shift-Association Caveat​

Here is the most important architectural detail for workforce analysts to keep in mind: the report associates customer service representatives with planning groups through their scheduled shifts.

Why does Microsoft build the association through shifts rather than static user profiles? Because in a dynamic contact center, agents may move between shift plans or cover different operational groups over a two-year historical window. Tying the planning group filter to the scheduled shifts ensures that historical reporting stays strictly aligned with the shift plans that were actually in force when adherence was calculated.

However, that also means the filter is only as smart as your shift configuration. If planning groups are not created, or if representatives do not have scheduled shifts tied to a shift plan associated with that planning group, applying the filter will return an empty dataset.

• Section Summary: Accessed via the Copilot Service workspace under Workforce management, the Planning group filter works in tandem with Duration, Time Zone, Shift Plan, and Agent filters. Because agents are linked to planning groups through their scheduled shifts, historical reporting reflects how work was scheduled at the time, up to the report's two-year data retention limit.

Under the Hood: What Recalculates and How Microsoft Does the Math​

It is worth asking a fundamental analytical question: does filtering by planning group change how Dynamics 365 defines or calculates adherence? No. Based on general industry principles and Microsoft’s documentation, the filter alters the population scope of the query, not the underlying mathematical engine. Once the subset of shift records is isolated by planning group, Dynamics 365 recalculates its standard summary, representative, and interval metrics.

According to Microsoft Learn, adherence is governed by three mechanisms: expected state versus actual presence state, user state mapping (which defines which presence states—such as Available, Busy, or Away—satisfy a scheduled activity like a Call, Conversation, Break, or Training), and tolerance (a configured grace period that absorbs minor timing deviations).

Furthermore, administrators can mark specific scheduled activities—such as a 30-minute training block—as Not Tracked, excluding them entirely from penalizing or rewarding the representative.

Microsoft Learn defines the exact formulas used to recalculate the summary cards when a filter is applied:

$$\text{Tracked Schedule Time} = \text{Total Schedule Time} - \text{Not Tracked Time}$$

$$\text{Time In Adherence} = \text{Tracked Schedule Time} - \text{Time Out of Adherence}$$

$$\text{Adherence \%} = \left( \frac{\text{Time In Adherence}}{\text{Tracked Schedule Time}} \right) \times 100$$

A Concrete Calculation Example​

To see how tolerance and tracking exclusions play out in the recalculated grids, consider the shift example documented by Microsoft Learn for a representative named Maria working an 8-hour (480-minute) shift from 9:00 AM to 5:00 PM:

• Configured Rules: Call activities allow Available or Busy states with a 5-minute tolerance. Conversation activities allow Available or Busy with no tolerance. Breaks and Lunch require Away with no tolerance. Training expects Away and is marked Not Tracked.
• Morning Sign-In Deviation: Maria is scheduled for Calls at 9:00 AM but remains Offline until 9:10 AM. The report splits this into two intervals: 9:00 to 9:05 is marked In Adherence (5 minutes absorbed by the Call tolerance), while 9:05 to 9:10 is marked Out of Adherence (5 minutes beyond tolerance).
• Midday Unscheduled Away Time: During a scheduled Conversation block from 11:15 AM to 1:00 PM, Maria switches her presence to Away from 12:00 PM to 12:25 PM. Because Conversation has no configured tolerance, all 25 minutes count as Out of Adherence.
• Afternoon Training Exclusion: From 3:30 PM to 4:00 PM, Maria attends scheduled Training. Because Training is Not Tracked, those 30 minutes are subtracted from the 480-minute Total Schedule Time, leaving 450 minutes of Tracked Schedule Time.
• Early Sign-Out: Maria goes Offline at 4:40 PM during a scheduled Call block ending at 5:00 PM. The first 5 minutes (4:40 to 4:45) are absorbed by the Call tolerance, leaving 15 minutes (4:45 to 5:00) Out of Adherence.

When the report rolls up those intervals, Maria has 450 minutes of Tracked Schedule Time and 45 minutes Out of Adherence ($5 + 25 + 15$). That yields 405 minutes In Adherence, or exactly 90.00% Adherence.

Representative and Activity Grids​

Below the top-level summary cards, the filtered report updates two detailed tables:

1. Representative Grid: Displays each agent’s Adherence %, Total Schedule Time, Time Out of Adherence, and Total Time Worked (the total duration the agent was signed in and working during the period, regardless of schedule). Comparing Total Time Worked against Total Schedule Time lets supervisors spot overcoverage or undercoverage within a specific planning group. Note that if a representative has scheduled time in that planning group but never signs in during the period, Microsoft Learn notes the report displays 0.00% adherence and 0 time worked.
2. Activity Summary Grid: Breaks shifts down into individual continuous intervals showing Actual activity, Scheduled activity, Start time, End time, Total duration, and Adherence status (In Adherence, Out of Adherence, or Not Tracked).

• Section Summary: Applying the planning group filter recalculates Adherence %, Time Out of Adherence, and Total Schedule Time across summary cards, representative grids, and interval logs. The calculation subtracts Not Tracked activities and applies activity-level grace tolerances before computing the final compliance percentage.

Admin Prerequisites and Deployment Checklist​

Because Microsoft classifies this feature as "Enabled for users by admins, makers, or analysts" (or marketers in the roadmap metadata), it will not magically populate with usable data in an unconfigured environment. If your contact center supervisors open the adherence historical analytics report and find the planning group filter empty or missing, walk through this administrative checklist based on Microsoft Learn’s documentation:

1. Install the WEM Package: An administrator must install the Workforce Management for Customer Service package from the Power Platform admin center.
2. Enable Workforce Management: Ensure Workforce Management is turned on within the Copilot Service admin center.
3. Verify Queues and Channels: Confirm that all voice, chat, email, or custom channels and queues you intend to group together are already configured in the Customer Service admin center or Copilot Service admin center.
4. Create Planning Groups: In the Copilot Service workspace site map, go to Workforce Management -> Planning Groups, select New, define the Name and Time Zone, and use Add Demand Scope to bind unique queue-and-channel combinations to the group.
5. Link Shift Plans to Planning Groups: Open your shift plans (or create new ones under the planning group via Add New Shift Plan or Add Existing Shift Plan), set the Planning Group lookup field on the Details card, and save. Ensure representatives have scheduled shifts published under those associated shift plans.

The Bigger Picture: Native WEM vs. Third-Party Giants​

Stepping back to look at the broader enterprise software landscape, this update—while humble on the surface—highlights Microsoft’s steady march to make Dynamics 365 Contact Center and Customer Service a self-contained WEM contender.

Historically, enterprise contact centers running on Dynamics 365 often bolted on dedicated third-party workforce management suites like Verint, Calabrio, or NICE to handle complex multi-queue forecasting, intraday management, and historical adherence. Over the 2026 release wave 1 cycle, Microsoft has systematically closed the foundational gaps in its native WEM module—adding planning group support across real-time adherence trackers, historical analytics, forecast scenarios, and capacity plans, alongside intraday volume spike alerts.

Does a planning group filter in a historical report suddenly replace decades of specialized enterprise WEM customization? Probably not for massive, hyper-complex global BPOs with esoteric union scheduling rules. And administrators should remember that historical adherence is strictly backward-looking within a two-year window; it won't fix a broken shift plan or retroactively assign agents who were scheduled outside a planning group.

Still, for organizations already invested in the Power Platform and Dynamics 365 ecosystem, having planning groups thread consistently from demand forecasting all the way through real-time tracking and historical adherence analytics removes a major point of friction. When your reporting finally mirrors the way your teams actually work, you can stop guessing which queue tripped the breaker and start fixing the schedule.