One Version and updates in Finance and SCM

Dynamics 365 Finance and Supply Chain Management run under Microsoft's One Version service-update policy: every production environment, in every region, on every tenant, is updated to a current platform version on a fixed cadence. Customers have limited flexibility around timing and no ability to remain indefinitely on an older version. This is one of the biggest cultural differences from on-premise AX.

The cadence. Microsoft ships Service Updates roughly every six weeks — about eight per year — each bundling new features, fixes, and platform changes. Service Updates apply in a rolling fashion across the tenant base; customers can choose between channels (e.g. General vs Early access) for some control over which release lands when.

Pause windows. Customers can pause Service Updates for a small number of cycles in a calendar year, deferring an update — typically used to skip a busy period like year-end close. After the maximum pause is consumed, the update applies automatically. The pause is per-environment and configured through LCS.

Service Update vs Application/Platform update. Platform updates are runtime and infrastructure changes — these are mandatory and continuous. Application updates change Finance/SCM standard code; these are part of the Service Update bundle and follow the same cadence.

Custom code obligations. Custom code (X++ extensions, integrations, reports) compiled against an older platform may break against a newer one. Microsoft's tools include Code Upgrade services in LCS that scan custom code for breaking changes ahead of a service update.

Quality assurance. Microsoft pre-tests Service Updates against a sample of customer environments and gates rollout by region. Customers should still run their own regression suite against the preview service update on a sandbox before applying to production.

Why One Version. Microsoft cannot economically support hundreds of AX versions in production for decades. One Version is the price of SaaS: you get continuous improvements, security patches, and uniform support, in exchange for keeping current. The discipline is real but the rewards — performance gains, AI features, regulatory updates — accrue without big-bang upgrades.

Operational reality. Mature Finance/SCM customers treat each Service Update as a small ops task: install in sandbox a week or two ahead, run the regression suite, brief power users on new features, accept production rollout. With practice it becomes routine.