A Dynamics 365 support arrangement after hypercare should cover four things: One Version update management with automated regression testing, a standing enhancement backlog with agreed capacity, environment administration and integration monitoring with named response times, and a small consistent team that knows your estate. If the contract does not name all four, it is not a support arrangement.
Every implementation ends the same way: a few weeks of hypercare, a handover deck, and the partner rolling off to the next programme. What begins at that point lasts far longer than the implementation did. A Dynamics 365 estate will be live for ten years or more, taking Microsoft's updates the whole way, and the support arrangement decides whether it ages well or badly. We have taken over enough estates from lapsed arrangements to know the difference between good support and nominal support, and it is concrete.
One Version updates arrive on Microsoft's calendar whether or not anyone is available. A real arrangement owns that cadence: each release lands in a sandbox promptly, an automated regression suite runs over the processes the business cannot lose, findings are fixed inside the window, and production updates on schedule. If the contract does not say who runs regression testing and how it is automated, updates are being waved through on hope. The One Version post covers the routine in detail.
A live ERP produces a steady stream of small, sensible requests: a report, a workflow change, a new legal requirement. Nominal arrangements turn every request into a quote, which teaches the business to stop asking, and the estate fossilises while the business changes around it. Good arrangements run a standing backlog with agreed monthly capacity, prioritised by someone on the client side and delivered through the same pipelines and standards as the original build. The estate keeps up with the business in small, safe steps.
Environments need looking after: refreshes, capacity, user access, performance. Integrations need monitoring that notices a failure before month-end does. None of this is glamorous, and its absence is invisible until it is expensive. The tell in a support contract is specificity: named environments, named integrations, named response times. "Support for your Dynamics environment" with nothing underneath it is a help desk, and a help desk is not what keeps an ERP healthy.
Cheap support fails in a predictable way: a rotating cast of strangers rediscovering your configuration at your expense. Continuity is worth paying for. A small, stable team builds up knowledge of your estate, covers both functional and technical work, and has a path to deeper specialists when something serious surfaces. This is also where a blended team earns its place. Routine work runs from our delivery centre in Vietnam at delivery-centre rates, Australian consultants stay across the estate for the judgement calls, and the client sees one team working to one standard.
Some vendors price ERP support as an annuity and manage it to keep you dependent. We take the opposite view: documentation stays current, knowledge is shared as we go, and the client's own team becomes as capable as they want to be. Clients stay because the arrangement is worth it that month. That is the only durable reason to stay.
The period immediately after go-live, usually two to six weeks, when the implementation team stays on at full strength to fix issues quickly while users settle in. Support proper starts when hypercare ends.
Yes. The handover needs the environment inventory, integration documentation, the regression suite if one exists, and access to the Lifecycle Services project. We take over estates from other partners regularly; the first month is spent confirming what is documented matches what is deployed.
Most arrangements are a fixed monthly fee for a set capacity, with a rate for work beyond it. The price matters less than what the fee buys. Ask for the named environments, integrations and response times, and ask who runs regression testing.
No, and it is often not the right fit. Implementation partners are organised for programmes. Support needs a team organised for continuity.
Our Dynamics 365 practice runs support arrangements on this shape, several of them for years past the implementations they followed.
Marcel Rizzolo is Director of Coder Trove.