Dynamics 365 Roadmap & Release Waves: What’s Coming in 2026
Microsoft releases Dynamics 365 updates twice yearly through a structured release wave system—Wave 1 (April–September) and Wave 2 (October–March)—with features ranging from AI-powered agents and Copilot integrations to dual-write improvements and sandbox testing available 4–6 weeks before general availability.
Understanding Microsoft’s Release Wave System
Microsoft maintains a predictable, twice-yearly release cycle for Dynamics 365 that ensures enterprises can plan upgrades, test changes, and manage organizational readiness. Unlike traditional monolithic release schedules, the release wave system provides two distinct periods per calendar year, each spanning approximately six months.
The Two-Wave Release Cycle
Wave 1 (April–September): The spring and summer release wave introduces features and updates available starting in April, with most organizations rolling them into production by September. Early access programs open typically in February, allowing partners and early adopters to validate functionality in sandbox environments.
Wave 2 (October–March): The fall and winter wave delivers updates in October, ramping through the holiday season and extending into early spring. Early access usually opens in August, giving organizations a four- to six-week testing window before mandatory adoption in production.
Key Timeline Milestones
Understanding the release timeline helps organizations plan resource allocation and change management:
- Roadmap Publication: Microsoft publishes detailed release notes and feature documentation in March (for Wave 1) and September (for Wave 2).
- Early Access Availability: Approximately 4–6 weeks before general availability (GA), features become available in designated sandbox environments for testing and validation.
- General Availability (GA): Features roll out to all production environments, though staggered rollouts may occur over 2–4 weeks.
- Feature Toggle Period: Some features remain optional or configurable for 30–90 days post-GA to allow organizations time to adapt.
- Mandatory Features: Critical infrastructure or compliance updates become mandatory, while most new features remain opt-in.
2025 Release Wave 2: Recent Capabilities (Oct 2025–Mar 2026)
2025 Release Wave 2 represented Microsoft’s most significant AI and automation advancement to that point. Organizations that adopted 2025 Release Wave 2 gained access to agentic capabilities, advanced Copilot integrations, and infrastructure improvements across the entire product portfolio.
Dynamics 365 Sales: Autonomous Agents & Enhanced Forecasting
Sales Cloud receives substantial AI upgrades with autonomous agents that assist in deal progression, territory coverage, and pipeline health. New capabilities include:
- Sales Copilot Enhancements: Copilot now generates automated deal summaries, recommends next-best actions based on historical patterns, and surfaces account intelligence without user prompting.
- Autonomous Agents: AI agents can autonomously identify at-risk deals, recommend remediation actions, and trigger escalation workflows—reducing manual deal reviews.
- Forecasting Intelligence: Advanced ML models predict pipeline velocity, contract win probability, and revenue timing with 15–20% greater accuracy than previous releases.
- Territory Coverage Analysis: AI-powered territory planning identifies under-penetrated accounts, recommends account assignments, and optimizes coverage models.
- Relationship Intelligence: Enhanced LinkedIn integration surfaces relationship changes, company news, and engagement opportunities in real time.
Customer Service & Contact Center: Agentic Capabilities & Multimodal Intelligence
Customer Service Cloud now integrates omnichannel agentic systems capable of handling complex customer interactions autonomously:
- Autonomous Agents: AI agents triage incoming tickets, resolve tier-1 issues without human intervention, and escalate complex cases with full context.
- Multimodal Intent Detection: Copilot now understands customer intent across email, chat, phone transcripts, and social channels with improved natural language processing.
- Sentiment & Urgency Analysis: Real-time emotion detection flags high-severity or escalated-emotion interactions for immediate agent assignment.
- Workforce Management Integration: Scheduling, capacity planning, and agent availability are now AI-optimized, reducing hold times and improving SLA compliance.
- Knowledge Article Auto-Population: Copilot surfaces relevant help articles and knowledge base content without agent search, accelerating issue resolution.
- Proactive Outreach: AI identifies customers experiencing issues before they contact support, enabling proactive engagement.
Field Service: Copilot-First Mobile Experience & Automated Inspections
Field Service Cloud emphasizes AI-driven frontline worker productivity:
- Mobile Copilot Assistant: Copilot guides technicians through work orders, provides procedural guidance, and captures field data without manual form entry.
- Automated Inspections: Computer vision and IoT sensor integration enable automatic asset condition assessment and predictive maintenance.
- Service Scheduling Optimization: AI optimizes route planning, technician allocation, and job sequencing to minimize travel time and maximize jobs per shift.
- Document & Report Generation: Copilot auto-generates service reports, work order summaries, and handoff documentation from field notes and photos.
- Real-Time Collaboration: Enhanced mixed-reality integration allows remote experts to guide on-site technicians through complex procedures.
Finance & Supply Chain Management: Async Dual-Write, Natural Language Queries & MCP Agents
Finance and Supply Chain modules receive critical infrastructure and AI enhancements:
- Asynchronous Dual-Write: Improved dual-write synchronization between Dynamics 365 and Dataverse now operates asynchronously, reducing lock contention and improving system performance during high-volume transactions.
- Natural Language Queries: Finance users can ask questions in plain English ("What’s my DSO this quarter?" or "Show me margin trends by region") and receive instant answers without SQL knowledge.
- MCP Agent Development: The Model Context Protocol enables organizations to build custom intelligent agents that autonomously process accounts payable, accounts receivable, and supply chain workflows.
- Procurement Intelligence: AI-driven supplier recommendations, contract compliance monitoring, and spend analysis now integrate with supplier quality metrics and delivery performance.
- Demand Sensing: Enhanced forecasting combines historical demand, market signals, and supply chain constraints to improve demand planning accuracy.
- Inventory Optimization: AI balances safety stock levels, reorder points, and carrying costs across the supply network.
Dynamics 365 Business Central: AL Language & Copilot Expansion
Business Central, Microsoft’s cloud ERP for mid-market organizations, continues AL language enhancements and Copilot feature expansion:
- AL Language Improvements: Better compiler diagnostics, improved IntelliSense, and enhanced debugging support streamline custom development.
- Copilot-Assisted Development: Copilot in Business Central suggests AL code patterns and generates boilerplate customizations.
- Expanded Copilot Features: Copilot assistance now covers accounts payable, financial reporting, and order-to-cash processes.
- Power Automate Enhancements: Deeper integration with cloud flows allows Business Central data to trigger cross-application automations.
Customer Insights & Journey Optimization
Customer Insights expands AI-driven personalization and journey orchestration:
- Enhanced AI Segmentation: ML models now automatically identify high-value customer cohorts, churn-risk segments, and propensity-to-buy audiences without manual rule configuration.
- Journey Optimization: AI suggests optimal channel sequencing (email, SMS, push notification) and timing to maximize engagement while minimizing unsubscribe rates.
- Real-Time Personalization: Content and offer recommendations adapt in real time based on current session behavior, historical preferences, and predictive models.
- Cross-Cloud Integration: Unified customer profiles now seamlessly integrate data from Dynamics 365 Sales, Customer Service, Marketing, and third-party sources.
What to Expect: 2026 Release Wave 1 (Apr–Sep 2026, Currently Active)
Based on Microsoft’s published roadmap and historical patterns, 2026 Release Wave 1 is expected to focus on:
- Deeper AI Integration: Further agentic capabilities in low-automation areas (e.g., human resources, project operations).
- Performance & Scale: Infrastructure improvements supporting larger datasets, higher transaction volumes, and reduced query latency.
- Interoperability: Enhanced integrations with third-party AI services (OpenAI, Anthropic) and expanded Microsoft Graph integration.
- Security & Compliance: Advanced threat detection, zero-trust networking, and expanded industry-specific compliance features (healthcare, financial services).
- Industry Cloud Acceleration: Continued investment in vertical solutions for healthcare, financial services, retail, manufacturing, and sustainability.
Preparing for Release Waves: Best Practices
Sandbox Testing Strategy
Organizations should activate early access features in a dedicated sandbox environment 4–6 weeks before GA. This window allows teams to:
- Test business process impacts and identify required customization updates.
- Validate third-party integrations, ISV solutions, and custom code compatibility.
- Plan user training and change management initiatives.
- Document configuration changes needed to support new features.
- Prepare support team runbooks for new functionality.
Change Management & User Adoption
Effective change management increases user adoption and ROI from new features:
- Executive Sponsorship: Secure C-level support for new capabilities and allocate budget for training and change initiatives.
- User Feedback Loops: Conduct focus groups with power users to identify feature adoption barriers and customize rollout communication.
- Training & Documentation: Develop role-specific training materials and update system documentation to reflect new workflows.
- Phased Rollout: Enable new features for pilot groups first, gather feedback, then roll out organization-wide.
- Support Readiness: Equip support teams with documentation, troubleshooting guides, and escalation paths for new functionality.
Accessing Early Access Features
To enable early access in your Dynamics 365 environment:
- Navigate to Settings > Features > Preview Features in your Dynamics 365 admin center.
- Select Enable Early Access for your sandbox environment.
- Review the early access feature list and enable specific capabilities for testing.
- Submit feedback through the in-product feedback button to influence final feature design.
- Document testing results and submit to your implementation partner or Microsoft support team.
Dynamics 365 Migration Costs: What to Budget for GP, NAV, and AX Upgrades [2026]
Complete breakdown of ERP migration costs. Budget ranges for Dynamics GP→BC ($50K-$250K), NAV→BC ($30K-$200K), AX→F&O ($150K-$750K). What's included and hidden costs.
Read MoreLegacy Products: End-of-Life Timeline
Microsoft is sunsetting older Dynamics products to focus investment on cloud-native Dynamics 365:
- Dynamics SL (Solomon): Mainstream support for Dynamics SL 2018 ended January 9, 2024, with extended support continuing through July 11, 2028. Organizations should migrate to Project Operations or Dynamics 365 Project-based services.
- Dynamics GP (Great Plains): Follows the Modern Lifecycle Policy with a single retirement date of December 31, 2029 (security patches continue through April 30, 2031). Migration paths exist to Dynamics 365 Finance or Business Central depending on complexity.
- Dynamics NAV (Navision): The most recent version (NAV 2018) has mainstream support ended January 10, 2023, with extended support through January 11, 2028. Business Central is the recommended migration platform.
- Dynamics AX 2012: Extended support for Dynamics AX 2012 R3 ended January 10, 2023. Dynamics 365 Finance is the successor product.
Organizations running legacy products should begin migration assessments immediately to avoid support gaps and ensure access to modern AI and cloud capabilities.
How Dynamics 365 Compares: Release Velocity & Feature Innovation
Dynamics 365 vs. SAP
SAP (Semi-Annual Updates): SAP S/4HANA Cloud Public Edition follows a semi-annual release schedule with major releases in February and August each year. Between major releases, smaller non-disruptive feature drops are delivered. Feature maturity varies—some innovations require multiple release cycles before general availability.
Dynamics 365 Advantage: Twice-yearly release waves provide greater planning predictability. More importantly, Dynamics 365 features typically reach GA with production-grade maturity, reducing post-release stabilization periods.
Dynamics 365 vs. Oracle
Oracle (Quarterly Updates): Oracle Cloud Infrastructure (OCI) and Oracle ERP Cloud follow quarterly release schedules (February, May, August, November). Oracle Cloud Applications receive feature updates quarterly, but configuration options and customization depth can obscure feature discoverability.
Dynamics 365 Advantage: Dynamics 365’s release notes are exceptionally detailed, feature toggles are transparent, and Microsoft provides community feedback loops through the Ideas Portal and early access programs. Organizations experience fewer surprise behavior changes and have greater control over feature enablement timing.
AI & Agentic Capability Leadership
Dynamics 365’s 2025 Release Wave 2 represents an inflection point in enterprise AI adoption. The deep integration of autonomous agents across Sales, Customer Service, and Field Service, combined with MCP agent development capabilities in Finance and Supply Chain, positions Dynamics 365 ahead of competing platforms in agentic system maturity.
SAP and Oracle are investing heavily in AI, but Dynamics 365’s native Copilot architecture and Model Context Protocol support provide structural advantages for organizations building custom intelligent workflows.
Key Takeaways
- Microsoft’s release wave system—twice yearly in April and October—ensures predictable feature cadence and testing windows.
- Early access features become available 4–6 weeks before general availability, allowing organizations to validate changes in sandbox environments.
- 2025 Release Wave 2 (Oct 2025–Mar 2026) brought autonomous agents to Sales, Customer Service, and Field Service; advanced dual-write improvements; and MCP agent development capabilities. 2026 Release Wave 1 is now active (Apr–Sep 2026).
- Organizations should establish sandbox testing protocols, change management programs, and user training initiatives to maximize adoption of new features.
- Legacy product support windows: Dynamics GP retires December 31, 2029 (security patches through April 30, 2031); Dynamics NAV 2018 extended support ends January 11, 2028. Migration planning should begin immediately.
- Dynamics 365’s release velocity and agentic capabilities provide competitive advantages over SAP’s semi-annual S/4HANA Cloud releases and Oracle’s quarterly Cloud Applications updates.
- Monitor the published roadmap and leverage early access programs to prepare for upcoming releases and maximize business value.
Frequently Asked Questions
1What’s the difference between Wave 1 and Wave 2 releases?
Wave 1 (April–September) and Wave 2 (October–March) are distinct release cycles. Wave 1 typically focuses on foundational features and infrastructure improvements, while Wave 2 often includes more complex agentic capabilities and AI enhancements. Both waves follow identical processes: early access 4–6 weeks before GA, with optional feature toggles post-GA.
2When should we enable early access features in our sandbox?
Enable early access 4–6 weeks before the wave’s general availability date. This window provides sufficient time for your team to test functionality, validate customizations, identify integration impacts, and plan user training. Waiting until after GA limits your testing window and increases the risk of production issues.
3Are all new Dynamics 365 features mandatory?
No. Most features ship with toggles allowing organizations to opt in at their own pace. Some infrastructure or security updates may be mandatory, but Microsoft provides advance notice. Critical updates typically remain optional for 30–90 days post-GA, giving organizations time to prepare.
4How do I access the Dynamics 365 roadmap?
Visit <strong>Microsoft Learn > Dynamics 365 Release Plans</strong> or access the <strong>Power Platform Release Plans</strong> portal. Microsoft publishes detailed release notes in March (Wave 1) and September (Wave 2). Your Microsoft account manager can also provide access to private roadmap sessions and briefings.
5What’s the migration timeline for Dynamics GP and NAV?
Dynamics GP follows Microsoft’s Modern Lifecycle Policy with a retirement date of December 31, 2029 (security patches through April 30, 2031). Dynamics NAV 2018 (the last NAV release) entered extended support, which ends January 11, 2028. Organizations should begin migration assessments as soon as possible to ensure sufficient time for transition to Dynamics 365 Finance or Business Central before support windows close.
6How does Dynamics 365’s release cadence compare to SAP and Oracle?
Dynamics 365 releases twice yearly (April and October). SAP S/4HANA Cloud Public Edition follows a semi-annual schedule (February and August). Oracle ERP Cloud releases quarterly (February, May, August, November). While quarterly updates offer more frequent drops, Dynamics 365’s semi-annual cycle offers better planning predictability and typically features production-grade feature maturity at GA. Dynamics 365 also provides more transparent release notes and community feedback mechanisms.
7What’s the Model Context Protocol (MCP) and how does it relate to Release Wave 2?
MCP is an open standard enabling AI models to interact with external tools, data sources, and business systems. In Dynamics 365 Finance and Supply Chain, MCP enables organizations to build custom autonomous agents that handle workflows like accounts payable, procurement, and demand forecasting. This represents a major shift toward agentic automation in enterprise processes.
8How should we plan change management for new features?
Establish a phased approach: (1) test in sandbox 4–6 weeks pre-GA, (2) gather feedback from power users and stakeholders, (3) develop role-specific training and documentation, (4) pilot new features with a user group, (5) enable for organization-wide rollout post-pilot. Secure executive sponsorship and allocate dedicated change management resources to maximize adoption.
Related Reading
Copilot in Dynamics 365: AI-Powered Automation Across Sales, Service & Operations
Deep dive into Copilot capabilities across Dynamics 365 modules, including autonomous agents, real-time assistance, and enterprise AI architecture.
Microsoft Dynamics Legacy Product End-of-Life Timeline [2026]
Complete timeline of end-of-life dates for Dynamics GP, NAV, SL, and AX, with migration paths to Dynamics 365 Finance and Business Central.
Dual-Write in Dynamics 365: Architecture, Setup & Troubleshooting
Technical reference for asynchronous dual-write, synchronization patterns, and performance optimization in Dynamics 365 and Dataverse.
Migrating from Dynamics GP & NAV: Strategy, Timelines & Partner Selection
Comprehensive migration guide for organizations moving from legacy on-premises Dynamics to cloud-based Dynamics 365 or Business Central.