Updated October 2026
Microsoft’s retirement of its twice-yearly release wave plans changes how organizations track what’s coming to (Finance and Supply Chain Management). Instead of publishing announcements twice a year, Microsoft now posts upcoming Dynamics 365, Power Platform, and Dataverse capabilities to its continuously updated AI at Work roadmap. The way updates are built and delivered stays the same; F&SCM service updates keep their established schedule. What changes is how teams learn about upcoming changes. For finance, supply chain, and IT teams, that means paying closer attention to individual roadmap items, understanding which changes are mandatory, and preparing for new AI capabilities that can do more than answer questions.
Key Highlights
- Microsoft has retired the twice-yearly release wave announcements in favor of a continuously updated AI at Work roadmap. F&SCM update delivery is unchanged.
- The Release Planner retires on November 15, 2026.
- Dynamics 365 F&SCM version 10.0.49 includes supplier collaboration, planning, warehouse, and cash management improvements.
- Some updates are mandatory in production environments, making it important to distinguish required changes from optional features.
- Copilot is evolving toward AI agents that can perform tasks within existing ERP permissions and business rules.
What Does the End of Release Waves Mean for Dynamics 365 F&SCM?
Dynamics 365 F&SCM has shipped through under Microsoft’s One Version model for years, and that does not change. What changes is how Microsoft announces upcoming capabilities. Previously, teams could use the twice-yearly release wave plans to review upcoming capabilities, assess their impact, and coordinate implementation plans around a predictable schedule.
That model has now been retired. Dynamics 365, Power Platform, and Dataverse now publish upcoming capabilities to the AI at Work roadmap as they are committed. Microsoft says the change doesn’t affect how products are built, released, or deployed, and products with established release schedules keep following them. Organizations that relied on release wave announcements as their main planning tool will need to adjust their approach.
Microsoft will retire the Release Planner by November 15, 2026. Personalized views saved there will not carry over, so teams that depend on it should rebuild their tracking before then.
The practical challenge is not more frequent updates. It is establishing a reliable way to determine what has changed, when a change takes effect, and whether it requires action from finance, supply chain, or IT.
Why Is ERP Update Planning Becoming More Important?
Without a twice-yearly release plan to review, it can be harder for organizations to anticipate changes that affect everyday work. Teams can no longer rely on a single planning cycle to review everything that may affect their operations.
Finance teams have a particular reason to pay attention. More than half of finance teams still take over a week to close their books, and month-end close already places considerable demands on staff. An ERP update that changes a report, moves a field, or alters a familiar process can add complications when teams are already working against deadlines.
The end of the release wave model does not create these pressures, but it removes one of the planning tools organizations used to manage them. Instead of reviewing planned changes in two release wave plans, teams must evaluate roadmap items as they are published and determine how each one affects existing processes.
Supply chain and IT teams face a similar challenge. Changes to planning, warehouse operations, or system configuration may require review and coordination, even when they surface as individual roadmap items rather than in a release wave announcement.
A practical response is to make update review an ongoing responsibility. Teams should identify who monitors changes, assess the impact on business processes, and determine which updates need testing, communication, or other preparation. The goal is to replace a predictable release calendar with a repeatable process for managing change.
What's New in Dynamics 365 F&SCM Version 10.0.49?
Dynamics 365 F&SCM version 10.0.49 shows why this matters. Its new capabilities would previously have been summarized in a release wave plan; now teams need to track them through the roadmap and the release notes.
The current update includes several areas of development:
- Supplier collaboration: A new Supplier Engagement tool supports collaboration with suppliers.
- Planning improvements: Updates provide enhancements in planning capabilities.
- Warehouse improvements: Warehouse-related functionality continues to advance.
- Cash management: The update includes cash management upgrades.
For organizations using F&SCM, understanding the available features is only part of the work. Teams also need to know which capabilities are optional and which changes are mandatory in production environments.
That distinction matters because a mandatory change is not simply another feature to consider when convenient. If a change is already required in production, the organization needs to understand its implications and prepare accordingly. Knowing the status of an update helps teams avoid surprises and reduces the risk of discovering a change only after it affects daily operations.
The version 10.0.49 update reinforces the need for regular review. Rather than assuming that significant changes will be summarized in a twice-yearly release plan, organizations need to track individual updates and understand how they affect their particular use of the system.
How Is Copilot Changing the Way Teams Use Dynamics 365 F&SCM?
Alongside the roadmap change, Microsoft is advancing AI capabilities that could change how employees interact with enterprise applications. Copilot is moving beyond a chat experience that answers questions toward AI agents capable of carrying out tasks within business systems.
The broader shift is significant. Gartner expects 40% of enterprise applications to feature task-specific AI agents by 2026, compared with fewer than 5% in 2025. This projection highlights the growing role of AI that can perform defined tasks rather than simply provide information.
Within an ERP environment, this direction opens up different possibilities for everyday work. Western Computer highlights Copilot capabilities such as generating a cross-company view that native reports may not provide and turning a customer email into a quote or sales order. These activities go beyond retrieving information because they involve helping complete work within the system.
Permissions and business rules remain important to this approach. AI agents operate within the controls that govern the ERP environment, rather than being treated as separate tools with unrestricted access.
For finance teams, the potential value is especially relevant when existing processes depend on repeatedly gathering information, reviewing reports, and waiting for the next step. AI-assisted task execution represents a different way of approaching work, although organizations still need to understand the capabilities available to them and how those capabilities fit their processes.
How Can Teams Prepare for the End of Dynamics 365 Release Waves?
Organizations can begin by treating update management and AI adoption as connected parts of their ERP planning.
First, establish a regular process for reviewing Dynamics 365 F&SCM updates. Identify the changes that affect your environment and determine whether they are mandatory or optional. Second, evaluate their implications for finance, supply chain, and IT workflows, paying particular attention to reports, fields, and established procedures.
Finally, review emerging Copilot capabilities in the context of actual business tasks. Consider where AI-assisted work could change existing processes and what permissions, business rules, and operational requirements need to be understood before adoption.
Frequently Asked Questions
Q: What replaced Microsoft's twice-yearly release wave model?
A: Microsoft now publishes upcoming Dynamics 365, Power Platform, and Dataverse capabilities to its continuously updated AI at Work roadmap. The change affects how updates are announced, not how they are delivered.
Q: When does the existing Dynamics 365 Release Planner stop being available for reference?
A: The Release Planner retires on November 15, 2026.
Q: What does Dynamics 365 F&SCM version 10.0.49 include?
A: It includes a new Supplier Engagement tool, planning and warehouse improvements, and cash management upgrades.
Q: Are all F&SCM updates optional?
A: No. Some changes become mandatory in production environments, so teams need to distinguish required changes from optional features.
Q: How is Copilot evolving in enterprise applications?
A: Copilot is moving beyond answering questions toward AI agents that can perform tasks within enterprise systems while operating under existing permissions and business rules.
Preparing for the Next Stage of Dynamics 365 F&SCM Updates
The end of release wave plans and the evolution of Copilot both point toward a more ongoing approach to ERP management. Teams will need to monitor changes regularly, understand which updates require action, and evaluate how emerging AI capabilities fit their business processes.
For organizations using Microsoft Dynamics 365 Finance and Supply Chain Management, the next step is to review current update practices and identify where more consistent monitoring and preparation would help. Western Computer is ready to help you learn more about these developments and consider what they mean for your team. our experts today.
By Western Computer,
The article is misleading. There is no change in how Microsoft ships the updates, just how they are going to be annunced.
Thank you, Caroline. You're right: Microsoft's change affects how upcoming capabilities are announced (release wave plans and the Release Planner are giving way to the AI at Work roadmap), not how F&SCM updates are built or delivered. We've corrected the article to reflect that. We appreciate you taking the time to point it out.