See who needs which Dynamics 365 license, and what the gaps are costing you.
F&O License Management compares the licenses your users' security roles require with the licenses assigned in Microsoft 365 and the seats you've bought. Finance and IT see the violations to fix and the licenses they're paying for but don't need.
- Role-based license requirements
- Base and attach licenses
- Monthly cost impact
- Read-only on security data
Illustration shows example data.
Each user is classified, with a note explaining why
Compliant
The assigned licenses cover what the user's security roles require.
Under-licensed
The user's roles need more than the assigned license, for example a Full license where only Team Members is assigned. The workspace names the role driving the requirement.
Unlicensed
Roles grant access in Finance & Operations, but no Finance & Operations license is assigned in Microsoft 365.
Over-licensed
Assigned licenses exceed what the roles require. Users who are disabled or have no roles but still hold licenses are flagged too.
Needs review
Something needs a decision, such as roles that haven't been mapped to a license level yet.
Four inputs, one calculation
- 1
License catalog
List your Dynamics 365 license SKUs with the application they cover, monthly price and seats purchased.
- 2
Role mapping
Set the license level each security role requires per application: Team Members, Activity or Full.
- 3
Assignments
Record the licenses each user holds in the Microsoft 365 admin center, and snapshot their current F&O roles.
- 4
Calculate
Run the compliance engine on demand or as a scheduled batch job, then review the results in the workspace.
Built around how Dynamics 365 licensing actually works
- Rules
Base and attach logic
A user needing Full access in several apps gets one base license and attach licenses for the rest. Higher licenses cover lower requirements, and an attach license without a base is flagged.
- Coverage
Across the F&O applications
Requirements are tracked for Finance, Supply Chain Management, Commerce, Project Operations and Human Resources.
- Seats
Purchased vs assigned vs required
For every SKU, see seats bought, seats assigned, seats the roles require, unassigned seats, and the purchase and assignment gaps.
- Cost
The money in each gap
Monthly prices turn the results into the shortfall needed to fix violations and the overspend on licenses nobody needs.
- Drill-down
From violation to role
Select a user to see their security roles and the license each one requires, so you know whether to change the license or the role.
- Safety
Read-only on your security
The engine only reads standard user and role data. It writes to its own tables, never to standard security or user records.
- Automation
Scheduled refresh
Recalculate interactively or as a recurring batch job, with an option to reload the latest user role assignments each time.
- Onboarding
Sample tenant included
Load a demonstration data set with deliberate compliance issues to explore the workspace and train your team.
- Access
Manager and viewer roles
Managers maintain SKUs, role mappings and assignments and recalculate. Viewers get read-only access to the workspace.
License Management at a glance
- Platform
- Dynamics 365 Finance & Supply Chain Management
- Status
- Available
- Supported versions
- Dynamics 365 Finance & Operations. Supplied as a deployable package for your version.
- Deployment
- Deployable package applied through Lifecycle Services or the Power Platform admin center, sandbox first.
- Documentation
- Setup guide and reference
- Licensing
- Contact us for licensing and pricing
- Microsoft Marketplace
- Contact us for access
The illustration on this page uses example data. Request a demo to see the product with scenarios like yours.
More TSL Labs extensions
Not sure your licenses match your security roles?
Let's run the numbers before your next renewal or Microsoft review.