The roadmap became continuous

Microsoft announced on 25 August that Dynamics 365, Power Platform and Dataverse would join the AI at Work roadmap from September. Plans would publish continuously with in-development, rolling-out and launched states. Release Planner would retire by 15 November, while Message Center remained the source for tenant-specific change.

For marketing, sales, service and field work, a fixed six-month review was no longer enough. An item could change date or status without a new wave publication. Process owners needed a retained feature ID, review date and named decision about pilot or production.

The customer’s route to a person had to remain

Gartner reported on 4 August that 87 per cent of 3,566 surveyed customers considered access to a person essential when a company used generative AI in service. Fifty-eight per cent of AI users had let it complete a task. The result supported action-oriented self-service alongside a visible alternative for complex or sensitive cases.

When a roadmap item promised an agent capability, teams needed to test both action and handover. A marketing conversation could become a lead, service case or field visit. Consent, identity, agreement and relevant history had to travel with it, and customers needed to understand when a person took over.

The change log became part of the process

A monthly review could retrieve filtered CSV or RSS, compare status and connect the change with process maps and test evidence. The team measured incorrect routing, abandoned self-service, repeated customer information and field work with missing context. The roadmap then governed customer experience rather than serving as a feature list.

Controls in practice

Microsoft said existing roadmap items with preview or general availability from 1 June 2026 onward would move, while historical plans remained in Learn. Organisations therefore needed to retain links and decisions from earlier release waves while following new feature IDs in the continuous surface.

Every customer-process item needed an availability matrix for region, licence and channel. Before marketing announced a service or sales promised a workflow, status had to be launched in the relevant environment. Service and field teams needed a fallback when rollout slipped or production behaviour differed from the pilot.

Sources

Microsoft Dynamics 365 Blog: One always-on AI at Work roadmap, 25 August 2026.

Gartner: Customers require access to a human agent, 4 August 2026.

Microsoft Dynamics 365 Blog: Customer Insights as an intelligence layer, 15 July 2026.

Microsoft Dynamics 365 Blog: Agentic CX in sales and service, 7 July 2026.

For discussion

How do we connect a roadmap change with one owner, one customer journey and one verified launch status?