Business Central licensing and pricing

How Business Central is licensed — Essentials vs Premium, Team Members, External Accountants, and what really drives total cost.

Updated 2026-05-06

Business Central licensing is, on the surface, simple. There are three named-user licenses plus an accountant license, sold per user per month, with Microsoft list pricing published on its site. The complexity is in matching license type to actual user behaviour.

Essentials is the standard full-user license. It covers financials, sales and purchasing, projects, inventory, warehouse, distribution, and basic supply chain. Most users in most companies are Essentials.

Premium is Essentials plus manufacturing and service management. Premium is required if anyone in the company uses those modules, and crucially you cannot mix: in a single tenant, all full users must be on the same SKU — either all Essentials or all Premium. This trips up companies that have a small service department and discover that one user's needs force every other full user up to Premium.

Team Member is a lower-cost license for employees who only need read access plus a narrow set of write actions: time entry, expense entry, approval workflows, updating their own data, and consuming reports. It is not a general data-entry license — posting transactions, processing orders, or creating items is not allowed.

External Accountant is a free license for the customer's external accountant, with the same rights as a full user, scoped to the company they support.

What actually drives total cost is rarely the license fee. Implementation (partner services), ISV add-ons from AppSource, storage beyond the included database capacity, environments (sandboxes are mostly free, but additional production tenants are extra), integrations (Power Automate, API calls, middleware), and support all add up. A typical SMB implementation is somewhere between three and twelve months of partner time, often costing several multiples of the first-year license spend.

A pragmatic rule of thumb: budget the license, then budget the same amount again for implementation in year one, and a smaller recurring slice for managed services and enhancements after go-live.

Related guides