Welcome to the first post of the Dynamics 365 license enforcement Advent Calendar. In the post, you will get an introduction to why Microsoft made the decision to go for license enforcement. What happened this year and even before?
Read morePosts
A large part of the year 2025, I spent time on the upcoming user license enforcement for Microsoft Dynamics 365 F&O. This involved both working with clients and spending time to help out in the community and the Viva Engage feedback forums.
Now we are coming to the end of the year and reaching (again) the date when license enforcement starts, I have one wish: All I want for Christmas is…. a correctly functioning license report for Microsoft Dynamics 365 F&O users.
Read more
Since Microsoft announced the postponement and roll-out strategy change of the license enforcement for Microsoft Dynamics 365 F&O apps, the engineering team responsible for the license consumption reporting has not been retired. Feedback provided by clients worldwide is evaluated, put on a roadmap, prioritized, and executed.
In this post, you will learn about enhancements provided to the Power Platform Admin Center (PPAC) report. This is both on the visuals as well as the data presented. This post is created based on a preview of the User license consumption report.
Read more
Image created by AI using Microsoft DesignerWorkflow and security do have a strong relationship in Microsoft Dynamics 365 Finance and Operations. A user not assigned to a workflow task can’t approve a workflow instance. Also, the user should have correct permissions from the security settings as I explained before in another blog. (Workflow security in Dynamics 365 Finance and Operations)
In this blog, I will explain the behavior of a setting available on the Workflow parameters form, called Require explicitly assigned users.
Read more