# IT Fandango

Independent D365 F&O Strategic Advisory

- Site: https://itfandango.com/

## Dynamics 365 Testing, Part 3: Leveraging Testing Automation After Your ERP Go-Live

- Link: https://itfandango.com/articles/dynamics-365-testing-leveraging-testing-automation-after-your-erp-go-live/
- Published: 2025-09-16T10:40:31+01:00
- Author: Marco Romano

# Dynamics 365 Testing, Part 3: Leveraging Testing Automation After Your ERP Go-Live

**Why it matters now, testing tools to use, and how to save time and money with 
it**

16 September 2025

## Introduction

Go‑live isn’t the end of your Microsoft Dynamics 365 Finance and Operations testing.
It’s the start of a new phase where the stakes are higher, the pace changes but 
doesn’t slow down, and the tolerance for mistakes is close to zero. Why?

First, Microsoft’s One Version philosophy means scheduled and automatic updates 
that you can delay but not avoid. Your Microsoft Dynamics 365 system is a platform
that keeps evolving whether you like it or not. You’ll get new versions, cumulative
updates, bug fixes, and new features on Microsoft’s timetable, not yours.

Then, there are the infamous phase 2 requirements. You know all those user requests
that were pushed back during the implementation to [avoid scope creep](https://itfandango.com/articles/d365-fo-implementation-challenges/#6)?
They’re back now. Users want the ERP to do something new, something different, or
the same thing in a different way — and they expect it fast.

When you change something, you need to ensure it works. This means validation, and
this is what changes after go-live. Testing is no longer about proving the system
works. It’s about making sure it keeps working exactly as it did yesterday, even
after tomorrow’s update or new feature. In practice, this means a shift of importance
towards regression testing and an increasing reliance on automation to protect your
production environment.

In this article we’ll focus on what happens after your Dynamics 365 F&O go‑live 
and how to maintain business continuity without drowning in manual testing effort.
We’ll cover:

 * How **post‑go‑live testing **differs from implementation testing
 * Why **automated regression testing **is now essential
 * The Microsoft Dynamics 365 **testing tools** you should be using
 * How to build smart, maintainable **automated test suites**
 * How to include **testing in your business‑as‑usual operations**

### Key takeaways

Here are the key lessons you’ll learn from this article:

 * **Stability:** Post‑go‑live testing is required to keep your Microsoft Dynamics
   365 F&O system stable across updates, bug fixes, and business changes
 * **Speed:** Manual regression testing is too time‑consuming and unreliable to 
   keep up with Microsoft’s automatic update schedule
 * **Continuity:** Smart test automation helps you perform regression testing faster,
   reduce human error, and maintain business continuity
 * **Prioritisation:** Start by automating high‑impact, low‑variance processes —
   not everything, and not all at once
 * **Tooling:** RSAT, Task Recorder, and Azure DevOps give you a solid foundation,
   but may not be enough for complex or cross‑system testing requirements
 * **Governance:** Sustainable test automation needs stable test environments, reusable
   scripts, and ownership embedded in BAU

### Wait! Before we begin…

Go-live is a milestone, but further testing is pointless if your Dynamics 365 ERP
is not working as it should. We wrote a **practical guide for senior leaders **of
companies already live with D365 F&O, describing symptoms that your new ERP is failing
to deliver the promised benefits, what are the likely root causes, and what to do
about them. Download your free copy from the form below.

![](https://itfandango.com/wp-content/uploads/2025/05/Mockup-Underperforming-Free-
Guide-Cover-Extended-1024x739.png)

Field guide to underperforming D365 F&O systems

Seven operational symptoms your ERP is failing to deliver after go-live

**Download your free copy!**

 The form can be filled in the actual [website URL](https://itfandango.com/articles/dynamics-365-testing-leveraging-testing-automation-after-your-erp-go-live/).

---

## Implementation testing vs post‑go‑live testing

Testing during a Dynamics 365 F&O implementation and testing after go‑live are two
very different games. The rules change, the goals change, and the consequences for
getting it wrong become much more expensive.

### Testing during the implementation

Implementation testing is wide‑angled. You are dealing with a brand‑new Microsoft
Dynamics 365 system, fresh configurations, custom developments, and a user base 
that potentially has never touched Dynamics 365 F&O before.

We have seen [in our previous article](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/)
what the key phases are:

 * **Functional testing** to check that specific features work against requirements
 * **End-to-end (E2E) and System Integration Testing (SIT)** to follow a transaction
   from start to finish through processes and other systems
 * **User Acceptance Testing (UAT)** to ensure that users can operate the system
   autonomously and meet agreed success criteria and exit criteria

Despite this structured approach, much of this is manual and, to a degree, exploratory.
[Test cases evolve](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/#4)
as the system design gets finalised. Scripts get rewritten as new requirements pop
up (it happens, let’s face it). Your test team is building understanding and confidence
that the ERP system is fit for purpose before your company runs on it.

### Testing after go‑live

Once you are live, the focus narrows. Users and consultants already know the system
works (or at least, they should). The job now is to make sure it keeps working the
same way after every change.

That’s where regression testing comes in. You’re re-running proven test cases to
confirm that updates, bug fixes, patches, and configuration tweaks haven’t broken
anything. The goal is stability, not to rediscover all the edge cases you already
dealt with during implementation.

Manual testing still matters (we’ll get to that), but relying solely on manual testers
is too time consuming and too risky. Structure and automation become the only sustainable
way to keep pace with Microsoft’s scheduled updates and your own internal changes,
without holding key users hostage every few months to perform regression testing
every few months.

Stable, repeatable test suites in a non‑production environment give you confidence
that your production update won’t derail operations. And unlike in implementation,
a failed test now isn’t just a red mark in a spreadsheet. It’s a potential real-
world problem — lorry drivers stuck in the factory car park because nothing’s shipping,
a finance director losing it over invoices not being sent to clients, or a production
line halted because raw material consumption can’t be recorded in the system. I’ve
seen all three.

---

## Why automated testing is now essential

Post‑go‑live, the overall volume of testing might be smaller than during implementation,
but every wrong change can grind your business to a halt. That’s why automation 
moves from being a “nice to have” to the backbone of your business‑as‑usual (BAU)
testing process.

### It ensures business continuity

Once you’re live, you’re no longer in full control of your production environment.
Microsoft pushes platform updates on a fixed schedule. ISVs release patches and 
new features. Super users tweak configurations. Any of these can break something—
often in places you don’t expect, like upstream in a process or in a connected system.

Manual regression testing can’t keep up. It’s slow, reliant on busy people, and 
often based on guesswork from a business analyst skimming release notes and guessing
any potential impact. That’s not a safe testing process.

Automated testing changes that. You can re-run proven test cases whenever a scheduled
update lands in your non‑production environment, catching problems before they hit
production. This way, way safer. A strong automated regression suite helps you adopt
the latest version of Dynamics 365 confidently, without risking operational downtime.

### It reduces dependency on humans

During implementation, it’s easy to get 20‑30 people from your test team in a room
to run through user acceptance testing together. In business‑as‑usual, that luxury
disappears. People are back to their day jobs. Coordinating manual testers across
multiple departments becomes a logistical nightmare and burns valuable resources.

And when your testing depends on other teams acting first (for example, finance 
can’t test payment runs until procurement has created and receipted a purchase order),
manual testing slows to a crawl. By the time everyone’s done, Microsoft has released
the next update and you’re back at the start.

Automation removes these bottlenecks. It runs the full process from start to finish
without waiting for someone in another department to be free. It also reduces fatigue
and human error — the two biggest killers of accuracy in manual regression testing.
The result is faster, cleaner test cycles that don’t rely on assembling a small 
army of testers every month.

### It simplifies test maintenance

Coverage and speed are not the only benefits of test automation. Automation enforces
predictability and structure, so you need a well‑maintained test suite that evolves
as your business needs change. If every new feature, updated process, or rollout
to a new country requires a business analyst to start from scratch, you’ll never
keep up.

The goal is a library of automated tests built around your core business processes,
not individual button clicks. This makes it easier to adapt when things change, 
regardless of whether that’s a Microsoft Dynamics 365 platform update, a series 
of consecutive updates, or a regulatory change.

Well‑structured test scripts should be quick to update and easy to maintain, ideally
by non‑technical users. Keep them under version control in Azure DevOps, tie them
directly to your process documentation, and update them alongside configuration 
changes. Do it right, and you’ll have a scalable, flexible testing capability that
can react quickly without the lag and cost of a purely manual approach.

---

## Testing tools for Microsoft Dynamics 365

If you are serious about your testing efforts after the Dynamics 365 F&O go-live,
you will need tools. Not a random mix of Excel tabs and sticky notes, but specialist
applications that let you perform regression testing quickly, repeatably, reducing
human error and intervention. Microsoft gives you a starting point, so let’s start
with it.

### Regression Suite Automation Tool (RSAT)

![](https://itfandango.com/wp-content/uploads/2025/08/image-1024x405.png)

A screenshot of Microsoft’s RSAT.

The **Regression Suite Automation Tool** is Microsoft’s built-in answer to automated
regression testing for D365 F&O. It works with Azure DevOps test cases and the Task
Recorder to create automated test scripts that you can re-run whenever you like.
In theory, you can record a process once, link it to a test case, and replay it 
across environments without touching a thing.

In practice, RSAT works best when the processes you are testing do not change much.
Stable, high-value business flows like sales order creation, invoice posting, or
purchase order receipts are perfect candidates. The tool can handle variations, 
but constant changes in forms, fields, or business logic will lead to extra maintenance
work.

It is not flashy, but it does the job and doesn’t have extra costs.

### Task recorder and Azure DevOps

![](https://itfandango.com/wp-content/uploads/2025/08/image-1-1024x323.png)

Task recorder is embedded in Dynamics 365 F&O and can be opened directly from the
environment.

**Task Recorder** is your way of capturing exactly what happens in a process. It
is simple: you turn it on, run through the process, and it records every click, 
field entry, and system response. These recordings are very often used to create
documentation and training materials, but they can also be used as a basis for automated
RSAT scripts.

![](https://itfandango.com/wp-content/uploads/2025/08/image-2.png)

The Test Plans feature of Azure DevOps allows you to manage your test plans and 
test suites.

**Azure DevOps** is where you store, track, and manage those test cases. It gives
you version control, traceability, and the ability to organise your testing backlog.
It is also your home for defect tracking, test execution history, and reporting.
You should have already used Azure DevOps heavily during the D365 F&O implementation
project, so by now you should be very familiar with it.

When used together, Task recorder, RSAT, and Azure DevOps give you a decent baseline
testing framework without having to invest in third-party automation tools. However…

### Choosing the right tool for the job

Just because RSAT is included in your standard Microsoft toolkit, it does not mean
it is always the best option. Its limitations are well known: it’s not intuitive,
it requires technical knowledge to maintain the test cases, and it’s confined to
D365 F&O. So if your testing requirements extend beyond the ERP system or you want
to empower your users (you should), RSAT may not be the best choice. There are solid
options in the market, like **Leapwork **and **Executive Automats**. If you’re already
familiar with them, this article might be too basic for you.

In short, the right testing automation tool is the one that:

 * **Can be maintained by key users without a team of techies**: think low-code 
   or no code, plus modular test cases that you can reuse across multiple processes.
 * **Is platform-agnostic, integrating seamlessly across applications**: your E2E
   processes may extend beyond Dynamics 365 F&O, so you want something that works
   well across all your test environments without complex configuration.
 * **Fits well into your internal release management process**: you want a tool 
   that saves time rather than adding another layer of work every time you plan 
   a new release.

We know that if you stick only to manual testing, you will eventually fall behind.
But if you automate badly, you will create a convoluted and unreliable testing process
that nobody trusts. Choose wisely, and the tools will do the heavy lifting so your
team can focus on higher-value work.

---

## Best practices for post‑go‑live test automation

Automating testing after your Dynamics 365 F&O go-live is a smart move, but it’s
not instant magic. You can’t just flip a switch and have every test case automated
overnight. Success comes from starting in the right place, focusing your efforts,
and embedding automation into your day‑to‑day governance.

### Start with a solid foundation

If you diligently documented your efforts during the ERP implementation project,
this is where it pays off. Reuse what you can: process maps, test cases, configuration,
dataset, task recording and so on are a valuable repository of artifacts to save
time to set up your test automation.

Chances are that you did not focus much on automation during the implementation 
itself, but reusing what you can from it will simplify things massively — this is
yet another confirmation that in a D365 F&O implementation [every step builds the foundations for the next one](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/).

But make sure you build your automated tests on clean, consistent, and version‑controlled
test data and system configuration. Wherever possible, keep those stable across 
environments — the production environment is messy, so refreshing a test environment
with its content carries an inherent risk of false failures due to bad records. 
The same goes for test scripts: design them to survive UI tweaks and minor process
changes, and store them under version control in Azure DevOps so updates are quick
and traceable.

### Target high‑impact, low‑variance processes first

You don’t need to automate everything, nor should you aim for that. Start with the
core processes that keep your business running and don’t change often — examples
include posting journals, receipting purchase orders, or starting a production order.
These are high value scenarios with low variance but high risk if broken, and they
are relatively stable to automate easily.

Avoid chasing every obscure exception from day one. Automate what will hurt you 
most if it fails, not what happens once a quarter. You can expand coverage over 
time once your core regression suite is in place.

### Balance test automation with human oversight

Automated tools handle the heavy lifting of regression testing, but they are not
a replacement for people. Manual and exploratory testing still matter for new features,
unexpected behaviours, and user experience checks.

The point of automation is to free your human testers from repetitive checks so 
they can focus on spotting the things automation can’t. Think of test automation
as your always‑on safety net, and your people as the ones who check if the net is
in the right place.

### Embed automation into BAU governance

Testing is not a one‑off project phase during the implementation (something we explained
in [this article](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/)),
nor it should be once you’re live with Dynamics 365 F&O. By then, it should be part
of your operational governance. So assign clear ownership for maintaining the regression
suite, run tests for every Microsoft update, and sign off the validation before 
you deploy changes to the production environment.

Integrate automation into your release process, which should work like this: update
applied to test environment → regression suite runs → results reviewed → targeted
manual checks → production deployment only if everything passes.

For regulated industries, the same governance process provides an audit trail of
what was tested, when, and with what results. This helps you produce the evidence
needed to keep auditors and senior stakeholders happy.

---

## Conclusion

Go‑live is not the end of your Dynamics 365 F&O testing. It’s the start of a constant
cycle of updates, fixes, and changes that can break your most important processes
overnight.

Manual regression testing is too slow and too dependent on people’s availability.
Automated tests let you keep pace with Microsoft’s update schedule, intercept problems
before they reach production, and protect business continuity without draining valuable
resources.

The formula is simple: start with clean data and stable scripts, focus on high‑impact
processes, keep human oversight, and make testing part of BAU governance. Do this
and updates stop being a gamble. Ignore it, and you’ll end up testing in production—
the most expensive way to find out something is broken.

**Sections:**

 * [Introduction](https://itfandango.com/articles/dynamics-365-testing-leveraging-testing-automation-after-your-erp-go-live/#1)
 * [Implementation vs post‑go‑live](https://itfandango.com/articles/dynamics-365-testing-leveraging-testing-automation-after-your-erp-go-live/#2)
 * [Why testing automation](https://itfandango.com/articles/dynamics-365-testing-leveraging-testing-automation-after-your-erp-go-live/#3)
 * [Testing tools for D365](https://itfandango.com/articles/dynamics-365-testing-leveraging-testing-automation-after-your-erp-go-live/#4)
 * [Automation best practices](https://itfandango.com/articles/dynamics-365-testing-leveraging-testing-automation-after-your-erp-go-live/#5)
 * [Conclusion](https://itfandango.com/articles/dynamics-365-testing-leveraging-testing-automation-after-your-erp-go-live/#6)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

The post [Dynamics 365 Testing, Part 3: Leveraging Testing Automation After Your ERP Go-Live](https://itfandango.com/articles/dynamics-365-testing-leveraging-testing-automation-after-your-erp-go-live/)
appeared first on [IT Fandango](https://itfandango.com).

## Dynamics 365 Testing, Part 2: Common Traps And Best Practices In ERP Implementations

- Link: https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/
- Published: 2025-08-14T14:29:53+01:00
- Author: Marco Romano

# Dynamics 365 Testing, Part 2: Common Traps And Best Practices In ERP Implementations

**Prerequisites, setup, frequent setbacks, and key decisions to make for effective
testing**

14 August 2025

## Introduction

Testing in a Microsoft Dynamics 365 Finance and Operations (D365 F&O) ERP implementation
is not just another checkbox in the delivery plan. It is your best chance to expose
flaws, assumptions, and blind spots before the system hits production. But even 
the most structured testing strategy will collapse if you haven’t laid the right
groundwork.

Many organisations treat testing as the final hurdle, a thing you do once the “real
work” is done. That’s the first mistake. Testing is not a final check. It is a stress
test of your decisions, your data, your processes, and your people. If those aren’t
in good shape, testing won’t save you. It will simply expose everything you’ve ignored
up until that point.

In this article, we focus on four elements about testing best practices during your
implementation of Microsoft Dynamics 365 F&O:

 * **Prerequisites**: finalised solution design, detailed business processes, and
   valid test data
 * **Setup**: clear strategy, clean environments, tracking tools, and key owners
 * **Common traps**: bad test cases, unrealistic timelines, lack of accountability,
   and dirty data sets
 * **Next steps**: defect triage, retesting, signing off, and managing timelines

We’ll walk through what needs to be in place before testing starts, how to set up
your testing process properly, where we’ve seen projects fall flat on their face,
and what key decisions matter after each test round. This is how to lay the foundations
right, for the benefits of your Dynamics 365 implementation project.

### Wait! Before we begin…

Testing is one challenge of ERP projects, but there are others — so in our free 
guide, we described **10 common functional issues during a D365 F&O implementation**:
what they are, why they matter, what happens if they’re neglected, and how to spot
red flags before they become critical issues. Get your free copy from the form below.

![](https://itfandango.com/wp-content/uploads/2025/05/Mockup-Functional-Health-Check-
Free-Guide-Cover-Extended-1024x635.png)

D365 F&O functional health check

10 common implementation functional issues and how to identify them

**Download your free copy!**

 The form can be filled in the actual [website URL](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/).

---

## Short summary of key testing phases

Let’s start with a quick recap of the main testing phases in a Dynamics 365 F&O 
implementation, which we covered extensively in [this other article](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/).
These phases are sequential for a reason: each one builds on what came before it.
Skip or shortcut one, and the next one gets shakier.

 * **Functional testing**: During the system build, functional testing is useful
   to verify whether individual features do what they’re supposed to do, based on
   business requirements and solution design. Functional testing is the responsibility
   of (you guessed it) functional consultants, and it covers specific scenarios 
   and sub-processes. This testing type is one level above validating whether individual
   buttons or functions work, which is part of unit testing.
 * **Solution integration testing (SIT)**: At this stage, the focus shifts to how
   different modules and applications talk to each other. Can the ERP handle a sales
   order passed from your CRM? Does the stock reservation go all the way to your
   warehouse management system? This phase exposes issues with data flows, field
   mappings, interfaces, and process handoffs.
 * **End-to-end testing (E2E)**: Now you’re simulating how the business actually
   works. Transactions go through departments, systems, and people. From purchase
   requisitions to product receipt. From starting a production order to dispatching
   it to the client. This is where your overall assumptions get tested. Can the 
   system operate under real-world conditions, from start to finish?
 * **User acceptance testing (UAT)**: This is the final gate. Business users validate
   that they have a system suitable to support their daily operations. Here the 
   goal is not just passing test scripts, but also building people’s confidence.
   Can the company bet on running their operations with the new ERP?

These test phases are not optional. They are critical control points. Get sloppy
in functional testing, and features will fail under real conditions. Skip integration
testing end E2E, and processes will have loose ends because transactions won’t flow
smoothly. Ignore concerns raised by users during UAT, and your go-live will become
a firefighting exercise. Testing is cumulative. Weak foundations don’t get stronger
with time.

---

## Prerequisites for effective testing

![](https://itfandango.com/wp-content/uploads/2025/07/Building-foundations-1024x341.
jpg)

A building needs robust foundations before it’s constructed, and so does your testing
process.

Before you even think about test scripts or colourful Azure DevOps dashboards, you
need to make sure you have a testable software solution. That might sound obvious,
but we’ve seen too many projects shoot into test execution without knowing what 
they were testing exactly. Prerequisites are important: identify testing requirements,
define business processes, and finalise your solution design to ensure a smooth 
and effective testing process. Testing doesn’t start with testers. It starts with
the right decisions made early. Let’s see what these are.

### Stable and finalised solution design

Test cases are only as good as the software they’re testing. If your solution design,
system configuration, and custom features are incomplete, incorrect, or still changing
mid-test, then you’re not validating anything. You’re just burning hours. Yes, in
real-world projects, some design areas remain fluid while others stabilise. That’s
normal, especially when there are plenty of customisations. But you must know which
parts are locked and which are not, or your testing will be useless.

To enable test coverage with confidence, your** solution design** should:

 * Be documented and **agreed across all functional areas **and design documents
 * Meet specific requirements, which are defined from clear business needs
 * Include customisations, integrations, and cover any edge scenarios

Testing a moving target is a guaranteed way to waste time. Freeze what you need.
Document what you can. Flag anything still in progress.

### Mapped business processes with owners

A software solution can be final and complete, but it is only meaningful if it reflects
how the business actually works. Which is what testing is supposed to prove. That
means your business processes must be mapped, agreed upon, and owned by someone.
If users can’t explain what they do, or there’s internal disagreement about how 
something should work, then you’re testing a solution that may technically work 
while being completely useless for its purpose.

To avoid this, you need:

 * **Complete business process mapping**, end-to-end in all the core streams
 * Key users who are nominated process owners and have the last say
 * Visibility of exceptions, workarounds, sub-processes, and special cases

Incomplete processes without ownership are dangerous. If nobody is accountable for
the big picture, your testing will win the battle and lose the war. Make sure that’s
not your case.

### Fit-for-purpose test data

It is possible to have tests that succeed with mock-up records, but fail with real
ones. Testing sales order processing with a made-up, perfect customer (let’s just
select the first value in the drop-down) may pass functional testing, but it’s a
lot riskier with E2E testing. Validated test data is a huge factor in the thoroughness
of your testing process. That includes master data, configuration records, and transactional
examples that mirror real-world scenarios.

Good test data is data that:

 * Is your **actual migrated data **where possible, or a reasonable simulation where
   it’s not
 * Covers standard cases, edge cases, exceptions, and any specific business conditions
 * Includes correct configuration parameters, that match the production environment
   where possible

So migrate your data early. Refresh your test environments often. Keep a GOLD environment
for finalised configuration and master data. Guard it like your testing efforts 
depend on it. They don’t get stronger with time.

---

## Setting up for testing

![](https://itfandango.com/wp-content/uploads/2025/07/Excursion-gear-1024x348.jpg)

Preparing for a testing round is akin to setting up your gear before an excursion.

Once the prerequisites are in place, it’s time to think about how you actually run
the test themselves. Having the right setup can be the difference between controlled
execution and a chaotic scramble.

### Clear, organised test strategy

Testing without a strategy is just clicking around in the dark. You need a clear
testing strategy that lays out what you’re testing, why you’re testing it, and how
success will be measured.

Your **testing strategy **should include:

 * Test phases and timelines, including time for defects fixing
 * Test scope aligned to business priorities
 * Test scenarios that reflect real processes
 * Measurable and specific entry and exit criteria for each test phase
 * Where possible, test automation to streamline testing

Don’t just test for the sake of it. The goal is not 100 percent pass rates. It’s
confidence that the system behaves correctly across the range of real-world use.
And if it doesn’t, it’s about having enough knowledge to manage risk and make an
informed decision on whether to move forward.

### Environment readiness and ownership

You can’t run consistent testing in an environment that changes every other day.
And you can’t troubleshoot issues in an environment that doesn’t reflect the testing
conditions.

So make sure your **test environments**:

 * Are designated clearly (e.g. UAT vs SIT vs GOLD) and have clear owners
 * Are refreshed with the most recent data and config before testing starts
 * Grants and tracks the right access to the right people (no “test user 1”)

Naturally, to ensure your tests are run smoothly and results are reliable, prepare
your test environments to mirror the production environment as the project inches
towards go-live. Again, use a GOLD environment to safekeep finalised configuration
and master data.

### Tracking and execution tools

Forget Excel spreadsheets and email threads. Use a proper testing tool like Microsoft
Azure DevOps to manage your test cases. If this is viable, also use automation tools
for the testing process.

With **Azure DevOps**, you can:

 * Link test cases to processes, user stories, and business requirements
 * Track who executed what, when, and what the result was
 * Record defects directly from failed tests and assign them to owners
 * Develop a framework to execute automated tests later on

Proper testing tools reduce manual overhead and improve traceability. The right 
organisation and tools allow you to save time, reduce manual work, decrease chances
of human error, and facilitate tracking of each test run. The result is less noise,
more visibility, faster defect triage, and overall better decisions.

### Who owns testing?

If your test team is just consultants and QA staff, you’re having students grading
their own homework. Business users must play a central role. Because they understand
what’s acceptable and what’s not. They know the messy edge cases that never make
it into specs. They’re the ones actually using the system after go-live. And they
can tell when something works technically but is unusable operationally.

The testing process needs to be **jointly owned**:

 * Functional consultants help define scenarios and support defect resolution
 * Test leads supervise creation of scripts and coordinate execution with testers
 * Business users validate the processes, confirm outputs, and give go/no-go feedback

Naturally, the engagement of business users varies across test phases (lowest during
functional testing, highest during user acceptance testing). But if business users
aren’t actively involved in testing, then they won’t own the system and have no 
trust in it at go-live. And frankly, you shouldn’t either.

---

## Common testing traps

![](https://itfandango.com/wp-content/uploads/2025/07/Car-crash-with-snowy-road-
1024x346.jpg)

The best preparation and the fastest car won’t save you if you drive recklessly 
on dangerous roads.

Now, let’s take a step back. Even with a great strategy and perfect setup for your
testing, things can still go wrong. Here are the traps we see most often, and how
to avoid them.

### Poor test case design

Too many test cases only cover happy paths. These are the simple, ideal, fairy-tale
scenarios that rarely reflect how the business actually operates. This can be due
to bad test design. But** poor testing coverage **is often a direct consequence 
of poor functional solution design. Nobody thought that this use case or exception
might happen, so nobody wrote it down, so no test exists to verify if it can be 
handled.

In other situations, test cases may lack clarity, skip failure conditions, or ignore
validations that span roles and systems. Effective testing means pushing the system
to its edges, not just confirming that it works under perfect conditions. Invest
time in defining all scenarios that reflect real tasks, including edge cases, what-
ifs, and exceptions, so that you can have good test design and a complete test plan.

### Unrealistic timelines and compressed cycles

Together with user training, testing is always the phase that gets squeezed when
the project timeline slips. The upstream delays pile up, but the go-live date holds
firm. Suddenly, what was a six-week test window becomes two, and testers are told
to “do what you can with the time we have”.

This is not a testing strategy… it’s a panic move. Compressed timelines mean rushed
execution, minimal retesting, and defects that never see the light of day until 
users trip over them in production. These shortcuts often lead to more **time-consuming
rework** and defect resolution later, negating any perceived time savings. Testing
needs air to breathe. If you don’t build in contingency for rework and allow time
for meaningful validation, you’re not testing — you’re gambling.

### No business accountability

If testing is driven entirely by the IT department or by the system integrator, 
you can expect disengagement from key users and late-stage surprises. The most common
post-go-live complaint we hear when the ERP system is good but not good enough is“
we didn’t realise it worked like that”. This is a symptom of **passive business 
involvement** during testing. If users had tested the solution before signing it
off (assuming there was a formal sign-off), they would’ve known how it works, no?

This means that business users must validate the design of scenarios to test, be
active in test execution, own the outcome of the test cases, and push for fixing
any defects that were spotted. It’s their ERP. They’re the ones who need to sign
off with confidence. If they aren’t embedded in the process, the sign-off means 
nothing, and your risk of operational disruption after go-live skyrockets.

### Uncontrolled data

Testing can only be as good as the data behind it. We mentioned this already, but
it’s worth stating it again since we saw it happen more than once. If your test 
environment lacks relevant master data or realistic configuration, you’ll spend 
more time **diagnosing false errors **than validating the solution.

Then after go-live transactions fail to post, reports show blank fields, and testers
throw their hands up since the pass rate was high. Often, these cases aren’t solution
design issues by themselves, bur rather preparation failures. Make sure the data
landscape is planned just as carefully as the test scenarios. The goal is a credible,
production-like environment. Without that, your test results will be misleading 
at best, and dangerously wrong at worst.

---

## What happens next

![](https://itfandango.com/wp-content/uploads/2025/07/Rocket-taking-off-1024x343.
jpg)

Completing a testing phase is like a successful rocket launch: the work is not done
yet.

Ok, let’s say you did everything right. You managed to execute all your tests, with
great involvement from key users and without impacting the timeline. What now? Here
is what you should consider next, to make sure you’re not missing any important 
step.

### Defect triage and ownership

Once a test phase concludes, the tough work often begins. Too many project managers
treat testing like a destination. In reality, it’s a** feedback loop**. The outcomes
of your tests (the bugs, the gaps, the user feedback) all feed into the next iteration.
But this only works if you have a structured response process.

The first step is **defect triage**. Not all bugs are created equal. Some break 
the system. Others just annoy users. Others weren’t bugs in the first place, but
just missing configuration or human error. Your team needs a framework to categorise
issues, assign ownership, and track resolutions. Someone must own defect review 
meetings, log the outcomes, and ensure fixes are prioritised based on impact, not
just volume.

### Retesting and regression

A fix isn’t done until it’s verified. And not just by the developer who updated 
the code. Testers must confirm that the issue is resolved in the test environment,
using the same steps that originally triggered the fault. If relevant, key users
too must be involved in the retesting process. If it’s a critical fix, **regression
testing** may be needed to ensure the change hasn’t broken something else. This 
is where proper documentation, traceability, and automation really earn their keep.

### Closure and exit criteria

You also need to define what “done” looks like. That means having clear exit criteria
for each test phase. This could be a **pass rate threshold**, a list of known and
accepted defects, or a formal go/no-go checklist reviewed by stakeholders. What 
are the success criteria? How good is good enough? How much risk can you take? What’s
the plan either way? Without clarity, you risk advancing based on hope rather than
evidence.

### Managing timelines and decisions

Testing reveals the truth. Sometimes the truth hurts. If test results show more 
issues than expected or expose unstable processes, you must be ready to respond.
That might mean running another round of testing, adjusting the project scope, or
delaying go-live. It might also mean **escalating for business decisions**.

When making go/no-go decisions, focus on the most critical issues to ensure that
you can manage the risk (and any consequences), that you priorities are clear, and
resources are used effectively where it matters. What you must not do is pretend
everything’s fine just to stay on schedule. That’s how you sleepwalk into go-live,
just to wake up abruptly to a house on fire.

---

## Conclusion

Good testing doesn’t just prove your system works. It proves that your **design 
decisions hold up under pressure**, that your business users are ready, and that
the whole thing fits together in the messy, real world.

If you treat testing as a rubber stamp at the end of each project milestone, you’ll
miss the opportunity not just to fix, but potentially even to spot any issues present.
Bugs and defects will be built into the fabric of your ERP system, and testing will
fail to be a tool for alignment, validation, and confidence.

The foundations matter. So do the traps. [Invest in the prep](https://itfandango.com/solutions/d365-fo-advisory-retainer/),
structure the process, and take the results seriously. It’s the only way to make
sure your Dynamics 365 F&O system is delivered successfully. You don’t want to just
reach go-live. You want to go live with a stable solution that supports your business
without surprises, and continues to run smoothly for years to come.

**Sections:**

 * [Introduction](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/#1)
 * [Key testing phases](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/#2)
 * [Testing prerequisites](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/#3)
 * [Setting up for testing](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/#4)
 * [Common testing traps](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/#5)
 * [What happens next](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/#6)
 * [Conclusion](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/#7)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

The post [Dynamics 365 Testing, Part 2: Common Traps And Best Practices In ERP Implementations](https://itfandango.com/articles/dynamics-365-testing-best-practices-and-common-traps-in-erp-implementations/)
appeared first on [IT Fandango](https://itfandango.com).

## Dynamics 365 Testing, Part 1: Key Testing Phases During Your ERP Implementation

- Link: https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/
- Published: 2025-07-18T09:02:38+01:00
- Author: Marco Romano

# Dynamics 365 Testing, Part 1: Key Testing Phases During Your ERP Implementation

**Understand what each test phase is about and why it matters**

18 July 2025

## Introduction

Testing is possibly one of the most [underestimated parts](https://itfandango.com/articles/d365-fo-implementation-challenges/)
of a Microsoft Dynamics 365 ERP implementation — yet it’s a key element that marks
the difference between a solution that works and one that does not. Despite this,
too many organisations treat it as a tick-box exercise instead of a serious safeguard
to their ERP investment.

In this article, we break down the major types of testing you’ll encounter during
a Dynamics 365 F&O implementation:

 * **Main test phases:** functional testing, SIT, E2E, UAT
 * **Technical testing:** unit testing, performance testing, regression testing
 * **Other test types:** CRP, data validation, reporting, security roles, smoke 
   testing, and mock cutovers

We focus primarily on ERP implementation testing from a functional point of view(
that is, how the application impacts critical business processes), since it’s where
our expertise is. For each of those testing phases, we explain:

 * What they are
 * Why they matter
 * How things can go wrong
 * What a **worst case example** looks like

After this, we also briefly mention technical types of testing and other types of
tests and validation you should be aware of. But we will leave to future articles
any mention of specific testing tools, as well as preparation and prerequisites 
for testing.

Our goal here is to walk you through each testing stage so you can understand, prioritise,
and execute with clear ideas — before your go-live turns into go-wrong.

### Before we begin…

Testing is one challenge of ERP projects, but there are others — so in our free 
guide, we described **10 common functional issues during a D365 F&O implementation**:
what they are, why they matter, what happens if they’re neglected, and how to spot
red flags before they become critical issues. Get your free copy from the form below.

![](https://itfandango.com/wp-content/uploads/2025/05/Mockup-Functional-Health-Check-
Free-Guide-Cover-Extended-1024x635.png)

D365 F&O functional health check

10 common implementation functional issues and how to identify them

**Download your free copy!**

 The form can be filled in the actual [website URL](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/).

---

## Main implementation test phases

The robustness of any Microsoft Dynamics ERP implementation is determined by its**
testing process**. And no, we’re not talking about clicking a few buttons to see
if they work and calling it a day. These testing phases are the backbone of your
assurance layer. Done right, they expose flaws before they become operational disasters.
Done wrong, they become the reason your ERP stops working on day one. Below, we 
break down the main test phases your team must treat as non-negotiable.

### Functional testing

![A technician inspecting a car engine](https://itfandango.com/wp-content/uploads/
2025/07/A-technician-inspecting-a-car-engine-1024x683.jpg)

Functional testing is a check on individual components.

Functional testing is where your system capabilities get their first serious interrogation.
The question is: can the application perform its required tasks, based on the configuration
and business logic defined? Answering it is even more important if you have designed
extensions and customisations to the standard Microsoft Dynamics 365 F&O features.

So it’s not just a matter of working without bugs, but **working as intended**. 
Consequently, functional testing should be aligned with business needs and processes
to ensure that the solution meets specific criteria. Can your users post a journal
under this and that use case? Once done, is the posting correct?

Typically, the baton here sits with your functional consultants and QA testers, 
possibly using a mix of manual and automated testing tools. Business analysts and
key users should feed into the test cases to ensure they reflect reality, helping
to create comprehensive test scenarios for thorough process validation. If your 
team is smart, they’ll also start using a **test automation platform** early for
automating and managing test cases, laying the foundation for stable tests that 
can be reused and extended later. After all, manual testers can burn out when volume
increases, and manual testing is prone to human error, compromising coverage and
quality. But automation is only possible if your processes are clearly mapped and
the design is finalised, which isn’t always true.

Functional testing is also where bugs get baked in if nobody speaks up. We’ve seen
consultants test happy paths to death, yet skip every edge case — only to realise
post-go-live that users regularly deviate from standard textbook processes. People
don’t use the ERP in a predictable, linear way. Exceptions happen, use cases and
processes have variance. The job of functional testing is to predict and anticipate
this as much as possible.

#### What can go wrong

Even seasoned teams fall into predictable traps:

 * **Test cases don’t reflect real business use.** If your testing scripts are written
   by someone who’s never processed an invoice and doesn’t understand the solution
   design, you’re setting yourself up for failure.
 * **Tests are performed on incomplete data or incorrect configurations.** While
   full data migration may not be possible when functional testing takes place, 
   testing only on a restricted set of ad-hoc records can render test outcomes meaningless
   when real-world complexity hits.
 * **Functional documentation lacks testing guidance.** Many consultants skip the
   critical step of embedding test scenarios and expected outcomes into their functional
   design documents, especially for custom features. This leaves testers guessing
   what to validate and how success is defined, which often results in inconsistent
   or incomplete testing.

![](https://itfandango.com/wp-content/uploads/2024/04/thumbs-down-solid.png)

#### Worst case example

A logistics company built a custom feature in Microsoft Dynamics 365 F&O to handle
split shipments for partial deliveries. It looked fine during design, but it was
a different story when users began using it with real scenarios after go-live. Orders
with multiple warehouses or last-minute changes triggered errors and generated duplicate
shipment records. None of these edge cases had been tested, rendering the feature
almost unusable during business operations.

Sounds familiar? We know how to help.

[TALK TO US NOW!](https://itfandango.com/contact-us/)

### Solution Integration Testing (SIT)

![A mechanic checking a car's open bonnet](https://itfandango.com/wp-content/uploads/
2025/07/A-mechanic-checking-a-cars-open-bonnet-1024x683.jpg)

SIT is verifying that all components work well together.

Once you’ve confirmed each brick works individually, it’s time to see whether the
wall holds together. Solution Integration Testing (SIT) evaluates how well your 
Dynamics 365 solution components integrate across modules and external systems. 
Testing integrations and data flows between applications is the only way to ensure
seamless operation beyond individual functionalities.

This phase is where your consultants, integration leads, and infrastructure teams
all need to talk… and they rarely do unless forced. And yet, SIT is essential. It
validates business-critical **processes that cross application boundaries**, for
example between the ERP and a third-party warehouse system. You’ll want real data,
realistic scenarios, and systems configured exactly like production. No shortcuts
here.

If you’re lucky, your project has an automation strategy in place, and integration
test runs are repeatable. Automated testing simplifies the execution of integration
tests, making it easier to manage repeated test runs. Test automation also saves
time, reduces errors, and ensures consistency across cycles. If not, you’ll rely
on fragile manual walkthroughs and hold your breath.

#### What can go wrong

SIT fails in subtle but spectacular ways:

 * **Data and data mappings are incorrect or incomplete.** Missing field, inconsistent
   formats, simplistic or made-up records can bring down the whole chain across 
   the process.
 * **Systems are tested in isolation, not together.** Even with integrations in 
   place, outputs and inputs on the two sides are simulated and never run as full
   data flows. A dangerous shortcut that increases the risk of things breaking when
   all parts are used together.
 * **No one owns the end-to-end picture.** Each consultant owns their own area, 
   so problems with interfaces are more likely to be pushed around and fall between
   the cracks.

![](https://itfandango.com/wp-content/uploads/2024/04/thumbs-down-solid.png)

#### Worst case example

A retail company implemented Microsoft Dynamics 365 F&O and integrated it with both
a new customer web portal and a third-party warehouse management system. They tested
order flows from the portal to the ERP, and separately from the ERP to the 3PL system—
but not the full journey. After go-live, orders placed by customers in the web portal
failed to reach the warehouse due to an internal interface format error. This caused
order fulfilments to stall, forcing manual workarounds for two weeks and a drop 
in customer satisfaction.

Sounds familiar? We know how to help.

[TALK TO US NOW!](https://itfandango.com/contact-us/)

### End-To-End (E2E) testing

![A mechanic doing a car inspection with checklist](https://itfandango.com/wp-content/
uploads/2025/07/A-mechanic-doing-a-car-inspection-with-checklist-1024x683.jpg)

E2E testing is your final inspection from start to finish.

Now we’re simulating real life. End-to-end testing is where you validate that** 
full business processes** flow seamlessly across multiple users, departments, and
systems. Organisations rely on E2E testing to ensure their processes meet operational
goals and function as intended across all areas. Things don’t have to just work,
but they have to work _in concert from start to finish_. This is where you run transactions
from origin to completion, verify outputs, check financial postings, and ensure 
every handoff works. It’s testing a sales order from creation, through fulfilment,
to invoicing, and finally payment collection.

Business users must be front and centre here. They’re the only ones who truly understand
how the process unfolds day to day, with all its glorious messiness. Consultants
and test managers should enable, not dominate. The focus should not just be on expected
outcomes, but on confidence: thorough **E2E testing helps build trust** among key
users by demonstrating that the system can reliably support business operations.
This confidence is key for the next phase, UAT (more on this in a second).

Done well, E2E testing is a critical stress test of your overall solution design.
It’s the first time real users from different departments work together in the new
system, using shared data and end-to-end workflows. This is where gaps in handoffs,
misaligned configurations, and shaky process assumptions come to light. It also 
shows whether teams can operate in sync or if the design falls apart under cross-
functional pressure. Better to catch that now than later.

#### What can go wrong

E2E testing is where cross-collaboration is really put to the test, and will fail
if:

 * **You test only ideal paths and simple cases.** The real world doesn’t follow
   scripts. This is where variance and exceptions must be tested too. If your process
   collapses on the first deviation, it was never fit for purpose to begin with.
 * **Cross-team coordination fails.** Logistics doesn’t know what finance is doing,
   and sales is running its own show. They don’t work on the same data, so there
   is only local testing.
 * **Data doesn’t represent real operational loads.** Made-up records won’t cut 
   it anymore. You need real or representative data from start to finish.

![](https://itfandango.com/wp-content/uploads/2024/04/thumbs-down-solid.png)

#### Worst case example

In one implementation, E2E testing was executed in silos — sales, warehousing, and
finance each tested their steps independently because some areas of the solution
were still incomplete, so users worked with placeholder configurations. When those
were later finalised, key process flows changed. As a consequence, the tests performed
during E2E were no longer valid, and people were thrown into confusion during UAT.
Test scripts had to be rewritten on the fly, eating into time meant for actual validation
and impacting the project timeline.

Sounds familiar? We know how to help.

[TALK TO US NOW!](https://itfandango.com/contact-us/)

### User Acceptance Testing (UAT)

![A man driving a car on the road](https://itfandango.com/wp-content/uploads/2025/
07/A-man-driving-a-car-on-the-road-1024x576.jpg)

UAT is your road test, done by the driver.

User Acceptance Testing is where your business decides whether to bet its operations
on the new system. This is where the **entire solution is handled to business key
users**, who has to sign it off. Can you run your company with it? UAT validates
whether the configured system supports day-to-day work in a way that makes sense
to the people doing the work. This testing round is essential for ensuring the quality
of the final system, confirming that it meets business requirements and maintains
high standards.

If business users can’t complete their core tasks without confusion, workarounds,
handholding by consultants, or Excel lifeboats — then you’re not ready. Period. 
The mistake most companies make is treating UAT as a formality, failing to cover
key cases with real data and with **key users taking ownership**. And neglecting
to rectify and retest any failed test cases. Bug fixing can’t be postponed further.

Your best UAT cycles (yes, plural, as you may need more than one round) are immersive.
You give users real data, define business-oriented test cases, and let them do their
work. By now they should be **comfortable with the new ERP** and be aware of what
they want to test and how, based on their actual day job.

Tracking UAT outcomes is how you judge your overall readiness. Now more than ever
failed test cases must be logged, analysed, and retested — not ignored. The results
reveal whether issues are isolated or systemic, and whether the risk is manageable.
This informs your go/no-go call. If users aren’t confident, they won’t be magically
ready after once the ERP is live.

#### What can go wrong

Ignore UAT at your peril. Here’s how it fails:

 * **Users are underprepared.** They’ve never seen the system, let alone tested 
   it. Insufficient human resources (not automation tools) can make this worse, 
   as there may not be enough support or training available for users.
 * **Scripts are irrelevant.** If users can’t relate to the test cases, they’ll 
   skip steps or misinterpret the intent. They should be able to understand why 
   and how they’re testing something.
 * **Push to go-live overrides concerns.** Feedback is ignored, and issues are labelled
   as “phase 2 enhancements”. Sign-off is forced, because sticking to the project
   timeline becomes more important than having a stable solution.

![](https://itfandango.com/wp-content/uploads/2024/04/thumbs-down-solid.png)

#### Worst case example

A manufacturing company pushed through UAT even though users weren’t ready. Key 
users flagged that they hadn’t completed all scenarios and weren’t confident using
the new system without support. Despite this, management forced sign-off to avoid
delaying the go-live. As a result, they got post-go-live chaos. Things failed so
spectacularly that the IT team had to work late nights processing orders manually
and firefighting issues that should have been caught weeks earlier. What should 
have been a transition became a crisis.

Sounds familiar? We know how to help.

[TALK TO US NOW!](https://itfandango.com/contact-us/)

---

## Technical testing

Functional and process testing is not all that matters. In fact, while business 
users and stakeholders obsess over workflows, data, and outcomes, technical testing
quietly ensures that your Dynamics 365 solution doesn’t collapse under its own weight.

Unlike other test phases during the ERP implementation, **technical testing** lives
mostly behind the curtain. It’s run by developers, technical architects, and infrastructure
engineers, rather than business users or functional consultants. And while it might
feel distant from day-to-day operations, ignoring this layer is like building a 
skyscraper without checking the foundations.

Technical tests validate the system’s stability, performance, and resilience. Effective
technical testing starts during software development, relies on automation, and 
uses specialised testing processes and tools to verify the robustness of your entire
Dynamics 365 ERP solution. Let’s see how.

### Unit testing

Unit testing checks the smallest building blocks: individual functions or pieces
of logic. If your developer tweaks tax calculations or writes a new method, these
tests confirm that the code is actually working without technical errors. Done right,
they catch bugs early, before they reach functional experts or end users.

### Performance testing

This is your stress test. Performance testing simulates realistic transactional 
loads and concurrent usage to verify the system won’t buckle under pressure. Slowdowns
in production after go-live are often the result of performance tests that never
happened. Performance testing also verifies the power and resilience of your overall
setup, including devices and networks.

### Regression testing

Every change, like a new feature introduced by an upgrades or developing a new customisation,
risks breaking what used to work. Regression testing ensures stability by re-running
key test cases for existing features against new builds. Automating these is non-
negotiable. Without automated testing, teams resort to selective guessing.

---

## Other types of testing

Beyond the main and technical phases, there’s a handful of specialised testing and
validation types that may not have a dedicated item in your ERP implementation GANTT
chart — but they still are important. Some of these are early-stage fit checks. 
Others are post-configuration sanity tests. Together, they round out a** complete
Dynamics 365 testing strategy**.

### Conference Room Pilot (CRP)

A pre-build simulation of core business scenarios, sometimes done even before software
selection. It’s less about bugs and more about solution fit. If your solution doesn’t
make sense at this stage, you’ve got bigger problems than testing processes.

### Data validation

More of a validation than testing it itself, it checks that migrated data is accurate,
complete, and usable. If customer records are broken or historical orders are missing
key fields, other test phases will be impacted negatively.

### Reporting testing

Ensures business reports pull correct and relevant data and deliver the expected
information — again, this is more about validation than formal testing. Naturally,
it requires that data is valid and the design is complete to generate reports correctly.

### Security roles testing

Often done in an iterative way (even after go-live), it confirms that users can 
only access parts of the system that they’re supposed to. Incomplete or incorrect
security roles can negatively impact the effectiveness of later test phases like
UAT.

### Smoke testing and mock cutover

Smoke testing confirms basic system stability after each environment deployment 
and setup. It’s your first line of defence before deeper tests begin. Mock cutover,
meanwhile, simulates the full go-live sequence (data loads, config import, batch
jobs setup) to ensure the during the actual go-live people won’t unravel under pressure.

---

## Conclusion

Not every test type applies equally to every Dynamics 365 F&O implementation. If
your organisation runs a complex third-party tech stack, SIT becomes mission-critical.
If you’re rolling out heavy customisations, functional testing will demand more 
time and rigour. The key is **not skipping or compressing the tests that matter**,
since in most cases each testing phase builds on the last and has additional requirements
to be done correctly. Shortcutting test phases is a fast track to instability, poor
adoption, and rework after go-live. Treat testing as the safety system it is — and
give it the time and focus it deserves.

**Sections:**

 * [Introduction](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/#1)
 * [Main test phases](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/#2)
 * [Technical testing](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/#3)
 * [Other test types](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/#4)
 * [Conclusion](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/#5)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

The post [Dynamics 365 Testing, Part 1: Key Testing Phases During Your ERP Implementation](https://itfandango.com/articles/dynamics-365-erp-implementation-key-testing-phases/)
appeared first on [IT Fandango](https://itfandango.com).

## Implementing Dynamics 365: Preparing for a Successful ERP Implementation

- Link: https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/
- Published: 2025-05-30T15:35:24+01:00
- Author: Marco Romano

# Implementing Dynamics 365: Preparing for a Successful ERP Implementation

**Meeting these prerequisites is the difference between ERP success and a costly
and painful lesson**

30 May 2025

## Introduction

Implementing a new ERP is never just an IT exercise. When you’re talking about Microsoft
Dynamics 365, you’re not just replacing a legacy system. Instead (if you do things
right), you’re leveraging an entire ecosystem of products from Microsoft.

This article is a practical, no-nonsense guide to preparing for that journey. We’ve
written it for executives, programme sponsors, and project leaders who want to get
ahead of the chaos and avoid the common traps that derail ERP projects before they
even get going.

We’re not going to hype the technology and tell you how cool it is. We’ll tell you
how understanding the key decisions to make, involving the right people, and following
the correct processes will make or break your Dynamics 365 project before it even
starts.

### Key takeaways

 * **Dynamics 365 is not single application** but a modular platform. You need to
   understand how it works or you risk selecting the wrong solution for your need.
 * **Azure is more than just cloud hosting**, it’s a different operating model you
   will have to become familiar with.
 * **An ERP implementation is not just an IT project**, so you need a clear vision
   aligned with your business strategy.
 * **Vision needs to be translated into tangible business goals**, taking into account
   your starting point with honesty.
 * **Choosing the wrong Microsoft partner **will doom your project before it even
   starts.
 * But even the perfect Microsoft partner cannot make up for your **poor preparation
   and lack of internal knowledge**.

Ready to dive into each of these points? If you’re serious about a successful implementation,
the preparation work starts here.

---

## Understand the Microsoft Dynamics 365 ecosystem

### What is Dynamics 365? A unified platform to run the entire business

Let’s get this out of the way first, which seems to be the source of endless confusion:
Microsoft Dynamics 365 is not just a single enterprise system. It is a suite of 
different business applications that fuses CRM and ERP capabilities into a single,
cohesive unified platform running on the same environment. Microsoft’s idea is that
you start by implementing the business application(s) most relevant to your needs,
then you leverage the entire ecosystem by adopting the other ones step by step.

If there is one thing that Microsoft does better than competitors, is making available
an integrated ecosystem of applications, which you can use to run your operations
from customer interactions, through order fulfilment, to financial reporting across
the entire organisation. So Dynamics 365 is the hub where data, processes, and decision-
making come together, and it seamlessly integrates with other Microsoft products
like Office 365 and Power BI to enhance automation and data insights.

### How ERP and CRM capabilities became integrated

I’ll spend some time describing the difference between the two, but you can skip
ahead if you’re familiar with Dynamics 365 and how it evolved from the times of 
Dynamics AX and Dynamics CRM.

Historically, CRM (Customer Relationship Management) and ERP (Enterprise Resource
Planning) were treated as separate domains. Microsoft acquired different applications
from different companies in the early 2000 and created the Dynamics family (Axapta,
Navision, CRM, Great Plains, Solomon). Eventually Microsoft moved ERP and CRM to
cloud, which brought the addition of 365 to the name: that’s how Dynamics 365 Finance
and Operations (the cloud version of AX), Dynamics 365 Business Central (the cloud
version of Navision), and Dynamics 365 Customer Engagement (the cloud version of,
you guessed it, CRM) were born.

But wait, there’s more! While historically AX and CRM run on different architectures,
Microsoft put a lot of effort to make sure they could talk to each other, via the
so-called Common Data Services (nowadays known as Dataverse). This isn’t surface-
level integration. Dual-write allows Dynamics 365 applications to communicate natively,
enabling magical stuff like real-time stock adjustments between field service trips
and master plan runs. This is not trivial, and in an ideal scenario the Dynamics
365 suite can effectively operate as a single interconnected operational brain, 
rather a patchwork of loosely integrated tools.

So instead of two siloed systems, ERP and CRM, Microsoft now offers a plethora of
business applications built on a common architecture that enables seamless data 
flow and process integration across customer-facing and back-office operations. 
The suite is composed by different applications, whose names… well, they change 
frequently. So let’s get some clarity on that too.

### Dynamics 365, aka a suite to support various business functions

![The Microsoft Dynamics 365 logos in a round formation.](https://itfandango.com/
wp-content/uploads/2025/05/Dynamics-365-family.jpg)

Microsoft got really creative with its Dynamics 365 logos.

The Dynamics 365 suite comprises business applications that fall into two main categories(
as we said, ERP and CRM), although those distinctions are increasingly blurred. 
Here’s a simplified but comprehensive breakdown:

**ERP (Enterprise)**

 * Dynamics 365 Finance
 * Dynamics 365 Supply Chain Management
 * Dynamics 365 Commerce
 * Dynamics 365 Project Operations
 * Dynamics 365 Human Resources

**ERP (SMBs)**

 * Dynamics 365 Business Central

**CRM**

 * Dynamics 365 Sales
 * Dynamics 365 Customer Service
 * Dynamics 365 Contact Centre
 * Dynamics 365 Field Service
 * Dynamics 365 Customer Insights

What’s important to understand is that **these are not modules** ([D365 F&O has 40+ modules](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/)),
and in some cases they’re not even separate applications. This is because an ERP
is, by its nature, horizontally integrated: for example, Dynamics 365 Finance effectively
represents the financial and accounting side of the enterprise ERP offering. It’s
not a standalone financial systems like, say, QuickBooks.

You may use only Dynamics 365 Finance features, but you cannot deploy it (yet, at
least) as a standalone application. When you deploy a Dynamics 365 Finance and Operations
environment, you get access to all features, but you may choose to use only some
of them. Not last because what you use direct impacts the licenses you will consume(
a topic [we covered here](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/)).

The rest of this article focuses on Dynamics 365 Finance and Operations (mainly 
Finance and Supply Chain Management areas), since that’s where [our expertise lies at IT|Fandango](https://itfandango.com/solutions/d365-fo-advisory-retainer/).

### How Dynamics 365 solves complex business challenges

So now let’s take a step back to see the bigger picture. Since the technology is
clear, let’s answer one question: how does Dynamics 365 Finance and Operations support
your company operations? Microsoft’s flagship ERP is the right answer to your need
if you are a multinational organisation juggling one or more of the followings: 
multiple entities, tax regimes in multiple jurisdictions, intercompany trade, multiple
sales channels, project-based operations, engineer-to-order manufacturing, and more.
In fact, Dynamics 365 F&O has built-in capabilities for localisation, multicurrency,
and multi-entity management.

But the real secret weapon here? Power Platform. This is a suite of low-code tools
complimentary to Dynamics 365. Most notably, Power BI, Power Apps, and Power Automate
will reach everywhere your ERP doesn’t. You can build tailored satellite applications
to avoid costly customisations to the ERP, automate tasks and workflows, and generate
valuable insights to optimise operations. This is what I meant about leveraging 
the Microsoft ecosystem.

---

## Embrace the cloud with Microsoft Azure

![](https://itfandango.com/wp-content/uploads/2025/05/ITF-Blog-Embrace-the-cloud-
with-Microsoft-Azure.jpg)

### More than just cloud hosting

When you move to Dynamics 365, you’re also moving to Azure. For companies used to
managing on-premise systems, this isn’t just a change of infrastructure. It’s a 
shift in how your IT operates, especially during the deployment phase.

Azure offers global accessibility, automated scaling, and high availability as standard.
But it also shifts responsibility. There’s no longer a local server to reboot when
something goes wrong. Instead, performance issues might relate to resource sizing,
subscription mismanagement, or misconfigured network rules. And ultimately it will
be on your team to monitor and react.

### The security shift

Security doesn’t get easier in the cloud, it just moves to elsewhere. While Azure
provides excellent tools for encryption, access control, and monitoring, you’re 
still accountable for setting up security roles, managing integrations securely,
and ensuring data integrity and compliance across tenants and regions.

Cloud security requires new skills. Your IT team now needs to think in terms of 
conditional access policies, authentication layers, and log analytics, rather than
firewalls and antivirus. This might sound simplistic, but we’ve seen customers struggling
with it when the digitalisation process modernised their company’s tech 20 years
in one tenth of that timespan.

### Flexibility, with costs to match

Azure lets you scale resources up and down on demand. Need more capacity for parallel
development? Spin up another environment. Peak season passed? Dial it back. But 
without proper monitoring and governance, this flexibility turns into runaway costs.
Plenty of businesses are shocked by their first Azure invoice, so get your infrastructure
in order and don’t be one of them.

Plan ahead with the implementation cycle, distribute people’s workload wisely, review
performance needs regularly, and understand what each environment actually costs.
Implement data-driven decision making to ensure that your cloud monitoring and governance
are based on accurate information.

### A foundation to the ERP implementation process

Bottom line? Azure is a powerful enabler for your Dynamics 365 implementation, but
it’s not plug-and-play. Treat it as a core part of your ERP strategy, with the same
rigor as system design and process alignment. Get this wrong, and you’ll burn the
operating costs budget before you even go live.e ERP, automate tasks and workflows,
and generate valuable insights to optimise operations. This is what I meant about
leveraging the Microsoft ecosystem.

---

## Define your ERP vision and business goals

![](https://itfandango.com/wp-content/uploads/2025/05/ITF-Blog-Define-your-ERP-vision-
and-business-goals.jpg)

### Fit your ERP into a broader business vision

Implementing Dynamics 365 should be a deliberate strategic move, not just a reaction
to aging systems or a vague notion of “digital transformation”. Upgrading your enterprise
resource planning system (and everything that will change because of it) should 
be the operational engine behind your business strategy rather than a side product.

That means thinking beyond the IT domain. A Dynamics 365 implementation affects 
business processes, data architecture, and how your teams (from customer service
representatives to production planners and financial controllers) interact with 
their IT tools.

A unified platform like Dynamics 365 is capable of transforming how your company
runs, but only if it’s anchored to a clear business vision and a sound strategy.
The overall goal might be to modernise your IT landscape, support a future business
expansion, or align all your legal entities to use the same operational template,
but it has to be a clear one.

ERP implementations that start without vision end up half-baked and usually create
expensive rework.

### Set business outcomes that shape the system

Once the vision is clear, though, it’s time to get specific. What will success look
like in practice?

You need business goals that are measurable, time-bound, and grounded in how your
organisation actually works. Are you planning to consolidate reporting from all 
legal entities? Create a common data warehouse to receive data from all operational
systems and report accordingly? Gain visibility over your production steps, to actually
track materials and labour in your WIP? Whatever is it, define it clearly. Then 
design a solution that take it into account.

This is not trivial. An ERP runs on a clear financial and operational model to be
built on. You need clear business objectives, beyond IT, to get these right. In 
turn, these choices will guide scope decisions, user training plans, and the KPIs
you’ll use during the implementation process. A successful ERP project is measured
against outcomes, not just a timeline of “we went live in time and on budget”.

Too many implementation projects drift because their goals are abstract stuff like
better visibility or a more integrated system. Tie every design decision to a business
lever. That’s how you align delivery with value, and how you create a system that
supports your unique business processes.

### Tell the story and bring people with you

Now that the visions is grounded, it needs to be sold to a wider public. The implementation
team might understand the purpose of implementing Dynamics 365, but what about the
other key stakeholders?

Internal alignment requires a clear, repeated narrative: why this system, why now,
what changes, and what success looks like. In global organisations or diversified
business units, this is the difference between slow resistance and early buy-in.

Stakeholders don’t engage with configuration logic, they engage with outcomes. Effective
messaging improves user adoption, accelerates business readiness, and reduces friction
in the testing phase and post-go-live support. Again, this is not theoretical stuff
but what we’ve seen in practice over a decade of Dynamics 365 implementations.

Ultimately, your entire organisation will run on this new system, so they have to
own it. That ownership starts with understanding, and understanding starts with 
a story.

---

## Assess your current systems and readiness

![](https://itfandango.com/wp-content/uploads/2025/05/ITF-Blog-Assess-your-current-
systems-and-readiness.jpg)

### Understanding your starting point

Now, back again to the IT domain. We have a vision, we have measurable goals, and
hopefully we have key stakeholders on board. So before you leap ahead… look down
at where you’re starting from. What IT legacy systems are in place? What integration
challenges or data quality issues are hiding under the surface? What needs scrapping
or replacing?

Assessing your existing systems, infrastructure, and processes is a foundational
step in preparing for Dynamics 365. Far too often this is dismissed as an IT exercise
and in many cases it’s skipped altogether with the excitement of starting the implementation
process. But this is crucial: it’s about identifying risk, surfacing hidden complexity,
and clearing the path for a clean transition.

So what you really need to do is understanding your current business processes across
departments, especially those involving finance (AP, AR, etc.), supply chain management(
production, distribution, etc.), and third-party contact points like supplier and
customer interactions (procurement, sales). Many issues later in the project arise
because no one mapped the AS-IS situation with enough precision, including the location
of existing data that will have to be migrated. Trust us on this: if you don’t do
this preparation now, it’ll come back to bite you later.

### Key focus areas for readiness

So here’s a practical checklist of what to do. Before you start adopting Dynamics
365, you need to understand:

 * Which IT legacy systems need to be retired, replaced, or integrated
 * What effort may be required for data migration, cleansing, and validation
 * Whether your infrastructure and network are cloud-ready
 * How your existing business processes work and how they will change in the future

A clear-eyed assessment helps prevent surprises later, like finding out a critical
approval workflow was missed because it’s done via email, or when horrible data 
quality derails your testing timelines. This early preparation sets the stage for
later stages, including a successful data migration strategy that ensures data integrity
and system performance from day one.

As part of this effort, business analysts and system administrators should work 
together to assess cross-system dependencies and ensure your existing systems won’t
become anchors on your new platform. Getting this right is what separates project
success from post-go-live firefighting.

### What about the implementation process?

Assessing your starting point is good, but you also need to be aware of common issues
during the ERP implementation process (once you get there). So why not getting a
copy of our free guide ahead of time? We described **10 common functional issues
during a D365 F&O implementation**: what they are, why they matter, what happens
if they’re neglected, and how to spot red flags before they become critical issues.
Get your free copy from the form below.

![](https://itfandango.com/wp-content/uploads/2025/05/Mockup-Functional-Health-Check-
Free-Guide-Cover-Extended-1024x635.png)

D365 F&O Functional Health Check

10 common implementation functional issues and how to identify them

**Download your free copy!**

 The form can be filled in the actual [website URL](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/).

---

## Choose the right Microsoft implementation partner

![](https://itfandango.com/wp-content/uploads/2025/05/ITF-Blog-Choose-the-right-
Microsoft-implementation-partner.jpg)

### What makes a strong implementation partner?

Now let’s talk about who will be with you in this journey. Your system integrator
will become a key supplier and an extension of your team for months, possibly years.
It’s essential they bring more than just technical know-how. Look for experience
in your industry, a robust methodology, transparency in delivery, and most importantly,
a willingness to challenge your assumptions. Leveraging specialised expertise from
external support resources and the right Microsoft implementation partner will increase
your chances of a successful Dynamics 365 project.

Good Microsoft partners help you see around corners. They’ve done this before. They’ll
warn you when scope creep is setting in, question whether customisations are really
needed, and keep your strategic goals in focus.

But not all partners are the same. Stay away from cheap quotes. Mismatched or inexperienced
partners, who never implemented ERP before, are one of the most common root causes
of failure in Dynamics 365 ERP implementations. A good one can keep you out of trouble
before the project even starts.

### Weighing size vs specialisation

So which Microsoft partner should you choose? Large system integrators offer breadth
and scale. They have ready-made assets, offshore resources, and credibility with
Microsoft. But their delivery model can be rigid, their capacity split between multiple
clients, and you might find yourself working with less experienced consultants than
promised (ever heard of team A and team B?).

Boutique consultancies can play a critical role here. They will not replace your
internal ownership nor the system integrator, but will plug the gaps. They bring
specialist knowledge, cross-industry patterns, and the capacity to work shoulder-
to-shoulder with your implementation team. This is especially useful in complex 
business challenges where a standard approach with off-the-shelf methods would fall
short.

Specialist boutiques are also a hedge against project drift. They focus on quality
over scale and call issues out when they see them. If you leverage their specialised
expertise correctly, you can improve your project success, reduce deployment complexity,
and build tailored solutions that align with your specific requirements. And this
can make all the difference between implementing a solution that fits your needs
and one that turns out to be unfit for purpose.

### The importance of clear engagement terms

How you set the relationship with your partner will shape the entire working relationship
with them. Ensure that you define responsibilities on both sides, have a well-defined
scope and mechanisms to control it, clear timelines and milestones, and processes
to manage escalation and change requests. Where possible, this stuff should be in
writing in a contract.

Oh, and nedless to say, it’s difficult to have robust governance over the programme
if no discovery work was done beforehand, and you have zero clarity over your business
objectives are you’re just aiming to “implement Dynamics 365”. We said this earlier—
that’s a bit too vague, isn’t it?

Oh, and speaking about vagueness: be cautious with time-and-materials models, because
they incentivise doing more rather than doing better. Virtually the entire ERP implementation
industry works on a time-and-materials model, so your budget may run out sooner 
than you realise. Leave it unmanaged and this will be a certainty, not just a risk.
[Project scope can easily grow out of control](https://itfandango.com/articles/d365-fo-implementation-challenges/),
taking the budged with it. So focus on defining and controlling the scope. You want
a tailored solution for your needs, but this doesn’t mean that every single desire
must be realised before go-live. Implementing an ERP is marathon, not a sprint. 
And the go-live is not the finish line.

### Internal readiness to work with your partner

Even if you find the perfect, most capable Microsoft implementation partner for 
your Dynamics 365 implementation, they will never be able to make up for one thing:
a weak client team. You need decision-makers, subject matter experts, and internal
project governance (more on this in a moment). You also need to know your own processes,
tech, data, and what “good” looks like for your business. When the client side is
unprepared, even the best partner will struggle to provide ongoing support throughout
the project and beyond.

We’ve witnessed solid delivery teams flounder because the client couldn’t make decisions,
didn’t have process clarity, or relied entirely on outsiders to define their business.
Things were so slow and clunky to move, and the effort was so disorganised, that
at some point the implementation project collapsed under its own weight and was 
eventually halted. separates project success from post-go-live firefighting.

---

## Build a strong internal project team

![](https://itfandango.com/wp-content/uploads/2025/05/ITF-Blog-Build-a-strong-internal-
project-team.jpg)

### Governance and executive sponsorship

So how do you build a strong internal team? It starts wit the project sponsor, who
is not just a figurehead. This person secures funding, makes top-level decisions,
and shields the project from organisational politics. Without them, critical issues
will linger unresolved longer than they should.

Around him or her, a governance structure should ensure alignment across business
units and functional streams. A steering committee that meets regularly, understands
trade-offs, and can break deadlocks is required for a project of this size. A strong
committee makes a big difference when it comes to executive power.

### Solution architect and functional leads

These guys are your blueprint designers and operational leaders. The solution architect
ensures the system design supports your business model, both now and in the future.
They’re the linchpin between business requirements and technical implementation,
validating design choices and ensuring overall coherence.

Functional leads bring the operational expertise across project streams (sales, 
procurement, manufacturing, finance, etc.). They can quickly understand how your
company operates and they know how the system works, so they can make the right 
choices for your needs. Their job is to design the solution in detail, configure
the system, support testing, and ensure the system fits real-life needs rather than
just a textbook process.

These roles must exist within your organisation. You cannot outsource this entirely
to your partner and expect alignment. It’s your business, your processes, your ownership.

However, there is one challenge: true Dynamics 365 talent is hard to find. Building
up a permanent team will take ages, and relying on contractors may give you whoever
is available in that moment rather than who’s best for you. One workaround? Engage
a boutique consultancy of functional experts. They will augment your team while 
they align with you on key decisions. This is powerful: it means having on your 
side people who bring cross-industry expertise, know well how to implement solutions
within ERP projects, and can keep your system integrator honest and aligned.

### Business analysts and super users

Next, we have business analysts and super users. They are already part of your organisations
and are usually seconded to the project for the duration of the ERP implementation.

Business analysts help gathering requirements, challenging inconsistencies, and 
making sure documentation is accurate and clear. Their job is to think critically
and support super users who may not have sufficient understanding (nor interest)
in ERP concepts.

Super users are the change agents on each business units. They are usually not IT
specialist but cover a key part in executing testing, receiving training, and providing
user feedback on the solution. Post-go-live, they’ll be your first line of support
and your solution’s loudest advocates… or your sharpest critics if the new ERP doesn’t
make their life easier.

Having dedicated people in these roles is the foundation of a successful implementation.
When these roles are weak or too busy with BAU, you can expect misalignment, rework,
and low adoption to follow.

### Why your implementation team is the real success factor

A well-prepared internal team is the single most important asset you bring to the
table. It’s the difference between a system that’s configured _for_ you and one 
that’s shaped _by_ you. These roles aren’t just there to liaise with the partner.
They’re there to drive decisions, safeguard your priorities, and ensure the new 
system actually fits the business it’s meant to serve.

You can’t outsource ownership. The sooner you build real internal capability and
provide comprehensive user training, the smoother your implementation will be. By
the way, if you want to read more about selecting the right people for your project
team, [this article](https://itfandango.com/articles/your-d365-fo-project-team-champs-or-chumps/)
tells you everything you need to know with a bit of humour.

---

## Conclusion

There’s no shortage of Dynamics 365 [horror stories out there](https://itfandango.com/articles/d365-fo-implementation-challenges/).
Overruns, rewrites, and reworks are abundant. At the heart of most of them is the
same pattern: unclear goals, unprepared teams, and an overreliance on partners to
do both the thinking and the execution.

Getting your implementation right starts well before the system is built. It’s in
the vision. The governance. The choices about people and scope and trade-offs. Every
decision you make in the early stages either prevents problems or bakes them in.

If there’s one message we want you to take away, it’s this: ERP implementations 
don’t fail because the technology didn’t work. They fail because the business didn’t
lead.

Prepare well, and Dynamics 365 will transform your business. Prepare poorly, and
you will learn an expensive lesson for years to come.

**Sections:**

 * [Introduction](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/#1)
 * [Understand Dynamics 365](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/#2)
 * [Embrace the cloud with Azure](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/#3)
 * [Define your ERP vision and goals](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/#4)
 * [Assess your starting point](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/#5)
 * [Choose your Microsoft partner](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/#6)
 * [Build a strong internal team](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/#7)
 * [Conclusion](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/#8)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

The post [Implementing Dynamics 365: Preparing for a Successful ERP Implementation](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/)
appeared first on [IT Fandango](https://itfandango.com).

## Dynamics 365 License Types: A Guide on Upcoming Changes to D365 F&O License Enforcement

- Link: https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/
- Published: 2025-05-13T21:53:55+01:00
- Author: Marco Romano

# Dynamics 365 License Types: A Guide on Upcoming Changes to D365 F&O License Enforcement

**Why you’re about to pay a lot more for Dynamics 365 licenses (and what to do about
it)**

13 May 2025

## Introduction

Navigating the labyrinth of Microsoft Dynamics 365 licensing is no small feat. With
Microsoft’s upcoming enforcement changes, understanding how business applications
are licensed (Finance, Supply Chain Management, Commerce etc.), and what license
types exist out there (user, device, and tenant) has just dramatically increased
in priority for many companies. This guide demystifies each license type and outlines
the impending shifts, so you can remain compliant and cost-effective.

### Disclaimer

A word of caution: this article is based on the latest available Dynamics 365 licensing
documentation and enforcement guidance as of May 2025 (updated July 2025). The upcoming
changes to license enforcement are still evolving, and Microsoft may update its 
policies or tooling. Everything outlined here reflects the best information available
at the time of writing but, as always, this is subject to change.

### Key takeaways

 * **Optimising security roles to reduce license consumption isn’t a quick fix.**
   It’s a messy, time-consuming job that requires deep expertise. If you haven’t
   started already, you’re behind schedule.
 * **Dynamics 365 license types are about system access. **They are not just about
   what you buy, rather how much of the system users have access to. To avoid surprises,
   you need to understand:
    1. The different license types that exist for the Dynamics 365 apps suite
    2. How each Dynamics 365 business application is licensed
    3. How security role configurations drive actual license consumption
 * **The honour system is dead.** From 1 November 2025, Microsoft will enforce license
   compliance in Dynamics 365 F&O — no license, no access. If you’re not ready, 
   your users won’t be able to use your ERP.

### Wait! Before we begin…

Unexpected license costs are only one the issues in the Dynamics 365 Finance and
Operations journey. We wrote a **practical guide for senior leaders **of companies
already live with D365 F&O. It describes symptoms that your new ERP is failing to
deliver the promised benefits, what are the likely root causes, and what to do about
them. Download your free copy from the form below.

![](https://itfandango.com/wp-content/uploads/2025/05/Mockup-Underperforming-Free-
Guide-Cover-Extended-1024x739.png)

Field guide to underperforming D365 F&O systems

Seven operational symptoms your ERP is failing to deliver after go-live

**Download your free copy!**

 The form can be filled in the actual [website URL](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/).

---

## The Dynamics 365 ERP and CRM business applications

![A series of Microsoft application logos.](https://itfandango.com/wp-content/uploads/
2025/05/image-1024x406.png)

The colourful logo collection of the Microsoft Dynamics 365 business applications
and ecosystem.

Let’s clear something up straight away: **Dynamics 365 is not a single product**.
It’s a suite of cloud-based business applications, designed to support a wide range
of operational and customer-facing processes. Each application targets specific 
business needs and business areas. Broadly speaking, the suite covers both Enterprise
Resource Planning (ERP) and Customer Relationship Management (CRM), although those
terms are more legacy labels than functional boundaries these days.

This shift happened with the move from on-premise systems like Microsoft Dynamics
AX to Dynamics 365 in the cloud. Alongside the new architecture came a modular application
model. Microsoft no longer sells a monolithic ERP. Instead, what you get is a set
of integrated apps that work together, built on a common platform (yes, that’s where
Dataverse and dual-write come in — but let’s not go there today).

So what does this suite actually include, specifically on ERP and CRM?

 1. **ERP suite for enterprise organisations:**
 2.  * Dynamics 365 Finance
     * Dynamics 365 Supply Chain Management
     * Dynamics 365 Commerce
     * Dynamics 365 Project Operations
     * Dynamics 365 Human Resources
 3. **ERP for small and medium companies:**
 4.  * Dynamics 365 Business Central
 5. **CRM application suite:**
 6.  * Dynamics 365 Sales
     * Dynamics 365 Contact Center
     * Dynamics 365 Customer Service
     * Dynamics 365 Field Service
     * Dynamics 365 Customer Insights (formerly Dynamics 365 Marketing)

The naming convention is fluid and Microsoft changes it regularly. For example, 
the official name for the first group is now _finance and operations apps_, even
though many still call it Dynamics 365 Finance and Operations.

This is because within the ERP, these aren’t technically separate applications. 
You don’t install “Finance” or “Supply Chain Management” as standalone apps. What
you install is a unified ERP system, and the parts that you use drive your license
usage.

(It’s technically a bit more complicated than this, with certain parts enabled by
license keys and additional cloud-based features, but let’s keep it easy here — 
it’s already complex enough.)

That’s why these business applications “names” are best understood as **license-
defined groupings**. Each one covers certain functional areas of the Dynamics 365
ERP. So while the system itself is integrated, the parts that you use define which
applications and related licenses you will need to buy.

Oh, and it’s important to understand that these are not modules. They are still 
called apps or applications. Dynamics 365 Finance and Operations (the entire ERP)
has 40+ modules, [which I have explained in another article](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/).

So before I finally tell you about licenses, first I need to briefly explain what
these key applications actually do. From now on, I will only cover the Finance and
Operations side of things, that is the ERP suite for enterprise applications.

If you’re already familiar with it, just skip to the next section. Let’s dive in.

### Dynamics 365 Finance

Dynamics 365 Finance handles **core accounting and financial management** (like 
expense entry, financial reporting, budgeting, and more) making it essential for
finance employees, full users, and controllers who need consistent, detailed oversight
of financial data. As the backbone of your ERP, it enables strategic alignment between
financial operations and broader business needs.

### Dynamics 365 Supply Chain Management

Dynamics 365 Supply Chain Management in Dynamics 365 supports **inventory control,
procurement, manufacturing, and logistics**, giving supply chain managers and professional
users the tools to run critical business processes smoothly. For companies managing
physical goods, it’s the central hub for ensuring that operations stay efficient
and scalable.

### Dynamics 365 Commerce

Dynamics 365 Commerce delivers integrated **retail and POS capabilities** for omnichannel
sales, enabling customer service representatives and sales teams to manage the full
customer journey from online to in-store. It connects sales, product, and customer
data across channels to support seamless customer engagement and drive smarter decisions.

### Dynamics 365 Project Operations

Dynamics 365 Project Operations equips **project-based businesses** with planning,
costing, and delivery tools, combining project service automation and workflow visibility
to keep operations aligned and predictable. It’s built for field service teams, 
consultants, and full users who manage timelines, budgets, and deliverables.

### Dynamics 365 Human Resources

Dynamics 365 Human Resources supports HR professionals across the **employee lifecycle**,
covering everything from recruitment to benefits management. For organizations focused
on workforce stability and growth, it ensures your people strategy stays aligned
with your operational goals.

---

## The Dynamics 365 licensing model explained

Let’s take a step back and pretend you’re coming from SAP, have never touched Microsoft
Dynamics 365, and you’re [preparing to implement it](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/).
At first glance, the licensing looks simple: pick your business apps, count your
users, and buy what you need. Easy, no? No. It’s only easy until you realise what’s
lurking beneath the surface.

Let’s start with the basics: **Dynamics 365 uses a modular, role-based licensing
model**. It’s designed to be flexible, more like a Swiss Army knife than a sledgehammer.
The primary mechanism is named-user subscriptions (User Subscription Licenses or
User SL): you pay per user, per month, based on the system access they actually 
need. So far, no surprise.

However, in Dynamics 365 Finance and Operations, it’s what users _can do_ in the
system (not what you _think_ they do) that determines the required license. This
model’s strength lies in precision: give users only what they need to do their jobs,
and you will keeps costs under control. Don’t, failing to understand how role-based
access maps to license consumption, and you will pay way more than anticipated.

And yes, it’s convoluted and complex to setup correctly. Think reading the tax code
while riding a unicycle, and you can get an idea.

Oh, and if you’re **upgrading from Dynamics AX**, don’t assume anything. The architecture
might look familiar, but the licensing logic is now different (relying on both entry
points and security privileges — but this is a topic for the techies). One of the
biggest mistakes companies make is assuming traditional or legacy usage maps neatly
onto the new model. It doesn’t.

Anyway, while user-based licensing covers the biggest part of Dynamics 365 licensing,
there are exceptions. For example, you may be required to license the hardware (
via device licenses), or pay for additional platform-wide services (via tenant licenses).
These are handled through different license types, but more on that in a minute.

What matters now is this: understanding how your users interact with the system,
and configuring their access appropriately, is the only way to stay compliant and
avoid unnecessary spend. And with Microsoft’s enforcement deadline approaching fast,
waiting is no longer an option.

---

## The Dynamics 365 license types and what they actually mean

Now, for the real complexity. Dynamics 365 applications are licensed by subscription
type:

 * **Tenant licenses** apply to your entire Dynamics 365 environment and power organisation-
   wide features, like cloud services or integrations. Think your e-commerce integration.
 * **User licenses** are by far the most common and probably bulk of your costs,
   depending on how many employees use the system. They are assigned to named individuals
   based on their role. Think John in accounts payable.
 * **Device licenses** are required for shared terminals in environments like shop
   floors, warehouses, or retail counters. Think the handheld scanner used by the
   picking team.

Most organisations will need a blend of user, device, and tenant licenses to fit
their structure, workforce setup, and industry-specific needs. Manufacturing? You’ll
likely lean harder on device licenses. Professional services? Full user licenses
for the finance team, but cheaper team member licenses for timesheet users. There’s
no one-size-fits-all, but there is a right-size-for-you. Designing your solution
with that in mind is the first battle.

Indeed, getting the license mix right starts long before your first user logs in.
It begins with solution design at the time of planning your Dynamics 365 implementation—
at least on a high level. Do it wrong, and after go-live you’ll end up with a license
bill way higher than expected.

Because this isn’t just about ticking Microsoft’s compliance boxes, now that the
consumption enforcement is imminent. Sizing your license usage correctly is also
a matter of operational efficiency. It’s about ensuring people have whatever system
access they need (no more, no less) to do their job properly.

So what are those three license types about, how do system usage affect what licenses
you need?

---

## User licenses: priced per individual

User licenses in Dynamics 365 Finance and Operations are like boarding passes: assigned
to named individuals, valid for specific destinations (i.e. apps features), and 
priced according to how far they’re going. These licenses are the backbone of any
ERP setup, and they dictate what users can actually do in the system based on their
role and responsibilities.

Each user gets licensed individually, but not all licenses are created equal. For
D365 F&O apps, these user licenses come in four main tiers:

 * **Premium**
 * **Full **(**Base Licenses** and **Attach license**)
 * **Operations **(aka **Activity**)
 * **Team Member**

They vary depending on the extend system features are accessed.

For example, full users the ones posting finance journals, managing sales orders,
or scheduling production: they need the core features of the application. Team Members,
on the other hand, might just need to post their own timesheets.

Mixing these up is a costly mistake: too much access and you’re paying for features
no one uses; too little and people start building Excel workarounds that quietly
derail your entire system.

And before we go any further, here’s a non-negotiable: if you want to use the Dynamics
365 Finance and Operations ERP, you need to **buy at least 20 full user licenses**
for Finance or for Supply Chain Management (not a mix between the two). That’s Microsoft’s
minimum requirement for entry. The rest is built up from there.

So understanding these tiers isn’t just a trivial licensing nuance: it’s your main
financial control mechanism when it comes to your subscription costs. Get it right,
and your system runs smoothly without blowing the budget. Get it wrong, and you’re
either overpaying or under-delivering.

Now, let’s what each named user license actually means in practice.

### Premium license

Right now, **Premium licenses **look a lot like Full access user licenses. In terms
of day-to-day features, you won’t spot much difference. The distinction lies in 
behind-the-scenes metrics like capacity entitlements and storage thresholds for 
specific advanced features. These licenses are only available for Dynamics 365 Finance
and Supply Chain Management, and may evolve to include exclusive capabilities in
the future. If you’re assigning Premium licenses today, it’s likely because your
usage patterns push the limits of standard resource allocations, not because your
users need radically different tools (yet).

### Full access license (Base license and Attach license)

**Full-access user licenses** are your daily key users, the people who live in the
system. This includes roles like finance employees, operations leads, or customer
service representatives who need to enter, edit, and action things across the ERP.
These licenses come in two flavours:

 * The **Base license** is your initial (and most expensive) seat. Every full user
   starts here.
 * The **Attach license** is a discounted add-on that let you access other business
   applications in the suite, but only if you’ve already got a qualifying Base license.

Functionally, there’s no difference between a Base license and an Attach license.
They’re the same under the hood, so the only difference is pricing. Attach gives
you the same firepower for less, but only as a second seat. One catch, though: not
all Base licenses are compatible with all Attach licenses. So no, it’s not a pick-
and-mix free-for-all. But you can check your options in the picture below, straight
from the official Dynamics 365 Licensing Guide of May 2025.

![An image of license combinations from the Microsoft Dynamics 365 Licensing guide.](
https://images.surferseo.art/07346d13-118c-4f35-a991-9815caf6522b.png)

The allowed combinations of Base licenses and Attach licenses, according to the 
official Dynamics 365 Licensing Guide (May 2025).

### Operations (aka Activity) license

The **Operations license **(also known as** Activity license**) hits the middle 
ground, being designed for professional users who do real work in the system but
don’t need key features. Think entering purchase orders, updating inventory, or 
tracking production, but not posting financial journals or creating new production
orders. It delivers more capabilities than a Team Member license, but at a fraction
of the Base license cost. It’s a go-to option for cost savings without gutting access,
and a good opportunity for cost saving. Miss this option and you’re either paying
too much, or throttling your operations unnecessarily.

### Team Member license

**Team Member** **licenses **are the lightest of the user license types, ideal for
users who need limited access to the simplest areas of the ERP. They’re great for
light users who approve requests, track time, or submit their own expense entry.
That’s people who dip in and out of the system but don’t drive key processes.

---

## Device licenses: priced per hardware

Device licenses are assigned to a **specific piece of hardware**, not a person. 
They’re built for scenarios where multiple users share a dedicated terminal: think
warehouse floor scanners, retail tills, or shared PCs in a manufacturing plant. 
Instead of licensing every person who might use the system, you license the device
they all use.

This model is ideal for shift-based operations or high-turnover roles, where assigning
individual user licenses would be expensive and largely unnecessary. Device licenses
come in two forms: full-access (covering rich functionality for applications like
Finance and Supply Chain Management) and limited-access (designed for light tasks
like time entry or expense approval).

Depending on the Dynamics 365 application, these devices can be accessed via shared
logins (e.g. “Warehouse Computer”) or individual credentials. Full-access device
licenses are common for operations roles, while limited-access ones are useful where
multiple users only need to consume data or perform basic actions.

![An image of a warehouse scanner](https://rmsomega.com/wp-content/uploads/2022/
10/retail-photography-application-lowes-mc9300-20-3600x3600-1-scaled.jpeg)

A warehouse scanner would trigger a Device license.

---

## Tenant licenses: priced per system-level features

Tenant licenses apply to **your entire Dynamics 365 environment**, not to a specific
user or device. They enable platform-wide functionality (think Dataverse storage,
customer profile tracking, or AI services) that benefits everyone logged into the
system. Think of them as infrastructure-level power: invisible to users, essential
to operations.

Some business applications or features, like Customer Insights or Electronic Invoicing,
are only licensed at the tenant level — there’s no such thing as a per-user option.
Others, like Finance or Supply Chain Management, come with base capacity entitlements
that can be extended with Tenant-level add-on licenses. These might include more
storage, higher transaction volume, or other resource allowances pooled across the
whole tenant.

Tenant licenses are often overlooked in initial planning, but they’re critical for
scaling. If your organization exceeds default capacity limits (or expects to) you’ll
need to factor these into your licensing strategy early. In some cases, these licenses
aren’t optional bells and whistles, rather they’re what keep the system running 
when you start pushing serious volume.

![A picture of a laptop with a small supermarket cart on it.](https://www.infosysbpm.
com/content/dam/infosys-bpm/en/blogs/images/ecommerce-integration-guide-medium.jpg)

An e-commerce integration would require a Tenant license.

---

## Upcoming changes to Dynamics 365 licenses enforcement

Microsoft is finally putting an end to the licensing honour system in Dynamics 365
Finance and Operations. For years, you were trusted to assign the right licenses
without enforcement. That ends now. Two enforcement deadlines are approaching fast,
and they’ll fundamentally change how access to your ERP is managed.

### 1 September 2025: In-app warnings begin

From this date forward, any user accessing Dynamics 365 Finance and Operations without
a valid license will see an in-app banner instructing them to contact their administrator.
So far, this is a gentle reminder that will alert users (and by extension, IT departments)
to misconfigured or missing license assignments.

 * These warnings function as an early warning system to address license problems
   before they escalate into access blocks.
 * They provide a grace period to correct licensing issues while maintaining system
   access.
 * Administrators should treat this date as the final checkpoint to verify every
   user’s license status before stricter measures kick in.

### 1 November 2025: No license, no access

After this date, any user without a proper license assigned via the Microsoft 365
Power Platform Admin Center (PPAC) will be blocked from using Dynamics 365 F&O. 
There’s no fallback, no exceptions.

 * Licenses must be assigned through the Microsoft 365 Power Platform Admin Center.
   This will be the single source of truth for license consumption.
 * Licensing will work exactly like Microsoft Office: if your company has not purchased
   and assigned a valid seat to your user, you’re locked out and cannot utilise 
   the application.

This change centralises license management and aligns it with the broader Microsoft
365 ecosystem. It also means license assignments are no longer solely the Dynamics
365 system admin’s responsibility, but they require direct collaboration with the
overall IT admin team, who might have limited understanding of the specific Dynamics
365 licensing nuances.

### The PPAC licensing report is your new best friend

With this enforcement shift, the **Microsoft Power Platform Admin Center** (PPAC)
becomes the definitive source of truth for license consumption. Microsoft will use
this report for both enforcement and audit visibility.

 * All license usage and assignments will be monitored through this report, with
   data flowing to F&O for enforcement.
 * Any mismatch between user actions and assigned licenses will be flagged here.
 * Organisations must treat the PPAC licensing report as their primary diagnostic
   and planning tool going forward.

### You’ll need to commit (and pay)

Microsoft’s licensing is a technical shift with a commitment that has financial 
consequences. With enforcement becoming automated:

 * You must purchase sufficient licenses in advance and assign them correctly.
 * These licenses typically come with a minimum term commitment, especially under
   enterprise agreements.
 * License costs must be factored into both budgeting and governance, as this is
   no longer a “we’ll fix it later” compliance area.

### Prepare now or deal with the fallout later

So, if you’re still in “we’ll sort it later” mode, it’s time to snap out of it. 
Here’s what to do:

 * Audit your current license assignments against how users actually use the system.
 * Align your Dynamics 365 consultants, support, and admin teams. They’ll need to
   work together.
 * Review your contracts: know your renewal cycles, your minimums, and your true-
   up terms.
 * Put governance around license assignments. This isn’t a one-and-done job, it’s
   ongoing.

The bottom line: **enforcement is coming**, and Microsoft means it this time. If
you’re not ready, users will be locked out, costs will spike, and audit risks will
rise. If you are ready, it’s just another compliance box ticked quietly, in the 
background, where it should be.

---

## Conclusion and next steps

The days of vague licensing policies and “we’ll deal with it later” are over. After
1 November 2025, if users don’t have the right Dynamics 365 licenses properly assigned,
they won’t be able to access the system.

Yes, **this will likely cost you more money**. But the real decision is whether 
you spend it deliberately, by matching licenses to actual usage and tightening up
your compliance, or waste it reacting to preventable lockouts, missing licenses,
and late-night audit panics.

And let’s be honest, you’ll probably need expert help. Most organisations don’t 
have the internal bandwidth or specialised knowledge to map out license strategies,
optimise security roles, and navigate Microsoft’s constantly shifting licensing 
terms.

That’s where we come in, as an [independent boutique consultancy](https://itfandango.com/about-us/).

We’ll help you cut through the noise, clean up your license footprint, and put a
sustainable security model in place before the new rules hit. No fluff. No panic.
Just straight-talking guidance from people who’ve been in the trenches and know 
how to navigate security roles configuration and licensing landmines without losing
sleep… or budget.

### One last thing

If you want to know more about the type of D365 F&O problems we can help you with,
download our guide below. It’s designed for** senior leaders of companies already
live with D365 F&O**. We cover 7 symptoms that your new ERP is failing to deliver
the promised benefits, what are the likely root causes, and what to do about them.
Get your free copy from the form below.

![](https://itfandango.com/wp-content/uploads/2025/05/Mockup-Underperforming-Free-
Guide-Cover-Extended-1024x739.png)

Field guide to underperforming D365 F&O systems

Seven operational symptoms your ERP is failing to deliver after go-live

**Download your free copy!**

 The form can be filled in the actual [website URL](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/).

**Sections:**

 * [Introduction](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#1)
 * [D365 business applications](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#2)
 * [The licensing model](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#3)
 * [D365 license types](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#4)
 * [Upcoming changes](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#5)
 * [Conclusion and next steps](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#6)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

The post [Dynamics 365 License Types: A Guide on Upcoming Changes to D365 F&O License Enforcement](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/)
appeared first on [IT Fandango](https://itfandango.com).

## All Dynamics 365 F&O Modules, Explained

- Link: https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/
- Published: 2025-02-15T17:14:17+00:00
- Author: Marco Romano

# All Dynamics 365 F&O Modules, Explained

Without Fluff, So You Can Understand What They Do And If They’re Right For You

15 February 2025

## Introduction

### Why this article

Axapta is dead. Dynamics AX is dead. Dynamics 365 F&O is dead. The official name
at the time of writing is finance and operations apps (we still like to call it 
D365 F&O, though). What’s not dead, but very much alive instead, is **confusion 
with the Microsoft product naming**.

Microsoft is shifting toward app-based solutions, but what does that even mean? 
When you log into D365 F&O, do you see a big button for _Finance_ and another for
_Supply Chain Management_? No, you see a list of 40+ modules. And it’s not always
clear what each one does. The two names above are not actually modules or products
per se, but licenses (and that’s a topic for [another article](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/)).

But can’t you just check Microsoft Learn to, indeed, learn? In theory, yes. In reality,
Learn focuses more on features and products than modules. Module pages do exist,
but they’re sometimes chaotic, group different features together, or may be too 
vague for your use case. So, where does that leave you?

Here. This article breaks down D365 F&O modules into **clear functional groups**,
giving you a practical way to evaluate which ones matter for your business. No fluff,
no sales pitch — just straight-to-the-point explanations of what they do, when they’re
needed, and what risks you face if you don’t set them up correctly.

### A disclaimer

Before we move on, a few important notes:

 * **ERP modules don’t exist in silos.** The grouping here is for clarity, not an
   absolute truth. If you disagree with some of our choices, that’s fine — there’s
   no _official_ way to group them. We tried to use original names to avoid confusion
   with the current naming convention.
 * **D365 F&O evolves fast.** Microsoft releases updates twice a year. Some of what’s
   written here may change sooner than you expect, so bear this in mind.
 * **Industry matters.** If you’re in a niche sector, some of our observations may
   not be applicable to you. D365 F&O is expanding, and industry-specific modules
   are on the rise.

### What about implementing D365?

Knowing what you can do with D365 F&O is good, but also pointless if you’re unaware
of what can go wrong during the ERP implementation. That’s why we wrote a guide 
about **10 common functional issues during a D365 F&O project**: what they are, 
why they matter, what happens if they’re neglected, and how to spot red flags before
they become critical issues. Before you keep reading about all the modules, get 
your free copy from the form below.

![](https://itfandango.com/wp-content/uploads/2025/05/Mockup-Functional-Health-Check-
Free-Guide-Cover-Extended-1024x635.png)

D365 F&O Functional Health Check

10 common implementation functional issues and how to identify them

**Download your free copy!**

 The form can be filled in the actual [website URL](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/).

---

## All modules by functional group

### Core accounting

This functional group includes the following modules:

 * General ledger
 * Accounts payable (UK: Purchase ledger)
 * Accounts receivable (UK: Sales ledger)
 * Tax
 * Consolidations

They form the backbone of your financial management in D365 F&O. You can track income
and expenses, manage supplier and customer payments, stay tax compliant, and consolidate
financials across multiple entities. When set up correctly, they create an audit-
ready system that ensures financial accuracy and regulatory compliance.

If your business operates across multiple legal entities, deals with complex tax
requirements, or needs strict financial controls, these modules must be configured
carefully. Many organisations assume the standard setup will work, but gaps often
emerge — especially in areas like intercompany transactions and consolidation rules.

A weak accounting setup leads to reporting inaccuracies, reconciliation issues, 
and inefficiencies. We’ve seen companies struggle with fragmented financial data
and manual workarounds. If you want seamless financials in D365 F&O, getting expert
guidance early can save you time, cost, and frustration down the line.

---

### Financial management

This functional group includes the following modules:

 * Cash and bank management
 * Credit and collections
 * Budgeting
 * Fixed assets
 * Asset leasing
 * Cost accounting

These modules help you manage liquidity, control costs, and plan for financial stability
in D365 F&O. You can track cash flow, monitor assets, enforce credit policies, and
structure budgets to align with business goals. When configured correctly, they 
provide real-time financial visibility and better decision-making.

If your company operates in a cash-sensitive industry or has strict cost control
needs, these tools are critical. This is regardless of the industry, although some
modules are very specific (e.g. Asset Leasing). However, many businesses underestimate
the complexity of understanding and configuring correctly these features in D365
F&O, leading to major inefficiencies.

Misconfigured financial controls can lead to cash shortages, untracked liabilities,
or misaligned budgets that limit business agility. For example, we’ve seen companies
struggle with manual reconciliations and adopting rigid budget structures that don’t
reflect real business needs. If your setup isn’t tailored to your operations, you
may struggle with visibility, delayed decision-making, or encounter unexpected financial
risks.

---

### Product setup

This functional group includes the following modules:

 * Product information management (PIM)
 * Engineering change management

They ensure you define accurately how your products are identified, tracked, and
stored within your company. You can manage product data, design and release product
versions, and handle engineering changes to product specifications. Setting up products
correctly is the basis of efficient company operations, since most other features
of an ERP system depend on it.

Whether your company deals with physical products (stock) or services, you will 
need your PIM to be in order. However, if your company relies on complex product
design and configurations, strict regulatory compliance, or advanced version control,
you may also need the engineering change management features.

Without a structured setup in this area, your company will find it difficult to 
maintain product details and changes in the medium and long run. These issues have
knock-on effects on every other operational areas where items (products or services)
are involved: from procurement to stocking and fulfilment, from invoicing to financial
reporting.

---

### Procurement and supply

This functional group includes the following modules:

 * Procurement and sourcing
 * Landed costs

They help you manage purchasing activities, supplier relationships, and internal
requests for procurement. You can define approval workflows for purchase requisitions,
process requests for quotations, create supplier contracts, and manage indirect 
charges to orders.

Every company needs some form of procurement, and most companies require some level
of approval to go with it. However, businesses that rely on international sourcing
and oversea inbound transportation may also need features from the landed cost module.

A misconfigured setup in this area can lead to unsupervised procurement spending,
poor supplier visibility, and insufficient order tracking. This has an impact on
both accounting an operations: companies with a weak procurement setup may overpay
for goods, track margins incorrectly, and be affected by stockouts or delays in 
production and order fulfilment.

---

### Logistics operations

This functional group includes the following modules:

 * Inventory management (UK: Stock management)
 * Warehouse management
 * Transportation management
 * Fleet management

They ensure that goods are efficiently stored, moved, and tracked within your company.
You can manage inventory levels, optimise warehouse operations, coordinate transport,
and oversee fleet usage. When set up correctly, these modules improve inventory 
accuracy, reduce waste, and support efficient internal logistics.

Some form of basic inventory setup is essential for virtually any company using 
D365 SCM. However, if you handle large stock volumes or have complex warehouse operations,
you’ll likely need warehouse management features too. And if you deal with distribution
or have your own fleet of vehicles, the other two modules could be relevant for 
you as well.

Without a structured setup in this functional area, your company will risk inaccurate
inventory records, poor warehouse operations, and inefficient order fulfilment. 
Again, these will have an impact on both the operations and accounting, especially
if the financial setup for stock management is incorrect.

---

### Planning and manufacturing

This functional group includes the following modules:

 * Master planning
 * Production control
 * Time and attendance
 * Cost management

They are designed to help you plan production, control costs, and optimise manufacturing
processes. You can manage materials, ensure resources availability, schedule production
operations, and run the MRP to generate planned production orders. When set up correctly,
they reduce waste, improve lead times, and keep manufacturing aligned with demand.

Any company that transforms raw materials into finished products will need these
modules to some extent. For simple manufacturing, some production control and basic
cost management features will be enough, but complex manufacturing operations will
require advanced features, such as finite capacity operations, time registration
of production workers, or intercompany master plan.

A weak planning setup leads to material shortages, production delays, and cost overruns.
This is possibly the most dangerous area in D365 F&O for an incorrect setup, because
it will have catastrophic consequences on manufacturing operations, from inventory
shortages, to unprofitable production runs, and missed deadlines for order fulfilment.

---

### Sales and retail

This functional group includes the following modules:

 * Sales and marketing
 * Retail and commerce
 * Subscription billing
 * Pricing management
 * Rebate management

They handle how you price and sell products and services, whether through direct
sales, retail operations, or subscription-based models. You can manage sales channels,
define pricing strategies, create sales contracts, and invoice spot and recurring
orders. When set up correctly, these modules streamline managing revenue and servicing
clients correctly, improving both cashflow and customer experience.

All companies need at least a basic setup of the sales module, while the retail 
module (which connects to other D365 Commerce features) is designed for businesses
selling through physical stores or e-commerce platforms. Subscription billing is
relevant if you offer recurring services, while rebate management is essential if
you deal with deductions and royalties.

A weak setup of the sales side in your ERP system has all sort of consequences, 
from discrepancies with other systems like your CRM, to inconsistent pricing, a 
poor customer experience, eroded profit margins, cashflow issues, or even a complete
halt due to inability to invoice orders.

---

### Projects and assets servicing

This functional group includes the following module:

 * Project management and accounting (PMA)
 * Service management
 * Asset management

This is a seemingly odd mix, grouping together project-based work with features 
to run maintenance contracts service assets. PMA is effectively a mini-ERP, allowing
project-driven businesses in consulting, construction, engineering, and professional
services to manage contracts, plan resources and stock allocation, track the work,
and report on project financials.

Businesses that offer after-sales care after a project will benefit from service
management, while organisations that deal with high-value equipment and their maintenance
can use the asset management features. If your operations include on-site client
visits to provide support, there is a strong case here to integrate with D365 Field
Service.

However, these modules require other areas of D365 F&O to be set up correctly first.
And without a proper setup of the PMA and its connected modules, you may struggle
with incorrect cost allocation, budget overrun, inefficient resource utilisation,
poor on-site servicing, and delayed invoicing. These will ultimately lower the quality
of the delivery and impact business continuity and profitability.

---

### Human resources

This functional group includes the following modules:

 * Human resources
 * Leave and attendance
 * Expense management
 * Payroll

They help you manage your workforce in the system. You can handle employee records,
payroll, leave policies, time tracking, and expenses. When configured correctly,
they streamline HR processes, ensure compliance with labour laws, and improve visibility
into workforce costs.

Every company needs some level of HR management, but if you have a large workforce,
complex compensation structures, hierarchy-based approvals, or strict labour regulations,
these features will be more relevant for you. Organisations who allow their staff
to spend company money or reimburse their business expenses will also need expense
management features.

A poorly structured HR setup may cause compliance risks, disruption to approval 
processes elsewhere in the company, and potentially cause errors in payroll and 
manufacturing calculations.

---

### General and miscellanea

This functional group includes the following modules:

 * Common
 * Organisation administration
 * System management
 * Audit workbench
 * Questionnaires

They define your company’s structure and ensure security, governance, and system-
wide configurations in D365 F&O. You can manage users, set up workflows, enforce
audit controls, and configure business policies. When properly implemented, they
provide stability, compliance, and a seamless user experience.

All companies require basic legal entity setup and some system setup, especially
when it comes to **security roles configuration**. You may need to deep dive into
them if you operate across multiple legal entities, require strict audit trails,
rely heavily on bulk data import/export, or utilise features like electronic reporting.
The common module is mostly for end users to personalise and enhance their experience
while using the system.

Bad system setup can lead to security risks with unsuitable user access, poor system
performance with redundant batch jobs, and inconsistent data handling. Similarly,
bad organisational setup may affect number sequences and workflow efficiency.

---

## Conclusion

D365 F&O is constantly evolving. With over 40 modules (and more on the way), keeping
track of what they do, how they fit together, and which ones your business actually
needs is no trivial task.

This article gave you a high-level breakdown, but there’s more to the picture. Some
modules are essential for every company, while others only apply in specific industries
or scenarios. Knowing the difference and setting them up correctly will save you
from costly mistakes. If you need some help, just [book a call with](https://itfandango.com/contact-us/)
us to get started.

**Sections:**

 * [Introduction](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#1)
 * [Core accounting](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#2)
 * [Financial management](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#3)
 * [Product setup](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#4)
 * [Procurement and supply](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#5)
 * [Logistic operations](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#6)
 * [Planning and manufacturing](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#7)
 * [Sales and retail](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#8)
 * [Projects and assets servicing](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#9)
 * [Human resources](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#10)
 * [General and miscellanea](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#11)
 * [Conclusion](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/#12)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

The post [All Dynamics 365 F&O Modules, Explained](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/)
appeared first on [IT Fandango](https://itfandango.com).

## Adopt Vs Adapt: Are You Really In Control Of This Choice?

- Link: https://itfandango.com/articles/d365-fo-adopt-vs-adapt-are-you-really-in-control-of-this-choice/
- Published: 2024-12-17T11:47:25+00:00
- Author: Marco Romano

# Adopt Vs Adapt: Are You Really In Control Of This Choice?

How politics, pressure, and precedents overrule your common sense

17 December 2024

## Introduction

Implementing D365 F&O comes with an apparently simple choice: adopt standard system
features, or adapt them to your fit your needs through customisations. It sounds
like a straightforward decision, doesn’t it? For many organisations, the starting
approach is always the same: “simplify and standardise our processes, so we stay
as close as possible to out-of-the-box features”. Spoiler alert — it never works.

In fact, reality tells a different story. Most D365 F&O implementations end up with
a significant number of customisations, and not always for the right reasons. The
decision to adopt standard processes or adapt the system often slips out of your
control, driven by forces that have nothing to do with business value or technical
merit. So what’s really happening here? Why is this choice harder than it seems?
More importantly, how can you regain control over these decisions?

In this article, we’ll explore:

 * The merits of adopting vs adapting, and when each of them makes sense
 * The hidden factors that force your hand towards unplanned outcomes
 * How to take back control, avoid succumbing to complete chaos

Let’s start from the first point.

---

## Adopt: why you should change your processes

Your legacy system is probably older than some of your employees, with years of 
accumulated customisations and workarounds that made sense at the time. The result?
A maze of custom functions and convoluted processes that nobody fully understands
anymore.

D365 F&O comes with standard processes built on decades of ERP evolution. Microsoft
continuously invests in new features and modules, drawing from experience across
thousands of implementations worldwide. While the system may work differently from
what you’re used to, there’s usually solid reasoning behind it.

Consider your purchase order approval process. Your legacy system might have dozens
of special cases and unique workflows, some of which not practically in use anymore.
D365 F&O’s standard workflows is streamlined, yet flexible with an editor that handles
most cases efficiently while being much easier to maintain and use.

“But our processes are special!” you might say. Some truly are – we’ll get to those
later. But let’s be honest: many of your unique processes are just the accumulated
weight of history, not genuine competitive advantages.

Why changing your business processes to meet standard ERP features makes sense:

 * Lower total cost of ownership (no development, easier maintenance)
 * Cleaner processes with plenty of documentation online
 * Faster implementation and simpler upgrades
 * Easier scalability and standardisation across multiple entities

---

## Adapt: when customising the system pays off

While standardisation sounds great in theory, sometimes customising D365 F&O is 
not just desirable – it’s essential. The trick is knowing when to adapt the system
and how to do it without creating a maintenance nightmare.

Some processes are indeed truly special and unique. Perhaps they’re your competitive
edge, built from years of industry experience. Maybe they’re required by regulations
specific to your sector. Or perhaps changing them would cause such massive disruption
that customisation is actually cheaper than process change.

Consider a manufacturer with a unique quality control process that is embedded in
how they run their production orders. Or a distribution company with dozens of contract
types, each with their own fulfilment terms, ownership clauses, and goods handling
policies. In cases like these, the business case for customisation is clear and 
compelling.

But adapting doesn’t necessarily mean overhauling the out-of-the-box features. Standard
functions can be extended meaningfully, while sometimes a light touch is all you
need – especially if you leverage ISVs and third-party add-ons that can bring that
complexity away from the ERP itself.

When customising D365 F&O to adapt it to your needs makes sense:

 * Preserving genuine efficiency and competitive advantages
 * Meeting regulatory requirements and unique industry requirements
 * Avoiding massive business disruption when the gap is too wide

---

## Factors that force your hand

![](https://itfandango.com/wp-content/uploads/2024/12/businessman-with-manacles-
his-hands-1-1024x445.jpg)

So far, we’ve explored when to adopt standard processes and when adaptation makes
sense. But here’s the uncomfortable truth: things are never so black and white, 
and often this choice gets made for you by forces beyond your control. “Simplify
and standardise”, the guiding principle of every organisation thinking they will
finally get rid of their messy legacy ERP system, loses credibility as the D365 
F&O implementation journey progresses. Let’s look at the three main culprits that
can derail even the best-laid plans.

### Organisational inertia

History, they say, is written by the victors. In ERP implementations, it’s usually
written by users who’ve mastered every quirk of the legacy system over the past 
decade. You may be aware of the most elegant standard process in D365 F&O, but if
your users are deeply attached to their current ways of working, you’re in for quite
the battle.

It’s not just stubbornness (although there’s plenty of that). End users have invested
years in mastering the current system, building their reputation on their expertise.
Now you’re asking them to become novices again. No wonder they push for customisations
that make the new system behave like the old one – wouldn’t you?

This resistance often manifests as an endless stream of change requests. “Can we
add this field?”, “We need this extra status for orders that are on hold, but not
entirely on hold” (really, do you?), “The standard system doesn’t handle our special
cases”. Before you know it, you’re building a replica of your legacy system in D365
F&O – exactly what you were trying to avoid. It’s like moving to a new house but
insisting on placing every piece of furniture exactly where it was in the old one,
even if the new layout makes no sense.

### Stakeholder pressure

Sometimes the pressure comes from the opposite direction. Senior stakeholders, often
with limited understanding of the technical implications, can mandate changes that
force customisation. They mean well but, paraphrasing a common proverb, the road
to a D365 F&O hell is paved with good intentions.

Picture this: you’re several months into the implementation, system design is signed-
off, development is in full swing, and system configuration is ongoing. Then comes
the bombshell from the board meeting: “We’re expanding into the Asian market next
quarter, the system needs to support that.” Never mind that the requirements aren’t
clear, or that this completely changes the architecture finalised four months ago.
The message is clear – make it happen, don’t care how.

The result is a perfect storm of competing priorities, where the need to please 
influential stakeholders outweighs technical best practices and causes plenty of
rework. It’s rather like having several backseat drivers, each insisting on a different
route to the same destination. We can only drive to one place at once, if we want
to arrive in time and with the car in one piece.

### Resource constraints

Finally, there’s the brutal reality of constraints. You might know that this process
is ripe to be modernised and optimised, but do you have the time, budget, and people
to make it happen? Process change requires more than just technical configuration–
it needs thorough analysis, design of new workflows, change management efforts, 
extensive user training, and updates to procedures and documentation.

When you’re already struggling with tight timelines and limited resources for the
ERP implementation, the quick fix of lifting and shifting existing customisation
becomes temptingly attractive. After all, it’s easier to replicate what you have
in the new system than to modify ingrained human behaviour – at least in the short
term.

This is how you end up with “temporary solutions” that become permanent, and “quick
fixes” that create long-term technical debt. Not because it’s the right choice, 
but because it seems like the only feasible option at the time and something had
to give. It’s the classic “we’ll fix it properly in phase two” scenario – and we
all know how often phase two actually happens.

---

## How to regain control

![](https://itfandango.com/wp-content/uploads/2024/12/person-holds-key-with-word-
key-it-2-1024x434.jpg)

All is not lost. While these forces can seem overwhelming, there are proven strategies
to regain control over your adopt-versus-adapt decisions. Let’s explore how to turn
this challenge into an opportunity for meaningful improvement.

### Build your coalition

Have you ever seen a new business application already hated by everyone on day one?
That’s precisely what we want to avoid. The key to reducing resistance is involving
stakeholders early – and we mean really early, not just inviting them to project
updates where they can nod politely while checking their emails.

The earlier people understand what D365 F&O can do, the less likely they are to 
demand a carbon copy of the legacy system. Here’s how to make this happen:

 * Identify and empower change champions in each department who know and can advocate
   for standard system features
 * Create a structured process for gathering and evaluating change requests, making
   stakeholders feel heard while maintaining control
 * Build a change management plan that addresses not just system changes, but the
   human impact of process transformation

But sometimes you just cannot convince people easily, therefore…

### Base decisions on data, not politics

“But we’ve always done it this way” is not a business case. Neither is “because 
the boss man wants it”. To make sound decisions about (major) customisations, you
need a framework that cuts through the noise of opinions and focuses on real business
value.

Here’s how to create a fact-based decision-making process:

 * Set up a governance board with representatives from both business and IT to discuss
   and evaluate significant changes
 * Establish clear criteria for evaluating said change requests, including business
   impact, technical complexity, and long-term maintenance costs
 * Create a scoring system that weighs benefits against costs and risks, so that
   senior stakeholders can easily understand and relate to it

That said, it’s clear that you can’t be rational each time. So sometimes you just
have to compromise, because remember that you should…

### Play the long game

Rome wasn’t built in a day, and neither is a perfectly optimised D365 F&O implementation.
Sometimes the key to success is knowing when to compromise in the short term while
keeping your eyes on the long-term prize.

Consider this approach:

 * Look for quick wins that can build confidence in standard D365 F&O features
 * Keep stakeholders informed about desired future improvements to prevent disappointment
   with initial compromises
 * Plan for gradual process optimisation rather than trying to achieve complete 
   perfection at go-live

This is great, but if everything else fails you still have an ace up your sleeve.
Which is to…

### Bring in independent experts

Sometimes an outside perspective is the most effective way to cut through internal
politics and preconceptions. Independent experts can provide unbiased assessment
and validation, helping you make better decisions about your D365 F&O solution, 
whether it’s a meaningful customisation or a process adjustment (or a mix of both!).

Independent expertise can bring to the table:

 * Objective assessment of customisation requests based on experience with similar
   implementations
 * Fresh perspective on business processes that might benefit from standardisation
 * Support in building business cases for or against specific customisations, with
   guidance on future-proofing your decisions

---

## Conclusion

The choice between adopting standard processes and adapting D365 F&O through customisation
is rarely as straightforward as it first appears. While the mantra of “simplify 
and standardise” sounds great in theory, the reality is often more complex, influenced
by organisational dynamics, political pressures, and practical constraints that 
can force your hand.

The key is to make informed decisions that balance genuine business needs with technical
sustainability, ensuring that all stakeholders understand this reasoning and are
involved in the implementation project.

This requires a combination of:

 * Clear governance to evaluate customisation requests
 * Strong change management to support process transformation
 * Realistic planning that acknowledges both short-term needs and long-term goals
 * Independent expertise to validate your assumptions and guide your decisions

You will never manage to plan everything in advance with a D365 F&O implementation.
Invariably, things will turn out to be more complicated than expected — this is 
not scaremongering, it’s the reality we have seen over and over again, after many
years in the industry.

So if you need some support, or if you’re dealing with the consequences of tricky
customisations or processes that are still convoluted after you’re live with D365
F&O, reach out to us. We know exactly how to help you.

**Sections:**

 * [Introduction](https://itfandango.com/articles/d365-fo-adopt-vs-adapt-are-you-really-in-control-of-this-choice/#1)
 * [The case for adopting](https://itfandango.com/articles/d365-fo-adopt-vs-adapt-are-you-really-in-control-of-this-choice/#2)
 * [The case for adapting](https://itfandango.com/articles/d365-fo-adopt-vs-adapt-are-you-really-in-control-of-this-choice/#3)
 * [Factors that force your hands](https://itfandango.com/articles/d365-fo-adopt-vs-adapt-are-you-really-in-control-of-this-choice/#4)
 * [How to regain control](https://itfandango.com/articles/d365-fo-adopt-vs-adapt-are-you-really-in-control-of-this-choice/#5)
 * [Conclusion](https://itfandango.com/articles/d365-fo-adopt-vs-adapt-are-you-really-in-control-of-this-choice/#6)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

The post [Adopt Vs Adapt: Are You Really In Control Of This Choice?](https://itfandango.com/articles/d365-fo-adopt-vs-adapt-are-you-really-in-control-of-this-choice/)
appeared first on [IT Fandango](https://itfandango.com).

## The 7 Deadly Sins Of A D365 F&O Implementation

- Link: https://itfandango.com/articles/the-7-deadly-sins-of-a-d365-fo-implementation/
- Published: 2024-11-15T10:34:11+00:00
- Author: Marco Romano

# The 7 Deadly Sins Of A D365 F&O Implementation

The Road To ERP Implementation Disaster Is Paved With Good Intentions

15 November 2024

## Introduction

Implementing Dynamics 365 Finance and Operations (D365 F&O) is a complex endeavour
that can make or break your organisation’s digital transformation. So far, nothing
new.

But what if we told you that the path to ERP enlightenment is fraught with temptation,
and that even the most well-intentioned project teams can fall prey to the seven
deadly sins of D365 F&O implementation?

From the pride of thinking you can do it all in-house to the wrath of blaming everyone
but yourself when things go pear-shaped, these sins are as common as they are destructive.
They’re the reason why, despite all the advances in technology and methodology, 
ERP implementations still have a reputation for being risky, expensive, and prone
to failure.

But fear not! For every sin, there is a path to redemption. With the right knowledge
and a healthy dose of self-awareness, you can avoid temptation and navigate safely
to shore.

In this article, with a touch of humour, we will:

 * Explore the seven deadly sins of a D365 F&O implementation;
 * How they will lead your D365 F&O project to damnation;
 * Offer you guidance on the path to redemption.

By the end, you’ll be armed with the wisdom to spot these sins before they take 
root, and the strategies to keep your project on the straight and narrow path to
salvation.

---

## The 7 deadly sins

![](https://itfandango.com/wp-content/uploads/2024/10/hell-reduced.png)

To begin, let’s delve into the seven cardinal errors that can transform your D365
F&O implementation from a dream of efficiency into a hell of complications, frustration,
and eternal damnation.

### Pride, or the illusion of self-sufficiency

Pride in D365 F&O implementations manifests as the belief that your organisation
can handle everything in-house without external expertise. This overconfidence often
stems from past experiences with smaller systems or a misunderstanding of the complexity
involved in modern ERP implementations. It’s the dangerous assumption that your 
internal team, no matter how skilled in your current systems, can navigate the intricacies
of D365 F&O without specialised knowledge.

This sin frequently appears early in the project, when key decision-makers underestimate
the scope and complexity of the implementation. They might argue that nobody knows
their business better than they do, so why involve outsiders? While it’s true that
internal knowledge is crucial, it often fails to account for the technical and functional
nuances of D365 F&O that can make or break an implementation.

Pride can also manifest in resistance to change, with team members insisting on 
doing things “the way we’ve always done them” rather than adapting to new, more 
efficient processes offered by D365 F&O. This stubbornness can lead to missed opportunities
for improvement and unnecessary customisations.

### Greed, or the rush for rapid results

Greed in a D365 F&O context is the insatiable desire for quick implementation across
multiple entities or countries. It’s the unrealistic expectation of compressing 
timelines to achieve rapid go-lives, often driven by executive pressure or misaligned
financial incentives. This sin is particularly dangerous because it often comes 
from the top, with C-suite executives or board members pushing for ambitious timelines
without fully understanding the complexity involved.

The greed for rapid results can manifest in various ways. It might be the decision
to implement D365 F&O in six countries simultaneously, with a goal to go live in
all locations within the same quarter. Or it could be the insistence on a big bang
approach, bringing all modules and functionalities online at once, rather than opting
for a phased rollout.

This rush often leads to cutting corners in critical areas such as requirements 
gathering, system configuration, testing, and user training. The project team finds
itself under immense pressure to deliver, leading to hasty decisions and insufficient
attention to detail.

### Lust, or the allure of unnecessary features

Lust in D365 F&O implementations is the irresistible attraction to shiny new features,
unnecessary ISV solutions, or the promise of easy fixes. It’s the tendency to be
swayed by impressive demonstrations without considering actual business needs or
long-term implications. This sin often begins innocently enough, with stakeholders
attending demonstrations or conferences where they’re dazzled by cutting-edge features
or third-party add-ons.

The problem arises when these attractive but potentially unnecessary elements find
their way into the project scope without proper evaluation. Decision makers might
insist on implementing an advanced forecasting tool showcased in a demo, even if
the company’s current processes don’t require such sophistication. Or they might
push for an expensive ISV solution for a niche process that could be handled adequately
by standard D365 F&O functionality with minor configuration.

This lust for features can also manifest in the constant pursuit of the ‘latest 
and greatest’, leading to scope creep as new functionalities are continually added
to the project. The result is often a bloated system that’s more complex than necessary,
harder to maintain, and doesn’t deliver proportional value to the business.

### Envy, or the desire to replicate the past

Envy manifests as an unhealthy attachment to your legacy system, driving a desire
to replicate all its features in D365 F&O. This ‘lift-and-shift’ mentality often
stems from a fear of change or a misguided belief that the old way is always the
best way. It’s the sin of looking backwards instead of forwards, of trying to force
D365 F&O to behave exactly like the system it’s replacing, rather than embracing
new and potentially more efficient ways of working.

This sin is particularly common in organisations with long-standing legacy systems
that have been heavily customised over the years. Key users and stakeholders have
become so accustomed to their existing processes and interfaces that they resist
any change, even if it’s for the better. They might insist on replicating complex,
custom-built features from the old system, even when D365 F&O offers simpler, more
standardised alternatives that could streamline operations.

Envy can also manifest in constant comparisons between D365 F&O and the legacy system,
with users fixating on features or reports they’ve ‘lost’ rather than focusing on
the new capabilities they’ve gained. This backward-looking approach can severely
limit the potential benefits of the new system and lead to unnecessary customisations
that complicate future updates and upgrades.

### Gluttony, or the appetite for excessive customisations

Gluttony in D365 F&O projects is the tendency to over-customise the system, force-
fitting it to match every nuanced business process, regardless of how niche or infrequent.
It’s the inability to say ‘no’ to stakeholder requests, even when they go against
best practices. This sin often stems from a misguided belief that the ERP should
conform entirely to the business, rather than the business adapting some of its 
processes to align with ERP best practices.

Excessive customisation can start innocently, with seemingly small requests: “Can
we just change this field label?” or “We need this report to look exactly like our
old one.” But these requests quickly snowball, leading to a system that bears little
resemblance to standard D365 F&O. Each customisation adds complexity, not just in
the initial implementation but in ongoing maintenance and future upgrades. The more
you customise, the easier it is to justify the need for more customisations.

Gluttony can also manifest in the creation of overly complex workflows or approval
processes that go far beyond what’s necessary for effective operations. Stakeholders
might insist on replicating every exception and edge case in the system, rather 
than simplifying processes or handling rare scenarios manually.

### Sloth, or the neglect of critical preparation

Sloth represents the laziness of delegating all responsibility to the system integrator,
or reluctance to invest time and effort in crucial client-side activities. This 
includes neglecting business process mapping, skimping on thorough testing, or failing
to cleanse and validate data properly before migration. It’s the sin of taking shortcuts
in the foundational work that’s essential for a successful implementation.

This sin often manifests in a rush to move to the next phase without thoroughness,
such as configuring the system before fully understanding and documenting current
business processes. Organisations might skip or abbreviate the crucial step of process
mapping, assuming they can figure things out as they go along. This leads to a system
configuration that doesn’t truly meet business needs and may require costly rework
later.

Sloth can also appear as lack of ownership. Rather than adopting comprehensive governance
and conducting thorough checks throughout the project, organisations might rely 
on cursory checks or assume that the solution will work as intended. The attitude
of “it will be fine” can lead to serious issues post-go-live.

### Wrath, or the blame game

Wrath emerges when frustrations boil over, leading to finger-pointing and blame 
assignment. It’s the tendency to lash out at the software, the implementation partner,
or even internal team members when faced with delays or issues, rather than taking
ownership and working collaboratively towards solutions. This sin often rears its
head when the project encounters inevitable challenges or setbacks.

Wrath can manifest in various ways. It might be executives berating the project 
team for missed deadlines, without considering whether the original timelines were
realistic. Or it could be project managers constantly criticising the implementation
partner, blaming them for every issue that arises, rather than fostering a collaborative
problem-solving environment.

This sin is particularly destructive because it erodes trust and cooperation within
the project team and with external partners. It creates a toxic environment where
team members become defensive and may withhold information for fear of being blamed,
rather than openly addressing and solving problems.

---

## The path to redemption

![](https://itfandango.com/wp-content/uploads/2024/10/heaven-reduced.png)

Now that we’re aware of the pitfalls, let’s chart a course to redemption. How can
you avoid these sins and steer your D365 F&O implementation towards success?

### Pride

**Pride is believing that you can do everything alone**. To overcome it, acknowledge
that implementing D365 F&O requires specialised expertise that you do not have in-
house. To avoid eternal damnation:

 * Conduct a skills assessment of your internal team and identify knowledge gaps.
 * Create a balanced project team that combines internal business knowledge with
   external D365 F&O expertise.
 * Engage an independent advisor to provide unbiased guidance and challenge assumptions.

### Greed

**Greed is expecting results to occur impossibly fast.** Combat this rush by setting
realistic expectations and timelines, and educating executives about the risks of
compressed timelines. To avoid eternal damnation:

 * Consider a phased implementation approach, starting with a pilot company before
   full-scale roll-out.
 * Develop a detailed project plan that accounts for all phases of implementation,
   including adequate time for testing and training.
 * Build in contingency time for unexpected issues and scope adjustments, which 
   will happen anyway.

### Lust

**Lust is having no self-control over your requirements.** Resist the allure of 
unnecessary features by maintaining a strict focus on core business needs. Implement
a rigorous evaluation process for requirements. To avoid eternal damnation:

 * Conduct thorough requirements gathering sessions with all key stakeholders, ensuring
   alignment.
 * Prioritise features based on priority, complexity, business impact, and alignment
   with strategic objectives.
 * Implement a change control board to evaluate and approve any additions to the
   project scope.

### Envy

**Envy is comparing D365 F&O to your legacy system. **Instead of trying to replicate
your old solution, view the new ERP implementation as an opportunity for process
improvement and innovation. To avoid eternal damnation:

 * Conduct workshops to review and optimise current business processes before the
   solution design phase.
 * Educate stakeholders on D365 F&O best practices and standard functionalities.
 * Implement a change management programme to help users embrace new ways of working.

### Gluttony

**Gluttony is the excessive use of customisations.** To avert it, aim to strike 
a balance between truly necessary customisations and standard D365 F&O functionalities.
Make sure that system modifications are not the default choice. To avoid eternal
damnation:

 * Establish clear criteria for approving customisations, such as business criticality,
   impact on operations, and possible alternatives.
 * Implement a customisation governance board to review and approve all customisation
   requests.
 * Keep it simple, reducing the scope and complexity of every customisations and
   aiming for extensible designs.

### Sloth

**Sloth is failing to take ownership of your D365 F&O implementation.** To avoid
temptation, learn your duties and prioritise thorough preparation of all aspects
of the project. To avoid eternal damnation:

 * Define responsibilities for each stakeholder, from sponsor to key users.
 * Specify clear deliverables, to review and sign off before progressing.
 * Invest in creating comprehensive training materials and conduct thorough user
   training before go-live.

### Wrath

**Wrath is resorting to blame when things are not going as planned.** Prevent it
by fostering a culture of accountability and collaborative problem-solving, promoting
the “one team” approach with your suppliers. To avoid eternal damnation:

 * Establish clear roles and responsibilities for all team members and stakeholders.
 * Implement regular project health checks and open forums to discuss challenges.
 * Develop a structured issue resolution process that focuses on solutions rather
   than blame.

---

## Conclusion

So here you have it — the seven deadly sins of D365 F&O implementation laid bare,
along with your roadmap to redemption. You’ve journeyed through these treacherous
temptations emerging wiser and, hopefully, less likely to stumble into these all-
too-common pitfalls.

So, as you embark on (or continue) your D365 F&O journey, keep these lessons close
to heart: embrace humility, set realistic goals, focus on true needs, welcome change,
customise wisely, prepare thoroughly, and foster collaboration.

But if this is still not enough, and if you find yourself on the brink of ERP damnation,
do not fear to ask for “divine intervention”. Our specialty is to solve your D365
F&O functional issues, so we’re always ready to swoop in and steer your project 
towards the path of righteousness. After all, sometimes even the most virtuous ERP
projects need a little help to reach heaven.

**Sections:**

 * [Introduction](https://itfandango.com/articles/the-7-deadly-sins-of-a-d365-fo-implementation/#1)
 * [The 7 deadly sins](https://itfandango.com/articles/the-7-deadly-sins-of-a-d365-fo-implementation/#2)
 * [The path to redemption](https://itfandango.com/articles/the-7-deadly-sins-of-a-d365-fo-implementation/#3)
 * [Conclusion](https://itfandango.com/articles/the-7-deadly-sins-of-a-d365-fo-implementation/#4)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

The post [The 7 Deadly Sins Of A D365 F&O Implementation](https://itfandango.com/articles/the-7-deadly-sins-of-a-d365-fo-implementation/)
appeared first on [IT Fandango](https://itfandango.com).

## Can You Implement D365 F&O In-House?

- Link: https://itfandango.com/articles/can-you-implement-d365-fo-in-house/
- Published: 2024-10-12T06:47:00+01:00
- Author: Marco Romano

# Can You Implement D365 F&O In-House?

Spoiler Alert: you have multiple options, but this one is not the smartest Move

12 October 2024

## Introduction

Implementing D365 F&O is challenging, that’s a fact. Do it wrong, and the result
can be so catastrophic to grind your company operations to a halt (this is not an
exaggeration, I’ve seen it happen).

**Horror stories about failed implementations are abundant. **Delayed timelines 
and exceeded budgets are common. Rolling back to the legacy ERP is not unheard of.
Worst case, the finger-pointing is so extreme that the Microsoft implementation 
partner ends up being taken to court.

In all of this, some bold organisations decide to implement D365 F&O on their own,
i.e. without a system integrator. Is this approach actually possible? Are we really
too conditioned by the industry not to see the alternatives?

In this article, we will:

 1. Consider the option of carrying out the implementation in-house
 2. Explore reasons to choose an implementation partner instead
 3. Prove common assumptions wrong (and there are many!)
 4. Last, explain when a boutique consultancy is suitable for you

There are several options available for your D365 F&O implementation, but not all
of them are as promising as they sound. The key is to understand benefits and limitations
of each of them, which we will do now.

---

## In-house is better

The benefits of implementing D365 F&O in-house are easy to spot and, at first glance,
it seems like a path paved with advantages. The most apparent one is the significant
cost savings potential. By avoiding an implementation partner altogether, money 
that would be spent in their fees can be allocated to building a bigger internal
project team, seemingly achieving the **same manpower result at a lower cost**.

Moreover, doing everything in-house offers you unparalleled control over the implementation
process. You’re not subject to the partner’s prerequisites, capacity, timeline, 
or methodology. This flexibility allows you to tailor the implementation to your
organisation’s unique rhythm and needs, including taking strategic breaks (if necessary)
without such a significant impact on the budget. You can even prioritise certain
modules or functionalities based on your business imperatives, without having to
negotiate with an external party.

But perhaps the most compelling argument for an in-house implementation is the opportunity
to **build internal expertise**. It’s well known that knowledge transfer is always
a concern after the system goes live. The external implementation team leaves, and
your internal team is left without support. Instead, if your internal team is the
only team involved in the implementation journey since the beginning, they will 
develop deep, first-hand knowledge. Their expertise then becomes an immediate asset
for post go-live maintenance, upgrades, and optimisations. Your team becomes self-
sufficient from the get go, reducing reliance on external consultants.

However, in reality the option of doing things in-house may not be as beneficial
as it appears. But before we look into why, let’s make the case for using an implementation
partner.

---

## With a partner is better

Alternatively, partnering with a large consultancy for your D365 F&O implementation
offers its own set of compelling advantages. Adopting a new ERP is challenging, 
so why not leverage specialised expertise? Most Microsoft implementation partners(
aka system integrators, here used as synonyms) have typically conducted numerous
D365 F&O implementations across various industries, accumulating a wealth of knowledge
and refined methodologies.

In turn, this expertise often translates into a **faster implementation experience**,
because what needs doing is clearer. Implementation partners can anticipate common
challenges, leverage templatised solutions, and rely on better expertise to solve
complex requirements. In fact, they bring a level of experience that’s hard to match
with an in-house team, realistically not used to ERP implementations.

Another significant advantage is the **reduced risk of costly mistakes** or oversights.
D365 F&O implementations are complex endeavours with many moving parts. An experienced
Microsoft partner can help you avoid common pitfalls, design a suitable solution
blueprint, and carry out testing to ensure stability. Entrusting them can save you
from expensive rework or performance issues down the line.

Lastly, partnering with a system integrator allows you to maintain a better focus
on your core business operations. A D365 F&O implementation is resource-intensive,
often requiring dedicated attention from key stakeholders. But, by making your implementation
partner overall responsible for the delivery, you can reduce the pressure on your
team.

However, as with doing things in-house, the Microsoft partner approach is not without
its drawbacks. In most cases, issues stem from incorrect assumptions and wrong expectations.
So, let’s look into them and bring some clarity.

---

## Incorrect assumptions

![](https://itfandango.com/wp-content/uploads/2024/08/lens-color-glass-shirt-fresh-
smaller-1024x588.jpg)

Through the magnifying glass, some assumptions turn out to be plain wrong.

When it comes to wrong expectations held by key stakeholders about D365 F&O implementations,
we could write a book… or ten. Instead, here we will focus on three key ones: expertise,
cost, and incentives.

### Expertise

First and foremost, many organisations underestimate the level of expertise required
for a successful D365 F&O implementation. And by that I mean _massively _underestimate
it. Like all big projects, a D365 F&O implementation (often part of a bigger digital
transformation) can only turn out to be **more complicated than expected**.

Simply put, the type of expertise required to deal with something similar is not
found in-house. Even if your team has done another implementation a decade ago. 
Even if they took part in an implementation in their previous role. You need external
experts, period. The sooner this is clear, the less likely the chance of massive
mistakes. An ERP implementation is like a building, where every floor supports the
next one. Get the foundations wrong, and the consequences will be long-lasting.

That said, using **a large consultancy does not mean guaranteed expertise**. In 
fact, big implementation partners (like all big companies) tend to have a mix of
stellar and average consultants. There is no guarantee that your project will end
up with a team that has the right capabilities for it, so some caution is advised.
In a demand-dominated industry like D365 F&O expertise, the best talents are often
found in the open market, but it’s still difficult to find capable and vetted people
there (the best ones don’t hang around waiting for you).

### Cost

Here’s a truth-bomb: it’s extremely difficult to complete a D365 F&O implementation
within the original budget. **Scope in IT project tends to be fluid**, because not
everything can be planned in advance (requirements, rework, etc.) and this has an
impact on the time required to execute the work. D365 F&O projects are no exception.

Plus, the cost of changing things, or fixing mistakes, increases in later phases
of the implementation. This is nothing new, and typical of the waterfall approach(
implementing your ERP in an agile fashion will not solve this — but that’s a topic
for another article).

Wherever possible, things should be done once, and one right the first time. And
this is why doing everything in-house costs less is an incorrect assumption. A less
experienced team will take longer to execute tasks and make more mistakes, eventually
leading to a higher cost due to rework and fixes. I am yet to hear of a company 
who implemented D365 F&O successfully solely with in-house expertise.

Well then, is it better to have zero in-house expertise and trust the implementation
partner to do everything? No, that’s the opposite extreme and equally bad! Virtually
all implementation partners work on a time and materials basis, so costs can only
pile up if there is no control and clarity on the client side.

**An ERP implementation is a collaborative effort**: both parties need to put in
their own fair share of effort and work together for the project to be successful.
Costs are better kept under control when the scope is managed correctly, with clear
expectations about what’s possible and how long it will take.

Oh, and one more thing:** you cannot rush quality**. If you want a D365 F&O system
that works, prepare to invest time and money on it. Go for a cheap option like “
we will be live with the whole solution in four months!”, and you will end up spending
several times as much when things inevitably fall apart.

### Incentives

Thinking in terms of one team is surely a good idea for the implementation. However,
at the end of the day clients and suppliers have different incentives. That’s a 
fact in all business relationships, so it should be taken into account here too.

Most D365 F&O implementation partners operate on a **time and materials basis**:
get the project scope wrong, or design a weak solution, or take no ownership, and
you’ll ensure that the time of your Microsoft partner’s consultants is always billable—
much to their practice manager’s delight. There are also additional incentives, 
such as selling licenses or adopting a certain technology, that may benefit one 
party more than the other.

So how to deal with it? It’s often **a great idea to have a second pair of eyes**,
ideally independent, to ensure that everything is in order and that incentives for
all parties are balanced, so that a win-win outcome is achieved. This is not about
hiring a watchdog and pointing fingers. Instead, it’s the software equivalent of
measuring twice and cutting once.

---

## The boutique option

![](https://itfandango.com/wp-content/uploads/2024/08/male-female-business-people-
working-tablet-office-1024x708.jpg)

Now, I wouldn’t be doing my job properly if I didn’t tell you how engaging a boutique
consultancy company could benefit you… but since that’s who we are at IT|Fandango,
I promise I’ll keep the sales pitch to a minimum.

Boutique consultancies are smaller companies with specialised expertise in a certain
niche. D365 F&O is no exception; whether it’s advisory and governance, functional
services, or technical development. Small consultancies are on the rise, often offering
the **perfect solution to gaps left by a larger implementation partner**.

So why working with them? Let’s see how they score against the three key metrics
we used:

 * **Expertise**: Boutique companies specialise in one area and have fewer, vetted
   consultants, meaning deep knowledge across the entire team. Their structure often
   allows them to be flexible about how their services are provided.
 * **Cost**: Excluding specialised strategic advice, boutique companies tend to 
   be cheaper than larger partners, and they have way less overhead. Their agility
   results in an overall lower cost to bring you the same (or superior) results.
 * **Incentives**: With fewer clients, boutique consultancies can offer you dedicated
   attention and truly independent advice. Your success is crucial to their reputation
   and business, so you’re not just another number and their results are tied to
   yours.

Of course, there are drawbacks too: boutique consultancies may not have capacity
for larger projects, or lack across-the-board expertise. You can realise the best
value from a boutique consultancy when you **engage them to handle a specific requirement
in a gap area**.

For example, we at IT|Fandango specialise in solving functional issues with D365
F&O, such as gathering requirements, designing complex customisations, or configuring
security roles.

---

## Conclusion

Implementing D365 F&O is a complex, once-in-a-decade undertaking. **It can and will
take a toll on your organisation** and impact its future operations. We’ve seen 
that both in-house implementations and partnering with large consultancies have 
their merits and challenges, although it’s way riskier to do things completely alone.
Successful D365 F&O implementations often require a balanced approach, combining
internal knowledge with external expertise.

If there is only one thing you take away from this article, may it be this one: 
_let the implementation experts do the expert stuff, but build enough internal knowledge
to understand what they are doing._

If there are specific needs, **bring in independent specialists** to plug the gaps
before they become catastrophic holes. This is where boutique consultancies can 
offer true value, providing specialised knowledge and personalised attention.

By understanding the reality of different implementation approaches, you can make
an informed decision that best serves your organisation’s needs and requirements.
There will be other challenges for sure, but this is already a great way to start
with the right foot and de-risk your D365 F&O project.

**Sections:**

 * [Introduction](https://itfandango.com/articles/can-you-implement-d365-fo-in-house/#1)
 * [In-house is better](https://itfandango.com/articles/can-you-implement-d365-fo-in-house/#2)
 * [With a partner is better](https://itfandango.com/articles/can-you-implement-d365-fo-in-house/#3)
 * [Incorrect assumptions](https://itfandango.com/articles/can-you-implement-d365-fo-in-house/#4)
 * [The boutique option](https://itfandango.com/articles/can-you-implement-d365-fo-in-house/#5)
 * [Conclusion](https://itfandango.com/articles/can-you-implement-d365-fo-in-house/#6)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

The post [Can You Implement D365 F&O In-House?](https://itfandango.com/articles/can-you-implement-d365-fo-in-house/)
appeared first on [IT Fandango](https://itfandango.com).
