Entry Point Based Licensing (explained above). So now there are two separate licensing models in use currently: These privileges come from the roles assigned to the user via the role -> duty -> privilege hierarchy structure of the security model. The way to determine which license SKUs a user is now required to have is based on the privileges the user is assigned. There was no overarching license for either Customer Engagement or Finance & Operations, there were different areas within each application that required a particular license. The change that Microsoft made to user licensing in October 2019 was that the Operations level licensing is now broken out by application area into what are now called ‘license SKUs’. The licensing model looked like the following: From the ‘View Related Objects and Licenses for All Roles’ report in the AOT. The user interface in the View Permissions area of System Administration -> Security Configuration. You could report on the licensing either from: Team Members (will be listed as Universal in AOT). Operations (will be listed as Enterprise in AOT). 
The D365FO license types available were hierarchy based (from highest to lowest): MaintainUserLicense – user requires this license if the are assigned Update/Create/Delete to this object.ViewUserLicense – user requires this license if they are assigned Read access to this object.
In this methodology, each menu item had two separate parameters: In AX 2012 and versions of D365FO prior to October 2019, the only licensing mechanism within the system was ‘Entry Point Based Licensing’. So going forward, while I will still have individual posts on user licensing as well, this post will always be updated with the latest information. Since I’ve written multiple posts on this topic in the past, I thought it would be a good idea to combine the different posts and create a place that I can continually update with the latest information.
0 kommentar(er)
