What Is Microsoft Dynamics 365 Finance and Operations? The Split, the Apps, and SME Fit

What Microsoft Dynamics 365 Finance and Operations actually is

Microsoft Dynamics 365 Finance and Operations (often shortened to D365FO or F&O) is Microsoft's Azure-based SaaS ERP offering for financial and operational business processes. It provides ERP functionality without the customer having to manage the underlying infrastructure, and it evolved from the earlier Microsoft Dynamics AX product line.

The name is genuinely confusing today because the original unified product called 'Dynamics 365 for Finance and Operations' no longer exists as a single licensable app. In October 2019 Microsoft split it into two separately licensed applications, and the term 'finance and operations apps' now refers to the platform family rather than one product. So when someone says 'Finance and Operations' in 2026 they usually mean one of three things: the legacy combined app (pre-split), the platform family as a whole, or — most commonly — Dynamics 365 Finance plus Dynamics 365 Supply Chain Management licensed together.

This is a definitional page. If you are deciding between Business Central and F&O for your business, see our Business Central vs Finance and Operations tier guide; if you want module-level detail on the Finance app itself, see our Dynamics 365 Finance guide. This page stays focused on what the F&O name actually refers to.

• →Azure-based SaaS ERP: ERP functionality delivered as a cloud service, no infrastructure to manage.
• →Axapta lineage: descended from Microsoft Dynamics AX, the upper-mid/enterprise ERP codebase.
• →Name now refers to a platform family, not a single product — the original combined app was split in October 2019.

The split into Dynamics 365 Finance and Supply Chain Management

Announced at Microsoft Inspire 2019 in July and effective October 1, 2019, Microsoft split the single 'Dynamics 365 for Finance and Operations' product into two independently licensable apps: Dynamics 365 Finance and Dynamics 365 Supply Chain Management. The split was designed to give organizations more flexibility, allowing them to license only the functionality — Finance or SCM — that they needed.

Crucially, both apps still run on the same underlying finance and operations platform. They share the same data model when licensed together, the same infrastructure, the same One Version continuous service update cadence, dual-write integration with Dataverse, Power Platform integration, and common administration and security. Customers were not re-implementing from scratch: the platform and data model are shared, and existing customers on the legacy combined app transitioned to the split apps through the One Version update cadence and Microsoft's licensing guidance.

For a buyer this matters because it changes how you scope and license. You are no longer buying one monolithic ERP. You are buying Finance, or SCM, or both — and the broader 'finance and operations apps' family can also include Dynamics 365 Commerce, Project Operations, and Human Resources, all on the same fin-ops-core platform.

From Dynamics AX to Finance and Operations: the lineage

The codebase that became Microsoft Dynamics 365 Finance and Operations traces back to Axapta, the ERP Microsoft acquired and rebranded as Dynamics AX. Dynamics AX was Microsoft's upper-mid-market and enterprise ERP, distinct from Navision (which became Dynamics NAV and later Business Central) aimed at small and medium-sized businesses.

When Microsoft moved its Dynamics ERP line to the cloud under the Dynamics 365 brand, Dynamics AX became 'Dynamics 365 for Finance and Operations' — a single app combining deep financials and supply chain/operations capabilities. That unified app is what most documentation, partner articles, and older training material still refer to as 'F&O' or 'D365FO'. After the October 2019 split, the AX lineage continues inside both Dynamics 365 Finance and Dynamics 365 Supply Chain Management.

Understanding the lineage matters for two practical reasons. First, it explains why F&O targets enterprise and upper mid-market organizations: it inherits a codebase built for complex, global, high-volume operations, not for SMBs. Second, it explains the relationship to Business Central: BC comes from Navision (SMB), F&O comes from Axapta (upper-mid/enterprise) — they are different products on different codebases, not two tiers of the same app.

• →Axapta to Dynamics AX to Dynamics 365 for Finance and Operations, then split into Finance + SCM.
• →Navision to Dynamics NAV to Business Central: a separate SMB codebase, not a tier of F&O.
• →The AX lineage is why F&O targets enterprise and upper mid-market, not small business.

Who F&O targets: enterprise and upper mid-market

Microsoft positions the finance and operations apps for enterprise and upper mid-market organizations with complex, global, high-volume operations. The clearest fit signals are manufacturing, advanced warehousing and distribution, multi-entity finance, regulatory and compliance needs, and sophisticated supply chains. This is documented positioning, not partner opinion.

