Business Central Licensing Guide

The whole Business Central licensing map on one page

Most Business Central pricing pages stop at two numbers—$80 for Essentials and $110 for Premium—and leave buyers to discover the rest of the licensing model at renewal time. That is a mistake, because the per-seat price is only one layer of a five-layer model. Business Central is sold through five distinct license types (Essentials, Premium, Team Members, Device, and External Accountant), wrapped by a read-only Microsoft 365 entitlement, delivered across production and sandbox environments, and bounded by a shared database-storage quota that Microsoft reset on 1 November 2025. Getting any one of those layers wrong is where the avoidable cost and the compliance risk live.

The model is simpler than it first appears once you separate two questions that buyers routinely conflate. The first question is functional scope: which Business Central capability a named user is entitled to use, controlled by the license SKU assigned to that user. The second question is tenant capacity: how many environments and how much shared storage the whole organization gets, controlled by how many and which licenses the tenant holds. Licensing decisions are really two independent decisions - one per person (which seat) and one per tenant (how much floor space) - and this guide treats them separately so you can size each correctly.

The table below is the single reference for the rest of the page. It lists every Business Central license type, its verified 2026 list price (post–1 November 2025), what it entitles the holder to do, and the role it is built for. Every number is sourced from Microsoft’s pricing page, the May 2025 Microsoft Dynamics 365 Blog pricing announcement, Partner Center product-price updates, and Microsoft Learn capacity and licensing documentation—cited in the sources section. Structural rules (entitlement enforcement, environment quotas, storage allowances, reassignment limits, company caps) are unpacked in the sections that follow.

The five Business Central license types and what each unlocks

Business Central offers five paid license types - Essentials, Premium, Team Members, Device, and External Accountant - all purchased through the Cloud Solution Provider (CSP) channel. Microsoft's licensing documentation is explicit that CSP is the only acquisition channel for Business Central online; there is no direct self-serve purchase of production licenses from Microsoft, which is why every deal runs through a partner. A sixth, non-paid entitlement - read-only Business Central access through a qualifying Microsoft 365 license inside Teams - rounds out the access model for knowledge workers who never need to write data.

Essentials and Premium are the two full-user tiers, and the difference between them is functional, not financial. Essentials is the comprehensive common-business footprint: general ledger, accounts payable and receivable, cash flow, fixed assets, budgets, sales and marketing, purchasing, inventory, supply chain planning, project and warehouse management, workflows, analytics, Copilot, and Power Platform integration. Premium adds exactly two module families on top - Manufacturing (production orders, routings, machine centers, capacity) and Service Management (service orders, items, contracts, dispatching). The feature-by-feature delta and the upgrade decision are covered in our Essentials-versus-Premium guide; for licensing purposes the key point is that the same tenant, database, and application run either tier, and the license assigned to each named user controls what that user can do.

The remaining three seats exist to shape cost and fit access to reality. Team Members at $8 gives light users - people who read reports, approve workflows, enter time, or update personal records - a seat that costs a fraction of a full license. The Device license at $45 per device licenses a physical terminal rather than a person, so a warehouse running 60 shift workers through 12 scanners pays for 12 devices instead of 60 named users. And the External Accountant license, free up to three per tenant, lets an outside bookkeeping or audit firm work in the live tenant without burning a paid seat. Together these three are where a well-built Business Central license mix separates itself from a naive 'full license for everyone' default.

• →Essentials ($80) and Premium ($110) are the two full-user tiers; Premium adds Manufacturing and Service Management to the full Essentials scope.
• →Team Members ($8) covers light read-and-approve users; reading Business Central data is not restricted by the license.
• →Device ($45/device) licenses a shared terminal, not a person, for shift-based warehouse, shop-floor, and POS access.
• →External Accountant is free up to three per tenant, available with both Essentials and Premium, and does not consume a paid seat.
• →Microsoft 365 users get read-only Business Central access inside Teams when the tenant already holds BC licenses - no separate BC seat required.

Per-named-user licensing, CSP, and the entitlement enforcement model

Business Central is licensed per named user, and at least one full Essentials or Premium license is required per tenant - you cannot run a production tenant on Team Members or Device seats alone. Licenses are assigned in the Microsoft 365 Admin Center and then synced to Business Central, where the application reads the user's service plan from Microsoft Entra ID (formerly Azure Active Directory) and loads the matching entitlements as the user's license permissions. This is a critical mechanic to understand because it inverts the permission model most administrators assume.

