Microsoft ERP Options: Business Central vs F&O

Microsoft sells two ERP products today: Dynamics 365 Business Central, its ERP for small and mid-sized businesses, and the finance and operations apps (Finance, Supply Chain Management and their siblings, usually shortened to "F&O"), built for larger and more complex organisations. Everything else with "Dynamics" in the name is either a CRM app or a legacy product on its way out. The useful dividing line between the two is not headcount on its own. It is the licence floor, how often you can absorb change, how you will customise, and how hard your integrations will push the system.

I come at ERP choices from the integration side, the connectors and data flows around the system, so this comparison pays particular attention to extensions and API limits. Every price and limit below comes from Microsoft's own pages, checked on 13 October 2026.

The map: what "Microsoft ERP" means in 2026

When someone searches "Microsoft ERP" they are usually looking at one of four things:

• Business Central. Microsoft calls it its "flagship SMB ERP product" in the Dynamics GP end-of-support announcement. It is the destination for Dynamics NAV customers: Microsoft documents a migration path from NAV to Business Central online that runs through Business Central version 14 on-premises.
• Finance and operations apps. Dynamics 365 Finance, Supply Chain Management, Commerce, Project Operations and Human Resources share one platform. Microsoft's licensing guide describes Finance as enabling "medium-sized organizations and enterprises" to run global financial operations. AX 2012 R2 and R3 customers have a documented upgrade path into it.
• Dynamics GP. Being retired. Product support and updates end on 31 December 2029, and security patches end on 30 April 2031, according to Microsoft's announcement and the GP lifecycle page.
• Dynamics 365 Sales, Customer Service and the other CRM apps. These are not ERPs, although they share the Dataverse platform and licensing rules with the ERP products.

So the real choice is between two products, not two editions of one. They have different codebases, extension languages and operating models, and moving across later is a reimplementation, not an upgrade.

What each one costs to license

These are Microsoft's US list prices per user per month, paid yearly, as shown on the product pricing pages:

Product	List price	What it adds
Business Central Team Members	$8.00	Read data, approve workflows, update select records
Business Central Essentials	$80.00	Core finance, sales, purchasing, inventory, projects
Business Central Premium	$110.00	Essentials plus manufacturing and service order management
Dynamics 365 Finance	$210.00	Enterprise finance
Dynamics 365 Finance Premium	$300.00	Adds planning, budgeting and forecasting
Supply Chain Management	$210.00	Enterprise supply chain and manufacturing
Supply Chain Management Premium	$300.00	Premium tier of SCM

Source: Business Central pricing, Finance pricing and Supply Chain Management pricing, all checked 2026-10-13; feature notes from the Dynamics 365 Licensing Guide, March 2026. Microsoft says the pages are "for informational purposes only" and vary by country and currency.

The headline per-user gap matters less than the minimum purchase. The Microsoft Product Terms for Dynamics 365 set a minimum of 20 licences each for Finance, Supply Chain Management, Commerce and Project Operations, and 10 for the Premium editions of Finance and SCM, and those minimums must be maintained through the agreement term. At the list price of $210, twenty Finance users is a floor of $50,400 a year in licences alone, before any implementation work, and that is arithmetic from the pricing page and Product Terms linked in this paragraph. The same section of the Product Terms lists no minimum for Business Central.

Two more licensing rules change the arithmetic:

• Base and attach. When one user needs several Dynamics 365 apps, the first licence must be the highest-priced one (the "base"), and further apps are bought at a discounted "attach" price. That is in the March 2026 licensing guide, page 6. Ask for the attach price in writing for your exact mix.
• Check the price on the day you buy. The same March 2026 guide still quotes Business Central Premium at $100 in a footnote, while the live pricing page shows $110. Microsoft's own documents disagree, so quote from the price list on the date of your order, not from a PDF.

A newer line item is Copilot agents: both pricing pages say they need an Azure subscription and are billed in Copilot Credits. Treat that as a variable cost with its own budget owner.

The real dividing lines

Licence cost is the first filter, not the last. These are the questions I would put to any shortlist.

1. How much process complexity do you actually carry?

Business Central Premium already includes production orders, production BOMs, machine centres, capacity and supply planning, and service contracts, according to the licensing guide (page 10). A manufacturer does not need F&O just because it manufactures. The case for F&O is depth: many legal entities, complex warehouse and supply-chain processes, and enterprise financial planning. Write down the processes that genuinely need that depth. If the list is short, Business Central is probably the honest answer.

2. How many companies and environments?

Business Central online allows up to 300 companies in one environment, per Microsoft's operational limits. A customer with Essentials or Premium licences can use one production environment and three sandboxes at no extra charge. Database storage starts at 80 GB per tenant, plus 2 GB per Essentials user and 3 GB per Premium user, as set out on the capacity page. Few small groups hit these ceilings, but a business that stores many files in the ERP or runs one company per franchise should model them first.

3. Can you absorb Microsoft's update rhythm?

Both products are evergreen, and neither lets you sit on an old version for years.

• Business Central ships two major updates a year, in April and October, plus monthly minor updates. After a major release you get a five-month window to schedule the update, then a one-month grace period. After that comes an enforced period in which extensions that block the update "might be automatically uninstalled" so the update can succeed. Source: Business Central update cycles.
• Finance and operations ships four service updates a year (February, April, July and October). You must take at least two of them and can pause only one at a time. Source: service update availability.

The practical question is who runs regression testing when an update lands. If nobody owns it, extensions and integrations are what break.

4. How will you customise?

Both platforms now allow customisation only through extensions, which is the right design for upgrade safety:

