What is on the Dynamics 365 deprecation calendar, and what…

What is on the Dynamics 365 deprecation calendar, and what breaks on each date?

There is no single Dynamics 365 deprecation calendar. There are many lists, in different documentation sets, on different update cycles, in different formats — some calendar dates, some version numbers, some release waves with no date at all. The removed-or-deprecated home page links seven finance-and-operations lists plus the Power Platform one; the 2026 wave 1 deprecations page links fifteen product pages and three more under Other deprecations. Here is the merged version for an ERP estate, notice commitments alongside the endings.

Shelf life. Compiled 31 July 2026. Two things date it fast: 2026 release wave 2 has not published, and version 10.0.49 has not reached general availability although its deprecation entries are live. Re-derive it each quarter; assume it is stale once 2026 release wave 2 publishes — Microsoft's generic table gives September 16 as the example wave 2 date, with no year attached.

Four words that do four different things to you

Microsoft files all of this under one heading — Removed or deprecated features — and, across the nine deprecation pages we opened, defines two of the four outcomes: "A removed feature is no longer available in the product. A deprecated feature isn't in active development and might be removed in a future update."

**Deprecated [DEPR]** — What it means for you: Announced. Still works. A removal date may or may not exist · A current Microsoft example, quoted: "Deprecated. GIA will reach end of support on July 1, 2027." (SCM)
**Unsupported** — What it means for you: Still runs. Nobody fixes it. No date attached · A current Microsoft example, quoted: "Unsupported. As of April 2022, the job card device is no longer supported…" (same page)
**Removed* — What it means for you: Gone from the product · A current Microsoft example, quoted: (Preview) Rename item number*: "The capability is completely removed for all customers." (same page)
**Blocked for new deployments** — What it means for you: Existing use continues; you cannot start a new one · A current Microsoft example, quoted: "Starting in Supply Chain Management version 10.0.41, the deprecated master planning engine is blocked for all new deployments. Existing deployments can continue using it on a per-company basis." (master planning)

A register recording all four as "deprecated" has lost the thing it exists to hold: whether the feature stops on a date, stops when it breaks, or has already stopped for anyone starting fresh.

The calendar

Each row leads with the thing, quotes Microsoft's sentence, carries its page.

**New Lifecycle Services project creation (Finance, Supply Chain Management, Project Operations) — Microsoft's published wording: "Starting February 16, 2026**, you can't create new cloud implementation projects in Microsoft Dynamics Lifecycle Services…" (freeze) · What happens: In force, for new cloud implementation projects only — on-premises, Commerce, AX 2012 upgrade and tenant-move projects are unaffected. The deprecation register adds: "Existing customers with active Lifecycle Services projects retain access" (platform)
**Before-and-after field values in Dataverse audit events sent to Microsoft Purview — Microsoft's published wording: "Starting in May 2026**, Dataverse will no longer include before-and-after field change values in the audit events that are sent to Microsoft Purview." (Power Platform) · What happens: Dated May 2026 — Microsoft's page still reads "will no longer include" as of its 27 July 2026 update. Purview still receives the events; the value pair goes
**Static Dynamics 365 ERP MCP server — Model Context Protocol, the open standard that connects AI agents to business systems — (the earlier Dataverse-connector version) — Microsoft's published wording: "This static server will be retired on October 1, 2026**." (MCP) · What happens: Microsoft: "to avoid disruption when the static server is retired, use the new dynamic Dynamics 365 ERP MCP server"
**Version 10.0.47 (and every version, on its own date) — Microsoft's published wording: End of service November 20, 2026, in the "Targeted release schedule (dates subject to change**)" table, whose End of service column "indicates the date when no new cumulative service updates are provided" (schedule) · What happens: Microsoft "doesn't investigate, troubleshoot, or provide any fixes to issues on versions that reached their end of service" (policy)
**Asset Management mobile app — Microsoft's published wording: "Deprecated as of June 1, 2026… remains available for installation through Dynamics 365 apps in the Power Platform admin center until November 30, 2026**, with critical fixes from Microsoft during this transition period." (SCM) · What happens: Distribution ends, not the app: "Existing installations continue to work in customer tenants"
**Regression suite automation tool (RSAT) — Microsoft's published wording: "won't be supported after May 15, 2027" (heading); "deprecated and supported until 15th of May 2027" (Status); Deployment option: On-premises** (platform) · What happens: Support ends for the regression suite most One Version customers validate updates with. Four current pages disagree about its scope — see below
**Global Inventory Accounting (GIA) — Microsoft's published wording: "Deprecated. GIA will reach end of support on July 1, 2027." ([SCM](https://learn.microsoft.com/en-us/dynamics365/supply-chain/get-started/removed-deprecated-features-scm-updates)) · What happens: Support ends. Successor named only as "a multi-ledger costing solution". Published under the 10.0.49** heading — a release that has not shipped
**Exposing a Microsoft page as a SOAP, then an OData, endpoint (Business Central) — Microsoft's published wording: "In version 29.0, exposing a Microsoft page as a SOAP endpoint will no longer be possible"; "Starting in version 30**, it's no longer possible to expose a Microsoft page as an OData endpoint." (BC platform) · What happens: Integrations pointed at "any page from any app with the publisher Microsoft" break, Base Application included. Remedy: "copy the source code for the page and host the page in an extension/app"

