Dynamics 365 & Power Platform Rolling out #327

Conversation orchestration expands routing and overflow capabilities

Contact center routing adapts as conversations progress

Conversation orchestration in Microsoft Dynamics 365 Contact center uses administrator-configured natural-language playbooks to respond to changing conditions. Worldwide general availability is scheduled from late October to late November 2026.

Key points

  • Dynamic priority escalation reevaluates priority using conditions such as wait time, queue transfers and customer tier.
  • Overflow handling can offer callbacks, route to alternate queues or notify supervisors when configured conditions are met.
  • Customers can reconnect with previously engaged or preferred representatives, with fallback to the next qualified representative.
  • Bullseye routing progressively expands eligible representatives using skills, proficiency levels, teams or other business criteria.
  • Built-in validation identifies conflicts before administrators publish playbooks.

What to do

Keep existing Conversation Orchestration configurations; no additional preparation is required for existing customers. For new deployments, review the prerequisites, enable Conversation Orchestration and configure suitable playbooks. Tell administrators that publishing playbooks consumes Copilot credits, while runtime execution does not. Explain the routing and fallback scenarios to contact center teams.

Timeline

  1. April 2026 Preview (planned, not confirmed) Microsoft 365 Roadmap target: Roadmap preview target.
  2. October 2026 General availability (planned, not confirmed) Microsoft 365 Roadmap target: Roadmap general availability target.
  3. October 2026 Rollout start (planned, not confirmed) Worldwide general availability rollout begins in late October.
  4. November 2026 Rollout end (planned) Worldwide rollout is expected to complete by late November.
  5. 3 November 2026 Published
Speaker notes

The change keeps routing responsive throughout a conversation rather than relying only on its initial assignment. Administrators express scenarios in natural-language playbooks using guided templates. Overflow handling also covers direct inward dial calls when representatives are unavailable or do not accept calls. For asynchronous conversations, organizations can choose to consider presence status and active conversation limits before reconnecting a customer with a preferred representative. Existing customers can retain their configurations without additional preparation, while new customers must enable Conversation Orchestration and configure playbooks. Publishing playbooks consumes Copilot credits, but runtime execution does not; the sources do not establish the full licence prerequisites. The schedule runs through late November 2026, so the roadmap's Launched status should not be presented as evidence that worldwide rollout is complete.

Sources and links

Related cards

Area, status, change type, licence and flags are indicative. Always open the source before you act on a card.