How D365 F&O decides which license a user needs

In Dynamics 365 Finance & Operations, you don't pick a license for a user and then give them access. It works the other way around: the access you give a user decides which license they need. Once you understand that, most license problems become easy to explain.

It starts with menu items

Every form, report and action a user can open is reached through a menu item. Microsoft assigns each menu item a license requirement, for example Team Members, Activity, or a full license such as Finance or Supply Chain Management.

Privileges, duties and roles

Menu items are grouped into privileges, privileges into duties, and duties into security roles. When you assign a role to a user, they get every menu item inside it. The role's license requirement is the highest requirement of anything it contains.

The highest one wins

A user with several roles needs the highest license across all of them. That means one role with a single full-license menu item can move a user from Team Members to a full license, even if they never open that screen.

Why this matters

• Small role changes can be expensive. Adding one broad role to a group of users can move all of them to a higher license.
• Custom roles need care. Copying a standard role and adding a few extras is quick, but those extras often carry a higher requirement.
• The fix is often in the role. Removing a menu item the user never needs can bring them back down a tier without changing what they actually do.

What to check

For each user, compare the license they hold with the license their roles require. Then, for each role, look at which menu items drive its requirement. Kourx License Optimizer does both checks every week in its Role license analysis and Over-licensed users reports.