Normally licensing is a big puzzle for Dynamics 365 projects. Mostly because of the combination of products which comes as part of the implementation and the flexibility Microsoft provides with different licensing models for each of these projects. Even the experienced gets confused with this part without any doubt. I am one among them and by mere coincidence recently, I came across a gem of information from Mathew Burr regarding this.
Normally to understand and finalise on any licensing model, we need to go through the licensing guide which is little lengthy in nature and by the time we complete that guide there could tons of questions when we try to relate that to the components we might use in our project. That is where Mathew’s cheat sheet or licensing matrix comes handy for most of the consultants. He has nailed it along with his colleagues Jukka Nirranen and Richard Burdes.
I would like to share the same with our other fellows as well as this can save many of our times to at least get a vague idea in what we might need from a licensing perspective. Thanks once again to Mathew Burr, Jukka Nirranen and Richard Burdes for your time to get this ready for each one of us.
Original post I am referring to can be accessed here. Also attaching the pdf version in case you face any difficulty accessing the original post. All credits/copyrights to the original owners of this document.