If you have been running Dynamics 365 tests using RSAT, you have probably already seen the discussion.
At a recent Microsoft TechTalk, one message stood out:
RSAT is feature complete.
No new capabilities. No future roadmap expansion.
It continues to work today.
But it is not moving into a new phase of investment.
For many D365 QA leads and ERP managers, this was not entirely unexpected.
RSAT always solved a very specific problem.
The market evolved. Testing evolved. D365 environments evolved.
RSAT largely stayed where it started.
And now many teams are asking the question they postponed for years:
What comes next?
What RSAT Solved — And Where It Reached Its Limits
RSAT was built around a real challenge.
With D365 Finance & Operations and the One Version update model, testing became continuous. Businesses could no longer treat validation as a go-live activity. Wave updates made regression a recurring responsibility.
RSAT became Microsoft’s answer:
Record business tasks. Reuse Task Recorder assets. Automate validation. Connect with Azure DevOps.
For standard scenarios — it worked.
But D365 environments changed.
Customisations expanded. Integrations increased. Business logic became deeper.
And many teams discovered the same reality:
Most RSAT libraries were not regression suites. They were collections of UI recordings.
Every Wave update increased maintenance effort. Complex cross-functional scenarios remained difficult. Custom approval logic, modified finance mappings and bespoke integrations often sat outside meaningful coverage.
What “Feature Complete” Actually Means
- Current RSAT assets still work
Nothing breaks today.
“Feature complete” does not mean immediate retirement. But it does mean future investment is limited. As D365 evolves, teams should evaluate how their coverage evolves alongside it.
- Coverage gaps become more visible over time
New modules. New workflows. More integrations. More business rules.
D365 environments continue growing. Testing expectations grow with them.
The question becomes: will existing coverage scale with future requirements?
- Future automation decisions matter more now
For teams still expanding RSAT usage in 2026, this becomes a strategic discussion.
Not because RSAT disappears tomorrow.
Because long-term regression planning now matters more. The automation choices made today influence future flexibility.
What D365 Teams Are Doing Next
Three approaches are becoming common:
Path 1 — Low-code D365 testing platforms
Many teams move toward low-code testing tools with reusable D365 assets, Azure DevOps integration, broader scenario support and faster maintenance. These platforms often reduce effort compared with traditional RSAT maintenance.
The consideration: most still operate heavily at the UI layer. A tool that does not understand your custom approval workflow will still miss the same defects RSAT missed — just faster. Coverage quality depends on configuration, workflow understanding and business context.
Path 2 — Custom automation frameworks
Playwright. Selenium. SpecFlow. Maximum flexibility. Broader integration coverage. Deeper control.
The trade-off: higher build effort, ongoing maintenance, stronger engineering dependency. Usually better suited for mature internal QA teams.
Path 3 — Managed D365 QA approach
Some organisations combine pre-built D365 assets, domain expertise, tool flexibility and business workflow understanding.
The focus shifts from “Which tool do we buy?” to “What regression risk are we trying to reduce?”
Because manufacturing procurement logic is different from retail fulfilment. Financial controls differ from distribution workflows. Context matters.
The One Question That Decides Your Strategy
Before selecting tools — ask this:
How much of your regression risk sits inside customisations versus standard Microsoft flows?
If risk lives mostly inside standard scenarios — a low-code platform may be enough.
If risk sits in custom approvals, finance mappings, integrations, workflow exceptions and business rules built over years — then understanding those customisations becomes critical.
Tools help. Business understanding completes the picture.
This is the question RSAT was never really designed to answer.
And it may become the most important question of the next D365 testing phase.
Where Crestech Fits
We are not a RSAT replacement tool.
We help D365 teams understand existing coverage, customisation exposure, regression gaps, Wave readiness impact and future testing direction.
Tools matter. Business logic matters more.
If your team is reviewing what comes after RSAT, we are happy to have a practical discussion around what exists today, where risk concentrates and what a structured transition looks like.
No pitch. No tool-first recommendation. Just a working conversation.
If this was useful, share it with your QA lead, ERP manager or the team reviewing Wave readiness.
The RSAT conversation is no longer about replacement.
It is about regression strategy.
#Dynamics365 #D365FO #RSAT #ERPTesting #RegressionTesting #MicrosoftDynamics #D365Community #QualityAssurance #WaveRelease #D365Testing #CIO #CFO
