What is the best practice with regards to what license configuration/configuration keys one should enabled in a new instance of dynamics 365?
There are many functionalities related to regional keys, or module specific keys where it is clear a company will never use.
Is best practice to enable everything?
Enable just what is likely to be used?
Strictly enable just whatever will be used?
Are you aware of official Microsoft guidance about that?
In previous versions there was a general guideline to only activate license keys related to functionality a company is likely to use, since the different keys and functionalities might not necessarily work well with each other, or introduce performance issues.
I have seen at least one case in the past where "rogue code" related to unused functionality was wreaking havoc on performance in a couple of forms.
but I wonder if anything has changed with Dynamics 365?
*This post is locked for comments