Dynamics 365 Finance & Operations License Review

Summary

Dynamics 365 Finance & Operations License Review

Purpose:

The customer wants to ensure that Dynamics 365 Finance and Operations licenses are correctly assigned based on actual job roles and business needs. Currently, some users have more access than required, which creates security risks and unnecessary cost.

This engagement will review current licenses and recommend the right license type for each user role.

________________________________________

Objectives

• Check current Dynamics 365 license assignments

• Understand what users actually do in the system

• Reduce unnecessary high privilege access

• Recommend the correct Microsoft license per role

• Improve security and control license costs

________________________________________

Scope of Work

1. Review Current Setup

• Review current Dynamics 365 licenses in use

• Review user security roles and access levels

• Identify users with excessive or incorrect licenses

Output:

• List of current users, roles, and licenses

________________________________________

2. Understand Business Needs

• Meet with key stakeholders (Finance, Operations, IT)

• Identify user types (e.g. accountant, approver, viewer)

• Understand how each role uses the system

Output:

• Simple list of business roles and system usage

________________________________________

3. License Gap Analysis

• Compare business roles vs. assigned licenses

• Identify:

o Over licensed users

o Under licensed users

o Security risks

Output:

• Clear summary of licensing issues and risks

________________________________________

4. License Recommendations

• Recommend the correct Dynamics 365 license type per role

• Propose a cleaner, role based license structure

• Highlight potential cost savings and risk reduction

Outputs:

• Recommended license per role

• Updated user to license mapping

________________________________________

Deliverables

1. Current license and access review

2. Business role vs. system usage summary

3. License mismatch and risk findings

4. Recommended license model

________________________________________

Out of Scope

• System configuration or development

• Functional changes or training

________________________________________

Success Criteria

• Users have only the access they need

• Licensing is Microsoft compliant

• Reduced security risk

• Clear, documented licensing structure