Dynamics 365 Business Central: a published price, no Arabic

Two pages on Microsoft’s own website tell you most of what you need to decide about this system. The first publishes the price in plain figures, which almost no vendor at this tier does. The second publishes a table of supported languages, and Arabic is not in it. Neither page is hard to find, and between them they settle more of the shortlist than any demo will.

Origin, and what the name has been

The product is Danish by birth and American by ownership. It began in Denmark as Navision. Microsoft bought it in July 2002 for $1.45 billion — $660 million in cash plus 14.5 million shares, per Microsoft’s own filing with the SEC — the first billion-dollar foreign acquisition in the company’s history. It became Dynamics NAV, was rebuilt for the cloud, and shipped as Dynamics 365 Business Central in April 2018. Two major releases land every year, in April and October.

The lineage matters for one practical reason: the consultants, the forums and half the training material still say NAV, and the accumulated knowledge of two decades is filed under that name.

The other Dynamics, and why people confuse them

Microsoft sells two ERP products and gives them similar names. They are not two sizes of one thing — they descend from two different companies it bought.

	Business Central	Finance & Operations
Ancestor	Navision (Denmark)	Axapta (Denmark, different lineage)
Extension language	AL	X++
Target	Small and mid-sized	Large enterprise
Certification	MB-800	MB-310, MB-330

A proposal that says “Dynamics 365” without saying which one is not a proposal yet. Ask which product, and ask which exam its consultants sat.

Who it fits

Five to about three hundred users, in trading, distribution, light manufacturing and services. The strongest single case is a company already deep in the Microsoft stack: if your finance team lives in Excel and your company runs on Teams and Outlook, the integration here is native rather than bolted on, and it removes a genuine slice of the training budget.

The weakest case is a company with heavy statutory reporting in Arabic and no partner it trusts. That is not a hedge — see the language section.

What it actually costs

Read from Microsoft’s pricing page on 6 September 2026, US pricing:

Plan	Per user per month, billed annually
Essentials	$80
Premium	$110
Team Members	$8

The publication itself is worth something. Two other systems in this series publish no figure at all, which means you cannot build even a rough budget without entering a sales process first.

The Essentials-to-Premium line is the one that catches people. Manufacturing and service management are Premium only. And the rule underneath it is the expensive part: every full user on a tenant must be on the same plan. You cannot buy Premium for the four people in production and Essentials for the other forty. One user who needs manufacturing moves the whole company to $110.

Team Members at $8 is the most abused licence in this market. It is a read-mostly licence: read anything, update your own data, approve, enter time. It is not a cheap version of a full user, and a proposal that puts thirty of your forty people on Team Members has either misread your operation or is hoping you will not check until after signature. Count the people who create documents, and licence those as full users.

Then the lines Microsoft’s page does not carry: implementation, data migration, the Arabic layer, the e-invoicing layer, and integration work. In this region the last three are not optional extras — they are the project.

What it does well

The price is published. You can build a first-pass budget before you speak to anyone, and you can check what a partner quotes you against a public number.

Microsoft-stack integration is real. Export to Excel, edit, publish back. Records surfaced inside Teams. Documents from Outlook. This is the feature that most reduces resistance from finance teams, and it is measured in no comparison matrix.

A deep partner market across the region, which means you can replace your implementer — worth more than any single feature the day you need it.

Two releases a year, applied by the vendor. You do not carry the upgrade project. This is also a constraint, and it appears in the next section.

Where it breaks

Microsoft ships no Arabic interface. This is the fact that decides the system for a large share of buyers here, and it is published by Microsoft itself: the official languages table in the Business Central documentation has no Arabic row at all. The Israel row is marked, in Microsoft’s own words, no RTL and English only. So an Arabic UI is a partner’s translation layer — someone else’s product, on someone else’s release schedule, sitting between you and a system that updates twice a year whether the layer is ready or not. Ask who maintains it, ask what happened at the last two release waves, and put the answer in the contract.

Microsoft localises about twenty countries, and none of them is Arab. Saudi Arabia, the UAE and Egypt all run on the W1 (worldwide) base with the country layer marked Localized by: Partner. Your VAT return, your ZATCA phase-two integration and your UAE e-invoicing connector are all partner code. That is not automatically bad — plenty of partner localisations are solid — but it changes the question from “does the system support it” to “who supports it, and what happens when the specification moves”.

Your data may not be where you assume. Microsoft’s cloud regions do not map onto the Gulf the way buyers expect. Saudi Arabia, Kuwait, Qatar, Oman, Jordan, Lebanon and Yemen deploy into the UAE geography; Egypt deploys into the South Africa geography. If a regulator, a parent company or a tender document imposes in-country residency, check this before anything else in the file, because no amount of configuration moves it.

Forced updates cut both ways. You never fall four versions behind, and you never choose your timing either. A customisation or a partner localisation that breaks at a release wave breaks on Microsoft’s calendar, not yours. Budget a regression pass twice a year rather than discovering the need at the second one.

Team Members, again. It is listed twice on purpose, because it is the single most common reason a Business Central quotation looks cheaper than a competitor’s and is not.

“Dynamics” on a proposal means nothing by itself. See the two-products table above.

Learning it

Microsoft’s own material is free and genuinely good: the learning paths on Microsoft Learn are structured, current and written to the exam. Get a trial tenant, then run one complete cycle by hand — purchase order, receipt, sales order, shipment, invoice, payment — and watch the general ledger entries each posting produces. Anyone who understands that chain understands the system.

Learn the functional side before the technical one. AL development is a real skill and a poor first destination: a developer who cannot explain a posting group will build elegant extensions to the wrong process.

A fuller path is published in Arabic as the Business Central learning path.

The certification

Read from Microsoft’s certification page on 6 September 2026:

Item	Value
Certification	Dynamics 365 Business Central Functional Consultant Associate
Exam code	MB-800
Level	Intermediate
Duration	100 minutes
Renewal	Every 12 months, free, online
Price	Varies by country

One detail is worth noticing because it says something about Microsoft’s priorities rather than about the exam: the language list for MB-800 includes Arabic (Saudi Arabia). You can sit the exam in Arabic for a product that has no Arabic interface. The certification programme was localised; the product was not.

The annual free renewal is a genuine advantage over vendors that charge for recertification. Put the date in a calendar — the credential lapses quietly.

When to choose something else

If Arabic in the interface is a hard requirement and you have no partner you would bet the project on, look at Odoo, where Arabic is in the core product. If data residency inside your own country is imposed on you, this system’s geography map may end the conversation before the functional fit is even assessed. If your manufacturing is complex and only a handful of people touch it, price Premium across the whole headcount before comparing anything, because that is the real figure. If you are a group consolidating many entities under heavy statutory reporting, look one tier up at SAP S/4HANA. And if your team lives nowhere near Microsoft’s tools, the integration argument — the strongest thing in this file — does not apply to you, and you should weigh the rest on its own.

Where it is clearly right: a Microsoft-stack company of twenty to two hundred people, in trade or distribution, with a partner who can show you the Arabic and tax layer working in another client’s live system, not in a slide.