Behind the scenes, Business Central's Entitlements table defines which application objects each license permits, entitlements are grouped into Entitlement Sets, and each entitlement set maps to one of the Microsoft Entra ID service plans. When a user signs in, the service takes the intersection of the entitlements associated with their service plan and the permissions defined for them - and entitlements always take priority. Microsoft's documentation states the consequence plainly: even if an administrator grants a user SUPER permissions, if that user holds only a Team Members license, they can still access only the objects defined by the Team Member entitlements. Permissions cannot widen access beyond what the license grants.

Two practical implications follow. First, the Effective Permissions page (accessible from the User card in Business Central) is the authoritative way to see what a user can actually do, because it shows the intersection of license entitlements and assigned permission sets - not the permission sets alone. Second, because entitlements flow from the Entra ID service plan, license changes propagate the next time the user signs in after a sync; there is no in-application toggle that overrides the licensed scope. This is also why Business Central online does not use the classic Dynamics NAV .flf license files - the entire entitlement model is driven by the cloud identity and service plan.

• →At least one full Essentials or Premium license is required per tenant; production cannot run on Team Members or Device seats alone.
• →Entitlements flow from the Microsoft Entra ID service plan assigned to the user and are enforced on sign-in after sync.
• →Entitlements override permissions: a SUPER permission set cannot grant access beyond what the user's license entitles.
• →Use the Effective Permissions page to see the true intersection of license entitlements and assigned permission sets.
• →Business Central online uses Entra ID service plans, not the legacy Dynamics NAV .flf license files.

Team Members, Device, and External Accountant: the three seats that shape the bill

If Essentials and Premium are the floor of a Business Central license mix, the three cost-shaping seats are the levers that determine whether the bill is defensible. Team Members at $8 per user per month is built for people whose jobs are not tied to a specific operational function but who still need basic line-of-business access - executives reading dashboards, managers approving workflows, staff entering timesheets or updating personal records. Microsoft's Team Members documentation is clear that reading Dynamics 365 data is not restricted by the license; the restriction is on running full operational processes. For the customer-engagement apps, access is delivered through designated apps (Customer Service Team Member, Sales Team Member, Project Resource Hub), and the Team Member app can be customized up to a 15-entity cap.

The Device license solves a fundamentally different problem: many shift workers sharing a small number of physical terminals. At $45 per device per month (raised from $40 on 1 November 2025), it licenses the device rather than the person, so a three-shift warehouse running 60 workers through 12 scanners licenses 12 devices. Microsoft’s documentation specifies that up to the purchased number of users assigned to the “Dynamics 365 Business Central Device Users” security group can sign in simultaneously through the covered devices, and that device users are concurrent—they can even run scheduled job-queue tasks in background sessions. One hard limitation: a device user cannot be the first user to sign in to a new tenant; an Administrator, Full User, or External Accountant must complete initial setup first. Practical setup detail partners miss: the group name must be spelled in English exactly as “Dynamics 365 Business Central Device Users” (no extra spaces), and members of that group do not need a separate Business Central named-user license. The worker-to-device ratio rule of thumb is straightforward—at three or more workers per device across shifts, device licensing beats named-user licensing.

The External Accountant license closes the last gap. Microsoft's accountant documentation states that both Premium and Essentials Business Central licenses let you procure up to three External Accountant licenses per customer tenant, and that the licenses are free - you simply need to procure them through your partner so they appear on the subscription. An outside bookkeeper or audit firm gets full Essentials or Premium scope without consuming a paid internal seat, which matters at year-end and audit time when external access peaks. Rounding out the model, qualifying Microsoft 365 licenses grant read-only Business Central access inside Microsoft Teams when the organization already holds Business Central licenses - a no-cost way to expose records to knowledge workers who only need to look things up.

Environments: what is included and when you pay for more

Business Central environments are the second licensing dimension, and they are separate from per-user licensing. Microsoft's capacity documentation states that every Business Central customer with Premium or Essentials subscriptions can use one production environment and three sandbox environments at no extra charge. These environments can be created in any country or region where the Business Central service is available, which is how organizations handle multi-country operations, data residency, and parallel development-and-test streams without standing up separate tenants.

When one production and three sandbox environments are not enough, additional production environments are purchased through the CSP partner. Each additional production environment you buy includes three more sandbox environments and increases the tenant's shared database storage capacity by 4 GB. That 4 GB uplift is small but meaningful - it means environment expansion and storage expansion are coupled, so modeling both together avoids surprise quota exhaustion. The Business Central administration center is where administrators create, copy, and restore environments, and the environment quota is enforced whenever you try to create, copy, or restore.

