Microsoft recently released the 10.0.14(PU38) version of D365FO and along with that came a couple of changes for user licensing.

Resource Updates

I have updated the privilege to license SKU report that is available as a free resource from Fastpath.

This report will show the privilege to license SKU association and then the IsUnique value for that particular privilege license combination. This report is not available within D365FO and without this data it can make it very difficult to determine the license that would be required for a user when assigning roles or designing security to keep licensing in mind (unless you are using something like Fastpath Assure to help).

License Type Changes

There are now four Base license types:

  • Finance (Finance)
  • SCM (Supply Chain Management)
  • Retail (Retail)
  • ProjectOperations (Project Operations)

And there are six Attach license types:

  • Finance (Finance)
  • SCM (Supply Chain Management)
  • Retail (Retail)
  • Talent (Talent)
  • EAM (Asset Management)
  • ProjectOperations (Project Operations)

What’s the deal with privileges labeled with OPERATIONS licenses?

If you are utilizing the Excel file from above, you may notice that there are some privileges labeled as requiring an OPERATIONS license with a IsUnique value as FALSE. So what license is required in this situation?

 

This appears to be Microsoft’s way of simplifying the way privilege licensing is stored and is used for any privilege that requires any base license for compliance. So instead of listing the privilege multiple times for each base license with a IsUnique of FALSE (like you can see in the top screenshot) now they can just list it once with a license type of OPERATIONS with an IsUnique value of FALSE. It does not appear that Microsoft at this point in time is going back and changing how they are storing privilege license associations for privileges that were already assigned a license, but going forward it appears for new privileges that require a base license they will be using this method.

Conclusion

I’ll keep posting these types of updates as long as Microsoft keeps modifying their licensing plans. As always, if you have any questions feel free to reach out!