“Can you just check our Dynamics 365 is okay?”
It’s a request we hear often, and it’s hard to answer honestly without more context. Okay compared to what? Okay for today’s user count, or for the growth you’re planning next year? Okay meaning secure, okay meaning fast, or okay meaning nobody has complained this week?
A proper Dynamics 365 health check replaces that vague question with specific answers. Here’s what one should include.
What a Health Check Assesses
A health check isn’t a single test. It’s a structured review across several areas, each of which can go wrong in its own way.
Data model review
How your tables, relationships and columns are structured. Years of ad hoc changes often leave a data model that still works but has picked up unused columns, inconsistent naming and relationships that no longer reflect how the business operates.
Customisation assessment
Every plug-in, workflow and business rule is reviewed against two questions. Does it still serve a real purpose? Could it be replaced with standard configuration or a low-code alternative in Power Platform that is easier to maintain than custom code?
Integration health
Connections to your ERP, accounting software and other systems are checked for reliability, not just whether they show as connected. That means looking at error rates, retry logic and whether failures are quietly dropping data.
User adoption analysis
Low adoption is a common warning sign of a struggling implementation, and an easy one to ignore. A health check looks at real usage patterns: which features people use, which were built but ignored, and where users have quietly gone back to spreadsheets. The depth of this analysis depends on the usage and audit data your environment already records, so it’s worth checking what’s switched on before the review starts.
Security configuration
Security roles, column-level security and whether permissions match your current team structure, rather than the org chart at go-live.
Performance review
Form load times, query performance and whether customisations are creating bottlenecks that will get worse as data volumes grow.
What the Output Looks Like
A health check that just says “everything looks fine” is reassurance, not a health check. A proper one produces:
- A findings report with specific issues, not generalities. For example, “the Opportunity table has 14 unused custom columns” is useful. “Some clean-up opportunities exist” is not.
- Severity ratings, so you know what’s urgent and what can wait.
- A prioritised action plan, separating quick wins you can act on straight away from larger items that need proper scoping.
- Before and after benchmarks where possible, so the value of each fix is measured rather than assumed.
If you’re quoted for a health check and the deliverable isn’t described in this level of detail, ask exactly what you’ll receive before you commit.
How Long It Takes
Our health checks follow a structured timeline, not an open-ended “we’ll let you know”:
- Most assessments are completed within 48 hours, with findings and a prioritised roadmap
- More than 100 check points are reviewed across the areas above
- The findings report comes with a prioritised roadmap, not just a raw list of issues
Complex environments with several applications and heavy customisation take longer. Even then, the timeline should be agreed up front and measured in days, not open-ended weeks with no visibility of progress.
When to Get One
A health check is most valuable in a few specific situations.
Before a major change. Planning to add another Dynamics 365 application, bring on more users or connect a new system? A health check shows you what you’re building on before you commit budget to the next phase.
After a partner handover. If you’ve inherited a Dynamics 365 environment from another implementation partner, perhaps through an acquisition, a change of partner or simply because the original team moved on, a health check is the quickest way to understand what you have.
When adoption feels low but nobody can say why. Sometimes the platform is fine and the problem is training. Sometimes it’s the opposite, and users abandoned a process because it really was broken. A health check tells you which.
On a regular cadence. Organisations with a managed services arrangement often build health checks into their regular reviews, so issues are caught while they’re small rather than growing into a larger remediation project.
What a Health Check Won’t Do
It’s worth being clear about the limits. A health check identifies problems and opportunities. It doesn’t fix them. The output is a roadmap, not a completed project. Putting the recommendations into practice is a separate piece of work. Sometimes that’s a quick configuration change, and sometimes it’s a small project with its own scope and timeline.
Be wary of anyone who presents a health check as a one-off fix. It’s a diagnosis, not the treatment.
Your Next Step
If it’s been a while since anyone looked closely at your Dynamics 365 environment, or you’re not sure who last did, a health check is a low-risk way to find out what’s there before you decide what to do about it.
Book a health check or explore our wider audit and assessment services for Dynamics 365, Power Platform and data and analytics environments.
