Skip to main content

Insight · Microsoft Dynamics 365

Dynamics 365 licensing in 2026:
Is your setup ready?

Microsoft is tightening enforcement of licenses in Dynamics 365 Finance & Operations. This means users, roles, and access rights must more closely match the licenses actually assigned. For many companies, this can have both practical and financial consequences.

Dynamics 365 licensing 2026Microsoft Dynamics 365

What this is really about

This change is not only about what you have purchased. It is also about how your Dynamics 365 environment is actually used. If users have access to functionality that requires a higher license than the one assigned to them, it can create challenges when Microsoft starts enforcing the rules more consistently.

For most organisations this is not a brand-new licensing model. It is stricter enforcement of existing licensing requirements across Dynamics 365 Finance, Supply Chain Management, Commerce, Human Resources, and Project Operations. The earlier you review users, roles, privileges, environments, and license assignments, the easier it is to fix any gaps without urgency.

What is changing?

A short, plain-language summary of what to expect.

Stricter license enforcement

Microsoft is moving from soft guidance to consistent enforcement of Dynamics 365 license entitlements across Finance & Operations apps.

Access must match the license

Functionality a user can reach must align with the license assigned to them. Mismatches can cause access issues once enforcement is active.

Security roles matter more than ever

Custom security roles and broad privilege grants need to be reviewed; they are often the root cause of unexpected over-licensing requirements.

Base and Attach licensing rules

Team Members, Activity, Operations Activity, Base, and Attach licenses must be combined correctly per user — not just per organisation.

Old setups should be cleaned up

Inactive users, legacy access patterns, and historical service accounts should be reviewed and tidied before enforcement creates practical issues.

This is especially important if you…

The change lands hardest on these setups.

  • Use Dynamics 365 Finance
  • Use Dynamics 365 Supply Chain Management
  • Have many users or complex security roles
  • Have customised security roles or duties
  • Have used Dynamics 365 for several years
  • Are unsure about Base and Attach licensing
  • Have external users, service accounts, or older users with active access
“Licensing should not only be handled by procurement. It requires insight into business needs, Dynamics 365 roles, and Microsoft’s licensing logic.”
– BondIT advisory perspective

Typical challenges we see

Patterns that show up in almost every Dynamics 365 license review.

Too broad security roles

Roles that grant access to functionality far beyond a user’s actual job pull users into a higher license tier than they need.

Wrong license type per user

Users sit on Team Members or Activity licenses while performing tasks that require a Base or full Operations license.

Old or inherited access rights

Permissions kept ‘just in case’ over years of project work add up and quietly drive up license requirements.

Missing link between roles and licenses

There is no clear mapping between security roles in Dynamics 365 and the license entitlements they imply.

Unnecessary license costs

Some users are over-licensed for their actual usage, which means money is being spent that could be redirected elsewhere.

Want a clearer view of your current setup?

A short license review session is usually enough to surface the biggest risks and opportunities in your Dynamics 365 environment.

How BondIT can help

At BondIT, we help companies understand their Dynamics 365 licenses, security roles, and actual usage. The goal is simple: stay compliant, avoid unexpected access issues, and make sure you are not paying for more than you need.

  1. 1

    Analyse the current license setup

    We map your existing licenses, environments, and assignments to get a clear baseline.

  2. 2

    Review users, roles, and permissions

    We check which users have which security roles and what those roles actually allow them to do.

  3. 3

    Identify risks and optimisation opportunities

    We highlight under-licensed users, over-licensed users, and risky role configurations.

  4. 4

    Create a concrete action plan before 2026 enforcement

    You receive a prioritised plan with clear steps to take, owners, and a recommended timeline.

What do you get from a review?

Clear, practical outcomes you can take to your CFO, CIO, or steering committee.

  • An overview of current license risks across Dynamics 365
  • Clarity on which users actually need which licenses
  • Recommendations for role and permission adjustments
  • Specific license optimisation opportunities
  • A concrete plan to prepare for 2026 enforcement
  • Confidence before Microsoft’s enforcement has practical impact
“The companies that handle this calmly in 2026 are the ones that started reviewing their Dynamics 365 roles and licenses in 2025.”
– BondIT licensing advisory

Frequently asked questions

Quick answers to the questions we hear most often from CFOs, IT managers, and ERP owners.

Not necessarily. For many companies, this is mainly about Microsoft tightening enforcement of existing licensing requirements.

Do you want to make sure your Dynamics 365 licenses are ready for 2026?

BondIT can help you review your licenses, roles, and access rights so you are prepared before the new enforcement requirements have practical impact.

© 2026 BondIT Consultancy. All rights reserved.| 26.9.7