If you run Dynamics 365 Finance & Operations, you cannot avoid the question of how to test it. Microsoft ships updates on a continuous One Version cadence, your environment is almost certainly customized and integrated, and a single missed regression in a finance process can post the wrong numbers to your ledger. The Regression Suite Automation Tool, RSAT, is Microsoft’s own free answer to that problem, and for many D365 teams it is the first automation tool they ever touch.
This guide explains exactly what RSAT is, how it actually works end to end, what it costs, where it genuinely helps, and, just as important, the specific limits that lead many teams to outgrow it. Unlike most explainers on this topic, we go past the definition into the real mechanics and the 2026 reality of testing an increasingly AI-driven ERP, so you can decide whether RSAT is enough for your team or only a starting point.
Quick answer Dynamics 365 RSAT (Regression Suite Automation Tool) is a free Microsoft tool that lets functional power users record business processes in D365 Finance & Operations with Task Recorder and turn those recordings into automated regression tests, executed through Azure DevOps, no coding required. It is powerful for standard F&O regression testing but is limited to F&O only, runs on Windows, and needs re-recording when the UI changes.
Why testing Dynamics 365 F&O is non-negotiable
Before RSAT makes sense, it helps to be clear on what it is defending against. Dynamics 365 Finance & Operations is a system of record: it runs the processes your business cannot get wrong, order-to-cash, procure-to-pay, period close, tax, and payroll. Three forces make keeping it correct genuinely hard.
- Continuous updates. Under Microsoft’s One Version model, every environment receives service updates on a fixed schedule. Fewer, larger updates means each one carries more regression risk and cannot be skipped.
- Heavy customization. Almost no F&O deployment is vanilla. Extensions and configurations mean Microsoft’s testing cannot cover your specific setup, that responsibility is yours.
- Deep integrations. F&O rarely runs alone. It exchanges data with CRM, banks, tax engines, and third-party systems, so a change in one place can surface as a defect somewhere else entirely.
Regression testing, re-checking existing processes every time something changes, is the core defense. It is also the single most resource-hungry part of D365 QA, which is exactly the pain RSAT was built to relieve.
What is RSAT (the Regression Suite Automation Tool)?
RSAT is a free tool from Microsoft that automates the regression testing of business processes in Dynamics 365 Finance & Operations. Its core idea is elegant: rather than asking testers to write code, it lets a functional power user, someone who knows the business process, not necessarily a developer, record that process once and replay it automatically as many times as needed.
The purpose is to shrink the cost and time of user acceptance testing (UAT), the round of validation you run before accepting a Microsoft update or pushing custom code to production. Test parameters are separated from the test steps and stored in Excel files, so the same recorded process can be re-run with different data. RSAT is fully integrated with Azure DevOps, which handles execution, reporting, and investigation. Under the hood, the browser automation is driven by Selenium, which RSAT installs and manages for you.
What RSAT is not RSAT is not a full test-automation platform. It does not cover Sales, Customer Service, Business Central, or any application outside F&O; it does not do true end-to-end testing across systems; and it does not self-heal when the interface changes. Understanding those boundaries up front saves teams from expecting more than the tool was designed to give.
How RSAT works, step by step
Most articles define RSAT and stop. But you cannot judge whether it fits your team without seeing the actual workflow, because the workflow is where the effort, and the friction, lives. Here is the full path from a business process to an automated test result.
Step 1, Record the process with Task Recorder
Inside F&O, you open Task Recorder and walk through the business process you want to test, say, creating and posting a sales order. Task Recorder captures every interaction step by step. When you finish, you save the recording, either to Lifecycle Services (LCS) or locally as a developer recording file.
Step 2, Sync through LCS and Business Process Modeler
The recording is associated with a process in the Business Process Modeler (BPM) library inside LCS. Syncing the BPM library with Azure DevOps converts those structured process recordings into test cases and pushes them into your connected DevOps project. This sync is what keeps your documented processes and your executable tests aligned.
Step 3, Organize test cases in Azure DevOps
In Azure DevOps you create a test plan, organize test suites, and map the recorded tasks to test cases. Azure DevOps becomes the system that stores and manages your recordings, parameters, and results, which is also why an Azure DevOps Test Plans license is a hard requirement (more on cost below).
Step 4, Configure RSAT and generate parameter files
You install RSAT on a Windows machine, point it at your Azure DevOps URL with a personal access token, and connect it to your F&O environment using an authentication certificate that RSAT can generate for you. You then load the test plan, download the test cases, and generate the Excel parameter files that hold the test data, decoupled from the steps so one recording can be reused with many data sets.
Step 5, Execute, validate, and report
With everything wired up, you click Run. RSAT drives the browser through each recorded step via Selenium, using the Excel parameters, and can check expected values with validation steps, for example, asserting that on-hand inventory is above zero or that a “Production started” message appeared. Results flow back into Azure DevOps, where you review pass/fail outcomes, logs, and screenshots, and can even generate sign-off work items for functional or IT approvers.
Read back through those five steps and the trade-off becomes visible: RSAT removes the need to write code, but replaces it with a genuine amount of setup, LCS, BPM, Azure DevOps, certificates, Excel files, and Selenium, that has to be maintained over time.
How much does RSAT cost?
RSAT itself is free, it is available to all Dynamics 365 Finance & Supply Chain Management customers at no charge. The real cost is the Azure DevOps Test Plans license required to work with test plans, which runs about USD $52 per user per month. For a demo or trial environment you do not need to buy a license, but any production testing program does. Beyond the license, the true cost is human: the setup time above and the ongoing maintenance below.
The benefits of RSAT
For its intended job, standard regression testing of F&O, RSAT delivers real value, which is why it remains the default first step for so many teams.
- It is free and first-party. No license fee for the tool, built by Microsoft, and designed specifically for the One Version update rhythm.
- No coding required. Functional power users can build tests from recordings, which widens who on the team can contribute.
- Faster, more consistent UAT. Automating repetitive regression cycles saves substantial manual effort and removes the human error inherent in manual testing.
- Data-driven reuse. Because parameters live in Excel, one recording can be run across many data scenarios, and test cases can be chained to pass variables between steps.
The limitations of RSAT, and why teams outgrow it
RSAT’s constraints are not hidden, even Microsoft points larger customers toward additional tooling for complex configurations. The honest picture is that RSAT is excellent at a narrow job and strained outside it. Four limits matter most.
1. High maintenance, tests break on change
RSAT recordings are tied to specific UI steps. When a One Version update or a customization shifts the interface, the affected tests break and must be re-recorded. Because that work needs both business and technical knowledge, it tends to bottleneck on a few skilled people, and the maintenance burden grows exactly as your test suite grows, which is when you can least afford it.
2. F&O only, no true end-to-end coverage
RSAT works with Dynamics 365 Finance & Operations and nothing else. It cannot test Sales, Customer Service, Business Central, or any of the non-Microsoft systems your processes touch. Real business flows cross those boundaries, an order that moves from CRM to F&O to a shipping system, and RSAT simply cannot follow them, which caps genuine end-to-end testing.
3. Setup complexity and technical dependency
As the five-step workflow showed, standing RSAT up means configuring LCS, BPM, Azure DevOps, certificates, and Selenium. It is Windows-only and expects a level of environment knowledge that many functional teams do not have in-house, which slows time-to-value and concentrates risk on a small group.
4. No self-healing and limited scope for modern D365
RSAT has no ability to adapt when the UI changes, it fails rather than heals. And as Dynamics 365 becomes increasingly agentic, with Copilot and autonomous agents now taking actions inside the ERP, RSAT was never designed to validate AI-generated behavior. That is a widening gap between what RSAT tests and what a 2026 D365 environment actually needs tested.
Translated into business terms, these limits show up as high total cost of ownership, slower time to market, and a lower return on your automation investment, the metrics that eventually push teams to look beyond RSAT.
RSAT vs. modern AI-agent testing: a clear comparison
The alternative to RSAT is no longer just “another record-and-replay tool.” AI test agents take a fundamentally different approach, understanding the business process rather than memorizing UI clicks, which directly targets RSAT’s weak points.
| Capability | RSAT | AI-agent testing (e.g. Sofy) |
| Coverage | D365 F&O only | F&O, Sales, Supply Chain, Business Central, SAP, and cross-system flows |
| Maintenance on UI change | Re-record broken tests manually | Self-heals at the workflow level, no re-recording |
| End-to-end testing | Not supported | Validates full processes across applications |
| Setup | LCS + BPM + Azure DevOps + certs + Selenium | No Azure DevOps or Selenium plumbing required |
| Who can build tests | Functional power users (with technical support) | Business users, no code |
| Validating Copilot / AI agents | Not designed for it | Validates AI-generated actions and outcomes |
| Validation depth | UI steps + Excel value checks | Outcome validation at the data layer |
So should you use RSAT?
RSAT is a sound choice if your testing needs sit squarely inside F&O, your team has the technical capacity to set it up and maintain it, and your priority is free, first-party regression automation for standard processes. Many teams rightly start here.
You will likely outgrow it if your processes cross into other Dynamics 365 apps or external systems, if the maintenance of breaking recordings is consuming your QA capacity, or if you need to validate the Copilot and agent-driven behavior that increasingly defines a modern D365 environment. In those cases RSAT is best seen as a starting point, not the destination, and the move to self-healing, cross-application AI-agent testing is what removes the ceiling.
Frequently asked questions
What is Dynamics 365 RSAT?
RSAT (Regression Suite Automation Tool) is a free Microsoft tool that automates regression testing of business processes in Dynamics 365 Finance & Operations. Functional power users record processes with Task Recorder and convert them into automated tests that run through Azure DevOps, without writing code. It is designed to reduce the time and cost of user acceptance testing before Microsoft updates or custom deployments.
Is RSAT free?
The RSAT tool itself is free to all Dynamics 365 Finance & Supply Chain Management customers. However, it requires an Azure DevOps Test Plans license to manage test plans, which costs roughly $52 per user per month. A demo environment does not need the license, but any production testing program does.
How does RSAT work?
You record a business process in F&O using Task Recorder, sync it through Lifecycle Services and the Business Process Modeler into Azure DevOps as a test case, configure RSAT on a Windows machine to connect to Azure DevOps and your F&O environment, generate Excel parameter files for your test data, then run the tests. RSAT drives the browser through the recorded steps via Selenium and reports pass/fail results back to Azure DevOps.
What are the main limitations of RSAT?
RSAT only works with Dynamics 365 F&O, so it cannot test other D365 apps or external systems or perform true end-to-end testing. Its recordings break when the UI changes and must be re-recorded, creating a heavy maintenance burden. Setup is technically complex, it is Windows-only, and it was not designed to validate Copilot or AI-agent behavior in modern D365 environments.
What are the best alternatives to RSAT?
Modern AI-agent testing platforms are the leading alternative. Unlike RSAT, they self-heal when the UI changes (no re-recording), test across the full D365 portfolio and external systems for true end-to-end coverage, require no Azure DevOps or Selenium plumbing, and can validate AI-generated actions from Copilot and autonomous agents. This directly addresses RSAT’s coverage, maintenance, and modern-D365 gaps.
Outgrowing RSAT? See What Modern D365 Testing Looks Like
Sofy’s AI agents test Dynamics 365 without the re-recording, the Azure DevOps plumbing, or the F&O-only ceiling, self-healing through every One Version update and validating outcomes at the data layer.
