Dynamics 365 implementation: who does the work, and how it runs
A Dynamics 365 implementation takes Finance or Business Central from a signed license to daily use. Microsoft sells the licenses through resellers, and projects in its FastTrack program get workshops with its architects, who, Microsoft says, do not design or build the solution. Our team has taken both Business Central and Dynamics 365 Finance live.
Who does what on a Dynamics 365 project
Four parties take part in every project. A fifth, FastTrack, joins projects in Microsoft’s FastTrack program. Microsoft’s own pages give each a different job. A task that falls between them has no owner.
Scroll the table sideways to see every column.
| Party | Its job, from Microsoft’s pages |
|---|---|
| Microsoft | Builds the apps and ships the updates: four service updates a year for finance and operations apps |
| Your reseller | Sells licenses and add-on environments, as a Cloud Solution Provider or a License Service Reseller |
| FastTrack, for projects in its program | Runs workshops that check best practice and flag risks; has no formal role and does not design or build |
| The implementation team | The tasks the statement of work gives it, from Microsoft’s list of 11 |
| Your own team | Owns and designs the process flows, in Microsoft’s words; a steering committee keeps the project on its KPIs |
Microsoft’s strategy page names the gap between the last two rows. The customer may assume its implementation partner will handle a task, while the partner assumes the customer will. Its fix is a statement of work that defines assumptions, roles and duties, and names what is out of scope.
That page lists 11 tasks to write down, and says the list is not complete. They include process maps, screen design, data moves, links, test planning, user sign-off tests, security and roles, configuration management, reports, cutover, and change management. Each task needs an owner on paper before the build starts.
Our team works in that row: consulting and discovery, process mapping, implementation, data migration and training, sold on their own or as one project. You keep your license with your reseller. A CSP reseller can only order for you once you accept the Microsoft Customer Agreement.
Finance or Business Central: pick the app first
Dynamics 365 is a family of apps, and the work differs by app. Microsoft writes its implementation guide for mid-sized and larger firms. For startups and small businesses, it names Business Central instead.
Scroll the table sideways to see every column.
| Business Central | Dynamics 365 Finance | |
|---|---|---|
| Who Microsoft’s implementation guide points here | Startups and small businesses | Medium-sized and larger organizations, for the guide as a whole |
| Environments in the license | One production and three sandboxes, with Essentials or Premium | One production and one Tier 2 acceptance test environment |
| Updates | Two major releases a year, in April and October | Four service updates a year; you must take at least two |
| How setup data goes in | Configuration packages, for a company’s first setup | The Data management workspace, through staging tables |
| How regression tests run | Copy production to a sandbox and test there before each major update | RSAT, which Microsoft stops supporting after May 15, 2027 |
Finance projects also face a tooling change. Microsoft froze new Lifecycle Services projects for new customers from February 16, 2026. Its deprecation list names the Power Platform admin center as the replacement.
Our Business Central implementation page covers the smaller app: licenses, setup packages and design choices. The rest of this page covers Finance, with Business Central notes where they differ.
Microsoft’s five stages, and two names for stage one
Microsoft’s Success by Design splits a Dynamics 365 project into five stages. Its two pages disagree on the first name. The guide’s overview calls it Strategize. The Success by Design page calls it Discover. Both read on 19 November 2026. The other four names match.
Scroll the table sideways to see every column.
| Stage | What Microsoft says happens | The check that goes with it |
|---|---|---|
| Strategize or Discover | The team gathers and checks requirements and settles the high-level approach | The Solution Blueprint Review starts here |
| Initiate | The team defines every workstream in scope and updates the plan | Microsoft says the Blueprint Review should already be under way by now |
| Implement | The team builds to the agreed design and scope | Implementation Reviews on the data model, security and integration |
| Prepare | Final user acceptance tests and training | A cutover plan with go/no-go rules, mock go-lives and a support model |
| Operate | The system is live; the goal is to make it steady, then plan the next phase | Production runs the business |
Microsoft says system integrators (firms that implement Dynamics 365), software firms and customers can all use Success by Design. The method is not tied to one firm. Microsoft’s Implementation Portal holds each project’s data and its reviews, and lists who is on the project. Questions about a Go-live Readiness review go through the portal.
The go-live check has teeth. On projects run in Lifecycle Services, Microsoft sets up Finance production near the Operate stage, after the required LCS steps and a passed go-live check. New customers since February 16, 2026 start in the Power Platform admin center instead. We did not read Microsoft’s admin center pages for this guide.
Environments: what the Finance license includes
Microsoft’s standard cloud offer for Finance includes two environments. Every other one you need, from developer machines to extra test copies, you host or buy as an add-on. One is a Tier 2 Standard Acceptance Testing environment, kept for the length of the subscription. The other is production, provisioned near go-live.
Microsoft’s environment planning page adds rules that shape the project plan:
- Production runs the business. Microsoft says to use production to operate the solution, not to build it.
- One per coder. Each developer needs a development environment of their own. These can be cloud-hosted in your own Azure subscription, for evaluation and development only. You pay for what runs there.
- An unnamed admin account. Deploy every environment with an unnamed account from your own domain, not a person’s login.
- A clean start before cutover. Before the final cutover, you can ask for production to go back to a clean copy from up to 28 days earlier.
- One more sandbox after go-live. If you plan new releases, Microsoft says to add a Tier-2 or higher environment beside production.
- Add-ons take time. You buy extra ones through your reseller. Microsoft warns that delivery can take time.
Microsoft’s price page says Finance Premium comes with more capacity and storage than Finance. Check the licensing guide before you size test copies.
Moving data into Finance without surprises
Finance loads data through the Data management workspace. Each data entity gets a staging table, where rows can be checked, cleaned or converted before they move. You set the order the entities load in. Microsoft says to order them by what depends on what. Customers load before open orders, for example.
Two security rules matter for sensitive data:
- Data jobs are global. A job made in one legal entity is visible to the others. You can restrict a job by role, user or legal entity.
- A job opens its staging tables. Access to a data job means full access to its history and its staging data.
So payroll or bank data needs its own locked-down jobs. Since version 10.0.42, batch import and export jobs retry on their own when a batch restarts.
The people side matters as much. Microsoft’s data guide describes a data steward who owns your data assets. It says the users who know the data best should guard its cleansing. So have those users sign off each test load.
Reporting feeds need a move too. Microsoft’s deprecation list says Export to Azure Data Lake stops for good on November 30, 2026. A new Finance project should not build reports on it.
Testing before go-live and after every update
Microsoft’s testing guide says testing starts with simple manual tests and grows into automated tests. Agile projects test more often than waterfall ones. Testing doesn’t end at go-live. Across the Dynamics 365 family, Microsoft ships weekly, monthly and six-month updates. For Finance that means four service updates a year, so the test plan you write for go-live becomes the plan you run again before each one.
RSAT is the tool Microsoft built for Finance regression tests. Its deprecation list says RSAT won’t be supported after May 15, 2027, and names no replacement. Yet its service update page still recommends RSAT. We read the deprecation list on 18 November and the service update page on 19 November 2026. Keep test scripts in a form that can move.
Task recorder still records business steps. But Microsoft says it can no longer turn recordings into process diagrams. Plan process maps in another tool.
Service updates: four a year, and you must take two
Since version 10.0.39 (April 2024), Microsoft ships four Finance service updates a year, down from seven. They come out in February, April, July and October.
Scroll the table sideways to see every column.
| Update rule | Microsoft’s figure |
|---|---|
| Service updates a year | Four, down from seven |
| The fewest you may take | Two a year |
| Pauses | One update at a time |
| Sandbox first | Seven days before production |
| Autoupdate windows | Two, four weeks apart, for each update |
| Preview builds | Development or test environments only, never production |
Microsoft says 100 percent of Dynamics 365 online customers now run on one version. Your customizations ride on that version. So a change that passed its tests in February still needs a fresh regression run before the April update reaches your sandbox, seven days ahead of production.
New features arrive with each release. The Feature management workspace shows four states: Preview, Released, On by default and Mandatory. Turning a feature on applies to all legal entities. Decide feature by feature, with the process owners, not in bulk.
Custom code, standard features and AI
Microsoft’s strategy page says to match Dynamics 365’s standard features to your needs first. That keeps custom code down and makes updates easier. Custom code costs twice: once to build, then again in maintenance and support.
Where the standard app falls short, a small extension can close the gap. For links to other systems, note one Finance limit: OData actions added through extensions aren’t supported. Our Dynamics 365 integration page covers the routes.
AI agents in a Finance project
Success by Design now asks AI questions at each stage. Two matter most:
- A person in the loop. Define where people must review and approve an agent’s work.
- Test on data like yours. Before go-live, test agents on data that looks like production, not only on test data.
Microsoft ships its own agents for this family of apps. The Account Reconciliation Agent for Finance is a preview that Microsoft calls ready for production. In Supply Chain Management, the Procurement Agent sorts vendor emails. It tells order confirmations from change requests. It is a preview of the same kind. Microsoft’s Finance pricing page says an Azure subscription is required to use agents.
In one project, our team built a system of AI agents for RFQs and RFPs in ERPNext. Separate agents handle intake, item matching, pricing, supplier RFQs and reading supplier replies. Read the case study: a multi-agent RFQ system in ERPNext. Microsoft’s agents, and the jobs they leave for a custom agent, are set out on our Dynamics 365 AI agents page.
Training, and the late cuts that hurt
Microsoft warns that work at the end of a project gets cut to meet budget. Its list: speed tests, data checks, training and change management. Keep them in the contract from the start.
Training is not a one-off either. Microsoft calls it an ongoing process, because Dynamics 365 keeps changing. We train on site or remote, as your team prefers.
A steering committee keeps the project honest. Microsoft describes it as senior leaders with the power to keep the team on its KPIs. Name yours in the first week.
What our team does on a Dynamics 365 project
Our team’s Dynamics 365 go-lives are Business Central and Finance.
Support after go-live can be bought too, on its own or with the rest of the project.
Our team has taken nine ERPs live, from SAP to QuickBooks, so the system is your choice. If you are still choosing, start with ERP consulting.
Our team has moved companies off QuickBooks, Xero or Sage into a full ERP.
On-demand ERP modules are work our team has delivered, not only offered.
Microsoft builds Sales, Customer Service and Customer Insights in Power Apps, on Dataverse. Those CRM apps are not among our go-lives, so this page covers Business Central and Finance. Other ERPs have their own pages under ERP implementation services.
What drives the time and the cost
Microsoft’s strategy page says a Dynamics 365 budget typically covers the subscription and storage, plus the project work itself. That work runs from design and tests to the move off old systems, training, change management and later improvements. These rules from Microsoft’s own pages add to a Finance bill:
- Agents run on credits. Microsoft’s Finance pricing page says Copilot Credits are required to run prebuilt agents and agents built in Copilot Studio. Agents also need an Azure subscription.
- Sandboxes past two are add-ons. The standard offer covers one production and one Tier 2 test environment. Each extra one comes through your reseller, and delivery takes time.
- Extensions keep costing. Microsoft counts maintenance and support as a cost of their own, on top of the first build.
- Developer machines bill to you. Cloud-hosted development environments run in your own Azure subscription, and you pay for what runs there.
- Each legal entity adds work. Setup and tests repeat for each one.
No Microsoft page behind this guide gives a typical length for a Finance project. Microsoft’s own list prices for Dynamics 365 are gathered in Dynamics 365 cost. Published ranges from firms that sell ERP projects sit in ERP implementation cost. We price our work in each project’s contract, not on this site. The first call is free.
Questions
Do we need an official Microsoft partner to implement Dynamics 365?
Not for this work. What decides a go-live is a team that knows Dynamics 365 from the inside and builds on Microsoft's published APIs. Our team has taken Dynamics 365 Business Central and Dynamics 365 Finance live. You license Dynamics 365 from Microsoft or its reseller, and we take the consulting, setup, data move, training and agent build from there.
What does a Microsoft Dynamics 365 reseller do?
It sells you the licenses. Microsoft says Business Central licenses can only be bought through its Cloud Solution Provider program. For Finance, extra environments come from a Cloud Solution Provider or a License Service Reseller. You must accept the Microsoft Customer Agreement before a CSP reseller can order for you. Whoever implements, the contract should say who does each task.
Does Microsoft FastTrack build our Dynamics 365 system?
No. FastTrack works with projects that join its program, and Microsoft's page links its eligibility rules. Microsoft says its architects have no formal role on the project and do not design or build the solution. They run workshops at key stages, check the project against best practice and flag risks. Your project team supplies the facts for those workshops, so the build still needs a team you hire or staff yourself.
How many environments come with Dynamics 365 Finance?
Two. Microsoft's standard offer has one production environment and one Tier 2 test environment, kept for the life of the subscription. Production is set up near go-live, after a go-live check. Each developer needs a development environment, which can run in your own Azure account. More sandboxes are add-ons, bought through your reseller, and they take time to arrive.
How often does Microsoft update Dynamics 365 Finance?
Four times a year, in February, April, July and October. You must take at least two a year, and you can pause only one at a time. A sandbox gets each update seven days before production. Each update offers two autoupdate windows four weeks apart. Preview builds go only to test copies, never to production.
What happens to RSAT after May 2027?
Microsoft's deprecation list says support for RSAT, its Regression Suite Automation Tool, ends after May 15, 2027. It names no replacement. Its service update page, read the next day, still recommends RSAT for regression testing. So keep using it for now, but plan your test scripts so they can move to another tool before that date.
What should a Dynamics 365 statement of work include?
The detailed tasks, with assumptions, roles and duties, and what is out of scope. Microsoft's guide lists 11 tasks to spell out. They run from process maps and data moves to security, cutover and change management. It warns that each side may think the other owns a task. Write each owner down.
Can we load our own data into Dynamics 365 Finance?
Yes, through the Data management workspace. Each data entity gets a staging table, so you can check and fix rows before they reach the live tables. Load them in the order they depend on each other. Data jobs show in every legal entity by default. Access to a job also opens its staging tables. So lock jobs to the right roles before you load payroll or bank data.
Sources
Every source behind a figure or a vendor fact on this page, with the day we read it.
- Microsoft Learn, What is the Dynamics 365 implementation guide?Read 19 Nov 2026
- Microsoft Learn, Introduction to the Success by Design frameworkRead 19 Nov 2026
- Microsoft Learn, About Microsoft FastTrack for Dynamics 365Read 19 Nov 2026
- Microsoft Learn, Plan a Dynamics 365 implementation strategyRead 19 Nov 2026
- Microsoft Learn, What is the Dynamics 365 Implementation Portal?Read 19 Nov 2026
- Microsoft Learn, Environment planning for finance and operations appsRead 19 Nov 2026
- Microsoft Learn, Licensing in Business CentralRead 19 Nov 2026
- Microsoft Learn, Cloud Solution Provider program overviewRead 19 Nov 2026
- Microsoft Learn, Business Central environments in the admin centerRead 18 Nov 2026
- Microsoft Learn, Business Central update cyclesRead 18 Nov 2026
- Microsoft Learn, Apply company configuration packagesRead 19 Nov 2026
- Microsoft Learn, Manage your data in Dynamics 365 implementation projectsRead 19 Nov 2026
- Microsoft Learn, Data import and export jobs overviewRead 19 Nov 2026
- Microsoft Learn, Removed or deprecated platform features (finance and operations)Read 18 Nov 2026
- Microsoft Learn, One Version service updates FAQRead 19 Nov 2026
- Microsoft Learn, Service update availabilityRead 19 Nov 2026
- Microsoft Learn, Feature management overviewRead 19 Nov 2026
- Microsoft Learn, Task recorder resourcesRead 19 Nov 2026
- Microsoft Learn, Test your Dynamics 365 solution before deploymentRead 19 Nov 2026
- Microsoft Learn, Develop your own training strategyRead 19 Nov 2026
- Microsoft Learn, Open Data Protocol (OData), finance and operations appsRead 18 Nov 2026
- Microsoft Learn, Agents, Copilot and AI capabilities in Dynamics 365 appsRead 18 Nov 2026
- Microsoft Learn, Procurement Agent overviewRead 18 Nov 2026
- Microsoft, Dynamics 365 Finance pricing (plan features only)Read 19 Nov 2026
Bring your Dynamics 365 project plan
Tell us which app you run or plan to run, how many legal entities and users you have, and your target date. On the first call we go through Microsoft's stages with your plan in front of us. The first call is free.