RSAT Is Being Retired in 2027. Here Is What Replaces It for D365 Regression Testing
Microsoft has confirmed that the Regression Suite Automation Tool (RSAT) will not be supported after May 15, 2027. Dynamics 365 Finance and Operations teams that rely on RSAT for regression testing now have a fixed deadline to move to a supported alternative. This article explains what the deprecation means, why many teams had already reached a ceiling with the tool, and how to plan the transition before the deadline arrives.
What Microsoft announced
RSAT is marked for deprecation, and Microsoft will stop supporting it on May 15, 2027. After that date there will be no technical support, no bug fixes, no updates, and no new features. Organizations can keep running RSAT, but they do so entirely on their own, with any issue that surfaces becoming theirs to resolve.
Microsoft's guidance for a deprecated feature is the same here: plan your migration before support ends rather than waiting. For teams with hundreds of business processes and a recorded test library built up over years, this is a real deadline that needs a real plan.
(Reference: Microsoft Learn, Removed or deprecated platform features for finance and operations apps, https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/fin-ops/get-…)
Why this was coming anyway
For many D365 Finance and Supply Chain teams, the announcement was not a surprise. RSAT had not been a major area of investment for some time, and the deprecation simply makes formal a ceiling that practitioners had been hitting for years.
That ceiling usually follows a familiar pattern.
Setup is front-loaded and heavy. Standing up RSAT means configuring environments, Azure DevOps test plans, authentication, and the recording-to-playback pipeline before a single meaningful test runs.
Recordings are brittle. Because test cases are generated from Task Recorder recordings, they are tied to the UI as it existed at recording time. When a wave release moves a field or changes a form, the recording breaks.
Maintenance compounds. Every release adds to the pile of recordings that need checking and repair. The cost grows with the size of your library rather than shrinking.
It is built around the Finance and Operations apps, including Cloud POS in Commerce. It does not extend to the wider Customer Engagement estate, and Microsoft's own documentation steers teams away from using it for integration testing, pointing them to the data management framework instead. Real programs are full of integration points, so a meaningful part of coverage falls outside what the tool was built for.
None of this is a reason to criticise RSAT. It did useful work for years. But it explains why teams were already looking for something that does not begin from a blank recording every release, and why the May 2027 deadline is an opportunity to fix the underlying problem rather than just replace the tool.
The alternative: assemble instead of construct
There are two ways to arrive at a D365 regression suite. You can construct it, recording and authoring every scenario yourself and owning all of the maintenance that follows. Or you can assemble it, starting from pre-built test journeys that already model how standard D365 processes behave.
A composable test library is the second approach. Instead of recording each process from scratch, you select the journeys relevant to your implementation, configure them to your data and environment, and automate their execution. The standard-process logic is already modeled, so your team's effort goes to the part of the implementation that is genuinely unique to your business.
The Virtuoso QA Composable Library carries over 1,000 pre-built journeys spanning Finance, Supply Chain Management, Commerce, the Customer Engagement apps, Business Central, Human Resources, and Project Operations. Because the journeys are built to be resilient rather than tied to a single recorded UI state, they hold up across releases instead of breaking with every form change. For teams migrating off RSAT, that resilience is the point: you carry your coverage forward without carrying the maintenance problem with it.
What to do before May 2027
The deadline sounds distant, but for an enterprise with a large recorded library, the transition can take months. A practical sequence looks like this.
- Inventory your current RSAT coverage. Identify which business processes are automated today and which are business critical.
- Find the gaps. Note where RSAT coverage is thin, brittle, or missing, especially around integration scenarios it was never designed for.
- Evaluate a supported alternative now, while you still have time to validate it properly rather than under deadline pressure.
- Migrate by carrying coverage forward, not by rebuilding from scratch. The goal is to come out of the transition with broader, more resilient regression coverage than you had before.
Teams that start now turn a forced migration into an upgrade. Teams that wait until the final year risk rushed decisions, higher cost, and a gap in regression coverage at exactly the wrong moment.
What this looks like across a wave release
The real test of any approach is what happens when Microsoft ships an update. Wave 1 2026 is rolling out now, and Wave 2 will follow later in the year. The cadence is fixed and it is not optional.
With a recording-based suite, each wave is a project. You find what broke, re-record or repair it, and validate the suite back into a working state before you can trust it again. With an assembled suite, each wave is a run. The journeys already exist and hold their shape, so you are validating coverage you already have rather than rebuilding it.
Construction gets heavier with every release. Assembly gets lighter, because the library absorbs the standard-process maintenance and your team's attention narrows to what actually differentiates your implementation.
Frequently asked questions
Is RSAT being deprecated? Yes. Microsoft has marked the Regression Suite Automation Tool for deprecation. It will not be supported after May 15, 2027, after which there will be no technical support, bug fixes, updates, or new features.
Can I keep using RSAT after May 2027? Technically yes, but without any Microsoft support. Any problem that surfaces becomes yours to resolve alone, and with wave releases continuing to change the D365 UI, an unsupported recording-based suite becomes harder to maintain over time.
What replaces RSAT for D365 regression testing? Teams are moving to composable testing, where regression coverage is assembled from a library of pre-built, maintainable journeys rather than recorded from scratch. You select the journeys you need, configure them to your environment, and automate execution across the full D365 estate.
How long does migrating off RSAT take? It depends on the size of your library, but for enterprises with hundreds or thousands of test cases the transition can take months. That is why Microsoft recommends starting now rather than waiting for the deadline.
See the library
You do not have to rebuild your D365 regression suite from a blank page before May 2027. The coverage already exists, and it is supported.
Explore the Composable Library for Dynamics 365: https://www.virtuosoqa.com/solutions/composable-library-dynamics-365