You’ve gone live on Dynamics 365. The implementation project is finished, and the next question arrives quickly: who fixes it when something breaks?
Go-live isn’t the finish line. It’s the start of a different phase, with its own ongoing needs, and those needs are easy to overlook while everyone is focused on implementation sign-off.
This guide explains what Dynamics 365 managed services cover, how support tiers usually differ, what drives the scope and cost of an arrangement, and how to weigh paying for support against building it in-house.
What “Managed Services” Means
Managed services is more than a help desk. A good arrangement brings six things together:
- Proactive monitoring: spotting issues before your users do
- Incident management: a defined process for when something goes wrong, with agreed response times
- Health checks and optimisation: regular reviews against Microsoft best practice, not just checks that the system is still running
- Change management: controlled rollout of new features and fixes, with a rollback plan
- User support: a help desk that understands both the platform and how your business uses it
- Continuous improvement: using what support tickets reveal to make the system better over time
A good partner treats these as one connected discipline. A weak one sells you a ticket queue and calls it support.
How Support Tiers Differ
At Kompound, managed services are structured across three tiers: Essential, Professional and Enterprise. The tiers differ in four ways: how much of the working week is covered, how quickly we respond, how proactive the service is, and how much improvement work is included. Response times and coverage hours are agreed with each customer when we scope the engagement, because the right commitment depends on how critical Dynamics 365 is to your operation.
Essential
For organisations that need dependable support during business hours:
- Business hours support by email and phone
- Incident management and resolution
- Regular health checks
- Quarterly business reviews
- Support portal access
Best for: smaller deployments, teams working in a single time zone, and environments with light customisation.
Professional
For businesses that are still developing their Dynamics 365 setup, not just maintaining it:
- Extended support hours and faster response than Essential
- More frequent health checks
- Proactive monitoring and alerting
- Change management included
- Regular optimisation reviews
- Enhancement time included each month for small improvements
Best for: organisations adding users, processes or integrations, where the system needs to keep pace with the business.
Enterprise
For complex environments with several applications, heavy customisation or many integrations:
- Cover for critical issues, agreed in your service schedule
- Priority response times, scoped to your needs
- Strategic roadmap planning
- Priority access to specialists
- Enhancement time included, scoped to your needs
Best for: organisations whose Dynamics 365 setup is central to daily operations and changes regularly.
Why Included Enhancement Time Matters More Than the SLA
A lot of buyers miss this when comparing packages. The response commitment tells you how quickly someone picks up an issue. Included enhancement time tells you whether your system keeps improving.
Without it, every small change becomes a separate quote, a separate invoice and a separate wait. That might be a new column, an adjusted approval flow or a tweaked report. With enhancement time built in, small changes are handled within your monthly allowance as part of what you already pay for. Larger pieces of work are still scoped separately.
This is often the real difference between a basic tier and a more comprehensive one. It’s less about response time and more about whether your system stands still or keeps adding value.
What Drives Scope and Cost
Every managed services arrangement is priced on what it has to cover. These are the factors that move it most.
Number of applications in scope
Supporting Dynamics 365 Sales alone is simpler than supporting Sales, Customer Service and Field Service together. More applications mean more surface area, more integration points and more ways for things to interact unexpectedly.
Customisation depth
Heavily customised environments take longer to diagnose, because any fix has to account for the bespoke logic layered on top of the standard platform.
Integration complexity
Every system connected to Dynamics 365 is a place where problems can start outside Dynamics 365 itself. That might be your ERP, your accounting platform or a customer portal. Your support team needs to understand the whole chain, not just the Microsoft side.
Coverage and response commitment
Longer support hours and faster response commitments need people available to meet them. That’s the main reason higher tiers cost more.
Enhancement allowance
The more improvement time you want included each month, the more the arrangement will cost. In return, you’ll need fewer separately quoted pieces of work.
Buy Managed Services or Build Internal Capability?
This is worth answering honestly before you sign anything.
Managed services make sense when:
- You don’t have, and don’t want to hire, a dedicated Dynamics 365 administrator
- A slow or poorly executed in-house fix would hurt the business
- You want predictable, structured support rather than relying on one or two internal people
- Your platform spans several applications or integrations that need specialist knowledge
Building in-house makes more sense when:
- You already have IT staff with Microsoft platform experience
- Your deployment is small and stable, and rarely changes
- You’re comfortable bringing in a partner on an ad hoc basis for anything beyond routine admin
Many organisations land somewhere in between. They use a lighter managed services tier for specialist and proactive work, and a named internal person handles day-to-day user questions. That hybrid model is worth discussing openly with any partner you’re evaluating. The tiers above aren’t the only shape an arrangement can take.
What to Ask Before You Sign
- What exactly is included, and what is billed separately? Enhancement time, integration troubleshooting and issues in third-party systems are common grey areas.
- What response times and coverage hours will be written into the contract? Make sure the commitment for each severity level is specific and agreed in writing, not implied by a tier name.
- Who handles your issues? Ask whether the people resolving your tickets will know your environment, or whether each ticket starts from scratch.
- What happens when the monthly enhancement allowance runs out? Does unused time roll over? Is extra work quoted separately, or queued for next month?
- How is a health check conducted? Ask for a sample report. A real health check surfaces specific configuration and security findings, not a generic “all good” email.
- What’s the exit process? If you want to bring support in-house or change partners, how much notice is needed and what documentation do you receive?
Your Next Step
If you’re approaching go-live and haven’t settled on a support model, decide before launch. Leave it until three weeks after, and the first issue arrives with nobody sure who’s meant to fix it.
Book a consultation to talk through which tier fits your deployment and the response commitments your business needs, or see how we structure ongoing cover on our Dynamics 365 managed services page.
