# Dynamics 365 License Types: A Guide on Upcoming Changes to D365 F&O License Enforcement

- Link: https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/
- Published: 2025-05-13T21:53:55+01:00
- Author: Marco Romano

# Dynamics 365 License Types: A Guide on Upcoming Changes to D365 F&O License Enforcement

**Why you’re about to pay a lot more for Dynamics 365 licenses (and what to do about
it)**

13 May 2025

## Introduction

Navigating the labyrinth of Microsoft Dynamics 365 licensing is no small feat. With
Microsoft’s upcoming enforcement changes, understanding how business applications
are licensed (Finance, Supply Chain Management, Commerce etc.), and what license
types exist out there (user, device, and tenant) has just dramatically increased
in priority for many companies. This guide demystifies each license type and outlines
the impending shifts, so you can remain compliant and cost-effective.

### Disclaimer

A word of caution: this article is based on the latest available Dynamics 365 licensing
documentation and enforcement guidance as of May 2025 (updated July 2025). The upcoming
changes to license enforcement are still evolving, and Microsoft may update its 
policies or tooling. Everything outlined here reflects the best information available
at the time of writing but, as always, this is subject to change.

### Key takeaways

 * **Optimising security roles to reduce license consumption isn’t a quick fix.**
   It’s a messy, time-consuming job that requires deep expertise. If you haven’t
   started already, you’re behind schedule.
 * **Dynamics 365 license types are about system access. **They are not just about
   what you buy, rather how much of the system users have access to. To avoid surprises,
   you need to understand:
    1. The different license types that exist for the Dynamics 365 apps suite
    2. How each Dynamics 365 business application is licensed
    3. How security role configurations drive actual license consumption
 * **The honour system is dead.** From 1 November 2025, Microsoft will enforce license
   compliance in Dynamics 365 F&O — no license, no access. If you’re not ready, 
   your users won’t be able to use your ERP.

### Wait! Before we begin…

Unexpected license costs are only one the issues in the Dynamics 365 Finance and
Operations journey. We wrote a **practical guide for senior leaders **of companies
already live with D365 F&O. It describes symptoms that your new ERP is failing to
deliver the promised benefits, what are the likely root causes, and what to do about
them. Download your free copy from the form below.

![](https://itfandango.com/wp-content/uploads/2025/05/Mockup-Underperforming-Free-
Guide-Cover-Extended-1024x739.png)

Field guide to underperforming D365 F&O systems

Seven operational symptoms your ERP is failing to deliver after go-live

**Download your free copy!**

Field Guide to Underperforming D365 F&O Systems

 * About you
 * About your job role
 * About your company

First Name

Last Name

Business email

Job function

Seniority level

Company type

Geographic region

