What You Need to Know About Licensing Methodology Updates

1. SysAdmin Role
2. Licence None
3. Deprecation of Reports
4. Modification of the licensing methodology

SysAdmin Role

If a user is assigned the SysAdmin role, whatever other roles are assigned to them, they no longer need a license.

Licence None

If you have already looked at the licenses, you may have noticed that some system objects required a “None” license type. Microsoft now strives to identify these objects and properly license them. As a result of these changes to the object licenses, you may notice that some license requirements for users, roles, tasks and privileges change when updating to this release.

Deprecation of Reports

Microsoft announced that the calculation of legacy licenses was deprecated, which impacts the features we previously used to verify the required license or the exact security configuration for a particular license level. What led to the deletion of license information on the View Permissions page.

Several reports were available in Microsoft Dynamics 365 F&O, and an explanation was available via “View permissions” on the security configuration page. This information was not always in accordance with the Dynamics 365 licensing guide and had errors. Duplicating a standard role or other object could result in different licensing requirements than intended.

Removed License column from Assign Roles to User dialog form, which can be opened from the Users form. In addition, removed License column from View permissions form, which can be opened upon clicking on View permissions button after selecting any individual role from the Security configuration form. This information will not be visible anymore.

This information was based on a calculation logic that produced erroneous results in some cases. By opening the “Assign roles to user“ window, it was possible to export the grid data to Excel to get a list of required roles and licenses.

Modification of the licensing methodology

Microsoft wants to have a single source of reliable data and has integrated the calculation of licenses in the Power Platform Administration Center (PPAC) based on security metadata, security implementation and number of users per environment. Now, this calculation takes into account not only menu items, but also other types of objects. That is why this new calculation is called object-level calculation.

The following objects are part of the calculation:

• Menu item display
• Menu item action
• Menu item output
• Data entity
• Data entity method
• Service operation

For all objects in the standard application, a list of required licenses for each object is also available, depending on the level of access. By default, all read permissions are assigned to one team member, while managing commission settings requires, for example, a Supply Chain Management or Finance license.

The object types are all related to data access or maintenance. Menu items are found in the application, where data entities and service operations are objects used by external applications. For example, a data entity can be used by virtual entities. This can in turn be a data source in a Power App.

In version 10.44, Microsoft deployed several new tables that store the analyzed license information in the Power Platform Administration Center (PPAC)