Dynamics Community Forum Thread Details

How to Determine the Required License for a Custom Security Role in Dynamics 365 CE

Hi everyone,

I’m looking for a tool or method to efficiently determine which license a custom-developed security role requires in Dynamics 365. Currently, I have to manually check the role’s table permissions and cross-reference them with Microsoft’s licensing documentation (PDF), which is quite time-consuming.

Is there an automated way or a best practice to streamline this process? Any tips, tools, or experiences would be greatly appreciated!

Thanks in advance!

Categories:

Dynamics 365 Field Service

Dynamics 365 Customer Service

Hello CU04111006-0,

You're facing a common challenge in Dynamics 365 administration! Manually checking permissions against licensing documentation can be tedious. Here are some tips, tools, and best practices to help you determine the required license for a custom security role:

1. Utilize the Dynamics 365 Security Role Analyzer (Third-Party Tool)

Functionality: Several third-party tools (some free, some paid) specifically designed for Dynamics 365 can analyze security roles. They often include features like:
- Automated License Recommendation: The tool assesses the role's permissions and compares them to known licensing requirements. It then provides suggestions for the minimum required license.
- Permission Impact Analysis: These tools can help you understand the licensing implications of modifying existing roles or creating new ones.
- Reporting and Documentation: Many tools generate reports that document the role's permissions and the associated licensing needs, which can be valuable for auditing and compliance purposes.

2. Leverage Dynamics 365 Licensing Documentation (with a Focus)

Refine Your Search: Instead of searching the entire PDF, focus on specific areas related to the tables and permissions used by your custom role.

Utilize Keywords: Use keywords from the table names and permissions (e.g., "Account", "Read", "Write", "Create") to quickly locate relevant sections in the documentation.

3. Create a Custom Reference Guide

Internal Documentation: Based on your analysis, create an internal document that maps common security role configurations to the required licenses. This can serve as a quick reference guide for future role development and maintenance.

4. Consider Dynamics 365 Licensing Advisor (If Available)

Check for Availability: Some Dynamics 365 versions or environments might have access to a "Licensing Advisor" feature. If available, it can provide guidance on the licensing implications of specific security role configurations.

5. Test and Validate (Crucial Step)

Create a Test Environment: Test your assumptions in a sandbox environment. Create a user with the custom role and the minimum license you believe is required.

Verify Functionality: Thoroughly test the user's access within the sandbox to ensure they have the necessary permissions without any unexpected limitations.

Key Considerations:

Licensing Complexity: Dynamics 365 licensing can be complex, with different license types (e.g., Enterprise, Professional, Team Member) offering varying levels of access.

Regular Reviews: Licensing requirements can change with Dynamics 365 updates. Periodically review and update your internal documentation or utilize tools that automatically check for licensing changes.

By combining these strategies, you can significantly streamline the process of determining the required license for your custom security roles, saving time and reducing the risk of licensing errors.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more.
If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics query.

Best Regards,
Daivat Vartak

Quick Links

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides