Support planning guide
Dynamics 365 support costs: what to compare in a quote
Short answer
Dynamics 365 support costs depend on the app, customizations, integrations, coverage hours and work included. MS Dynamics Guys recommends separating one-time onboarding, recurring support, planned changes and Microsoft or third-party costs. A useful quote states these assumptions so you can compare providers on the same scope.
Four different things can be called support
| Model | What you buy | Question to ask |
|---|---|---|
| Microsoft product support | Access to the product support route covered by your agreement | Does the issue concern Microsoft's code or our customization? |
| Technical incident support | Investigation and repair of the agreed live-system scope | Which apps, interfaces and custom components are covered? |
| Managed application support | Incident work plus defined monitoring, updates and planned improvements | What capacity and operating responsibilities are included? |
| An embedded specialist | A person's time under your team's direction | Who triages tickets, owns response targets and approves releases? |
Build a like-for-like estimate
Use this planning structure, not a price promise:
First-year service budget = onboarding + 12 × monthly support fee + approved extra changes + separately billed testing or specialist work.
Add licenses, external infrastructure and vendor support fees separately when they apply. Do not double-count change capacity already included in the monthly fee. Confirm taxes, currency and minimum term in the proposal.
What changes the price?
- Product and deployment: Business Central AL work differs from CRM/Dataverse or Finance and Supply Chain work.
- System condition: missing source, fragile integrations and undocumented releases increase onboarding work.
- Coverage: the hours, time zones and escalation model determine staffing needs.
- Technical scope: list extensions, plug-ins, flows, interfaces and jobs individually.
- Workload: provide actual incident history and the expected change backlog.
- Acceptance: agree tests, release approvals and business sign-off.
Questions to send every provider
- What is the one-time onboarding fee and what written deliverables does it buy?
- Which apps, customizations and integrations are included?
- What support hours and time zone apply?
- Are response, workaround and resolution targets different?
- How much work is included, and how are extra changes approved and billed?
- Are update testing, monitoring and reporting included?
- Who handles Microsoft and third-party escalations?
- What are the minimum term, notice period and exit handover arrangements?
- Who owns the source code, documentation and operational accounts?
- What happens if critical source code or access is missing during onboarding?
Download the support-quote comparison worksheet (CSV). Record scope, pricing basis, assumptions and each provider response.
Why the lowest monthly fee can be misleading
A low retainer may exclude the work your team needs most. Compare the total scope: an incident queue, proactive monitoring and a change backlog are different services. Check whether the advertised price assumes a certain user count or an associated licensing relationship. Avoid comparing a limited helpdesk package with custom development coverage as if they were equivalent.
Your next step
Request a scoped support quote
Share the app, integrations, recent incident history and coverage needs. MS Dynamics Guys will review the information required for a support proposal, separating onboarding from ongoing work.
Product documentation referenced on this page
- Microsoft: Business Central support and reseller responsibilities Microsoft Learn, checked November 2, 2026
- Microsoft: support operating models Microsoft Learn, checked November 2, 2026