Dynamics 365 roadmap considerations

Dynamics 365 evolves continuously — two release waves per year, monthly updates, periodic strategic shifts. Building your organisation's Dynamics roadmap requires understanding Microsoft's direction, anticipating changes, and planning multi-year investments. Done well, the roadmap aligns with where the platform is heading; done poorly, you build into obsolete patterns.

Microsoft's release cadence.

• Two waves per year — April and October.
• Wave plan published months ahead.
• Continuous updates monthly.
• Major shifts announced strategically.

Predictable cadence; plan around it.

Where Microsoft is investing.

• AI / Copilot — heavy investment across all products.
• Industry clouds — vertical-specific bundles.
• Microsoft Fabric integration — analytics.
• Power Platform expansion.
• Customer Insights — Journeys — replacing outbound marketing.
• Customer Service Workspace + Contact Center.
• Sustainability.

The pattern of investment indicates strategic direction.

Where Microsoft is divesting.

• Legacy patterns — C/AL, classic CRM client, older marketing.
• Outbound marketing — deprecated in favour of real-time.
• On-premises — minimal new investment.
• Some niche modules that didn't scale.

Investments in deprecated areas have limited horizon.

Reading the wave plans.

• Public release plans announced ~6 months ahead.
• Per-product feature lists.
• Preview vs GA timing.
• Deprecation notices.

Roadmap planning starts from these.

Per-product roadmaps.

• Business Central — quarterly minor + wave major.
• F&O / SCM — wave-based.
• Customer Engagement apps — wave-based.
• Power Platform — continuous.
• Fabric — continuous.

Different cadences; coordinated overall.

Customer roadmap building.

• Where are we today — current state.
• Where do we want to be — vision.
• What Microsoft's adding — capabilities coming.
• What's deprecated — must migrate.
• Sequence — what comes when.

Multi-year view; aligned with Microsoft's direction.

Common roadmap themes.

• AI / Copilot adoption.
• Customer 360 / Customer Insights — Data.
• Industry cloud adoption.
• Fabric for analytics.
• Replacement of outbound marketing.
• Sustainability programme.

Each major theme is multi-year journey.

Deprecation handling.

• Notice typically 1-2 years ahead.
• Migration tooling often provided.
• Customer-specific timelines for transition.
• Risk of waiting — last-minute panic.

Track deprecations actively; plan migrations.

Major recent deprecations (as of 2026).

• Dynamics Marketing outbound — phased out in favour of Customer Insights — Journeys.
• C/AL in Business Central — long deprecated.
• Some older Sales features — replaced by sales acceleration.
• Older portal versions — replaced by Power Pages.

Each had migration path; plan ahead.

Upcoming themes (looking ahead).

• Deeper AI integration — Copilot across more workflows.
• Autonomous agents — proactive, multi-step automation.
• Fabric becoming dominant for analytics.
• Continued industry cloud expansion.
• Sustainability mandates — ESG reporting becoming standard.

Watch Microsoft Ignite, Build, Inspire events for direction.

Customer alignment.

• Stay current with at least N-1 version.
• Adopt new features that fit.
• Plan migrations for deprecated.
• Modernise customisations for current patterns.

The "stay current" discipline pays back over years.

Cost of falling behind.

• Larger jumps more expensive than incremental.
• Lost productivity from outdated patterns.
• Security gaps.
• Eventually forced migration at worst time.

Lagging is rarely cost-effective long-term.

Pace of adoption.

• Bleeding edge — preview, beta features. Risk vs early advantage.
• Early adopter — GA features quickly. Balance.
• Mainstream — stable, well-documented. Conservative.
• Laggard — only when forced. High risk.

Most enterprises target mainstream with selective early adoption.

Multi-year planning horizon.

• 3-year roadmap typical.
• Annual review and adjust.
• Quarterly tactical.
• Aligned with budget cycles.

The roadmap is living document.

Roadmap stakeholders.

• CIO / IT leadership — strategic direction.
• Business leaders — what capabilities needed.
• Architecture — technical feasibility.
• Operations — what's manageable.
• Finance — what's affordable.

Cross-functional alignment.

Engaging with Microsoft.

• Account team — relationship.
• Product groups — feedback channels.
• Customer Advisory Boards — strategic input.
• TAP (Technology Adoption Program) — early access.

For larger customers, engagement deepens.

Common roadmap pitfalls.

• Year-by-year tactical — no multi-year view.
• Vendor-driven — Microsoft sells; customer buys reactively.
• Stale roadmap — created once, never updated.
• Ignoring deprecations until forced.
• No cross-functional alignment.
• Bleeding edge adoption without business reason.

Roadmap maintenance cadence.

• Quarterly review.
• Annual major refresh.
• Per Microsoft wave — update for new capabilities.
• Pre-major-decision — review for alignment.

Investment classification.

• Maintenance — keep operating.
• Enhancement — incremental improvement.
• Strategic — major capability addition.
• Transformation — significant change.

Roadmap budget split across categories.

Risk on the roadmap.

• Bet too early — preview feature deprecated.
• Bet too late — competitor advantage.
• Bet wrong direction — Microsoft pivot.

Manage risk via portfolio approach; don't bet everything on one direction.

Strategic positioning. A clear Dynamics 365 roadmap aligns the organisation's investment with the platform's evolution. The investment in maintaining the roadmap is small; the cost of operating without one is misaligned investments and reactive scrambles.

For decision-makers:

• Build multi-year roadmap.
• Stay aligned with Microsoft's direction.
• Plan deprecation migrations proactively.
• Review and adjust regularly.
• Engage Microsoft strategically.

The Dynamics 365 platform is too valuable and changes too quickly to operate without a roadmap. The discipline of having one — and using it to inform decisions — separates organisations that get sustained value from those that struggle with constant catch-up.