A woman reviews a color-coded staff schedule and workflow dashboard on a large monitor in a modern office.
Dynamics 365 Contact Center now has shift rotation policies in Workforce Management. They let supervisors define a rotation pattern once and leave the scheduler to apply it. The roadmap lists the feature as launched, with general availability in August 2026, for the Worldwide standard multi-tenant cloud on the web. This piece covers what the feature does, how to set it up, and where the documented limits are.

A woman reviews a color-coded staff schedule and workflow dashboard on a large monitor in a modern office. What the feature does​

Supervisors use shift rotation policies to rotate customer service representatives across recurring time slots on a configurable cadence. Microsoft says this helps balance workloads, support 24/7 coverage and distribute shifts fairly. When the scheduler generates bookings, it uses the policy to select representatives whose rotation positions match the booking times.

The business case is less manual reassignment. Microsoft says organizations running 24/7 contact centers or rotating shifts can spend less supervisor time reassigning agents, because the pattern is defined once and the scheduler applies it automatically.

This is a configuration feature, not a new scheduling engine. The policy supplies the recurring pattern, and a shift plan still holds the operational detail. Per Microsoft Learn, a shift plan carries things like the planning group, skills, queues, calendar and shift activities. Supervisors run Schedule Workforce from the plan to schedule its resources.

A note on dates​

The sources disagree slightly on timing, and this is how they line up:

  • The roadmap entry says general availability in August 2026.
  • Microsoft's release-plan page lists general availability as Aug 14, 2026 in its archived table. That table lists nothing for public preview.
  • Earlier Message Center posts, relayed by third-party trackers, gave July 31, 2026 as the general availability date.
  • Message Center posts also gave June 30, 2026 for public preview.

Dates moved during rollout. If you are checking a specific tenant, test the feature there rather than relying on a single date.

Setting it up​

Prerequisite: An administrator must enable shift rotation policies in the Customer Service admin center under Workforce Management > Shift and Scheduling. Supervisors then open Customer Service workspace, go to Workforce Management, and select Shift rotation policies.

The policy list shows each policy's name, status (such as Active or Paused), cadence, number of slots, assigned shift plans and activation date. You can filter, sort and search it.

Creating a policy​

  1. On the Shift rotation policies page, select New.
  2. Enter a unique policy name.
  3. Pick an Activation date. It marks the start of the first rotation cycle, and you can't change it after you save the policy.
  4. Choose the Timezone. Slot times follow the policy's time zone.
  5. Enter the Cadence as the number of days in each rotation cycle.
  6. Select Add slot. Enter start and end times, choose every day or specific days, and optionally set different times per day. Then search for and select the representatives for that slot, and select Save & Close.
  7. Repeat until the policy has between 2 and 24 slots, then select Save.

Attaching it to a shift plan​

There are two routes:

  • From the policy: open it, select Assign Shift Plan, choose the plan and select Assign Selected.
  • From the plan: open the plan on the shift planning page, select Rotation policy in the plan settings, choose the policy and save. The Plan Details card also has a Shift Rotation Policy field.

Limits to know before you build​

RuleDetail
Slots per policy2 to 24
Representative membershipOne rotation policy at a time, but can fill multiple slots within it
Policies per shift planOne
Plans per policyThe same policy can be assigned to multiple plans
Activation dateFixed after saving
Deleting a policyNot possible while it is assigned to any shift plan

The one-policy-per-representative rule matters in practice. If your organization has people who float between teams, a cohort-based model will need some planning up front.

Changing policies after go-live​

  • Edits are forward-looking. Changes take effect at the next scheduler run, and previously generated schedules aren't updated. Don't expect a policy edit to fix bookings that already exist.
  • Switching a plan to a different policy takes cleanup. Microsoft says to remove the existing schedules for the affected representatives and rerun scheduling.
  • Pause freezes the rotation. Pause stops the rotation at its current cycle, and Resume restarts it from that point. While paused, representatives stay in their current slot positions and the scheduler keeps selecting from them. Pausing is therefore not the same as turning scheduling off.
  • Removing the policy from a plan stops rotation-based scheduling. The roadmap says supervisors can do this at any time. The Learn page covers assignment and reassignment but says little about what an unassigned plan does afterward.

The roadmap also says the scheduler can use available flexible workers or other eligible representatives when more staffing is needed. None of the sources I reviewed spell out the eligibility rules or precedence for that fallback. Test it before you rely on it for peak-hour gaps.

An example from Microsoft​

Microsoft's product blog sets out a four-week cadence with four slots and a cohort for each:

  • Early, Monday to Friday, 06:00 to 14:00
  • Late, Monday to Friday, 14:00 to 22:00
  • Peak support, Tuesday to Friday, 11:00 to 19:00
  • Weekend, Saturday and Sunday, 09:00 to 19:00

Every four weeks, each cohort advances one position. The aim is that weekend duty circulates across the team instead of landing on the same people every month.

Analysis: what to make of the claims​

Microsoft's blog says a biweekly morning, evening and night rotation takes 2–4 hours of supervisor time per shift plan, per cycle. That is Microsoft's own illustration, not an independently measured result. Your savings will depend on team size, how many plans you run and how much manual tweaking you do now.

The documentation also doesn't promise that coverage targets will always be met. Rotation controls who moves where. It doesn't guarantee that capacity matches demand. Teams that use capacity plans should still check the generated schedules against forecasts.

Pre-production checklist​

  1. Confirm the feature is switched on in the admin center.
  2. Choose the policy time zone and activation date carefully, since the date can't be edited.
  3. Check slot-day coverage for weekends and overlap periods.
  4. Confirm every representative sits in only one policy.
  5. Attach the policy to the intended shift plan and run a scheduling pass.
  6. Plan for the cleanup step if you later move a plan to a different policy.

For contact-center administrators the change is mostly good news. A recurring rotation can now live in a policy instead of in a supervisor's spreadsheet. The caveats are that the rotation is forward-looking, the activation date is permanent, and the fallback staffing behavior isn't well documented.

 

References

  1. Dynamics 365 Contact Center: Workforce engagement management - Automate shift rotations for consistent workforce coverage Microsoft 365 Roadmap 2026-10-22T23:45:27.308271Z
  2. Create and manage shift rotation policies | Microsoft Learn learn.microsoft.com
  3. Automate shift rotations for consistent workforce coverage | Microsoft Learn learn.microsoft.com