License optimisation for Dynamics 365

For mid-to-large Dynamics 365 customers, licensing is one of the largest IT cost lines — easily six or seven figures annually. The licensing model is structured but not trivially simple; without active optimisation, customers routinely overspend by 20–40%. The optimisation work is unglamorous, ongoing, and worthwhile.

The licensing structure. Dynamics 365 licenses come in several flavours, broadly:

• Base licenses — full functional access to a specific app (Sales Enterprise, Customer Service Enterprise, Finance, Supply Chain Management, Business Central Premium, etc.).
• Attached licenses — discounted licenses for users who already have a base license in another Dynamics 365 app. The "Attach" pricing rewards customers running multiple D365 apps.
• Team Member licenses — low-cost licenses for users who need read access and limited write capability across most D365 apps. Not a general write license.
• Operations Activity and Device licenses — for specialised scenarios.
• Add-ons — Copilot for Sales, AI Builder credits, additional storage, additional environments, premium connectors.

The optimisation areas.

1. Right-sizing per user. Audit users against actual usage:

• Users with base licenses who do read-only work → could be Team Members.
• Users with multiple base licenses → if they could be on Attach pricing instead, lower cost.
• Users with unused licenses — sitting in the directory but not active. Remove.
• Users at the wrong SKU tier (Professional vs Enterprise vs Premium) — match to actual feature needs.

A spreadsheet of users × licenses × actual usage (from telemetry) often surfaces 10–20% of licenses that can be downsized or removed.

2. Team Member compliance. The Team Member license is the most-abused. Microsoft has explicit rules about what Team Members can and cannot do:

• Allowed — read; update their own user record, employee record, time sheet, expense report; approval actions; consume reports; some scoped tables.
• Not allowed — post transactions, create sales orders, create / update items, run period-end routines, general data entry on transactional tables.

Tenants with Team Members doing real transactional work are non-compliant. Microsoft enforces through audit and through application-side license validation. Audit periodically; upgrade non-compliant users to full licenses or restructure their work.

3. Attached licensing. If a user has Sales Enterprise and Customer Service Enterprise:

• Without Attach — two full prices.
• With Attach — Sales at full, Customer Service at Attach (≈80% discount).

The Attach pricing is automatic in many cases but not always; verify on the Microsoft 365 admin centre that users are billed at Attach rates where applicable.

4. Unused environments. Sandboxes are mostly free up to a count; additional production environments are paid. Audit environments — old ones from finished projects, duplicates from re-orgs, abandoned proofs of concept. Decommission.

5. Storage. Dataverse storage above the included allocation bills as add-on capacity. Reduce consumption (see the capacity-planning guide) before buying more.

6. API call capacity. Tenants exceeding API call thresholds buy add-on capacity. Optimise flows to reduce calls (filter at trigger, batch operations, eliminate polling) before adding capacity.

7. AI Builder credits. Bundled with some licenses; standalone add-on otherwise. Audit consumption per model; retire unused models.

8. Connector usage. Some connectors require premium Power Automate licenses; audit which users are running premium-connector flows and whether they have the right license.

The annual licensing review.

• Q1 — actual usage report from last year.
• Q2 — identify optimisation opportunities, validate with Microsoft account team.
• Q3 — implement changes (re-assign licenses, decommission environments, restructure work).
• Q4 — review savings, plan next year's optimisation.

Annual licensing reviews routinely save 10–25% on subsequent year's spend for mature tenants.

Renewal negotiation. Major renewals (annual or three-year contracts) are negotiation opportunities. Microsoft account teams typically have room on:

• Volume discounts based on user count.
• Multi-year commitments (lower per-year rate for longer commitment).
• Bundle discounts (Sales + Customer Service + Field Service together).
• Specific promotional pricing for strategic accounts.

Engage Microsoft early; build the case from usage data.

Partner and ISV licensing. Beyond Microsoft's own licenses, ISV add-ons (country localisations, document automation, AP automation) add cost. Audit these too — which add-ons are actually used? Renegotiate or retire underused ones.

Operational discipline. License optimisation is procurement + IT joint work. Establish ownership, review quarterly, action annually.