Dynamics 365 Customer Service: Link Forecast Scenarios to Planning Groups for WEM

Microsoft is addressing that operational fragmentation in Dynamics 365 Customer Service. Tracked under Microsoft’s AI at Work Roadmap ID 576853 and the Dynamics 365 2026 release wave 1 plan, the ability to associate forecast scenarios with planning groups under Workforce Engagement Management (WEM) has reached general availability for Worldwide (Standard Multi-Tenant) web environments, with a general availability milestone of August 2026.

Rather than forcing forecasters to build, maintain, and manually aggregate individual queue-by-queue models, this update links forecast scenarios directly to a shared planning group definition. It is not a brand-new forecasting algorithm under the hood; rather, it is a crucial workflow and data-governance bridge that locks demand forecasting, capacity planning, and shift scheduling into a single operational boundary.

What Changed in Dynamics 365 Forecast Scenarios​

At its core, this update changes how demand scope is defined and inherited when generating volume and average handle time (AHT) predictions in the Copilot Service workspace. According to Microsoft Learn’s documentation for Dynamics 365 Contact Center and Customer Service, forecasters now have an optional Planning Group lookup when creating or editing a forecast scenario.

Here is how the system behaves depending on how you configure that field:

• Locked Alignment When Linked: When a forecaster selects a planning group on a forecast scenario, the Time zone, Channel, and Queue fields are automatically populated from the planning group’s definition and immediately become read-only. This prevents well-meaning analysts from accidentally tweaking a queue list or shifting a time zone on a forecast, which would otherwise cause the forecast to drift out of sync with the team’s actual capacity and shift plans.
• Backward Compatibility When Unlinked: Selecting a planning group is completely optional. If no planning group is selected, the Time zone, Channel, and Queue fields remain manually editable, and legacy scenario-creation workflows continue to operate without disruption.
• List View Sorting and Filtering: The Active Forecast Scenarios list view now includes a dedicated Planning group column, allowing workforce teams to sort and filter their growing library of scenarios by operational unit.
• Automatic Inheritance in Capacity Planning: When you generate a capacity plan directly from a forecast scenario, the capacity plan automatically inherits the scenario’s planning group. If you create a capacity plan from an externally uploaded forecast file instead, you can manually select the appropriate planning group during setup.

Section Summary: Linking a forecast scenario to a planning group populates and locks the time zone, channel, and queue parameters, adds list-level filtering, and passes the group context automatically to downstream capacity plans.

Why Planning Groups Matter: Ending the Spreadsheet Tax​

To understand why enterprise IT administrators and contact center directors care about this update, you have to look at what happens when forecasting and capacity planning are disconnected. Why spend thousands of dollars on enterprise workforce management software if your analysts still have to export CSV files to Excel just to add Queue A, Queue B, and Queue C together?

In Microsoft’s Workforce Engagement Management architecture, a planning group is the foundational operational unit. As documented in Microsoft Learn, a planning group bundles together:

1. A specific time zone that governs scheduling and forecasting intervals.
2. A demand scope consisting of one or more queue-and-channel combinations (for example, Tier 1 East Voice, Tier 1 East Chat, and Tier 1 East Email).
3. Service objectives that dictate how forecast demand translates into required headcount.

The Single-Membership Rule Prevents Double Counting​

One of the most practical guardrails detailed in Microsoft’s planning group documentation is a strict exclusivity rule: a specific queue-and-channel combination can belong to only one planning group at a time. If an administrator tries to assign a queue-and-channel pair that is already claimed by another planning group, the system throws a validation error upon saving.

From an data-integrity perspective, this is a lifesaver. In manual or ad-hoc forecasting setups, it is remarkably easy for two different supervisors to include the same overflow queue in their respective forecast scenarios. When those numbers roll up to leadership, the interaction volume is double-counted, resulting in inflated staffing projections. By anchoring forecast scenarios to planning groups—and enforcing mutually exclusive queue-and-channel memberships across those groups—Dynamics 365 eliminates double-counting at the schema level.

Connecting Forecasts to Service Objectives​

When a forecast scenario is tied to a planning group and then handed off to capacity planning, the capacity plan doesn't just inherit the queues and time zone; it also prepopulates the planning group’s service objectives. According to Microsoft Learn, these objectives include:

• Service Level (%): The target percentage of interactions answered within a set threshold (such as 80 percent).
• Target Answer Time (seconds): The time limit tied to the service level (such as 20 seconds).
• Shrinkage (%): Scheduled time where representatives are unavailable due to breaks, training, coaching, meetings, or unplanned absences.
• Concurrency: How many interactions a representative handles simultaneously (typically set to 1 for voice, and adjusted higher for chat or messaging channels).
• Occupancy (%): The percentage of logged-in time representatives are expected to spend actively handling customer interactions, including after-call work.

Because service objectives apply across all capacity plans linked to a planning group, Microsoft advises a crucial architectural rule of thumb: if different channels require different service-level targets, you should create separate planning groups for those channel scopes. For instance, if your voice queues demand an 80/20 service level with a concurrency of 1, while your email queues have a 24-hour response target and higher concurrency, lumping them into a single planning group will muddy your capacity math. Group together only the queues and channels that share common staffing pools and service goals.