An important licensing subtlety governs user-to-environment access. By default, every user created in the Microsoft 365 Admin Center and assigned a Business Central license gets access to all Business Central environments - sandbox and production - under the same license, acting within the scope of their license in each environment. A single named-user license is not consumed per environment; it travels with the user across the tenant. Administrators who need to restrict a user to a specific environment do so by changing that user's permissions or removing their access within the target environment - not by buying an additional license. This is why environment planning is a permissions-and-topology exercise, not a per-environment licensing exercise.

Database storage: the 80 GB base, Nov 2025 per-user allowances, and overage

Database storage is the third licensing dimension, and it is the one most often missed in budgeting because it is shared, not per-environment. Microsoft’s capacity documentation states that Business Central customers can use up to 80 GB of database storage plus an allowance per licensed user or device, and that this capacity is shared—meaning the sum of usage across all environments in the tenant must not exceed the limit. On top of the 80 GB base, the tenant earns extra storage based on the number and type of licenses it holds.

Effective 1 November 2025, Microsoft raised both list prices and the included per-license storage allowances in the same adjustment—the first Business Central price increase in more than five years. Per Microsoft’s official pricing announcement and Partner Center product-price table, the post–November 2025 per-license storage is 5 GB for each Premium license (was 3 GB), 3 GB for each Essentials license (was 2 GB), and 1.5 GB for each Device license (was 1 GB). Partner Sandbox remains a separate partner entitlement path. A 20-user Essentials tenant therefore starts with 80 GB plus 60 GB (20 × 3 GB) of shared database capacity, or 140 GB total across all environments—model that figure against your real data footprint, because companies, historical transactions, and document attachments grow storage faster than most teams expect.

What happens when you exceed the quota is the part that reassures finance teams. Microsoft’s documentation is explicit that exceeding the paid database storage limit does not interrupt transaction processing in existing environments—those environments remain accessible and continue to operate, and you are not automatically charged for the overage. What you lose is the ability to create or copy environments until you either reduce storage to fit the quota or purchase additional capacity. Additional capacity is bought through the CSP partner via named add-ons: Dynamics 365 Business Central Database Capacity (1 GB), Database Capacity (100 GB), and a lower-priced Database Capacity Overage (1 GB) available only to customers who have purchased at least one 100 GB add-on, plus a Business Central Additional Environment Add-on. Two storage-hygiene notes worth flagging: the Tenant Media and Tenant Media Thumbnails tables count toward database capacity, and when you uninstall an extension you must choose to delete its data or that orphaned data continues to consume your quota.

The 1 November 2025 price and storage reset (what changed)

On 6 May 2025 Microsoft announced the first Dynamics 365 Business Central list-price increase in more than five years, effective 1 November 2025 for new purchases and at next renewal for existing tenants. The same announcement raised included per-license database storage, so the higher seat price is paired with more capacity—not a pure takeaway. For buyers sizing a 2026 estate, use the post–November numbers as the default model unless a multi-year agreement still locks pre-adjustment rates until renewal.

Microsoft’s published before/after table (repeated in Partner Center September 2025 announcements) is the clean reference: Essentials moved from $70 to $80 per user per month with storage rising from 2 GB to 3 GB per license; Premium moved from $100 to $110 with storage rising from 3 GB to 5 GB; Device moved from $40 to $45 with storage rising from 1 GB to 1.5 GB. Team Members remained $8 on Microsoft’s public pricing page. The 80 GB tenant base, free 1 production + 3 sandbox environment entitlement, and External Accountant free seats were not re-priced in that announcement.

Two planning implications matter more than the headline dollars. First, storage modeling for renewals after November 2025 should use the higher per-license allowances—many tenants that were near capacity under the old table suddenly have headroom, while high-attachment industries still need media-table hygiene. Second, existing customers typically absorb the new list price at the next renewal rather than mid-term, so a three-year commitment made before the change can still price-lock prior rates until that term ends—confirm with your CSP, not from list pages alone.

Multiple companies, multi-country, and the operational limits

A single Business Central tenant can host multiple companies, which is how groups run several legal entities or divisions from one subscription rather than one tenant per entity. Company creation is an in-application construct: the same tenant, database, and license pool serves every company, and a named user's license entitles them across the tenant - administrators then control which company each user can reach through permission sets and security groups. This is the licensing foundation for multi-entity consolidation, intercompany transactions, and shared master data, all without multiplying the license count by the number of companies.

For organizations that need stronger isolation - separate data residency, independent update cycles, or firewalled legal entities - the lever is additional environments rather than additional tenants. Because each environment can sit in a different country or region and host its own set of companies, a multi-country rollout typically maps countries to environments within one tenant, with each additional production environment purchased through CSP. The trade-off is administrative: more environments mean more update management and more storage consumption against the shared quota, but no per-environment licensing beyond the environment add-on itself.

