Which platform carries which capability, what a licence actually covers, and what each release wave changes.
An AI optimization app computes the decisions Dynamics 365 records but never derives — pricing, stock, pick-path, quoting. Here's what the category is, how it differs from Copilot and your ERP partner, and who builds it.
Ordered by chapter. Each post stands alone but builds on the one before it.
Microsoft Fabric is the default answer for Dynamics 365 analytics right now — and it isn't always the right one. Here's the honest decision: when Fabric earns its place as your data foundation, and when it's overkill.
Dynamics 365 is an umbrella over two different ERPs with two different admin planes. Choosing between Business Central and finance and operations apps sets your admin portal, your update cadence, your developer language, how you obtain environments and who releases production. Every claim here is quoted from Microsoft's own pages.
Seven reference architectures for AI that optimizes decisions on Dynamics 365 — the Azure services, the D365 read and write surfaces, the cost shape, and where each pattern stops working.
No. Microsoft describes Dynamics 365 as a set of applications you choose one, some, or all of. The useful part is what the umbrella contains — two ERPs, a family of customer engagement apps, and Power Platform underneath — and where the seams between them fall.
Through the surfaces each ERP publishes for exactly that purpose — and the two ERPs under the Dynamics 365 umbrella publish different ones. Business Central names four built-in ways into Dataverse plus three web-service types. Finance & Operations names virtual entities, dual-write and data entities. On two of those surfaces Microsoft states that no copy of your data is made.
Microsoft publishes the app prices and the attach prices, but not the two user-licence prices most quotes actually turn on. Base plus attach, the seat minimums that differ by edition, and the four numbers you have to go and measure yourself.
Dataverse and Operations storage became one pooled entitlement in December 2025. Here is what the published entitlements are now, and the four different things Microsoft says happen when you exceed them — because storage, Business Central, Copilot Credits and platform requests each enforce differently.
Microsoft's standard cloud offer for finance and operations apps includes two environments — one production instance and one Tier-2 Standard Acceptance Testing instance. Everything past those two is bought as an add-on, run in your own Azure subscription, or provisioned against capacity you already hold, depending on which admin plane you are on. There are now two tier vocabularies in the documentation, the availability commitment covers production only, and a project that mixes the vocabularies buys the wrong thing.
Microsoft's deprecation register states that Lifecycle Services is being replaced by the Power Platform admin center. New project creation froze on 16 February 2026; self-service migration tooling is a mid-2026 preview. No page we found publishes a full retirement date. Microsoft names a destination for every retired capability — the question is whether each destination is actually there, and for three of them the answer is more complicated than the table suggests.
On a Supply Chain Management estate, "are we up to date" has three separate answers — the service update (10.0.48), the Planning Optimization Add-in, and the Demand planning app on its own 1.x version line. Microsoft publishes a calendar for one of them, and the One Version documentation and the release-plans hub publish no combined view. Here is where each answer lives and how the trains couple.
The Go-live Readiness Review is a Microsoft-side gate on your production environment, not a milestone your programme plan owns — and Microsoft's own pages describe who runs it, in what format, and where, three different ways. Here is each wording quoted, the deadline Microsoft publishes, the prerequisites that block submission before anyone reads your answers, and what the Power Platform admin center pages do and do not say about this gate.
One Version commits Microsoft to four service updates a year, a floor of two, one pause, and a backward-compatibility promise covering binary and functional compatibility. It also names its own exclusions in the same paragraph — non-X++ APIs and dependent software libraries. Here is the guarantee quoted, and the boundary quoted, from the pages that carry both.
Microsoft publishes the list of Azure regions where finance and operations apps run, and it is current as of 23 July 2026. The list is the easy part. Three different decisions get called "the region question" — the Azure region, the macro region geography that governs data residency, and the country localization driven by a legal entity's primary address — and they are answered on three different Microsoft pages.
Both Dynamics 365 ERPs update twice a year in April and October, and almost nothing else about their cadences matches. Business Central gives the admin a five-month window to pick a date and can cancel a running update; Finance & Operations gives seven calendar days on a sandbox and no rollback. The version numbers do not cross-walk either. Here are both cadences from Microsoft's pages, and where the change-management cost actually lands.
Two languages, two extension models and two separate Microsoft Marketplace offer types. Finance & Operations bans overlayering outright and Business Central is additive by construction — but X++ commits you to Chain of Command and its rules about the next keyword, while AL commits you to the object model and the .app package. What travels between them is the engine, not the binary.
A dated list of what Microsoft has published as retiring across Dynamics 365, with each date quoted in Microsoft's own sentence and each row carrying its URL — plus the four different things "retired" can mean, the notice Microsoft commits to alongside each ending, and the two dates in here that sit in a release wave Microsoft has not published yet. Compiled 31 July 2026; re-derive it every quarter.
Microsoft keeps backups 28 days for production, seven for sandboxes. What a point-in-time restore does, its downtime, and what it never brings back.
A refresh copies production into a sandbox, then disables every user, withholds every batch job, clears every secret and drops every endpoint. The checklist.
Microsoft's self-service migration moves F&O environment management out of LCS, one way, about 15 minutes of downtime per AOS. Sandboxes first.