I think it is safe to say that that the license enforcement announcement for D365FSC has created quite a bit of turmoil and stress within the community, and the rollout of features / reporting to help with this has been less than ideal so far. Microsoft has recently made a change that makes this process slightly harder so I wanted to quickly make a blog post around what the change is and current workarounds.
Currently there are at least 5 different areas where you can report on user licensing within D365FSC (there may be more that I am unaware of):
If you run your license reporting from any of these systems, the odds of two reports actually matching is very low. Microsoft has been working on a trying to address this by saying that PPAC will eventually be the ‘source of truth’ for license requirements going forward. But what do customers in the meantime do to try and address their licensing issues when they don’t know which reports to trust?
From my testing, I have found that the reports within D365FSC appear to be the most accurate and have been directing end users to utilize those to try and get ahead of the license enforcement happening later this year. I have equated the other licensing reports to just being ‘noise’ surrounding the licensing and that eventually PPAC, LCS, and M365 should all match what is in D365FSC.
Note: This recommendation may change in the future but is currently still my opinion.
There appears to be a struggle within Microsoft on how best to address the license discrepancies between different reports, based on a recent Proactive Quality Update there solution appears to be to remove the current licensing reports from within D365FSC.
Here are the release notes from 10.0.2095.159 PQU:
In D365FSC environments that are connected to Power Platform, you can see that those reports are no longer there. The below screenshot is from a Unified Developer Experience (UDE) instance on 10.0.43:
But in a cloud hosted environment (CHE) that is not connected to Power Platform that are on the same exact version of D365FSC, those reports still exist:
So it appears that the connection to the Power Platform is what is driving whether or not to show the reports and the actual code / objects that generate those reports are still available in the system.
Currently the best course of action is to have at least one CHE instance of each version within your organization not connected to Power Platform, if for no other reason than to ensure you have these licensing reports to utilize.
In my personal opinion, I think Microsoft has ‘gotten out over their skis’ slightly with removing these reports. I understand what they are trying to do, and think consolidating the license analysis is the correct move long term. However, removing accurate reports that work in D365FSC prior to getting the licensing reports within PPAC to be accurate is not a great customer experience.
The post Missing Licensing Reports in D365FSC appeared first on Alex Meyer.
Original Post https://alexdmeyer.com/2025/05/27/missing-licensing-reports-in-d365fsc/