Hi Dynamics Community,
We have been working diligently over the past months to get our user roles to comply with the new licensing requirements Microsoft is introducing from 2026. We seem to be in the first wave of enforcement, so it is critical that we are in compliance as soon as possible.
We use custom roles quite extensively, which have required a lot of attention to update to get to fit within a single license SKU. In almost all cases, users have tasks that fit within a single license SKU and so it has not been a problem to remove entry points from custom roles which caused minor spillover into other SKUs.
During the process of paring back entry points associated with user roles, I have been using the "Licenses usage summary" page in D365 FO as a guide. We are currently on FO version 10.0.45 (quality update 10.0.2345.76).
We have several instances where "Licenses usage summary" reports that a custom role is fully entitled under a single SKU. However, PPAC is citing the same role as necessitating attach licenses. When I drill down further in PPAC, it also shows that the role is fully entitled under the SKU that I have intended the role to fit within.
Ultimately, this discrepancy is causing a very large number of under-licensed users to appear within our PPAC report.
As an example, the following user shows required licenses of Finance, Human Resources and Project Operations.
This user is currently assigned a Finance license. Drilling down further shows that the role "_AP Supervisor fin. license" requires Finance, Human Resources and Project Operations licenses.
Drilling down again within this role shows that the role shows as fully compliant within a Finance license from within PPAC.
The same is true for the _AP User 1 fin. license role, for this user.
"Licenses usage summary" shows the same for the "_AP Supervisor fin. license" role.
Still, PPAC is flagging this user as under-licensed, and we have several users showing up in PPAC as under-licensed for exactly the same reason.
We have our enforcement date soon and my concern is that these users will encounter issues accessing D365 FO when this date rolls around. Is there something I am overlooking here?
I read through Andre Arnaud de Calavon's licensing advent calendar and found it very informative and helpful - still, I am doubtful on our compliance status when PPAC is showing me conflicting information.
Any input is highly appreciated. Wishing a happy New Year to the community.
