New licensing rules in Dynamics 365: Everything you need to know

Article summary: 

From 15 January 2026, Microsoft will begin enforcing user licensing for Dynamics 365 Finance & Supply Chain Management and related applications. This change means only users with correctly assigned licences will be able to access production environments. Organisations that don’t prepare risk workflow disruptions, unexpected costs, and compliance challenges. This article explains what’s changing, which applications are affected, and the practical steps businesses can take now to stay compliant and avoid downtime. 

Prepare for license enforcement with confidence 

Recently, we hosted a webinar for our customers walking through the upcoming Dynamics 365 license enforcement changes. For those who couldn't attend, here's what you need to know about preparing your organisation for these important changes. 

While a few details around Microsoft’s new licensing rules are still being clarified, one thing is certain: staying compliant matters regardless of when enforcement happens. Acting now will help your organisation avoid costly true-ups, audit risks, and unnecessary operational downtime. 

Having worked with customers since the original announcement, we've seen consistent patterns and helped resolve common issues.  

Here's the positive perspective: while these changes require action, they ultimately benefit your organisation through automatic compliance, improved security governance, and better cost visibility. Role building will be more clearly linked to cost, users will have appropriate access levels, and license compliance becomes automatic. 

Which applications will bimpacted? 

The new licensing enforcement affects all Dynamics 365 Finance & Operations applications, including Finance, Supply Chain Management, Commerce, Human Resources, and Project Operations. If you're running any of these applications in Microsoft-managed production environments, these changes will impact your organisation. 

The risks of inaction 

Failing to prepare ahead of enforcement can expose your business to several operational, financial, and security risks: 

Disruptions to your critical workflows 

From 15 days after your contract anniversary, any user without a properly assigned license will be blocked from accessing Dynamics 365. This could paralyse essential business processes including financial operations, supply chain workflows, and payment processing. 

Increased cost and compliance risk 

Organisations that have been operating with more users than licenses may face substantial unexpected costs. We've seen scenarios where misconfigured security roles trigger requirements for thousands of additional licenses. Beyond the financial impact, non-compliance can cause issues with audit. 

Expose gaps in your governance 

The enforcement changes shine a light on user access management practices. Many organisations will discover they have inactive user accounts, overly permissive security roles, or users with access beyond what their roles require. While uncomfortable, this transparency creates an opportunity. 

Cause unnecessary downtime 

If your users are suddenly locked out of the system due to missing licences, your essential business operations are at serious risk of coming to a standstill. For organisations running global operations on Dynamics 365, even brief outages can disrupt supply chains, delay customer orders, and impact financial reporting. 

Emergency license purchases and hasty security role reconfigurations add stress and increase the risk of errors. Users suddenly losing access to systems they need to do their jobs can halt operations and create support nightmares. 

How can I get ready for enforcement? 

We recommend a six-step approach:  

  1. Remove inactive accounts - use the User Security Governance User Activity Aging Report to identify users who no longer need access 
  2. Understand the licensing model - familiarise yourself with how security roles, duties, and privileges map to license requirements 
  3. Review user role and license mapping - use Power Platform Admin Center or Lifecycle Services reporting to investigate which roles trigger which license types 
  4. Validate with USG reporting - cross-reference your findings using the User Security Governance License Usage Summary Report to identify optimisation opportunities. This may require role customisation. 
  5. Align license assignments - provision and assign appropriate licenses through the Microsoft 365 Admin Center 
  6. Plan for additional licensing - make reservations for supplemental licenses if needed to ensure compliance ahead of enforcement 

What should you dtoday? 

Start by understanding your contract renewal and anniversary dates. Review Microsoft's licensing documentation and familiarise yourself with the six-step process. If your renewal is approaching, begin your preparation at the 90-day mark. 

Consider this an opportunity to define your overall access management approach. Successful access management means strong governance, automation of access assignments, and an enabled workforce with the tools to do their jobs. Consider automating onboarding and offboarding processes to reduce risk. Conduct regular reviews – particularly where users move roles, departments or projects. Implement continuous monitoring and governance 

Watch the full webinar recording here for detailed guidance, real-world examples, and answers to common questions from customers who are navigating these changes. 

Watch on-demand webinar

 

Key takeaways: 

  • From 15 January 2026, Microsoft will begin enforcing user licensing for Dynamics 365 Finance & Supply Chain Management and related applications 
  • Organisations that haven’t assigned the correct licences risk user lockouts, workflow disruptions, and compliance penalties 
  • Reviewing and optimising your current licence assignments can prevent costly true-ups and operational downtime 
  • Strengthening access management and governance will help ensure ongoing compliance and improve overall system security 

 

 

chris profile
Chris Clifford Principal Security Architect