Licensing Advent Calendar – Day 29 – Known issues

While Microsoft was changing the calculation logic and working on new licensing reports, some issues were reported. Initially, we lost track of all open and reported issues, but Microsoft added larger issues to the Known issues section on the Support page, where we can check the status. In this post I will elaborate on where to locate these reported issues and what you should know about them.

Known issues

As part of the unification efforts of the admin centers, Lifecycle Services (LCS) and Power Platform Admin Center (PPAC), the support page is now available in PPAC. You can navigate to Support > Known issues. Or use the direct link in a web browser: Support: Known issues | Power Platform admin center

You can search for the licensing-related issues by filtering on the Product category with the value Dynamics 365 Lifecycle Services. This will give more results than intended. In addition, you can use the search bar on the right side, where you can type licens. This will match the results having either licensing or license.

From all these known issues, you can check the status. If the issue is resolved, this means that the engineering team is ready. However, you will need to install the latest quality update or wait for the new report version to roll out in your tenant.

Let’s highlight some of the active, but also resolved issues.

Issue ID 5763889: Users with Deny and Write privileges

There are scenarios where deny permissions are set for menu items to ensure segregation of duties. The deny permissions should be carefully considered. In my opinion, it shouldn’t be a common practice to use this option. I have seen a lot of scenarios where standard privileges were copied, and instead of removing the entry points, the access was changed to deny without a real use case, like SoD or another exception. If you are in such a scenario, despite waiting for a possible upcoming implementation from Microsoft, I would suggest reviewing the security roles and implementing them according to best practices.

Issue ID 5887204: Duplicate rows for same user and same role

This issue was discussed several times in Viva Engage groups and during office hours. Where Microsoft initially thought that the issue was on a deprecated tab page, User Licenses, the issue appeared to be different. For reproduction, I created security roles having a requirement for 3 or 4 distinct licenses. Microsoft got access to my demo environment and was now able to reproduce the issue and solve it in the license calculation logic. This issue got fixed and released recently. I can confirm that I have the correct result now for security roles with 3 distinct licenses. In case of 4, there is another open issue where more than 3 licenses are not visible on the report today (issue 5908076).

Issue ID 5850339: Entra ID Groups

In the issue description, an issue is described about users being excluded in case they did not access the environment before. This issue was solved, but it was also possible to have users missing from reports in case they had manual role assignments and never logged in before. Together with this fix, I think this also solves it for all occasions where a user had not logged in before.

Other issues

Some updates were part of the roadmap and are not listed as known issues. In addition to license calculation and reporting issues, there were some wrong implementations of the security in standard privileges, where, e.g., read-only objects still showed up as write permission, and for that reason, required a higher license.

In case you have other issues, it is recommended to install the latest available quality update or consider an update to the most recent Dynamics 365 F&O version. If that does not solve the issue, it might be a bug that can be reported to Microsoft. In case you have custom roles, it is recommended to check the exact contents of the role for the correct access levels for all securable objects.

There is more…

During the Advent period, each day in December, I will share some thoughts and tips related to the Dynamics 365 user license enforcement. I extended the period for my series of blog posts to the last date of the year. If you have questions about this topic, feel free to contact me via LinkedIn, the comments section below, or the contact form on this blog.

Dynamics 365 Licensing Enforcement Advent Calendar

I do hope you liked this post and will add value for you in your daily work as a professional. If you have related questions or feedback, don’t hesitate to use the Comment feature below.


That’s all for now. Till next time!