$210 per user per month is the number everyone quotes for Dynamics 365 Finance and Supply Chain Management. It's real, but it's only the first line of the bill. Below is every other line a mid-size company tends to pay, with Microsoft's own licensing rules where they exist and a worked example you can redo with your own counts.
The short answer
- The full-user license is usually the biggest single line, but in our illustrative example it's only about half to three-quarters of the annual bill.
- The rest comes from attach and lighter licenses, environments, Azure, ISV add-ons, Power Platform, partner support, and testing Microsoft's updates.
- Partner support is the swing factor. At 15–25% of the original implementation a year, it can rival the license bill.
The license layer: four user types, one rule that matters
Microsoft raised Finance and Supply Chain Management from $180 to $210 per user per month on October 1, 2024, for new customers and for existing customers at renewal. The Premium tiers list at $300.
Microsoft's Dynamics 365 Licensing Guide (November 2026) sets out the user types:
- Base license. Every full user needs one, and it must be the highest-priced app that user has.
- Attach license. A cheaper license for each additional app the same user needs. ERP Research lists Finance and SCM attach at $30 per user per month. Attach licenses add no extra storage.
- Operations – Activity. For users who need more than Team Members but not full rights. ERP Research lists it at about $50.
- Team Members. Read-only access to Dynamics 365 data plus designated light tasks, such as expense entry. ERP Research's price list shows $8.
The guide also lists minimum purchases. Supply Chain Management, Commerce, and Project Operations each carry a 20-seat minimum.
In finance and operations apps, the security roles you assign decide which license a user needs, according to Microsoft Learn. One over-broad role can turn a $50 user into a $210 one. That's why role design is a cost decision, not just a security one.
Capacity and environments
For Finance and SCM, the licensing guide lists a tenant default of 90 GB of database and 80 GB of file capacity, plus 5 GB of each for every full user. At a few hundred users that's a lot of room. Storage overages tend to hit Dataverse-based apps, such as Sales and Customer Service, harder. Their default is 30 GB of database, plus just 250 MB per Enterprise user. ERP Research cites overage at $40 per GB per month.
Environments are a quieter cost. Each subscription includes one production environment and one Tier 2 sandbox. ERP Research puts additional Tier 3 and higher sandboxes, used for performance testing or a gold copy, at $1,500–$5,000 a month each.
Power Platform, Azure, and Copilot
Dynamics licenses include some Power Platform rights, scoped to the Dynamics app. Apps built outside that scope need their own licenses. Microsoft lists Power Apps Premium at $20 per user per month.
Azure bills separately for integration, data, and reporting workloads. Top Dynamics Partners, an independent directory, estimates $500–$5,000 a month for Azure and the same range for each ISV add-on.
Copilot is now part of the pricing structure too. Microsoft's Finance pricing page says Copilot Credits are required to run prebuilt and custom agents. Finance Premium includes 1,000 credits per user per month. Otherwise, you buy them separately.
Partner support and release testing
The ERP Software Blog, writing for a Microsoft partner, puts ongoing support at 15–25% of the original project services each year. Top Dynamics Partners estimates implementation at $1.5M–$3M+ for 300 or more users.
Updates arrive whether you're ready or not. Microsoft Learn says finance and operations apps get four service updates a year, in February, April, July, and October. You must take at least two, and you can pause only one in a row. Top Dynamics Partners estimates regression testing at $5,000–$15,000 per update cycle.
A worked example
This uses the 500-user company on our site: 350 full users and 150 activity users. We've added illustrative assumptions for the other lines. Change any of them to match your contract.
| Line | Assumption | Per year |
|---|---|---|
| Full users | 350 × $210 × 12 | $882,000 |
| Activity users | 150 × $50 × 12 | $90,000 |
| Attach licenses | 100 users on both Finance and SCM × $30 × 12 | $36,000 |
| Team Members | 200 occasional users × $8 × 12 | $19,200 |
| Extra sandbox | One Tier 3+ at $1,500–$5,000 a month | $18,000–$60,000 |
| Azure | $500–$5,000 a month | $6,000–$60,000 |
| ISV add-ons | Two at $500–$5,000 a month each | $12,000–$120,000 |
| Power Apps Premium | 50 users × $20 × 12 | $12,000 |
| Partner support | 15–25% of a $1.5M–$3M implementation | $225,000–$750,000 |
| Update testing | 2–4 cycles × $5,000–$15,000 | $10,000–$60,000 |
| Total | At list price | About $1.31M–$2.09M |
Illustrative only. The $210 and $50 licenses ($972,000) make up 47–74% of the total. Over five years, that's about $6.55M–$10.45M before discounts or price increases. Copilot, storage overages, and internal staff aren't included.
Two things stand out. First, discounts on the per-user price only touch part of the bill. Second, the lines that grow fastest, partner support and add-ons, are the ones you control least at renewal.
Worked example from this guide: about $1.31M–$2.09M a year in total. Prices from Microsoft and ERP Research.
View the data
| Line | Per year |
|---|---|
| Full users | $882,000 |
| Partner support | $225,000–$750,000 |
| ISV add-ons | $12,000–$120,000 |
| Activity users | $90,000 |
| Extra sandbox | $18,000–$60,000 |
| Azure | $6,000–$60,000 |
| Update testing | $10,000–$60,000 |
| Attach licenses | $36,000 |
| Team Members | $19,200 |
| Power Apps Premium | $12,000 |
| Total | About $1.31M–$2.09M |
What to do with this
Rebuild this table with your own invoices. Your partner statements of work, Azure bills, and ISV contracts usually sit in different budgets, so nobody sees the total. Once you do, you can decide which lines to cut, which to renegotiate, and which workflows would be cheaper to own outright. We build that last option, so weigh our view accordingly. Our Escape Path rebuilds those workflows with AI agents built in, moves finance and payroll to cloud products, and switches the old system off in 24–30 months. Pricing depends on scope, so we model it with your own numbers first.
Six questions to answer about your Dynamics bill
- How many full users actually need full rights, based on their roles, not their job titles?
- Which users carry attach licenses for apps they rarely open?
- What do we spend on partners each year, as a share of the original implementation?
- Which ISV add-ons and extra environments are still earning their keep?
- Who tests each service update, and what does that cost us in hours?
- What is our true five-year total, with all the lines above included?
Where to go from here
Put your real numbers into the model and see the full picture. If you'd like a second opinion, tell us what you run and what you pay, and we'll tell you honestly where the money is going. You can also see how a staged approach works on our Escape Dynamics 365 page.
Sources
- Microsoft: New pricing for Dynamics 365, effective October 2024
- Microsoft: Dynamics 365 Finance pricing
- Microsoft: Dynamics 365 Licensing Guide (November 2026)
- ERP Research: Dynamics 365 Finance and Operations price list
- ERP Research: Dynamics 365 pricing
- Microsoft Learn: Stay compliant with user licensing requirements
- Microsoft Learn: Power Platform licensing FAQs
- Top Dynamics Partners: Partner pricing
- ERP Software Blog: What does it cost to implement D365 Finance & Supply Chain Management?
- Microsoft Learn: Service update availability for finance and operations apps