Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Dynamics 365 Contact Center - Manage overnight shifts as a single continuous schedule

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, safely structured

We are announcing the ability to manage overnight shifts as a single continuous schedule in Dynamics 365 Contact Center. This feature will reach general availability on October 2, 2026. How does this affect me? With this feature, supervisors can now create and manage overnight shifts that span across midnight while maintaining a single continuous shift experience. Activities, breaks, meals, and ad-hoc work can be scheduled anywhere within the overnight shift and remain part of a single continuous itinerary. Supervisors can view and manage the entire shift without manually splitting schedules across calendar days. Activities that cross midnight are preserved as a single record and are not divided into separate activities. What action do I need to take? This message is for awareness, and no action is required.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

No related announcements were found in the saved public history. Check the source for newer announcements.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current