There is one ceiling to plan around. Microsoft’s operational-limits documentation sets a hard maximum of 300 companies per environment (the company limit introduced with 2023 release wave 1 and still in force). Capacity docs also note the tenant-level company-growth constraint that has applied since 2023 release wave 2. For groups planning aggressive multi-entity growth, that 300-company-per-environment cap is the constraint that eventually forces a second environment or a second tenant—not the per-user license count. Modeling company growth against the operational limit early prevents a mid-rollout discovery that the architecture cannot absorb the next acquisition.

• →One tenant can host multiple companies; a named-user license entitles the user across the tenant, with per-company access controlled by permissions.
• →Multi-country and data-residency needs are met with additional environments in different regions, not separate licenses per country.
• →Each additional production environment (via CSP) bundles three more sandboxes and 4 GB of shared storage.
• →Hard operational limit: 300 companies per environment (Microsoft Learn operational limits)—plan multi-entity growth against this ceiling.
• →Firewalled legal entities or independent update cycles are the typical trigger for adding environments rather than companies.

Trials, evaluation subscriptions, and converting to paid

Business Central offers a free 30-day trial that lets a prospect explore the full product without a license commitment. Beyond the standard trial, Microsoft provides a self-service evaluation subscription - sometimes called the viral trial - that comes with 10,000 licenses and is intended for nonproduction companies, so partners can let prospects and customers explore Business Central in demonstration and sandbox scenarios without touching a production tenant. These evaluation paths are how most discovery happens before any paid license is procured.

Converting a 30-day trial company into a live production tenant has one rule that catches teams off guard. Microsoft's licensing documentation states that for businesses converting a trial into their actual production company, the first user who signs in to Business Central after the license has been applied to the tenant must be a user with that license assigned. When a licensed user signs in first, the 30-day trial ends and trial-related notifications disappear, and the organization can begin real work. If an administrator is the first to sign in after the license is applied, the trial continues until it expires - a quiet trap that leaves a tenant nominally licensed but still behaving as a trial.

Entitlement enforcement has also tightened in sandboxes over time. In versions before 2020 release wave 2, entitlements were enforced only in production, which let prospective customers explore Premium functionality in a sandbox without purchasing a Premium license. Since 2020 release wave 2, license checks for entitlements are enforced in sandbox environments too, so the free Premium exploration path now runs through the evaluation subscription or a Business Central Premium trial available through the CSP program rather than through an under-licensed sandbox. Plan evaluation around these sanctioned subscription types to avoid hitting entitlement errors mid-proof-of-concept.

• →A free 30-day trial gives full product access without a license commitment.
• →The self-service evaluation (viral) subscription includes 10,000 licenses and is for nonproduction companies and demos.
• →To convert a trial to production, the first sign-in after the license is applied must be by a licensed user - not an administrator - or the trial keeps running.
• →Since 2020 release wave 2, entitlements are enforced in sandbox environments, not just production.
• →Explore Premium scope through the evaluation subscription or a CSP Premium trial rather than an under-licensed sandbox.

Attach licensing and where Business Central sits in the Dynamics 365 family

Business Central does not license in isolation when an organization also runs customer-engagement apps. Under the Dynamics 365 base-plus-attach model, the first qualifying application assigned to a named user is the base license at full price, and additional qualifying applications attach at a discounted rate. Business Central Essentials at $80 can serve as a base license, and CRM apps such as Sales Professional or Customer Service Professional can attach to it at the discounted $20 rate rather than as a second full seat. This is how a Business Central user who also needs light CRM avoids paying for two full licenses.

Business Central Premium sits at the ceiling of the Business Central family and does not have an attach tier above it, but a Premium user can still act as the base for CRM attaches where the user needs both ERP and sales or service access. The attach mechanic is distinct from anything inside Business Central itself - it governs how Business Central combines with the broader Dynamics 365 suite - and the detailed attach pricing ladder, Team Members enforcement across the suite, and the base-plus-attach rules are covered in our Dynamics 365 attach and Team Member licensing guide. For most small and medium-sized businesses, the relevant decision is narrower: whether a given BC user also needs a CRM seat, and if so, whether that seat should be an attach or a Team Members license.

It is worth separating Business Central's licensing from the Finance and Operations (F&O) licensing model, because the two are often confused. Business Central is per-named-user at $80-$110 with a fixed feature scope per tier; Finance and Supply Chain Management are per-named-user at $210 each with the attach layer stacking them. Organizations do not license 'Business Central' and 'Finance and Operations' together as one estate - they choose one ERP floor. When that floor is Business Central, the licensing map on this page applies in full; our Business Central versus Finance and Operations comparison and the broader Business Central pricing guide cover the floor decision and the total-cost math that sits on top of it.

