Team Members licence in a Sales deployment

What it does

Team Members is a low-cost named user subscription for people who need to read Dynamics 365 data and do a small set of light tasks, without needing a full Sales licence. In a Sales deployment it entitles the user to the Sales Team Member app and nothing heavier.

Key facts

Team Members is a named user subscription, not a device or concurrent licence. One person, one seat.
There are three designated Team Member apps across customer engagement: Sales Team Member, Customer Service Team Member and Project Resource Hub. Team Member users are entitled to these and not to Sales Hub, Customer Service Hub or custom apps.
The Sales Team Member app is preinstalled in any environment that has Sales Hub. You do not install it separately.
In the Sales Team Member app a user can work with contacts, view accounts, view leads and opportunities linked to accounts and contacts, and add notes and tasks. That is the shape of the entitlement.
A Team Member app is limited to 15 tables. They can be Dataverse core tables, Microsoft-published tables or custom tables — the limit is on the app, not on the type of table.
Reading data is not restricted by licence enforcement. A Team Member can read Dynamics 365 data beyond those 15 tables through subgrids, dashboards and lookups. Create, update and delete are governed by the use rights in the Licensing Guide.
Enforcement operates at app level, not privilege level. Microsoft blocks access to apps the licence doesn't cover; it does not individually police "can this user update an account".
Users hitting the block see an "Invalid License" message telling them to contact their administrator. Bookmarked URLs to restricted apps stop working once enforcement applies.
Administrator, customiser and maker roles are exempt from Team Member enforcement.
The Sales Team Member security role governs the app. It can be cloned and customised, but Microsoft's expectation is that you keep it aligned to the use rights in the Licensing Guide.
Two reports in the Power Platform admin center under Dataverse analytics help you police this: the Team Member conformance report and "Non-conformant usage by users with Team Member license". Microsoft describes them as general guidance, not a definitive enforcement tool.
Team Members carries no per-user Dataverse database, file or log capacity entitlement. Adding a hundred Team Member seats adds nothing to your storage pool.
Users on a full Sales licence can use Team Member apps freely. The restriction runs one way.

When to use / skip

Team Members is the right answer for people who orbit the sales process without running it: finance chasing an order, delivery consultants who want to see what was sold, service desk staff who need customer context. If the person's job is to look things up and occasionally add a note or task, this is the licence.

It is the wrong answer, and gets sold as the right one depressingly often, for anyone who edits opportunities, works leads, manages quotes, or lives in a custom app the client has built. The 15-table app limit and the app-level enforcement will catch up with that eventually, and the client's first sight of the problem is usually a compliance conversation with Microsoft rather than a technical error.

Also skip it where the client's plan depends on granting Team Members access to a custom model-driven app. That is not what the licence covers, regardless of what security roles you configure.

Configuration decisions

Which 15 tables go into the Team Member app. This is the single design decision that determines whether the licence works for your population.
Whether you customise the stock Sales Team Member app or build a Team Member app of your own within the same entitlement.
Whether to clone the Sales Team Member security role. Cloning is fine; widening it beyond the use rights is where you create the exposure.
Which personas genuinely sit at Team Member level versus which are being pushed there on budget grounds and will need upgrading within a year.
Whether you run the conformance reports as a regular operational check, and who reviews them.
Whether Team Member users need read access to tables outside the app — through subgrids and lookups that is allowed, and it can materially widen what the licence delivers.

Gotchas

Security roles do not define the licence. You can build a Team Member role that permits far more than the licence allows, the platform will not stop you, and the client is still non-compliant.
The 15-table cap applies to the app's table list, not to what the user can see. People miscount because subgrid and lookup access doesn't count towards it — that is a genuine allowance, not a loophole to build on.
Team Members grants no storage capacity. Clients who size capacity from headcount get this wrong every time.
Admin, customiser and maker exemptions mean your testing may not reproduce what a real Team Member user experiences. Test with an actual Team Member licence and a plain role.
Enforcement has been rolled out gradually rather than all at once. An environment that works today is not proof of compliance.
The conformance reports are guidance, not a clean bill of health. Passing them is not the same as being licensed correctly.

Consultant notes

Make the client name every Team Member persona explicitly and describe what each one does. Vague answers here become licence true-up costs later.
Demo the Sales Team Member app to the client's stakeholders early. It is deliberately narrow, and seeing it stops the "can we just give everyone Team Members" conversation.
Push back hard on Team Members for anyone who edits opportunities or works a pipeline. That is a Sales licence, and saying so early is cheaper than saying it in year two.
Test with a real Team Member licence before go-live, on a role that isn't an admin role. It is the only way to see what those users actually get.
Set the conformance report up as a monthly check with a named owner, and tell the client it is theirs to run after handover.

Worth another look if Microsoft tightens enforcement or changes the 15-table limit.