• Business Central is extended in AL, written in Visual Studio Code, by adding to or extending existing objects. See developing extensions in AL.
• Finance and operations is extended in X++. Microsoft states that extensibility is the only customisation framework and that overlayering, the old AX way of editing Microsoft's code directly, is not supported. See the extensibility home page.

This is also why moving from one to the other is a rebuild. AL and X++ extensions are not portable between the products, and nor are the data models underneath them. If an implementer proposes "start on Business Central and graduate to F&O later", ask them to price the second project now.

5. How hard will your integrations push it?

This is the dimension that is easiest to skip during selection and that integrations feel first. Business Central online enforces per-user API limits: 5 concurrent OData requests per user, a rate of 6,000 requests per user in a five-minute sliding window, and 429 Too Many Requests beyond that. See the operational limits. Microsoft's own advice for heavy integrations is to spread the load across several users or service principals.

Finance and operations throttles on resources rather than fixed per-user counts. You assign each integration a Low, Medium or High priority, and when the system is under pressure it returns "Too many requests" to the lower priorities first. See throttling prioritisation.

Either way, an integration that fires one synchronous call per marketplace order through one service account is a design that will fail on a busy day. Plan for queues, retries with back-off, idempotent writes and separate identities for separate integrations from the start.

6. Do you need to run it yourself?

Both have on-premises options, but they are not equal. Business Central on-premises receives the same fixes through cumulative updates, according to the update cycles page. Finance and operations on-premises cannot run on any public cloud, including Azure. You stand up your own high availability, disaster recovery and sandboxes, and some cloud capabilities are not included, per Microsoft's deployment options page. Unless data-sovereignty rules force it, I would treat cloud as the default for both.

A one-page decision checklist

Answer these honestly before a demo. Each "yes" leans you towards F&O; mostly "no" points to Business Central.

1. Will you have at least 20 full users of Finance or of Supply Chain Management, each on its own, for the whole contract?
2. Do you run many legal entities with intercompany flows, consolidation and multiple currencies as daily work, not an annual exercise?
3. Do warehouse, production or planning processes need depth that Business Central Premium's manufacturing and service features do not cover? Test this in a sandbox with your own data.
4. Do you have, or will you fund, a team that runs regression tests at least twice a year, and ideally four times?
5. Will your integrations generate sustained high API volume that needs prioritised throttling rather than per-user limits?
6. Is the budget for licences plus implementation comfortable at the 20-user floor and above, before any Copilot consumption?

And three questions that apply whichever way you lean:

• Which of our current customisations survive as extensions, and which are we retiring?
• Who owns each integration identity, its retry logic and its monitoring?
• What is our plan for the April and October (or quarterly) update windows?

Where Microsoft ERP selections go wrong, and how to spot it early

These are the warning signs to look for in a proposal or a shortlist:

• Buying F&O for prestige. The signal is a licence count padded to reach 20 users, with several "full" users who only approve or look things up. If most of your people would be Team Members, the floor is telling you something.
• Ignoring Business Central's API limits. The signal is an integration design with one service user and no queue. Ask the implementer what happens when the 429 responses start.
• Treating updates as optional. The signal is a statement of work with no line for update testing after go-live.
• Planning a later move between the products. There is no in-place upgrade between them. Budget a reimplementation, or choose the bigger product now if you are genuinely sure you will need it.
• Racing the GP deadline. If you are on Dynamics GP, plan to be live on the new system with at least one full year-end behind you before the end of 2029.
• Leaving Copilot consumption unbudgeted. Agree who approves Azure-billed agent spend before the first agent is switched on.

For the hosting question that sits under every one of these choices, see cloud ERP vs on-premise in 2026.

When neither is the right answer

Microsoft's ERPs make most sense for organisations already standardised on Microsoft 365, Entra ID and Azure. If that is not where you live, compare more widely. I work with Odoo more than any other platform, so weigh my opinion accordingly; I compare the main options by size, industry and budget in Choosing the right ERP for your business.

How I would run the decision

1. Write the process list first. Note which processes need F&O depth and which are standard in Business Central Premium.
2. Price the floor. Use the current price list, the Product Terms minimums, the attach prices in writing, and a line for agent consumption.
3. Prototype the hardest integration against a sandbox. Push realistic volume through it and see where throttling bites; it settles more arguments than any demo.
4. Read the update calendar. Put the next four update windows in the plan with named owners.
5. Get a second opinion before signing. Have someone who is not selling the licence review the architecture.

My technical architecture review is built for Odoo deployments: custom code, integration patterns, infrastructure and upgrade compatibility, ending with a written report and a walkthrough call. If Odoo is on your shortlist next to Microsoft, that is where it fits. For a Microsoft-only shortlist, or if you simply want to talk the decision through, get in touch first.

Frequently Asked Questions

What is the difference between Business Central and Dynamics 365 Finance and Operations?

They are separate products. Business Central is Microsoft's ERP for small and mid-sized businesses, extended in AL, with two major updates a year. Finance and operations is the enterprise platform, extended in X++, with four service updates a year and a 20-licence minimum per product in the Product Terms.

Can I start on Business Central and move to F&O later?

Yes, but it is a new implementation and data migration, not an upgrade. Your AL extensions and integrations would have to be rebuilt, so price both projects before you choose.

How many users do you need for Dynamics 365 Finance?

The Product Terms set a minimum of 20 licences for Finance and for Supply Chain Management, and 10 for their Premium editions, maintained through the agreement term.

What should Dynamics GP customers do?

Plan the move well before the deadline. Product support and updates for GP end on 31 December 2029, and security patches on 30 April 2031. Microsoft positions Business Central as the successor; compare it with alternatives anyway.

Is Business Central only for very small companies?

No. Premium includes manufacturing and service management, and one online environment can hold up to 300 companies. In practice the limits that bite are per-user API throttling and the update window, so test both against your own volumes.