Business Central Team Member vs Essential License: The Exact Table Limits That Trigger Non-Compliance

The CFO sees $70/user/month and $8/user/month on the pricing sheet. The directive is immediate: put everyone on the $8 license unless they absolutely need the $70 one. Two years later, Microsoft's EA telemetry flags 50 Team Member users who have been posting sales orders. The true-up penalty wipes out every dollar saved.

Business Central Team Member licenses are not cheap loopholes for operational staff. They are highly restricted, read-heavy licenses with hardcoded write limitations enforced by Microsoft's backend telemetry. If you assign a Team Member license to an operational employee, they will either be unable to do their job, or your partner will customise permission sets to force it to work — instantly pushing you out of compliance.

Team Member

$8/user/mo

What they can do

Read anything their permissions allow
Approve or reject workflow tasks
Enter personal time and expenses
Update existing customer/vendor records
Create quotes and purchase requisitions

Essential

$70/user/mo

Required when users

Create new Customer, Vendor, or Item records
Post Sales Orders or Purchase Orders
Generate or post GL journals
Process inventory receipts or shipments
Execute warehouse picks or put-aways

The Hard Line — What Triggers an Essential License

The moment a user crosses from reading and updating into creating and posting, the Team Member license becomes invalid. Microsoft's backend telemetry tracks the user's Entra ID against table inserts — specifically Sales Header, G/L Entry, Purchase Header, and inventory transaction tables. When the EA audit hits, they flag every user whose Entra ID appears in insert operations on these tables while holding a Team Member license.

⚠️ When a partner modifies standard permission sets to allow an $8 user to post a sales order, the system might technically process the transaction. Microsoft's backend telemetry still records the table insert against that user's Entra ID — and bills accordingly at EA renewal.

The 3 Custom Objects Write Rule

The most misunderstood aspect of the Team Member license involves ISV add-ons and custom development. Companies frequently build custom tables in AL code assuming that because the table is custom, standard licensing rules don't apply. Microsoft anticipated this.

3
Maximum Custom Objects a Team Member Can Write To
A Team Member license allows write access to a maximum of 3 custom tables (object range 50000+). Writing to a 4th custom table requires an Essential license for every user performing that action. Read access to custom tables is unlimited.

If your partner deploys an extension that requires users to write data into four custom tables to process an internal ticketing or approval workflow, the Team Member license is instantly invalidated for every user interacting with that fourth table.

How to Audit Your Environment — License Configuration

You cannot rely on guesswork. Business Central provides a direct mechanism to audit user activity against their assigned license tier:

Log into BC with a Super user account → open Tell Me search (Alt+Q) → type License Configuration
This page maps Entra ID licenses (Essential, Premium, Team Member) to the specific BC permission sets legally allowed for that tier
If you have custom permission sets assigned to Team Members, verify they do not contain Insert or Modify grants on restricted tables like G/L Entry or Sales Header
Navigate to User Information or Effective Permissions pages — cross-reference users holding Team Member licenses against the specific tables they are modifying
Look specifically at the 3 Custom Objects rule — if a Team Member has Insert or Modify access to more than three custom tables in the 50000+ object range, you have a compliance failure

The EA renewal audit is not a negotiation. Microsoft uses automated telemetry to identify which users are executing which operations. If operational staff are masked behind Team Member licenses, the financial penalties will be severe and include back-pay at list price.

The Right Approach to License Assignment

Before assigning any license in BC, map the user's actual daily tasks against the Team Member boundary. A Finance Director who only runs reports and approves payment journals is a legitimate Team Member. An AP Clerk who creates vendor invoices and posts payment journals is not — regardless of what the partner's permission set technically allows them to do.

The question is not "can the system technically process this transaction?" — the question is "is this user legally licensed to initiate this transaction?" Those are two completely different standards.

A complete Business Central license governance review — identifying Team Member violations, custom object write rule breaches, and permission set compliance gaps — delivered within 48 hours. No system access required.