Use this license cleanup guide to prepare for changes to Dynamics 365 license enforcement
Microsoft is cracking down on Dynamics 365 license enforcement. New tools and reports promise to make managing users easier, but on January 15, 2026, users who haven’t been assigned a license will lose access to their Finance and Operations production environments.
Don’t get caught by surprise! Below is a step-by-step guide on how to reconcile system users with your current licenses and subscriptions, assign named users to licenses, and ensure you’re compliant with Microsoft’s requirements.
Contents
November 1, 2025
Find your current license utilization report here:

| Scenario | What it means | Next action |
|---|---|---|
| No Issues:
Available Seats ≥ Required Seats and all are Assigned Utilization Status: “All licenses are assigned.” | You’re good to go! All available seats cover your user requirements, and every user has been assigned a license. | No action required. Consider reducing your total licenses if excess capacity exists. |
| Fully licensed but need assignments:
Available Seats ≥ Required seats, but are not fully assigned Utilization Status: “X licenses can be assigned.” | Sufficient licenses exist, but some users haven’t been assigned a license. | Assign licenses to unlicensed users. |
| Under licensed:
Available Seats < Required Seats Utilization Status: “You are using X more licenses.” | More users are triggering license requirements than you have seats for. | Perform an audit: review security roles, reduce permissions or duties, or determine if more licenses are needed. Then assign licenses to users. |
Device licenses and usage are not included in the PPAC license report. We recommend that you manually track physical device usage (such as warehouse scanners and POS terminals) and ensure purchased quantities match your needs.
Time for a true-up!
Export the PPAC license report to CSV for use in detailed analysis:
Create a separate master list of all expected current F&O users:
Now you can compare the two lists:
Now that you’ve exported the PPAC license report and compared it against your list, it’s time to analyze user role permissions in Dynamics 365 Finance & Operations.
In Finance & Operations, go to System Administration > Security Configuration. Select the user role in question, click “View Permissions” and review Duties/Privileges that are contributing to the license tier:


If using custom roles, consider duplicating and modifying them to remove non-essential privileges or duties. Ensure the new role supports business needs while minimizing license impact.
If specific privileges are still triggering higher licenses and you believe they shouldn’t, document them and escalate with your partner and/or Microsoft.
Below is a simplified summary of the different Dynamics 365 F&O user-based license types. For the full description of each license, refer to the latest edition of the Microsoft Dynamics 365 licensing guide: link
(Note: the above is a link to the May 2025 licensing guide. To find the latest Dynamics 365 licensing guide at any time, visit the Microsoft resource site: Licensing Documents.
| License Type | Description |
|---|---|
| Team Member | Mostly read-only users. Can view data and reports. Limited transactional rights. |
| Activity | Approvers, warehouse, or shop floor users who interact via shared terminals or perform confirmations. Depending on access requirements, Activity license holders can also include customer service and order entry personnel. Operations–Activity users generally are allowed to:
Examples of allowed tasks:
|
| Base | Full or transactional access. Includes finance, inventory, or production responsibilities. Attach-type licenses are required when using multiple Base functionality areas (e.g., Finance, Supply Chain, Commerce, Project Operations, etc.). |
We have found the following simple tips greatly helpful:
Starting in 2025, Microsoft requires that all D365 Finance & Operations users be explicitly assigned a license through the Power Platform Admin Center. This ensures correct access and avoids unexpected license errors. To look up users that need to be assigned a license, follow these steps:
1. Go to https://admin.powerplatform.microsoft.com
2. Make sure to toggle on the “New Admin center” look in the upper right-hand corner.
3. Go to Licensing > Finance and Operations. By default, the form auto-filters to the production environment.
4. Review the list of users to identify those who are unassigned or incorrectly assigned.
5. To assign users, continue to the next step.
If you identify a user or group in PPAC that needs a license assigned, you’ll make the assignment in the Microsoft 365 Admin Center. Here’s how:
1. Go to the Microsoft 365 Admin Center (https://admin.microsoft.com) > Billing > Licenses.
2. Select the desired license name, such as Dynamics 365 Finance.
3. Select Assign licenses > add the desired user(s) to assign > click Assign.
Tip: You may want to create and then assign Entra groups for sets of users requiring the same license type.


Yes, we have seen recent inaccuracy issues with reporting in PPAC as Microsoft releases new features. The Microsoft product team is actively working on resolutions.
Microsoft is refining and restructuring PPAC and making significant changes to its layout and functionality. In the future, PPAC will be a centralized hub for managing both licenses and environments.
In the meantime, it’s critical to assign licenses to users. We recommend you independently track your expected user counts, actual system users, and assigned security roles to establish a reliable baseline to compare against PPAC’s data.
It’s important to independently track your expected user counts, actual system users, and assigned security roles to establish your license baseline for comparison against PPAC’s reports. This blog post contains detailed instructions for comparing your license actuals against what’s in PPAC. Here’s a summary of the process:
Microsoft has not yet released formal guidance on how it will check for compliance. However, at this point we recommend assuming that license validation will occur at the license type level. This is signaled by the PPAC report, which audits expected user counts by license type and outlines the number of users required per license category.
Microsoft is introducing significant enhancements to security governance in Dynamics 365 Finance and Operations, aiming to provide administrators with more robust tools for managing user roles, ensuring compliance, and optimizing licensing. These are currently in preview and expected to be released in July 2025 (Dynamics version 10.0.44). These features will greatly speed up security role creation, analysis, and adjustments.
As it specifically relates to licensing:
Microsoft 365 Admin Center:
Power Platform Admin Center (PPAC):
Lifecycle Services (LCS):
Contact us to speak with a licensing expert today. We can help you prepare for Microsoft’s upcoming license enforcement changes and optimize costs.