UAT Studioby Salvion
Dynamics 365 UAT

User acceptance testing for Dynamics 365

For the go-live of Dynamics 365 Sales or Customer Service, and for the updates that follow. Business testers get their own scripts, issues come in with the screenshot and the record, and the steering committee gets a clear go/no-go.

Testers never need a licenceReady-made scripts for Sales and Customer ServiceData stored in the EU
Start a free 14-day pilotSee pricing
Who it is for

For everyone in a Dynamics 365 UAT

UAT Studio was built from real Dynamics 365 go-lives, by a consultant who ran them himself. It fits a Microsoft team: sign in with Microsoft, issues to Azure DevOps, updates in Microsoft Teams.

Test leads and project managersPlan the test days, follow progress per group and run the triage.
Dynamics 365 consultants and developersSend issues to Jira or Azure DevOps and see at once what to retest.
Implementation partnersRun the UATs of all your clients in one place, with your own logo on the Partner plan.
Business testersAccount managers and service agents who test their own processes, without training in a test tool.
Process owners and the steering committeeSign off per group and decide on the go/no-go with facts.
The hard parts

What makes a Dynamics 365 UAT hard, and how UAT Studio handles it

A CRM UAT is tested by people who do not test for a living, in an environment that keeps changing, against a date that does not move. This is how UAT Studio handles each part.

Business testersPeople who test once or twice a yearYour testers are account managers and service agents with a day job. They need a clear script and one place to record what they see.
  • They sign in with a code by email: no account, no password, no licence
  • Each tester sees only their own scripts, and records Pass, Fail, Blocked or N/A per step
  • On a laptop, a tablet or a phone
  • The browser extension for Chrome and Edge opens their tests in a side panel next to Dynamics 365; your test lead tells testers where to get it
EnvironmentsWhich environment, which build?The UAT runs in a test environment, and new solutions are imported while testing goes on. Everyone has to know what was tested where.
  • The environment, release and build are kept per round, and shown on the go/no-go report
  • An issue links straight to the Dynamics 365 record where it went wrong
  • A fail in the side panel takes a screenshot, the record link and the error messages of the page along
Test dataThe right user and the right recordsA case can only be routed or approved by the right security role, with the right queue and the right customer. Testers lose hours when that is not ready.
  • A test role and a test account per tester: their script says Log in as …
  • Test data per step, next to the action and the expected result
  • Notes for testers for test mailboxes, naming rules and who to call
  • Export or delete everything at the end of a project
The release calendarUpdates all year roundMicrosoft no longer bundles Dynamics 365 changes in two release waves a year. New features roll out all year and are announced on the Microsoft roadmap, and any of them can change how your system works. Test again on a fixed rhythm, before the changes reach your users.
  • Each project follows a rhythm, every month or every quarter, and the projects page shows the current period with a link to the Microsoft roadmap
  • Admins get one email per period, two weeks before it starts
  • Start a regression round copies the test cases of an earlier UAT, with their steps, test data and expected results: Must only, Must and Should, or all
Sign-offA decision the business stands behindThe go-live is decided by the business, not by the project. They need to see what was tested and what is still open.
  • Sign-off per group: Accepted, Accepted with conditions or Rejected
  • By default, no acceptance while a Critical issue is open
  • The go/no-go report as a PDF or slides, and an evidence pack for auditors

New to a Dynamics 365 UAT? The environments, security roles, test data, testers and sign-off, step by step: Read the guide.

Release readiness

Know which test cases a Dynamics 365 update touches

Salvion imports the items of the Microsoft roadmap, files each under an app and checks it. Per month or per quarter, you see the items for the apps you use, with their status, and review them in one go.

What this project usesTick once on Setup which parts of Dynamics 365 your UAT covers. Only the changes under those parts count.
Review the releaseAI shows your test cases the release touches, with the reason, proposes test cases for what is not covered yet and lists the required updates for your admin, with their dates.
The regression roundCreate it with exactly the test cases you chose. A reminder comes when it is not signed off 3 days before production, and the release report goes into the go/no-go report.

An add-on of €99 per month for every plan: add it under Plan & billing. What goes to the AI

Start faster

Start from what you already have

Template library Dynamics 365Ready-made UAT scripts for Dynamics 365 Sales and Customer Service: leads and the business process flow, products and quotes, approvals, Outlook, forecasts, cases from email, unified routing, SLAs, knowledge management, Copilot, the customer portal and security roles. An add-on to every paid plan; the test cases you import stay yours.
An example projectAdd a Dynamics 365 example to your workspace: a complete project with test cases, testers, results and issues to click through, with fictional data.
Your own test casesImport them from Excel, or from exports of Jira (Xray, Zephyr Scale), Azure DevOps and TestRail.
AI test designTest cases proposed from your user stories in Jira or Azure DevOps. You approve each one. It can also run on the AI model of your company, such as Microsoft Foundry / Azure OpenAI, the route for Microsoft Copilot users too. How it works
Automated tests next to the UATThe JUnit report of EasyRepro, Playwright or your own tests on the dashboard, next to the results of the business. An add-on of Team, included in Business and up. Automated tests
Questions

Dynamics 365 UAT: questions we hear often

Does UAT Studio need access to our Dynamics 365 environment?

No. Testers work in your test environment as they always do. UAT Studio does not read data from Dynamics 365: the browser extension only sends what a tester saves with a failed step, such as the screenshot and the link to the record.

Can testers sign in with their Microsoft account?

Yes. Next to a code by email, everyone can sign in with their Microsoft work account. Nothing has to be set up for your organisation.

Can we use the same test cases for the next update?

Yes. Choose Dynamics 365 as the CRM of the project. Before the next round of updates, Start a regression round copies the test cases you choose into a new project, with the test cases that matter most.

Which test cases does an update touch?

With the Release readiness add-on, Review this quarter or Review this month shows the test cases the roadmap items of the period touch, with the reason, and proposals for new test cases. Then you create the regression round with exactly those test cases.

Does it work with Azure DevOps and Microsoft Teams?

Yes. Issues become Bug work items in Azure DevOps and the state comes back; test cases can be read from Azure DevOps Test Plans. Microsoft Teams gets a card in a channel for new issues, rounds and sign-offs.

Where is our data stored?

In the EU (Frankfurt). See For procurement and IT for security, the sub-processors and the data processing agreement.

Try it on your next Dynamics 365 release14 days free, with your own test cases and the connections included.Start pilot

See also Salesforce UAT, the UAT checklist and all integrations. Microsoft, Dynamics 365, Azure DevOps and Microsoft Teams are trademarks of the Microsoft group of companies. UAT Studio is not affiliated with or endorsed by Microsoft.