D365 F&O Continuous Updates: Governing Change After the End of Release Waves

Organizations running Dynamics 365 Finance and Operations (F&O) have worked with D365 F&O continuous updates for several years, but until recently they had a twice-yearly release plan explaining what those updates would bring. That reference point is gone. In August 2026, Microsoft confirmed that Dynamics 365 roadmap content would move to the AI at Work roadmap, with new capabilities published as soon as plans are committed instead of being collected into release wave 1 and release wave 2 announcements.

For F&O, the loss of the release plan lands on an update model that already carries a heavy volume of change. Microsoft ships four service updates a year, and since version 10.0.47 its proactive quality updates have arrived every two weeks instead of every 28 days. Together, that adds up to roughly 30 scheduled change events a year, each capable of touching general ledger posting, procurement, warehouse operations, or the integrations that connect F&O to banks, tax engines, and Dataverse.

The timing adds pressure. Microsoft's Regression Suite Automation Tool (RSAT), which many F&O teams use to validate updates, reaches end of support on May 15, 2027. Decision-makers across IT, finance, and risk therefore face two shifts in the same year: less advance visibility into what is coming, and the retirement of a tool many organizations relied on to confirm what had changed. How update validation is planned, owned, and evidenced in 2027 deserves a deliberate leadership decision.

Key Takeaways for Executive Leadership

1. D365 F&O continuous updates now arrive without a release plan to summarize them, so the service update calendar, Message Center, and each version's What's New page become the primary planning inputs.

2. Four service updates, biweekly quality updates, and features moving to mandatory status create a volume of change that manual regression testing cannot cover consistently.

3. With RSAT support ending in May 2027 and auditors paying closer attention to technology controls, update validation needs a documented method that will hold up through future releases.

What the End of Release Waves Means for Finance and Operations

Microsoft has framed the change as one of disclosure. Its announcement states that products with established release schedules will continue to follow them, and that Message Center remains the channel for tenant-specific change notices. The F&O service update schedule is therefore unchanged, which keeps the dates predictable even though the content is now revealed item by item on the AI at Work roadmap.

What F&O teams lose is a single document that grouped six months of functional change by module. Finance, supply chain, and IT leads used release plans to decide which business processes deserved deeper testing before a given service update. That triage now has to be assembled from individual roadmap entries, version release notes, and the preview build itself, which places more of the interpretation on the customer's own team.

The F&O Service Update Schedule Now Sets the Planning Calendar

The mechanics of D365 F&O continuous updates are published well in advance. Under the current service update policy, Microsoft releases service updates in February, April, July, and October. Customers can take all four and must take at least two, and they can pause only one update at a time. Each version is available as a preview roughly two months before general availability, and the sandbox auto update runs seven days before production. Version 10.0.51 reaches general availability on March 12, 2027, and 10.0.53 on September 10, 2027.

Proactive quality updates run beneath that cycle. Starting with 10.0.47, Microsoft moved these cumulative builds of platform and application fixes from a 28-day schedule to a two-week cadence, with production receiving each build at least five days after sandbox environments. Fixes reach customers sooner as a result, and the time available to confirm that nothing else shifted is now measured in days.

Each type of change in F&O follows its own rhythm and gives the customer a different degree of control, which is why one testing approach rarely suits all of them. The table below summarizes the differences.

Mandatory Features and RSAT Retirement Raise the Stakes

Feature management gives F&O customers time to adopt new behavior, but that time is limited. In version 10.0.49, about 38 features became mandatory, 14 were turned on by default, and 10 were removed from Feature management and made permanent. Several of them sit close to the ledger, including customer and vendor netting and cash control. A feature that was safely deferred last year can become active in production with the next service update, and the processes it touches need testing before that happens.

The retirement of RSAT compounds the timing problem. Microsoft will stop issuing updates and fixes for the tool after May 15, 2027, a date that falls during the preview period for version 10.0.52. Organizations still relying on RSAT for regression coverage would be running an unsupported tool against a platform that changes every two weeks, and the distance between those two rates of change grows with each release.

What Audit Data Says About Technology-Related Control Failures

For technology and finance leadership alike, the most persuasive case for structured update validation comes from audit outcomes. Deloitte's February 2026 analysis of internal controls, drawing on Audit Analytics data from December 2025, reports that 61 percent of companies disclosing a material weakness in the previous 12 months had a technology component in that weakness. Ninety-eight percent of disclosed material weaknesses had a documentation component, and 64 percent were attributed to inadequate personnel to operate controls.

Those findings map closely onto F&O update practice. A service update applied without recorded validation is a change-management event with no evidence trail, which mirrors the documentation gap that appears in almost every disclosed weakness. Regression testing that depends on a handful of finance users finding time between close cycles is the personnel gap in another form. Both tend to surface in audit as technology control weaknesses, even when the underlying cause is capacity.

Testing practice across the market helps explain why these gaps persist. The World Quality Report 2025-26, based on 2,000 interviews with senior IT executives, found that only 6 percent of enterprises use generative AI in ERP testing, and that integration complexity, cited by 56 percent, is the leading challenge in enterprise quality engineering. F&O estates, with dual-write to Dataverse, data entities feeding external systems, and ISV solutions layered over standard modules, sit squarely inside that integration problem.

Building F&O Regression Testing Around a Continuous Cadence

