With the launch of Release 10.0.12/PU36 rolled-out this month, there will be some licensing changes, which I will share with you here:
The types of licenses available are:
* Base is the $180 USD unit price license.
** Add on is the $30 USD license.
License analysis is now performed through a combination of entry point and privilege level license. The entry point analysis shows how many Team Member, Activity and Operations licenses are needed. The privilege level analysis is used to determine what type of license level a user needs for Operations (Finance, SCM, Talent, Retail).
How to determine a user’s license requirements
The entry point license level analysis is used to determine the amount of Operations, Team Member and Activity licenses required. The report located in the following route is used to carry out this process: System Administration -> Queries -> License -> User Licenses Count.
In order to perform the license privilege level analysis needed to determine the Operations license level the user actually needs to be assigned (Finance, Supply Chain Management, Talent, Retail or Projects), the report located in the following route is used: System Administration -> Queries -> License Reports -> User License Estimator.
There is an excel file to aid this process that shows the association between privileges and licenses. This result is extracted from the LicensingServicePlansPrivilege table within D365F&SCM. This file shows the privilege and license required, as well as a column named “IsUnique“.
In the “IsUnique” column:
- If the value is FALSE, it means the user must have at least one of the Activity or Team Member licenses assigned to them.
- If it is TRUE, the user must have that particular license assigned as a “BASE” or “ADDON” license. This is due to the fact that certain privileges access areas that are “shared” across different D365F&SCM modules, and, as such, they must be accessed by multiple types of different licenses.
The following process must be followed:
- Step 1: Determine whether the user has a role assigned that contains a privilege defined by Microsoft in order to require one of the new license SKU’s. If that is the case, a license is applied based on privileges by using the attached Excel file, which shows the association between privileges and licenses SKU.
- Step 2: Determine whether a user has an object assigned that requires an Operations license in accordance with the entry point license methodology. If that is the case, the user must have at least 1 base license assigned to them.
- Step 3: If neither one of the first two criteria are met, the license based on the entry point takes over to determine whether the user requires an Activity or Team Member license.
Modification of standard privileges (grant additional access or eliminate access)
- Customized Privileges
- If a customized privilege is created that requires an Operations level license, it will be included in Step 2 described above.
- On the contrary, if the customized privilege does not require an Operations level license, it will be included in Step 3 described above.
- If it is a privilege defined by Microsoft to require one of the new license SKU’s, then the privilege license SKU logic still applies.
- If a modification is made to a license that would require an Operations level license, it would be included in Step 2 described above.
- Otherwise, the privilege modified after the license based on the entry point takes over to determine whether an Activity or Team Member license will be required.
The standard Security Roles that come with Dyn365F&SCM also help determine which type of license you may need.
If you have any doubts regarding how this update affects your licensing, we can provide assistance on how to normalize your licensing. Don’t hesitate to contact us at Dynamics365team@alfapeople.com.