Copilot is part of the full-user license for embedded Business Central experiences, but agentic features are metered separately. Microsoft’s Business Central pricing page is explicit that Sales Order Agent and Payables Agent require Copilot Credits sold separately—either pay-as-you-go (no upfront commitment; billed for actual monthly consumption against an Azure-linked environment) or prepaid Copilot Credit capacity packs. Public Copilot Studio pricing lists capacity packs at 25,000 Copilot Credits for $200 per pack per month, with pay-as-you-go available as an alternative meter; partner and Microsoft documentation commonly cite about $0.01 per Copilot Credit under the pay-as-you-go path. Receipt-to-expense style agent actions can consume fixed credit amounts per upload (for example, 50 Copilot Credits per uploaded receipt in Microsoft’s consumption-billing guidance), so model agent volume before you treat “Copilot included” as free automation at scale. Embedded Copilot chat and drafting inside Business Central remain part of Essentials and Premium; the agents are the metered layer.

Three license-mix scenarios you can copy into a budget

List prices only become useful when they map to roles. The three scenarios below use 2026 USD list pricing (post–November 2025) on annual billing and ignore taxes, partner discounts, ISV apps, and implementation. They are starting points for a board pack—not quotes. Swap Team Members for full seats only where people post transactions or run operational processes every day.

Scenario A is a distribution or professional-services back office on Essentials. Scenario B is discrete manufacturing or field-service operations that need Premium’s manufacturing and service management modules plus shop-floor Device seats. Scenario C is a finance-heavy group that maximizes free External Accountant seats and Microsoft 365 read-only Teams access for knowledge workers. In every case, storage is 80 GB plus the per-license stack—and agent volume for Sales Order Agent or Payables Agent is budgeted as Copilot Credits, not as more named users.

• →Never budget only full seats: every $8 Team Member that replaces an $80 Essentials seat saves ~$864/year at list.
• →Device math: 12 scanners × $45 = $540/month versus 60 named Essentials seats at 60 × $80 = $4,800/month—about $4,260/month saved when the floor is truly shared concurrent access.
• →Premium is the right default when anyone needs production orders, routings, capacity, or service/dispatch—not when you hope manufacturing will appear later.
• →External Accountant (up to 3 free) and M365 read-only in Teams are free layers; procure External Accountant SKUs so they appear on the subscription.
• →Add Copilot Credits only if you will run Sales Order Agent, Payables Agent, or other metered agents—embedded Copilot in Essentials/Premium is already included.

Assembling a compliant license mix (and the mistakes that inflate it)

A defensible Business Central license mix is the product of four decisions made against the real org chart: which users are full operational users (Essentials or Premium), which are light consumers (Team Members), which access the system through shared terminals (Device), and which are external finance professionals (External Accountant). The most common mistake is defaulting every employee to a full license out of caution, which converts what should be $8 Team Members seats into $80 or $110 seats; on a 50-user organization where 20 users are genuinely light, that mistake costs roughly $17,280–$24,480 per year at list price ($72–$102 extra per light user per month × 20 × 12). The second most common mistake is under-using the Device license on shift-based floors, licensing 60 named workers when 12 shared terminals would do—and after the November 2025 reset, Device list price is $45/device/month with 1.5 GB storage each, still far cheaper than full seats for concurrent floors.

Compliance is the other half of a defensible mix, and the rule that catches most teams is license reassignment. Microsoft's Online Services Terms do not allow temporary assignment of a license from one user to another; specifically, a license cannot be reassigned on a short-term basis - meaning within 90 days of the latest assignment - except to cover a user's absence or the unavailability of an out-of-service device. Reassignment for any other purpose must be permanent. The practical consequence is that bouncing a single license between shift workers to dodge per-user licensing is a terms violation; the sanctioned pattern for shift work is the Device license, which is purpose-built for concurrent multi-user access through a covered terminal.

Finally, a Team Members conformance review before every renewal prevents the quiet drift that turns a saving into a true-up. Microsoft exposes a Non-conformant usage by users with Team Member license report in the Power Platform admin center, under the Dataverse analytics area, downloadable and filterable by environment and date, that flags where $8 users are behaving like full users. Usage drifts over time - a Team Member who started approving expenses and ends up owning a queue of operational tasks has crossed the use-rights line - and a tenant with widespread non-conformance is the tenant that gets asked, at renewal, to backfill the under-licensed seats. Right-sizing the Team Members tier against the conformance report is the highest-ROI license-mix work most organizations never do.

Frequently asked questions