Every implementation ends the same way: a few weeks of hypercare, a handover deck, and a partner rolling off to the next programme. What begins at that moment lasts far longer than the implementation did. A Dynamics 365 estate will be live for a decade or more, absorbing Microsoft's continuous updates the whole way, and the quality of its support arrangement decides whether it ages like infrastructure or like neglect.
Having taken over enough estates from lapsed arrangements, the difference between good and nominal support is concrete. Here is what the good version contains.
One Version updates arrive on Microsoft's calendar regardless of anyone's availability. A real arrangement owns the cadence: each release lands in a sandbox promptly, an automated regression suite runs over the processes the business cannot lose, findings get fixed inside the window, and production updates on schedule. If the support contract does not name who runs regression testing and how it is automated, updates are being waved through on hope. I wrote about the machinery in the One Version post; the point here is that support without it is not support.
A live ERP generates a steady stream of small, sensible asks: a report, a workflow tweak, a new legal requirement. Nominal arrangements make every ask a quote, which teaches the business to stop asking, which is how estates fossilise while the business changes around them. Good arrangements run a standing backlog with agreed capacity, prioritised by someone on the client side, delivered under the same pipelines and standards as the original build. The estate keeps moving at the speed of the business, in small safe steps.
Environments need administration: refreshes, capacity, user access, performance. Integrations need monitoring that notices failures before month-end does. These are unglamorous, and their 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 no nouns underneath is a phone number, not an arrangement.
The failure mode of cheap support is a rotating cast of strangers rediscovering your configuration at your expense. Continuity is worth paying for: a small consistent team that accumulates knowledge of your estate, with functional and technical coverage and a path to deeper specialists when something serious surfaces. This is also where a blended model earns its keep. Routine work runs from our Vietnam delivery centre at delivery-centre rates, Australian consultants stay across the estate for the judgement calls, and the client sees one team with one standard.
The uncomfortable truth about ERP support is that some vendors price it as an annuity and manage it for dependency. The healthier posture is the same one we take on handover generally: documentation current, knowledge shared, and the client's own team as capable as they want to be. Clients stay because the arrangement is worth it that month, which is the only durable reason to stay.
Our Dynamics 365 practice runs support arrangements on exactly this shape, several of them for years past the implementations they followed.
Marcel Rizzolo is Director of Coder Trove.