Two more, briefly. The Audit file (NL) Electronic Reporting format — "Deprecated: By January 1, 2027… won't be supported", replaced by Audit File Financial XAF 4.0 in XML (NL) (Finance). And the Data Integrator templates for Dynamics 365 Field Service, which "will no longer be available after February 28, 2027".

Read the Business Central row twice: those are versions, not dates. And Microsoft's base-app page prints a neighbour inconsistently — the Peppol removal sits under the heading Changes in 2027 release wave 1 (version 30.0) while its text reads "removed in 2027 release wave 1 (version 29.0)."

Some of this sits in a wave nobody has published. https://learn.microsoft.com/en-us/dynamics365/release-plan/2026wave2/ returned HTTP 404 when we requested it on 31 July 2026, and Microsoft's release-schedule article publishes key dates for 2026 release wave 1 only — its generic table gives wave 2 September 16 and October 1 as example dates with no year attached; its wave 1 section carries the hedge "Delivery timelines and projected functionality may change or may not ship." Version 10.0.49 is in the same position — [PLAN], at general availability (self-update) September 11, 2026 (schedule), dates subject to change. The notice is real and quotable. The release carrying it is not out.

What Microsoft commits to by way of notice

A calendar of endings without the notice commitments is a scare, not a brief. The cross-product baseline: "The feature or capability will continue to work and will be fully supported until it's officially removed… Deprecation notifications can span a few months or years" (2026 wave 1 deprecations). Below that, the commitments differ by documentation set.

**Finance and operations apps — One Version FAQ — "The deprecation notice is announced in the product documentation 12 months** before Microsoft removes a feature from the app." With its own exception: "For breaking changes that only affect compilation time, but that are binary compatible with sandbox and production environments, the deprecation time is less than 12 months." (source)
**Supply Chain Management — the deprecated master planning engine** — "There's currently no timeline for the full removal… Microsoft isn't currently planning to remove it." And: "If Microsoft decides to remove the deprecated master planning engine, the company will announce those plans at least 12 months before the removal date." (source)
**Business Central — "When an object is marked as obsolete, another 12 months pass before the code is removed, in some cases even longer. Microsoft doesn't set a specific date for the removal** due to engineering and architectural considerations." (source)

Currently is Microsoft's word, twice, in the master planning row. Quote the first sentence alone and a non-plan becomes a threat; quote the second alone and a real deprecation becomes a shrug. Both belong in the register.

Where one product is written up four ways

The most useful thing here is not a date. It is a disagreement.

**Removed or deprecated platform features (ms.date 2026-06-09) — "won't be supported after May 15, 2027"; Status: "deprecated and supported until 15th of May 2027"; Deployment option: On-premises** (source)
**RSAT overview (ms.date 2026-05-27)** — The same banner, then: "The Regression suite automation tool (RSAT) significantly reduces the time and cost of user acceptance testing (UAT) for finance and operations apps." (source)
**Service update availability (ms.date 2026-06-04)* — "We recommend that you use tools such as the Regression suite automation tool (RSAT) for regression testing." — under Service update overview* (source)
**One Version service updates FAQ (updated 2026-04-13)** — "The Regression suite automation tool (RSAT) is available now and significantly reduces the time and cost of UAT." (source)

A dated deprecation whose scope field reads On-premises, on a product two current cloud pages recommend, for the job One Version makes unavoidable. We adjudicate none of it. If your update regression rests on RSAT, get in writing which page governs a cloud tenant after May 2027.

Where we would draw the line

We would not build against anything here without a named successor. Where Microsoft names one — Planning Optimization, the dynamic MCP server, XAF 4.0 — the migration is an engineering task. Where it names a category, as with "a multi-ledger costing solution", there is nothing to build against yet, and treating it as a plan is how a programme acquires a dependency on a page.

We would not let an optimization app inherit a retiring surface. Every Optimizer we build reads posted Dynamics data through supported entities and writes its decision back behind an approval step, on Dataverse and Azure. That constraint is why a retirement like the static MCP server is a configuration change, not a rebuild.

And we would not sell this as urgency. The nearest hard date is October; the furthest sits in a release wave that has not published. The failure mode is not ignoring a date. It is nobody owning the list.

What to do this week

Put the two index pages on your risk register with owners: the removed-or-deprecated home page and the 2026 wave 1 deprecations page.
Record which version each environment runs and read its end-of-service date off the targeted release schedule — noting Microsoft's own table header, dates subject to change.
Ask whether anything you own talks to the static Dynamics 365 ERP MCP server. Nearest hard date, clearest failure.
Re-derive this table once 2026 release wave 2 publishes. Do not update it from a summary — including this one.

About Cognilium Cognilium builds AI optimization apps for Microsoft Dynamics 365 — companion apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Dynamics is your system of record. Cognilium is your system of intelligence. https://cognilium.ai · https://www.linkedin.com/company/37180269/

If a date here lands inside something you own, book a fifteen-minute call and we will walk your estate against it — no deck. https://cognilium.ai