Dynamics 365 Sales licence tiers

What it does

Dynamics 365 Sales is sold as four named-user subscriptions: Sales Professional, Sales Enterprise, Sales Premium, and Microsoft Relationship Sales (Sales Enterprise bundled with LinkedIn Sales Navigator Enterprise). The tier a user holds decides which Sales app they can open and which capabilities the platform will let them turn on.

Key facts

The four SKUs are Sales Professional, Sales Enterprise, Sales Premium and Microsoft Relationship Sales. There is no "Sales Basic" and no per-app Sales licence — Power Apps per-app is a different thing entirely and does not entitle Sales functionality.
Each tier maps to an app: Sales Professional users get the Sales Professional app, Enterprise and above get Sales Hub. Both apps can be visible in the same environment, but a user may only use the one their licence covers.
Sales Enterprise, Sales Premium and Microsoft Relationship Sales include the basic features of Sales agent. The premium Sales agent features need a separate Microsoft 365 Copilot licence on top — that is a Microsoft 365 purchase, not a Dynamics one.
Sales Premium is not a different application. It is Sales Enterprise with the digital selling capabilities uncapped plus the advanced relationship intelligence that reads Exchange data as well as Dataverse.
Microsoft Relationship Sales is a bundle, not a tier above Premium. It pairs Sales Enterprise with LinkedIn Sales Navigator Enterprise seats and is bought as one line.
Three purchase routes: direct from Microsoft, through the Microsoft 365 admin center under Billing > Purchase services, or through a partner (including volume licensing). Some SKUs still require a conversation with a Microsoft rep rather than a self-serve buy button.
Licences are assigned per user in the Microsoft 365 admin center. Assignment alone does not grant application access — a security role is still required inside the environment.
Certain Sales licences carry a monthly Copilot Studio credit allocation. Credits are not cumulative and reset each month; the quantities live in the Dynamics 365 Licensing Guide, not on Learn.
Microsoft moves the feature boundary between tiers between release waves. Treat any tier comparison older than about six months as unreliable and re-read the current Licensing Guide.

When to use / skip

Sales Professional is the right answer far less often than clients hope. It suits a small sales team running a straightforward lead-to-opportunity-to-quote process with light customisation and no appetite for the sales accelerator, forecasting depth, or the AI capabilities. If the organisation already runs Customer Service Enterprise, or has any serious integration or automation ambition, the Professional price gap tends to evaporate once you hit its entitlement ceiling and have to migrate everyone.

Sales Enterprise is the default. It covers the full customisation surface, the whole Sales table set, and gives you the digital selling features at a capped monthly volume — which for a lot of teams is enough to prove value before anyone commits to Premium.

Premium is worth it when the capped capacities genuinely bite (a large team running sequences at scale, or scoring high lead volumes) or when advanced relationship intelligence over Exchange data is a real requirement rather than a demo. Buy it for the users who need it, not the whole org. Relationship Sales only makes sense where the team already lives in Sales Navigator; if they don't, you are buying LinkedIn seats that go unused.

Configuration decisions

Which tier each persona gets. Split by behaviour, not job title — inside sales running sequences may need Premium while account managers sit fine on Enterprise.
Whether to mix tiers in one environment. It works, and it is usually the cheaper answer, but you then need feature gating in the UI so unlicensed users aren't shown things they can't use.
Whether Sales Professional is a starting point or a destination. If it is a starting point, plan the migration cost now rather than discovering it in year two.
Whether Microsoft 365 Copilot seats are in scope, and who owns that budget line — it usually sits with the M365 team, not the CRM programme.
Where Copilot Studio credits get allocated. Left at tenant level they can be consumed by unrelated agents; pin them to the Sales environment if Sales is meant to have them.
Whether Team Member licences cover your peripheral users, and which of them genuinely only need read plus notes and tasks.

Gotchas

Assigning a licence does not make the app appear. Users need a security role too, and the classic support ticket is "I've got Sales Enterprise and I can't see anything".
A user with a Sales Professional licence can see the Sales Hub tile in an environment that has both apps installed and will get an access error on opening it. Hide the app they aren't entitled to rather than explaining it repeatedly.
Buying Premium for the tenant does not upgrade anyone. Licences are per user, and mixed-tier environments are common enough that admins forget to reassign.
The Licensing Guide, not Microsoft Learn, is the contractual document. Learn pages describe what a feature does, not what you are entitled to do with it, and the two drift.
Copilot Studio credits reset monthly and do not roll over. Sizing off a quiet month will leave you short at quarter end.
"Sales agent" appearing in the product does not mean every part of it is covered by the Sales licence. The premium behaviour is gated behind Microsoft 365 Copilot.

Consultant notes

Get the client to send you their current subscription list from the Microsoft 365 admin center before you design anything. What they think they bought and what is on the tenant frequently differ.
Demo the Enterprise capped features honestly. Showing sales accelerator on an Enterprise licence and then discovering the monthly cap in UAT is a bad conversation to have late.
Push back on blanket Premium. Per-persona licensing is nearly always defensible and saves real money without hurting the rollout.
Before go-live, check that every user has both a licence and a role, and that the app each persona can see matches the licence they hold.
Keep a one-page tier decision record in the solution design. In year two someone will ask why half the team is on Enterprise.

Worth another look after the next release wave, or whenever Microsoft shifts a capability between Enterprise and Premium.