A testing model that fits the F&O calendar usually scales the depth of validation to the weight of each change:

1. For every proactive quality update, run a focused suite against the sandbox during the five-day window, covering the financial flows where an unexpected change would reach the ledger.

2. For every service update, run the full regression suite against the preview or user acceptance testing environment, including integrations and ISV extensions, and record results against the version number.

3. Before a feature becomes mandatory, test the affected scenarios with the feature enabled, so its enforcement in production has already been validated.

4. Store the evidence from all three in the change record, where internal and external auditors can review it.

Running that model by hand would ask finance and supply chain users to test almost without pause, which is the workload Elevaite365's Finance and Operations testing approach is designed to absorb. Teams can import existing Task Recorder recordings as they are or capture live processes as editable, reusable steps, and organizations moving off RSAT have a direct conversion path for the coverage they have already built.

End-to-end scenarios such as order to cash and procure to pay can span F&O and connected systems, run unattended on a schedule, and execute in parallel so a full regression pass fits overnight. Tests adjust when Microsoft changes the interface, and each run produces step-level evidence, with screenshots, timings, and playback, packaged for sign-off and audit review.

In practice, the five-day quality update window and the seven-day service update window become periods in which full validation is realistic, so teams no longer have to trade coverage for timeliness. Leaders weighing the investment can estimate the cost of their current manual cycles with the Elevaite365 ROI calculator.

Making D365 F&O Continuous Updates an Audited Discipline

D365 F&O continuous updates will keep arriving on Microsoft's published schedule in 2027, and the absence of release plans will not slow them down. What shifts is how much of the interpretation, prioritization, and proof now sits with each organization. Leadership teams that define who reviews the roadmap, which processes are tested at each type of update, and where the evidence is kept will be able to answer an auditor's questions about any release without reconstructing events after the fact.

With RSAT support ending in May and four service updates already on the calendar, 2027 is a natural point to formalize that model. Organizations that act early will spend the year validating change on their own terms, while those that wait are more likely to be choosing tools and processes under the pressure of a live update cycle.

Frequently Asked Questions

Are release waves ending for Dynamics 365 Finance and Operations?

Yes, as an announcement format. Since September 2026, Microsoft no longer publishes release plans for Dynamics 365, and new F&O capabilities appear on the AI at Work roadmap once they are committed.

The service update schedule itself has not changed. F&O versions continue to follow the published calendar, and Message Center and the What's New page for each version remain the most dependable sources for what a specific update contains.

How many service updates does F&O receive each year?

Four, released in February, April, July, and October. Customers must take at least two per year and can pause only one update at a time.

If a pause ends and the environment has not been updated to a supported version, Microsoft applies the latest update automatically. Planning to fully test at least two updates a year, and preferably all four, avoids being moved onto a version that has never been validated.

What are proactive quality updates in F&O?

They are cumulative builds of platform and application fixes, applied every two weeks starting with version 10.0.47. Production environments receive each build at least five days after sandbox environments.

Because they are frequent and cumulative, quality updates can change existing behavior between service updates. The five-day gap between sandbox and production is the practical window for confirming that critical processes still behave as expected.

Should every proactive quality update be regression tested?

Critical financial processes should be, using a focused suite instead of the full library. The full suite is usually reserved for service updates and feature changes.

Exposure is the deciding factor. Processes that post to the general ledger, generate payments, or feed regulatory reporting carry the highest cost if a fix alters their behavior, so they belong in the suite that runs every two weeks.

How does RSAT end of support affect F&O update testing?

RSAT stops receiving updates and fixes after May 15, 2027, so Microsoft will no longer keep it compatible with new F&O versions. Teams that still depend on it should plan their migration before the 10.0.52 cycle.

The tool is likely to keep running for a while after that date, but each new service update and quality update raises the chance of incompatibility. Converting existing RSAT test cases while they can still be checked against a known, working version protects the investment already made in that coverage.

elevaite365 is a Microsoft-focused solutions provider specializing in test automation for Dynamics 365 applications. Learn more at elevaite365.com.

A note on statistics used in this article:

1. The Deloitte material weakness figures (61 percent of companies disclosing material weaknesses had a technology component; 98 percent of disclosed material weaknesses had a documentation component; 64 percent were due to inadequate personnel operating controls) are sourced from Deloitte's article on internal controls and material weakness prevention, published February 27, 2026, which cites Audit Analytics data from December 2025 covering the preceding 12 months. Deloitte is a Big 4 professional services firm, and Audit Analytics is an independent research provider tracking public company disclosures.

2. The World Quality Report 2025-26 figures (6 percent of enterprises using generative AI in ERP testing; integration complexity cited by 56 percent as the leading enterprise quality engineering challenge) are sourced from the 17th edition of the report, based on 2,000 interviews with senior IT executives in 23 countries conducted by Coleman Parkes Research in June and July 2025 and published in November 2025. The report is co-published by Capgemini, Sogeti, and OpenText. Capgemini is an independent global consulting and research firm.

3. Schedule and product details (service update cadence, proactive quality update cadence, version 10.0.49 feature changes, and RSAT end of support) are sourced from Microsoft's AI at Work roadmap announcement and Microsoft Learn documentation on service updates, proactive quality updates, version 10.0.49, and RSAT.