Most of the money in a Microsoft Dynamics 365 Business Central subscription is decided by a few rules that never come up in a demo. The plan every user needs is set by the most demanding department. A cheap seat type that looks like it covers half the company covers fewer people than expected. And a discount that cuts the bill for anyone already running another Dynamics 365 application stays invisible unless someone asks for it.
This is written for the buyer, not the administrator. We quote no prices. Microsoft publishes current pricing on the Business Central pricing page, and the full rules live in the Dynamics 365 Licensing Guide. Figures below reflect the June 2026 edition.
The three user license types
Your bill is driven almost entirely by how many people fall into each of three buckets.
Business Central is licensed per named user. A named user is a person, not a login, and licenses cannot be rotated around the team: Microsoft does not allow reassigning a license to a different person within 90 days of the last assignment, other than to cover an absence or an out-of-service device.
| License | What the person can do |
|---|---|
| Essentials | Full use of finance, sales and marketing, purchasing and payables, inventory, supply planning, projects and time sheets, warehousing, and fulfillment. |
| Premium | Everything in Essentials, plus manufacturing (production orders, bills of materials, capacity planning, finite loading) and service management (service orders, service items, service contracts, dispatching). |
| Team Members | Read data across the system, update certain existing records, approve items routed to them, and a short list of other tasks. Detailed below. |
Essentials suits a distribution business, a professional services firm, a non-profit, or a food company that buys and sells rather than makes. Premium is for a business that builds things or runs a field service operation.
Two things come with every Essentials or Premium seat: up to three External Accountant licenses at no charge, covered below, and read-only access to Business Central records inside Microsoft Teams for colleagues who hold a qualifying Microsoft 365 license, per Microsoft's documentation.
The Essentials and Premium rule that sets your floor
This is the most expensive surprise in Business Central budgeting, and the rule is narrower than the version usually repeated.
Business Central holds your books in a company, and one environment can hold many companies. Each company carries an Experience setting that is either Essentials or Premium, and that setting governs who can work in it. Per Microsoft's documentation: "Users with an Essentials license can't sign in to a company that uses the Premium experience." A Premium user may sign in to an Essentials company but cannot use Premium features there. The restriction runs one way only.
The consequence is straightforward. If your operating company needs manufacturing or service management, that company is set to Premium, and every full user who works in it needs a Premium license. Not just the eight people on the shop floor. The controller, the accounts payable clerk, the buyers, the sales team, and the warehouse supervisor too. A four-person manufacturing requirement can lift 30 seats to Premium, and that difference is permanent operating cost rather than a one-time project line.
Microsoft's June 2026 guide does allow Essentials and Premium to be deployed in separate environments on the same Microsoft account, with the caveat that "licensed users can only access the environment for which they are entitled." That helps a holding company with genuinely separate operating businesses. It does not help a single business whose sales, finance, and production teams share one set of books, because splitting them means splitting the data.
Before you sign, list every person who will need to open the company that carries manufacturing or service management, and price that list at Premium.
Team Members: read a lot, change a little
Team Members is the license people hope will cover half the company inexpensively. It covers a narrower group than expected, and the gap usually shows up after go-live.
Per the June 2026 guide, a Business Central Team Members license grants a named user these rights, for their own use and not on behalf of others:
- Read data within Business Central.
- Update existing data and entries, such as customer, vendor, or item records created earlier.
- Approve or reject tasks in all workflows assigned to that user, limited to records a Team Members user can already access.
- Create, edit, and delete a sales or purchase quote.
- Create, edit, and delete personal information.
- Edit job time sheets for approval.
- Use the Power Apps and Power Automate rights that come with a Dynamics 365 license.
The module can also be extended with a maximum of 15 additional tables, custom or standard.
Read that list for what is missing. Creating a sales order is not there. Posting an invoice is not there. Neither is receiving inventory, running a payment journal, or issuing a purchase order. Team Members works well for an executive who wants numbers, a project manager who approves time, or a department head who signs off on spend. It falls apart the moment someone needs to transact.
The common case is an inside sales coordinator budgeted as a Team Member who turns out to enter orders all day, or a receiving clerk who posts goods receipts. Both need a full license, and a seat upgraded six weeks after go-live costs you the difference for the rest of the term.
Attach licensing: the discount to ask about by name
If anyone in your business already uses another Dynamics 365 application, this is likely the largest single lever on your Microsoft bill, and it is rarely raised unprompted.
Microsoft prices multi-application users through a base and attach structure. The first application a person holds must be the highest-priced one, and that is the base license. Further Dynamics 365 applications for that same person can then be bought as attach licenses at a materially lower rate. Per the guide: "Base and attach licenses are identical in their core capabilities and are only differentiated in price."
The June 2026 guide shows Business Central Essentials available as an attach license to users whose base license is one of these:
- Dynamics 365 Sales Enterprise
- Dynamics 365 Customer Service Enterprise
- Dynamics 365 Customer Service Premium
- Dynamics 365 Field Service
So the account manager who already carries a full Dynamics 365 Sales license and now needs to check inventory and raise invoices does not pay the full Business Central rate. Across a sales team of 15, that is a meaningful annual difference.
It runs the other way too. A user based on Business Central Essentials can attach Sales Professional or Customer Service Professional, and one based on Business Central Premium can attach those two plus Customer Service Enterprise, Field Service, or Sales Enterprise. Business Central Premium itself is offered only as a base license, never as an attach.
Three points:
- The base has to stay active. Microsoft enforces this in the admin tooling: an administrator cannot assign an attach license to a user without the required base.
- Attach licenses do not add capacity. Same functionality, but no extra database storage or environments. They ride on what the base license already brought.
- It is a per-person structure. What matters is how many individuals overlap across two applications, not how many products your company owns.
Device licenses for shared stations
If you have terminals that many people touch and no one owns, licensing the terminal instead of the people is usually cheaper, at some cost in flexibility.
A Business Central Device license covers a shared device: a shop floor station, a warehouse scanner, a receiving desk, a point-of-entry terminal. Per Microsoft's licensing documentation, the license "allows multiple users to simultaneously use a device that is covered by the license," and the number of device licenses you own sets how many users in the designated device group can be signed in at once. Devices can use a shared login or individual logins.
The trade-offs:
- Device licenses give limited access to a subset of Business Central, not full user capabilities. They are for scanning, clocking, and posting the transactions the station exists to post.
- A device user cannot be the first person to sign in to a new environment. A full user, administrator, or external accountant has to do initial setup.
- If a person also needs to work from their own laptop, the license does not follow them. That person is a named user.
License the device when several people share one station and none of them needs Business Central anywhere else. License the person when the reverse is true.
Your external accountant does not need a paid seat
A small saving, and an easy one to miss when a bookkeeping firm asks for access.
Every Essentials or Premium customer can procure up to three External Accountant licenses at no charge. Per Microsoft's guide, these "provide the same use rights as assigned Business Central licenses, except access to user set up or administrative tasks." Microsoft's accountant documentation notes they are free but still have to be procured, and there is an Invite external accountant action in the product. Your accountant needs a work account based on Microsoft Entra ID. If your outside firm needs a fourth person, that one is paid.
Environments and storage: what is included
Storage overruns do not stop you trading, but they do stop something you will want to do, usually at the worst moment.
Every subscription includes one production environment and three sandbox environments. Sandboxes are for testing, training, and rehearsing an update on a copy of live data.
Storage is pooled across the account rather than allocated per environment. Microsoft's capacity documentation sets the default at 80 GB plus an allowance for each licensed Essentials or Premium user. That per-user allowance is stated slightly differently in the licensing guide and on the capacity page, so confirm the current figure with your partner.
What happens when you exceed it is the useful part: "Exceeding the paid database storage limit doesn't interrupt transaction processing within the existing environments." Trading continues, administrative work stops. Over quota, you cannot create new environments or copy existing ones until you reduce data or buy more capacity, which means you cannot spin up a sandbox copy of production to test an update, precisely when you most want one. Extra capacity is sold in 1 GB and 100 GB increments, and each extra production environment brings three more sandboxes and 4 GB of shared capacity.
Two ceilings matter for growth planning: Microsoft caps an environment at 300 companies and 3 TB of compressed data.
Cloud, on-premises, subscription, and perpetual
Almost every new buyer lands on the cloud subscription, and the alternatives carry conditions worth knowing.
Business Central online is a subscription. You pay per user per month and there is nothing to buy outright. Those licenses grant non-perpetual rights, so access ends when the subscription ends.
Business Central can still be deployed on-premises or in a private hosted environment. Cloud subscribers get dual use rights, which let a properly licensed cloud user access an equivalent on-premises deployment without buying separate client access licenses. Those rights expire with the cloud subscription. On-premises has historically also been sold under a perpetual model with an annual enhancement plan, and Microsoft has been narrowing that path for new customers. If perpetual on-premises licensing matters to you, verify it against the current Microsoft Product Terms rather than treating it as available.
Add-on software: the line item that is not on your Microsoft invoice
This is the most common gap between a budget and reality, and it has nothing to do with Microsoft's pricing.
Business Central covers general business processes well. It does not ship with everything a specific industry needs. Lot traceability for food and beverage, quality management for regulated manufacturing, advanced warehouse execution, freight and rating, subscription billing, payroll, and most tax engines typically come from third-party companies that publish add-ons for Business Central. These are mature products, and for many businesses buying one is the right answer.
The budgeting point is that they are licensed separately, by the publisher, on the publisher's terms, and the number of add-on licenses you need does not have to match your Business Central user count. For a business with two or three industry-specific requirements, add-on licensing can approach or exceed the Microsoft licensing on the same deal.
That is manageable when it is on the page early, and awkward when the Microsoft subscription is approved as the software budget and the add-ons arrive as a second conversation. When you evaluate, ask which requirements the base product covers, which need an add-on, and what each one costs annually.
Knowing when Business Central is the wrong size
Buying the larger product early is expensive. Buying it late is disruptive.
Business Central Premium is the top of the line. Above it sit different products: Dynamics 365 Finance and Dynamics 365 Supply Chain Management. They are separate applications on a different platform with their own licensing, storage, and environment models, so moving between them is a new implementation rather than an upgrade.
Signals worth acting on: many legal entities with complex intercompany and consolidation requirements, multi-country statutory reporting at scale, transaction volumes pressing against the limits above, warehouse operations needing advanced execution, or manufacturing needing full production scheduling rather than production orders. For most businesses under a few hundred users, Business Central is the right size.
Two updates a year, on Microsoft's calendar
You will be updated whether you plan for it or not. Planning costs a few days a year.
Microsoft ships two major releases a year, in April and October, plus minor updates in most other months. Per Microsoft's update documentation, you get real but bounded control:
- The update period runs five calendar months from general availability, and your administrator can schedule the update for any date inside that window.
- A one-month grace period follows, during which the date can no longer be pushed out.
- Then the enforced period. During it, any extension that causes the update to fail "might be automatically uninstalled from the environment so that the update succeeds." Data belonging to an uninstalled extension is not deleted and can be recovered once a compatible version is installed.
That last point is the risk to manage, and it points back at the add-on question, since every third-party app and customization has to stay current with the release wave. The routine is modest: a month before each major release, restore production into a sandbox, run the update there, and have daily users test what would hurt most if it broke.
Buying, committing, and changing seat counts
The terms you accept at purchase decide how quickly you can shrink, and shrinking is the direction that costs money if you get it wrong.
Business Central is sold through Microsoft's Cloud Solution Provider program, which in practice means through a partner, and the licensing guide also lists direct purchase from Microsoft. A partner-led purchase generally comes with implementation and support attached. The pricing structure is the same either way.
- Term length and billing frequency are two decisions, not one. The term is how long you are committed (monthly, annual, or three-year). The billing frequency is how often you are invoiced (monthly, or once up front for the year). An annual term can still be billed monthly, so confirm both on the order. Commit annually and pay annually. The annual term carries a lower rate than month-to-month, paying up front means one invoice a year instead of 12, and your rate is fixed for the term. Month-to-month only earns its premium if you expect to leave the platform inside a year, which is not the position of a business that has just implemented an ERP.
- Adding seats. You can add seats at any point mid-term, prorated to your renewal date.
- Removing seats. Under Microsoft's new commerce cancellation policy, seat counts can only be reduced within seven days of the licenses being added, whether that was at initial purchase, at renewal, or mid-term. After that window closes, the count is fixed until the next renewal. If headcount moves seasonally, size the committed base to your trough and add above it.
- Price during the term. A price change published by Microsoft does not change what you pay mid-term. New pricing applies at renewal, transition, or new purchase, so renewal is the moment your bill can move.
Trying it before committing
Microsoft offers a free trial that runs 30 days. Beyond that, any paid subscription includes three sandbox environments, which is where meaningful evaluation happens: load a representative slice of your data, run your month-end close, and put your own people in front of it rather than watching a scripted demo. Partners can also provision Premium trial subscriptions, so you can test manufacturing and service management before committing the whole user base to the higher plan.
The gotchas, in one place
- Premium is contagious within a company. One department's manufacturing requirement lifts everyone in that company to Premium.
- Team Members cannot create sales orders or post invoices. Count only read, approve, and time-entry people in that bucket.
- Attach pricing exists and nobody volunteers it. A user already holding Dynamics 365 Sales Enterprise, Customer Service Enterprise, Customer Service Premium, or Field Service can attach Business Central Essentials at a lower rate.
- Seat reductions lock after seven days. Adding is easy. Removing waits for renewal.
- Add-on software is a separate bill. Ask what the industry requirements cost annually, from the publisher, before you sign.
- Storage overrun blocks sandboxes, not trading. You find out when you try to test an update.
- Updates arrive twice a year and eventually cannot be deferred. Extensions that block one may be uninstalled automatically in the enforced period.
- Licenses cannot be rotated between staff. Reassignment within 90 days is limited to covering an absence or an out-of-service device.
- Your external accountant is free, up to three of them. The fourth is a paid seat.
- Prices hold for your term and reset at renewal. Put the renewal date on your calendar with a month of notice.
A useful next step
The number that matters is your split: how many people need Premium because of the company they work in, how many are full Essentials users, how many are true Team Members, how many shared stations could be device licenses, and who already holds another Dynamics 365 application and could carry an attach license instead.