Caf2Code LLC’s Post

Your Dynamics 365 custom roles are costing you money. Lots of it. Seriously. How? Security roles consist of:  • privileges  • duties  • sub-roles Each of these grants a certain level of specific access. Most of the time, out-of-the-box roles consist of access that triggers one license type. The "Human resource manager" role has privileges and duties that touch the full HR base license. This one license - one role model quickly changes with custom roles. Let's look at one example A company gets RandomConsultant to implement Dynamics for them. RandomConsultant likes to churn through clients. 😤 They create roles without any thought. NosyNancy tells RandomConsultant she needs this list of access. RandomConsultant creates the role with NosyNancy's wishlist. The role? With only five duties assigned to it? Triggers five FULL licenses. That's a really expensive role. This is an extreme example but the message still stands. You must review your custom roles. Evaluate the necessities of the end-users. Does NosyNancy really need to be able to update employee marital status? Drill into the duties, and privileges to ensure you have only what you need And nothing more. Microsoft can tell if you are using modules outside of your license. It doesn't pay to be out of compliance. And it doesn't bring you value to be overlicensed either. To Recap: • Create security roles with licensing in mind. • Only assign duties and privileges to roles that are absolutely necessary. • Do not assign roles to users who don't need that level of access. • Create a system for regularly evaluating your licensing and roles to stay compliant. What am I missing? If this is all too much, don't worry the Caf2Code LLC team is happy to help. Reach out to us for more information and to answer your questions. --- PS Follow #Caf2Code for insights and tips from our team.