The contrast with Microsoft's SMB tier is explicit. Microsoft positions Dynamics 365 Business Central for small and midsize businesses — it is the documented ERP choice for companies that are outgrowing entry-level tools. F&O sits one tier above that, for organizations whose complexity has outgrown Business Central or who started at enterprise scale.

What this means in practice: F&O is licensed per named user at a higher per-user price than Business Central, it requires partner-led configuration, performance testing, data migration, and often extensions or ISV solutions, and Microsoft recommends its FastTrack program and the 'Success by Design' methodology for these projects. The capability ceiling is much higher than BC — but so is the total cost of ownership and the implementation footprint. Flectic's AI-Accelerated Delivery Framework is designed to deliver up to 3x faster than a conventional rollout within those ranges — qualified by our delivery methodology, not a blanket guarantee.

• →Positioned for enterprise and upper mid-market: complex, global, high-volume operations.
• →BC is the documented SMB tier; F&O is one tier above, for complexity that has outgrown BC.
• →Per-user cost, implementation footprint, and TCO are all materially higher than BC.

Should an SME be looking at F&O at all?

For most SMEs reading this, the honest answer is no — not as a starting point. F&O's per-user pricing (roughly US$210/user/month for Finance, US$180–$240 for the combined Finance + SCM full-user license) and its 12–24+ month typical implementation runway are calibrated for organizations whose complexity genuinely requires that ceiling. If you are under roughly 200 users, run a single-digit number of entities, and operate on an SME budget, Business Central is the structurally better fit and the lower-risk starting point.

That said, F&O becomes the right answer when specific scale triggers fire: user count crossing roughly 200 with complex roles; legal entities growing past roughly 5–10; multinational multi-currency consolidation; advanced, process, or discrete manufacturing that strains BC Premium's model; or heavy customization that strains the AL-extension model. The decision is really about which growth stage you are at, not which product is universally better.

Flectic is platform-neutral across both D365 tiers plus Odoo, so we will not steer you toward F&O if BC genuinely covers your 5–7 year plan — and we will not steer you toward BC if your growth trajectory puts you in F&O territory inside that window. The right next step is a scale-trigger assessment, which is exactly what our ERP Readiness Call is built for.

• →Most SMEs should start at Business Central, not F&O — lower per-user cost, shorter implementation.
• →F&O becomes the right answer when scale triggers fire: 200+ users, 5–10+ entities, multinational consolidation, advanced manufacturing.
• →Plan the tier choice around a 5–7 year horizon, not just today's headcount.

How F&O is licensed and how the legacy app transitions

Because of the 2019 split, there is no single 'F&O' license anymore. Buyers license Dynamics 365 Finance, Dynamics 365 Supply Chain Management, or both — and can attach Commerce, Project Operations, or Human Resources from the same platform. Light-user tiers (Team Members at roughly $8/user/month, attach licenses for qualifying base holders at roughly $20/user/month) layer on separately, so not every seat needs to be a full-user license.

Existing customers on the legacy combined 'Dynamics 365 for Finance and Operations' app were not forced into a rip-and-replace. They transitioned to the split apps through Microsoft's One Version continuous update cadence and the licensing guidance Microsoft published alongside the split. The shared platform, data model, and dual-write integration with Dataverse meant the transition was a licensing and configuration change rather than a re-implementation.

For new buyers, the practical implication is to scope by capability, not by the old monolithic name. If you only need deep financials, license Finance. If you only need supply chain and operations, license SCM. If you need both, license both on the shared platform. Avoid buying the full family 'just in case' — Commerce, Project Operations, and Human Resources each add cost and should be triggered by a real business requirement, not bundled by default.

• →No single 'F&O' license anymore — buy Finance, SCM, or both, and attach other family apps as needed.
• →Legacy combined-app customers transitioned via One Version updates, not a re-implementation.
• →Scope by capability: avoid bundling Commerce, Project Operations, or HR without a real requirement.

Flectic is platform-neutral across both D365 tiers

If you have read this far, you have noticed what is missing from this page: a sales pitch for F&O. That is the point. Single-platform partners steer you toward the license they carry. Flectic is the partner that can look at your business and honestly recommend either D365 tier — plus Odoo if your budget and stack point that way — because we deliver all three and we would rather earn your implementation than lose your trust with a rigged verdict.

Our AI-Accelerated Delivery Framework is designed to deliver up to 3x faster than a conventional rollout, our lifecycle support continues after go-live, and our SME focus means we work within real budgets rather than enterprise-program timelines.

Smarter ERP. Faster Transformation. Continuous Growth.