Dynamics 365 licensing is one of the most complex areas of the Microsoft ecosystem, and organisations routinely make mistakes that result in significant overspending or compliance exposure. From buying higher-tier licences than users actually need, to misjudging Team Member limitations, misusing custom Power Apps to bypass licensing, paying double for multi-app users, and rubber-stamping renewals without review — these errors are costly and widespread. This guide details the five most common Dynamics 365 licensing mistakes, explains how each one occurs, quantifies the financial impact, and provides actionable guidance for CIOs to avoid them.
Dynamics 365 licensing is unusually complex even by Microsoft standards. Unlike Microsoft 365 where most users get a single plan, Dynamics 365 operates on a per-app model with multiple licence tiers (full user, Team Member, attach, device), each with specific use rights and restrictions. The licensing rules differ between CRM applications (Sales, Customer Service, Field Service, Marketing) and ERP applications (Finance, Supply Chain Management, Business Central), and Microsoft periodically changes the rules, pricing, and bundling options.
This complexity creates fertile ground for mistakes — and the financial consequences are significant. A single miscategorised user type across hundreds of seats can cost tens of thousands of dollars annually. Compliance violations, if discovered during an audit, can result in back-payment claims and forced purchases at list price. See CIO Playbook: Dynamics 365 Licensing.
The most common and expensive mistake is buying full Dynamics 365 licences ($65–$210/user/month depending on the app) for users who only occasionally view data, run reports, or perform very light tasks. It also occurs when licences purchased for a specific project or module remain assigned long after the use case has ended.
The root cause is typically a “set and forget” approach to licence assignment combined with overestimation of user needs during initial deployment. IT teams err on the side of caution — assigning full licences to everyone who might need access rather than assessing what each user actually does. The result is shelfware: licences assigned but unused, or licences at a tier far above what the user’s role requires.
Assess each user’s actual needs before assigning a licence. Many employees who primarily consume information or perform very light tasks (viewing dashboards, approving requests, entering time entries) can be covered by a Team Member licence at approximately $8/user/month — a fraction of the full licence cost. Periodically audit licence assignments against actual usage data from the Dynamics 365 Admin Centre. If a licence has not been actively used in 90 days, flag it for removal or reallocation. Right-sizing licences to actual needs eliminates shelfware and can produce immediate savings.
The inverse of over-licensing is misusing Team Member licences for users who perform core business functions. The Team Member licence is strictly limited to read-only or very light interactions across Dynamics 365 — viewing records, basic data entry on specific entities, and personal task management. It does not cover creating or managing sales opportunities, resolving support cases, processing invoices, managing inventory, or running core business workflows.
Organisations sometimes assign Team Member licences to users performing these core tasks either to save money or because they do not fully understand the restrictions. This creates compliance exposure: users performing actions beyond Team Member rights are non-compliant, and Microsoft has begun implementing technical enforcement that blocks restricted actions. When enforcement activates, users lose access to critical functions mid-workflow — a productivity and operational disruption on top of the compliance risk.
| Licence Type | Approx. Cost | Permitted Activities | Not Permitted |
|---|---|---|---|
| Full User — Sales | ~$65/user/month | Full CRM: manage leads, opportunities, quotes, orders, forecasting | N/A — full access to Sales module |
| Full User — Customer Service | ~$50/user/month | Full case management, knowledge base, omnichannel, SLA tracking | N/A — full access to Service module |
| Full User — Finance | ~$180/user/month | Full ERP: general ledger, AP/AR, budgeting, fixed assets, financial reporting | N/A — full access to Finance module |
| Full User — SCM | ~$180/user/month | Full ERP: procurement, inventory, manufacturing, warehouse, logistics | N/A — full access to SCM module |
| Attach Licence | ~$20/user/month | Full access to a second Dynamics 365 app when user already has a qualifying base licence | Cannot be used standalone — requires a qualifying base licence |
| Team Member | ~$8/user/month | Read-only access, personal views, basic data entry on limited entities, approve workflows | Creating/managing leads, opportunities, cases, orders, invoices, or any core business process |
Map every Team Member assignment against Microsoft’s published use rights documentation. If a user’s role involves any core business function — entering sales opportunities, resolving support tickets, processing purchase orders, approving invoices — they require the appropriate full licence. The cost difference is significant, but the compliance and operational risk of misassignment is far greater. See Licensing Dynamics 365 CRM & ERP Applications.
Some organisations attempt to reduce costs by building custom Power Platform applications on top of Dynamics 365 data and assigning users lower-cost Power Apps licences instead of Dynamics 365 licences. While this may work technically (the app can read and write to Dynamics 365 entities via Dataverse), it violates Microsoft’s licensing intent. Microsoft explicitly prohibits using lower-cost licences to indirectly access or replicate Dynamics 365 functionality that normally requires a full licence.
The rule is straightforward: if a user accesses Dynamics 365 standard entities (accounts, contacts, leads, opportunities, cases, products, orders, invoices) through any interface — whether the native Dynamics 365 app, a custom Power App, a Flow/Power Automate process, or an API integration — they require the corresponding Dynamics 365 licence. Building a custom app that reads from and writes to the same data does not eliminate the licensing obligation. Microsoft’s audit teams specifically look for this pattern.
Use Power Apps licences for genuinely custom or standalone solutions that do not interact with Dynamics 365 standard entities. If the app accesses Dynamics 365 data, users need the appropriate Dynamics 365 licence. Power Apps should extend and enhance Dynamics 365 functionality — not serve as a mechanism to evade its licensing requirements. When in doubt, consult Microsoft’s licensing documentation or engage independent advisory. See Dynamics 365 Licensing: Cloud vs On-Premises.
A surprisingly common and entirely avoidable mistake is assigning multiple standalone full licences to a single user when Microsoft’s attach licence model would cover the same access at a fraction of the cost. For example, a user who needs both Sales ($65/month) and Customer Service ($50/month) might be assigned two standalone licences totalling $115/month. Under the attach model, the same user would have one base licence (Sales at $65) plus one attach licence (Customer Service at ~$20), totalling $85/month — a 26% saving per user. For ERP applications where full licences cost $180/month, the savings from using attach licences are even more substantial.
This mistake occurs because procurement teams or administrators assign licences individually without awareness of the attach model, or because different departments purchase licences independently without coordination. In large organisations with hundreds of Dynamics 365 users, duplicate standalone licences can add hundreds of thousands of dollars in unnecessary annual spend.
Audit every user with more than one Dynamics 365 licence. In virtually all cases, one licence can be converted to an attach licence as long as the user has a qualifying base licence. The base licence should be the highest-priced application; additional applications are then licensed as attachments. Work with your Microsoft representative or licensing partner to switch duplicate standalone licences to base+attach. This correction yields immediate, significant savings with no loss of functionality.
Many organisations renew their Dynamics 365 licences year after year with the same quantities and types without re-evaluation. Business needs change: departments grow or shrink, projects end, modules are adopted or abandoned, and users change roles. If licensing is never revisited, the organisation pays for an outdated configuration that no longer reflects reality. Additionally, Microsoft periodically introduces new licence types, bundles, or pricing that could better suit current needs — but organisations that auto-renew never discover these options.
The financial impact compounds over multi-year EA terms. An organisation carrying 50 unused full licences at $100/user/month for three years pays $180,000 for software nobody uses. That same budget could fund additional cloud services, migration projects, or training programmes that deliver actual business value.
Treat every renewal as an opportunity to recalibrate. Before renewing, audit current usage: identify licences that are unused, underused, or assigned to the wrong tier. Check whether Microsoft has introduced new options that better suit your needs. Adjust licence counts and mix to match the current state. Begin renewal planning at least 6 months in advance to allow time for analysis, internal alignment, and negotiation. See Negotiating Dynamics 365 Volume Discounts and Dynamics 365 in Enterprise Agreements: EA vs CSP.