_I have read and agree to the [Terms and Conditions](https://itfandango.com/terms-conditions/)
and [Privacy Policy](https://itfandango.com/privacy-policy/)_

---

## The Dynamics 365 ERP and CRM business applications

![A series of Microsoft application logos.](https://itfandango.com/wp-content/uploads/
2025/05/image-1024x406.png)

The colourful logo collection of the Microsoft Dynamics 365 business applications
and ecosystem.

Let’s clear something up straight away: **Dynamics 365 is not a single product**.
It’s a suite of cloud-based business applications, designed to support a wide range
of operational and customer-facing processes. Each application targets specific 
business needs and business areas. Broadly speaking, the suite covers both Enterprise
Resource Planning (ERP) and Customer Relationship Management (CRM), although those
terms are more legacy labels than functional boundaries these days.

This shift happened with the move from on-premise systems like Microsoft Dynamics
AX to Dynamics 365 in the cloud. Alongside the new architecture came a modular application
model. Microsoft no longer sells a monolithic ERP. Instead, what you get is a set
of integrated apps that work together, built on a common platform (yes, that’s where
Dataverse and dual-write come in — but let’s not go there today).

So what does this suite actually include, specifically on ERP and CRM?

 1. **ERP suite for enterprise organisations:**
 2.  * Dynamics 365 Finance
     * Dynamics 365 Supply Chain Management
     * Dynamics 365 Commerce
     * Dynamics 365 Project Operations
     * Dynamics 365 Human Resources
 3. **ERP for small and medium companies:**
 4.  * Dynamics 365 Business Central
 5. **CRM application suite:**
 6.  * Dynamics 365 Sales
     * Dynamics 365 Contact Center
     * Dynamics 365 Customer Service
     * Dynamics 365 Field Service
     * Dynamics 365 Customer Insights (formerly Dynamics 365 Marketing)

The naming convention is fluid and Microsoft changes it regularly. For example, 
the official name for the first group is now _finance and operations apps_, even
though many still call it Dynamics 365 Finance and Operations.

This is because within the ERP, these aren’t technically separate applications. 
You don’t install “Finance” or “Supply Chain Management” as standalone apps. What
you install is a unified ERP system, and the parts that you use drive your license
usage.

(It’s technically a bit more complicated than this, with certain parts enabled by
license keys and additional cloud-based features, but let’s keep it easy here — 
it’s already complex enough.)

That’s why these business applications “names” are best understood as **license-
defined groupings**. Each one covers certain functional areas of the Dynamics 365
ERP. So while the system itself is integrated, the parts that you use define which
applications and related licenses you will need to buy.

Oh, and it’s important to understand that these are not modules. They are still 
called apps or applications. Dynamics 365 Finance and Operations (the entire ERP)
has 40+ modules, [which I have explained in another article](https://itfandango.com/articles/all-dynamics-365-fo-modules-explained/).

So before I finally tell you about licenses, first I need to briefly explain what
these key applications actually do. From now on, I will only cover the Finance and
Operations side of things, that is the ERP suite for enterprise applications.

If you’re already familiar with it, just skip to the next section. Let’s dive in.

### Dynamics 365 Finance

Dynamics 365 Finance handles **core accounting and financial management** (like 
expense entry, financial reporting, budgeting, and more) making it essential for
finance employees, full users, and controllers who need consistent, detailed oversight
of financial data. As the backbone of your ERP, it enables strategic alignment between
financial operations and broader business needs.

### Dynamics 365 Supply Chain Management

Dynamics 365 Supply Chain Management in Dynamics 365 supports **inventory control,
procurement, manufacturing, and logistics**, giving supply chain managers and professional
users the tools to run critical business processes smoothly. For companies managing
physical goods, it’s the central hub for ensuring that operations stay efficient
and scalable.

### Dynamics 365 Commerce

Dynamics 365 Commerce delivers integrated **retail and POS capabilities** for omnichannel
sales, enabling customer service representatives and sales teams to manage the full
customer journey from online to in-store. It connects sales, product, and customer
data across channels to support seamless customer engagement and drive smarter decisions.

### Dynamics 365 Project Operations

Dynamics 365 Project Operations equips **project-based businesses** with planning,
costing, and delivery tools, combining project service automation and workflow visibility
to keep operations aligned and predictable. It’s built for field service teams, 
consultants, and full users who manage timelines, budgets, and deliverables.

### Dynamics 365 Human Resources

Dynamics 365 Human Resources supports HR professionals across the **employee lifecycle**,
covering everything from recruitment to benefits management. For organizations focused
on workforce stability and growth, it ensures your people strategy stays aligned
with your operational goals.

---

## The Dynamics 365 licensing model explained

Let’s take a step back and pretend you’re coming from SAP, have never touched Microsoft
Dynamics 365, and you’re [preparing to implement it](https://itfandango.com/articles/dynamics-365-erp-prepare-successful-implementation-essential-guide/).
At first glance, the licensing looks simple: pick your business apps, count your
users, and buy what you need. Easy, no? No. It’s only easy until you realise what’s
lurking beneath the surface.

Let’s start with the basics: **Dynamics 365 uses a modular, role-based licensing
model**. It’s designed to be flexible, more like a Swiss Army knife than a sledgehammer.
The primary mechanism is named-user subscriptions (User Subscription Licenses or
User SL): you pay per user, per month, based on the system access they actually 
need. So far, no surprise.

However, in Dynamics 365 Finance and Operations, it’s what users _can do_ in the
system (not what you _think_ they do) that determines the required license. This
model’s strength lies in precision: give users only what they need to do their jobs,
and you will keeps costs under control. Don’t, failing to understand how role-based
access maps to license consumption, and you will pay way more than anticipated.

And yes, it’s convoluted and complex to setup correctly. Think reading the tax code
while riding a unicycle, and you can get an idea.

Oh, and if you’re **upgrading from Dynamics AX**, don’t assume anything. The architecture
might look familiar, but the licensing logic is now different (relying on both entry
points and security privileges — but this is a topic for the techies). One of the
biggest mistakes companies make is assuming traditional or legacy usage maps neatly
onto the new model. It doesn’t.

Anyway, while user-based licensing covers the biggest part of Dynamics 365 licensing,
there are exceptions. For example, you may be required to license the hardware (
via device licenses), or pay for additional platform-wide services (via tenant licenses).
These are handled through different license types, but more on that in a minute.

What matters now is this: understanding how your users interact with the system,
and configuring their access appropriately, is the only way to stay compliant and
avoid unnecessary spend. And with Microsoft’s enforcement deadline approaching fast,
waiting is no longer an option.

---

## The Dynamics 365 license types and what they actually mean

Now, for the real complexity. Dynamics 365 applications are licensed by subscription
type:

 * **Tenant licenses** apply to your entire Dynamics 365 environment and power organisation-
   wide features, like cloud services or integrations. Think your e-commerce integration.
 * **User licenses** are by far the most common and probably bulk of your costs,
   depending on how many employees use the system. They are assigned to named individuals
   based on their role. Think John in accounts payable.
 * **Device licenses** are required for shared terminals in environments like shop
   floors, warehouses, or retail counters. Think the handheld scanner used by the
   picking team.

Most organisations will need a blend of user, device, and tenant licenses to fit
their structure, workforce setup, and industry-specific needs. Manufacturing? You’ll
likely lean harder on device licenses. Professional services? Full user licenses
for the finance team, but cheaper team member licenses for timesheet users. There’s
no one-size-fits-all, but there is a right-size-for-you. Designing your solution
with that in mind is the first battle.

Indeed, getting the license mix right starts long before your first user logs in.
It begins with solution design at the time of planning your Dynamics 365 implementation—
at least on a high level. Do it wrong, and after go-live you’ll end up with a license
bill way higher than expected.

Because this isn’t just about ticking Microsoft’s compliance boxes, now that the
consumption enforcement is imminent. Sizing your license usage correctly is also
a matter of operational efficiency. It’s about ensuring people have whatever system
access they need (no more, no less) to do their job properly.

So what are those three license types about, how do system usage affect what licenses
you need?

---

## User licenses: priced per individual

User licenses in Dynamics 365 Finance and Operations are like boarding passes: assigned
to named individuals, valid for specific destinations (i.e. apps features), and 
priced according to how far they’re going. These licenses are the backbone of any
ERP setup, and they dictate what users can actually do in the system based on their
role and responsibilities.

Each user gets licensed individually, but not all licenses are created equal. For
D365 F&O apps, these user licenses come in four main tiers:

 * **Premium**
 * **Full **(**Base Licenses** and **Attach license**)
 * **Operations **(aka **Activity**)
 * **Team Member**

They vary depending on the extend system features are accessed.

For example, full users the ones posting finance journals, managing sales orders,
or scheduling production: they need the core features of the application. Team Members,
on the other hand, might just need to post their own timesheets.

Mixing these up is a costly mistake: too much access and you’re paying for features
no one uses; too little and people start building Excel workarounds that quietly
derail your entire system.

And before we go any further, here’s a non-negotiable: if you want to use the Dynamics
365 Finance and Operations ERP, you need to **buy at least 20 full user licenses**
for Finance or for Supply Chain Management (not a mix between the two). That’s Microsoft’s
minimum requirement for entry. The rest is built up from there.

So understanding these tiers isn’t just a trivial licensing nuance: it’s your main
financial control mechanism when it comes to your subscription costs. Get it right,
and your system runs smoothly without blowing the budget. Get it wrong, and you’re
either overpaying or under-delivering.

Now, let’s what each named user license actually means in practice.

### Premium license

Right now, **Premium licenses **look a lot like Full access user licenses. In terms
of day-to-day features, you won’t spot much difference. The distinction lies in 
behind-the-scenes metrics like capacity entitlements and storage thresholds for 
specific advanced features. These licenses are only available for Dynamics 365 Finance
and Supply Chain Management, and may evolve to include exclusive capabilities in
the future. If you’re assigning Premium licenses today, it’s likely because your
usage patterns push the limits of standard resource allocations, not because your
users need radically different tools (yet).

### Full access license (Base license and Attach license)

**Full-access user licenses** are your daily key users, the people who live in the
system. This includes roles like finance employees, operations leads, or customer
service representatives who need to enter, edit, and action things across the ERP.
These licenses come in two flavours:

 * The **Base license** is your initial (and most expensive) seat. Every full user
   starts here.
 * The **Attach license** is a discounted add-on that let you access other business
   applications in the suite, but only if you’ve already got a qualifying Base license.

Functionally, there’s no difference between a Base license and an Attach license.
They’re the same under the hood, so the only difference is pricing. Attach gives
you the same firepower for less, but only as a second seat. One catch, though: not
all Base licenses are compatible with all Attach licenses. So no, it’s not a pick-
and-mix free-for-all. But you can check your options in the picture below, straight
from the official Dynamics 365 Licensing Guide of May 2025.

![An image of license combinations from the Microsoft Dynamics 365 Licensing guide.](
https://images.surferseo.art/07346d13-118c-4f35-a991-9815caf6522b.png)

The allowed combinations of Base licenses and Attach licenses, according to the 
official Dynamics 365 Licensing Guide (May 2025).

### Operations (aka Activity) license

The **Operations license **(also known as** Activity license**) hits the middle 
ground, being designed for professional users who do real work in the system but
don’t need key features. Think entering purchase orders, updating inventory, or 
tracking production, but not posting financial journals or creating new production
orders. It delivers more capabilities than a Team Member license, but at a fraction
of the Base license cost. It’s a go-to option for cost savings without gutting access,
and a good opportunity for cost saving. Miss this option and you’re either paying
too much, or throttling your operations unnecessarily.

### Team Member license

**Team Member** **licenses **are the lightest of the user license types, ideal for
users who need limited access to the simplest areas of the ERP. They’re great for
light users who approve requests, track time, or submit their own expense entry.
That’s people who dip in and out of the system but don’t drive key processes.

---

## Device licenses: priced per hardware

Device licenses are assigned to a **specific piece of hardware**, not a person. 
They’re built for scenarios where multiple users share a dedicated terminal: think
warehouse floor scanners, retail tills, or shared PCs in a manufacturing plant. 
Instead of licensing every person who might use the system, you license the device
they all use.

This model is ideal for shift-based operations or high-turnover roles, where assigning
individual user licenses would be expensive and largely unnecessary. Device licenses
come in two forms: full-access (covering rich functionality for applications like
Finance and Supply Chain Management) and limited-access (designed for light tasks
like time entry or expense approval).

Depending on the Dynamics 365 application, these devices can be accessed via shared
logins (e.g. “Warehouse Computer”) or individual credentials. Full-access device
licenses are common for operations roles, while limited-access ones are useful where
multiple users only need to consume data or perform basic actions.

![An image of a warehouse scanner](https://rmsomega.com/wp-content/uploads/2022/
10/retail-photography-application-lowes-mc9300-20-3600x3600-1-scaled.jpeg)

A warehouse scanner would trigger a Device license.

---

## Tenant licenses: priced per system-level features

Tenant licenses apply to **your entire Dynamics 365 environment**, not to a specific
user or device. They enable platform-wide functionality (think Dataverse storage,
customer profile tracking, or AI services) that benefits everyone logged into the
system. Think of them as infrastructure-level power: invisible to users, essential
to operations.

Some business applications or features, like Customer Insights or Electronic Invoicing,
are only licensed at the tenant level — there’s no such thing as a per-user option.
Others, like Finance or Supply Chain Management, come with base capacity entitlements
that can be extended with Tenant-level add-on licenses. These might include more
storage, higher transaction volume, or other resource allowances pooled across the
whole tenant.

Tenant licenses are often overlooked in initial planning, but they’re critical for
scaling. If your organization exceeds default capacity limits (or expects to) you’ll
need to factor these into your licensing strategy early. In some cases, these licenses
aren’t optional bells and whistles, rather they’re what keep the system running 
when you start pushing serious volume.

![A picture of a laptop with a small supermarket cart on it.](https://www.infosysbpm.
com/content/dam/infosys-bpm/en/blogs/images/ecommerce-integration-guide-medium.jpg)

An e-commerce integration would require a Tenant license.

---

## Upcoming changes to Dynamics 365 licenses enforcement

Microsoft is finally putting an end to the licensing honour system in Dynamics 365
Finance and Operations. For years, you were trusted to assign the right licenses
without enforcement. That ends now. Two enforcement deadlines are approaching fast,
and they’ll fundamentally change how access to your ERP is managed.

### 1 September 2025: In-app warnings begin

From this date forward, any user accessing Dynamics 365 Finance and Operations without
a valid license will see an in-app banner instructing them to contact their administrator.
So far, this is a gentle reminder that will alert users (and by extension, IT departments)
to misconfigured or missing license assignments.

 * These warnings function as an early warning system to address license problems
   before they escalate into access blocks.
 * They provide a grace period to correct licensing issues while maintaining system
   access.
 * Administrators should treat this date as the final checkpoint to verify every
   user’s license status before stricter measures kick in.

### 1 November 2025: No license, no access

After this date, any user without a proper license assigned via the Microsoft 365
Power Platform Admin Center (PPAC) will be blocked from using Dynamics 365 F&O. 
There’s no fallback, no exceptions.

 * Licenses must be assigned through the Microsoft 365 Power Platform Admin Center.
   This will be the single source of truth for license consumption.
 * Licensing will work exactly like Microsoft Office: if your company has not purchased
   and assigned a valid seat to your user, you’re locked out and cannot utilise 
   the application.

This change centralises license management and aligns it with the broader Microsoft
365 ecosystem. It also means license assignments are no longer solely the Dynamics
365 system admin’s responsibility, but they require direct collaboration with the
overall IT admin team, who might have limited understanding of the specific Dynamics
365 licensing nuances.

### The PPAC licensing report is your new best friend

With this enforcement shift, the **Microsoft Power Platform Admin Center** (PPAC)
becomes the definitive source of truth for license consumption. Microsoft will use
this report for both enforcement and audit visibility.

 * All license usage and assignments will be monitored through this report, with
   data flowing to F&O for enforcement.
 * Any mismatch between user actions and assigned licenses will be flagged here.
 * Organisations must treat the PPAC licensing report as their primary diagnostic
   and planning tool going forward.

### You’ll need to commit (and pay)

Microsoft’s licensing is a technical shift with a commitment that has financial 
consequences. With enforcement becoming automated:

 * You must purchase sufficient licenses in advance and assign them correctly.
 * These licenses typically come with a minimum term commitment, especially under
   enterprise agreements.
 * License costs must be factored into both budgeting and governance, as this is
   no longer a “we’ll fix it later” compliance area.

### Prepare now or deal with the fallout later

So, if you’re still in “we’ll sort it later” mode, it’s time to snap out of it. 
Here’s what to do:

 * Audit your current license assignments against how users actually use the system.
 * Align your Dynamics 365 consultants, support, and admin teams. They’ll need to
   work together.
 * Review your contracts: know your renewal cycles, your minimums, and your true-
   up terms.
 * Put governance around license assignments. This isn’t a one-and-done job, it’s
   ongoing.

The bottom line: **enforcement is coming**, and Microsoft means it this time. If
you’re not ready, users will be locked out, costs will spike, and audit risks will
rise. If you are ready, it’s just another compliance box ticked quietly, in the 
background, where it should be.

---

## Conclusion and next steps

The days of vague licensing policies and “we’ll deal with it later” are over. After
1 November 2025, if users don’t have the right Dynamics 365 licenses properly assigned,
they won’t be able to access the system.

Yes, **this will likely cost you more money**. But the real decision is whether 
you spend it deliberately, by matching licenses to actual usage and tightening up
your compliance, or waste it reacting to preventable lockouts, missing licenses,
and late-night audit panics.

And let’s be honest, you’ll probably need expert help. Most organisations don’t 
have the internal bandwidth or specialised knowledge to map out license strategies,
optimise security roles, and navigate Microsoft’s constantly shifting licensing 
terms.

That’s where we come in, as an [independent boutique consultancy](https://itfandango.com/about-us/).

We’ll help you cut through the noise, clean up your license footprint, and put a
sustainable security model in place before the new rules hit. No fluff. No panic.
Just straight-talking guidance from people who’ve been in the trenches and know 
how to navigate security roles configuration and licensing landmines without losing
sleep… or budget.

### One last thing

If you want to know more about the type of D365 F&O problems we can help you with,
download our guide below. It’s designed for** senior leaders of companies already
live with D365 F&O**. We cover 7 symptoms that your new ERP is failing to deliver
the promised benefits, what are the likely root causes, and what to do about them.
Get your free copy from the form below.

![](https://itfandango.com/wp-content/uploads/2025/05/Mockup-Underperforming-Free-
Guide-Cover-Extended-1024x739.png)

Field guide to underperforming D365 F&O systems

Seven operational symptoms your ERP is failing to deliver after go-live

**Download your free copy!**

Field Guide to Underperforming D365 F&O Systems

 * About you
 * About your job role
 * About your company

First Name

Last Name

Business email

Job function

Seniority level

Company type

Geographic region

_I have read and agree to the [Terms and Conditions](https://itfandango.com/terms-conditions/)
and [Privacy Policy](https://itfandango.com/privacy-policy/)_

**Sections:**

 * [Introduction](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#1)
 * [D365 business applications](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#2)
 * [The licensing model](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#3)
 * [D365 license types](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#4)
 * [Upcoming changes](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#5)
 * [Conclusion and next steps](https://itfandango.com/articles/guide-to-microsoft-dynamics-365-license-types-2025/#6)

![Author Profile Image](https://itfandango.com/wp-content/uploads/2024/04/Copy-of-
_DSC4810_colore_Edit-cropped.jpg)

Marco Romano

D365 F&O Independent Advisor

 * [LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)

[Connect with me on LinkedIn](https://www.linkedin.com/in/marcoromano-itfandango/)