Section Summary: Planning groups act as a single source of truth for workforce artifacts. They enforce a one-group-per-queue-and-channel rule to prevent double-counting and carry preset service objectives directly into capacity plans.

Prerequisites and Step-by-Step Configuration Guide​

This capability is not turned on automatically for end users out of the box; it is classified as enabled by administrators, makers, or analysts for users. Before a forecaster can link a scenario to a planning group, the environment must meet several technical prerequisites documented on Microsoft Learn:

Administrative Prerequisites​

1. Package Installation: A system administrator must install the Workforce Management for Customer Service package via the Power Platform admin center.
2. Routing Configuration: All target channels and queues must already be configured inside the Customer Service admin center or Copilot Service admin center.
3. Security Privileges: To create and manage forecast scenarios, the user’s security role must hold the Read privilege on the msdyn_dataanalyticsreport_forecast table.
4. External Data Preparation (If Applicable): If you plan to forecast using external historical data rather than internal Dynamics 365 data, the file must be uploaded beforehand via the Manage External Data option.

Step 1: Verify or Create the Planning Group​

1. Open the Copilot Service workspace and navigate to Workforce Management > Planning Groups in the site map.
2. Select New on the Active Planning Groups page.
3. On the Details card, enter an identifiable Name (e.g., Voice Tier 1 - East), an optional Description, and the governing Time Zone.
4. In the Demand Scope view, select Add Demand Scope and choose each Queue and Channel combination that drives workload for this team.
5. Select Save, and optionally attach your Service Objectives (Service Level, Target Answer Time, Shrinkage, Occupancy, and Concurrency) via the Service Objectives lookup field.

Step 2: Associate a Forecast Scenario with the Planning Group​

1. In the Copilot Service workspace site map, go to Workforce Management > Forecasting (or Forecast Scenarios).
2. Select New and choose either Short-term (intraday intervals, supporting a duration of up to 42 days) or Long-term (daily intervals, supporting up to 1,095 days). You can also open an existing scenario and select Edit.
3. On the Details card, specify the scenario Name, Duration (Days), and locate the Planning Group lookup field.
4. Search for and select your target planning group. Notice that the Time zone on the Details card, along with the Channels and Queues on the Configuration parameters card, automatically populate from the group and lock as read-only.
5. On the Configuration parameters card, choose your Forecast entity (Conversation or Case).
6. On the Historical data card, choose Internal or External for the data source, set the Historical data start date, and pick a holiday calendar under Seasonality.
7. On the Forecast refresh schedule card, configure Auto refresh and the run time slot (note that Auto refresh is unavailable if you use an External data source).
8. Select Save.

Operational Gotchas and Troubleshooting Tips​

When working with linked forecast scenarios, keep these documented system behaviors in mind so you aren't caught off guard:

• Scenarios Start in Draft: Saving a new forecast scenario does not trigger an immediate calculation. The scenario remains in Draft status until its first scheduled run window.
• Immutable Core Settings After Creation: While you can edit a scenario later to change its Name, Duration, Historical data start date, Seasonality, refresh schedule, or Planning Group association, you cannot change the Forecast type (Short-term vs. Long-term), Interval, Forecast entity, or Data source once the record is created.
• Snapshots vs. Auto Refresh: If you edit a scenario’s inputs and want to generate a fresh forecast immediately using Create New Snapshot on the command bar, be aware that this button is disabled whenever Auto refresh is turned on. When a new snapshot runs, it executes as a background job (trackable via View Job History) and automatically refreshes downstream capacity planning data once completed.
• Deletion Locks: You cannot delete a forecast scenario if it is currently being used by a capacity plan.

Section Summary: Administrators must first deploy the Workforce Management package in the Power Platform admin center and ensure users have Read access to msdyn_dataanalyticsreport_forecast. Once a planning group is selected on a scenario, core scope settings lock in automatically, and the forecast generates on its scheduled run.

Critical Governance and Compliance Boundaries​

While tightening the integration between forecasting and capacity planning saves considerable administrative overhead, IT leaders and contact center managers should remain realistic about what this feature does—and does not—do.

First, associating a forecast scenario with a planning group guarantees configuration alignment, not statistical perfection. A planning group prevents a forecaster from accidentally leaving out a chat queue or picking the wrong time zone, and it stops two teams from double-counting the same queue. However, as Microsoft explicitly notes in its documentation, the underlying forecast accuracy still depends heavily on the depth and quality of your historical interaction data as it accumulates over time.

Second, Microsoft includes a prominent responsible-use and legal compliance warning in its Dynamics 365 forecasting documentation that every enterprise should take seriously. Microsoft states that forecasting is not intended for use in making decisions that affect a person's employment—including compensation, rewards, seniority, or other employee rights and entitlements. Furthermore, organizations deploying Dynamics 365 Workforce Engagement Management are solely responsible for complying with all local laws governing employee analytics, monitoring, and the recording and storage of communications.

For organizations running complex customer service operations inside the Microsoft ecosystem, linking forecast scenarios to planning groups is a welcome maturations step for Dynamics 365 WEM. By anchoring forecasting, capacity modeling, adherence tracking, and shift planning to a single shared definition, contact center leaders can spend far less time auditing mismatched spreadsheets and much more time actually managing service delivery.