Best practice guide

Business Central Licence Types: What Each User Can Actually Do

Business Central cost is usually estimated by headcount, but the licence type determines what each user can do — and entitlements override permissions, so an administrator cannot grant access a licence does not carry. The distinctions that matter before a quote.

Most Business Central cost estimates start with headcount. That is the wrong starting point: the licence type assigned to each person determines what they can do, and the difference is enforced by the platform rather than by configuration.

Three paid licence types, one purchase route

Microsoft's licensing documentation for Business Central lists the paid licences for business users as Essentials, Premium and Team Member, and states that Business Central licences can only be purchased through CSP.

That last point shapes the commercial conversation: licences are bought through a partner in the Cloud Solution Provider programme, so licensing and implementation are usually discussed together rather than separately.

Entitlements override permissions — the rule that surprises administrators

This is the single most important licensing mechanic, and it is regularly misunderstood.

Microsoft documents that when a user signs in, the service applies the intersection of the entitlements associated with their licence and the permissions defined for that user, and that entitlements always have higher priority over permissions. The documentation gives the decisive example: even if an administrator grants a user SUPER permissions, a user holding a Team Member licence can still only access the objects defined by the Team Member entitlements.

The practical consequence is that a permissions problem and a licensing problem look identical to the person experiencing them. Where a user cannot reach a page, check the licence before rebuilding permission sets — no amount of permission configuration will grant access the licence does not carry.

Essentials and Premium are not interchangeable at company level

The distinction is not only about which features a person can use. Microsoft's guidance on creating users according to licences records that:

  • a user with a Premium licence can sign into a company whose Experience is set to Essentials, but cannot use Premium features there; and
  • a user with an Essentials licence cannot sign in at all to a company whose Experience is set to Premium.

For a group running several companies in one environment, the Experience setting on each company therefore interacts directly with licence assignment. A company switched to Premium locks out every Essentials user in that company — worth establishing before the switch, not after.

Microsoft 365 licences give read access in Teams, not a licence substitute

Microsoft documents that a person accessing Business Central with a Microsoft 365 licence is entitled to read, but not write, Business Central data through a simplified interface in Microsoft Teams.

This is useful for colleagues who need to look something up rather than transact — but it is explicitly read-only, and it is described as an addition to Premium or Essentials plans rather than a replacement for them. Access also depends on the specific Microsoft 365 or Office 365 plan held; Microsoft publishes the supported plan list.

Related licensing points worth confirming early

  • Power BI. Microsoft notes that users accessing Power BI reports containing Business Central data must also hold a paid Business Central licence — Essentials, Premium or Team Member.
  • Environments. Premium and Essentials subscriptions include a production environment and sandbox environments; confirm the current entitlement before planning a multi-environment setup.
  • Security groups. Microsoft records that user groups have been replaced by security groups, so guidance written against the older model may not match the current interface.

What to establish before requesting a quote

  1. List users by what they actually need to do, not by department.
  2. Identify who only needs to read or approve — those may be Team Member or, in Teams, Microsoft 365 read access.
  3. Confirm the Experience setting intended for each company, and check it against the licences held.
  4. Identify Power BI consumers and confirm their Business Central licence position.
  5. Confirm current licence terms and prices with a CSP partner — published terms change, and this article is not a price list.

Where the wider implementation scope is the question rather than licensing alone, that is addressed under SCSB's Business Central implementation service.

General-information limitation

This article is general information about Microsoft licensing concepts, not licensing, legal or pricing advice for a particular organisation. It does not determine which licences an organisation requires, what they cost, or what any agreement permits. Licence terms, entitlements and supported plans are set by Microsoft and change over time. Confirm the current position against Microsoft's own published material and your CSP partner before purchase.

To discuss your requirements, contact SCSB.

Microsoft product references source checked: 25 July 2026.

Microsoft, Microsoft 365, Microsoft Teams, Microsoft Entra ID, Power BI and Dynamics 365 Business Central are trademarks of the Microsoft group of companies.

Related insights

Ready to modernise your work?