What Dynamics 365 and Power Apps Really Cost to Run in 2026: Licences, Capacity and Hidden Lines

What are the Microsoft list prices for Dynamics 365 per user in 2026?

The table gives Microsoft's US list prices in USD per user per month, paid yearly, as shown on each product's pricing page (checked on 31 October 2026). Microsoft states on those pages that the figures are for information, that the actual price can differ by currency, country and region, and that the price you pay appears at checkout or on your reseller's quote. Treat the table as the starting line of a budget, not as a quote.

Two things are deliberately missing. The attach prices (the lower price for a second Dynamics 365 app on the same user) and the price of the Customer Engagement Team Members licence are not shown on Microsoft's product pages, so we do not repeat a number here: check the Dynamics 365 Licensing Guide or your reseller. Copilot Credits are sold separately on several of these plans, as each pricing page notes.

What do Power Apps and Power Pages cost on top of Dynamics 365?

Power Apps Premium is 20 USD per user per month, paid yearly, and 12 USD per user per month for organizations that commit to at least 2,000 licences; the Developer Plan is free for building and testing (Power Apps pricing, checked on 31 October 2026). The same page lists the Dataverse database capacity add-on at 40 USD per GB per month, pooled at tenant level.

Power Pages is priced per website, not per employee. Authenticated users cost 200 USD per pack of 100 users per site per month, and anonymous users 75 USD per pack of 500 users per site per month, both paid yearly (Power Pages pricing, checked on 31 October 2026). Each authenticated user counts against one website per calendar month, so a partner portal and a customer portal are two lines, and the packs are bought in whole units. If you are still deciding whether you need a portal at all, the Power Pages or custom front end guide covers that choice.

What can a Team Members licence do, and where do the limits bite?

Team Members is the light licence for people who mostly read, approve and make small updates. Microsoft's Business Central pricing page describes it as limited access to read data, approve workflows and create or update select information, at 8 USD per user per month paid yearly (checked on 31 October 2026). The Customer Engagement Team Members rights are defined in the Dynamics 365 Licensing Guide, and they are narrower than most buyers assume.

The common mistake is to plan the budget on Team Members for people who will in practice work opportunities, cases or orders every day. That is a licence compliance gap waiting for the next true-up, and it usually surfaces when the renewal is already on the table. The second limit is technical: Team Members, like Microsoft 365 licences with Power Platform access, carries 6,000 Power Platform requests per 24 hours, against 40,000 for a full paid licence (request limits).

• List every role and what it actually does in the system in a normal week, not what its job title suggests.
• Check each light role against the Licensing Guide use rights before the budget is signed off.
• Re-check after go-live: roles drift, and a reader who starts editing records needs a full licence.

How does base plus attach licensing change the per-user cost?

Dynamics 365 is licensed as a base app per user plus attach licences for further Dynamics 365 apps on the same user, at a lower price than a second full licence. A salesperson who also handles service cases needs a base licence for one app and an attach licence for the other, not two full licences. The rules on which apps can be attached, and at what price, are in the Dynamics 365 Licensing Guide.

Attach licences have a side effect people miss: Power Platform request limits come only with the paid base licence, and an attach licence adds no requests of its own (request limits). If you are reworking an estate at renewal, the renewal negotiation guide covers how to restructure the mix, and the procurement guide explains what a partner or reseller adds to the list price.

What happens when you outgrow your Dataverse storage capacity?

Dataverse storage is a capacity line, not a per-user line. The tenant receives database, file and log capacity from its licences, and the Power Platform admin center shows how that entitlement is calculated, including per-licence accruals. The default environment includes 3 GB of database, 3 GB of file and 1 GB of log capacity (Dataverse capacity). Above the entitlement, the database add-on is 40 USD per GB per month at list (Power Apps pricing, checked on 31 October 2026).

Running over is not just a billing event. Microsoft documents a progressive overage lifecycle: when the tenant first exceeds its effective capacity, creating, copying, restoring and recovering environments is blocked; after 30 days unresolved, affected sandbox environments are limited to administrators; after 90 days, sign-in to those sandboxes is blocked (Dataverse capacity). The usual drivers are audit history, email and attachments stored in Dataverse, and full copies of production into sandboxes. Our guide to Dataverse storage capacity cleanup covers how to bring it back under the line.

Which other lines do buyers miss: premium connectors, request limits and sandboxes?

These lines rarely appear in a first quote and often appear in the second year. None of them is large on its own; together they are the gap between the licence spreadsheet and the invoice.

• Premium connectors. Flows and apps that use premium connectors, such as HTTP calls or many third-party systems, need premium licensing for the users who run them, or a capacity licence on the flow. Check each integration against the Power Platform Licensing Guide.
• Request limits. A paid Dynamics 365 or Power Apps Premium user gets 40,000 Power Platform requests per 24 hours; Team Members, Power Apps per app and Microsoft 365 users get 6,000. Integration accounts draw on a tenant pool of 500,000 requests plus 5,000 per Dynamics 365 Enterprise or Professional licence, up to 10,000,000, and a Power Platform requests add-on raises a user limit by 50,000 (request limits).
• Process licences for heavy flows. A throttled cloud flow is fixed with a Process licence (250,000 requests per 24 hours per licence), not with the requests add-on, which cannot be assigned to a flow (request limits).
• Sandbox environments. Every sandbox consumes Dataverse capacity, and a full copy of production can double your database use overnight. Decide how many sandboxes you really need and whether they need production data.
• Copilot Credits. Several plans list agent and Copilot capabilities that require Copilot Credits sold separately, as the Customer Service pricing and Finance pricing pages state.
• Implementation, support and an internal owner. These are not Microsoft lines, but they sit in the same budget and outlast the project.

How do you build a total cost of ownership for Dynamics 365?

Build it per year, per line, for at least three years, and keep the Microsoft lines apart from the people lines so each can be challenged on its own. We do not repeat a worked model here: the Dynamics 365 vs Zoho One 3-year cost model shows one for 50 users, line by line.

Which licences does an ERP buyer need: Business Central or Finance and Operations?

The list prices differ by a wide margin, 80 or 110 USD per user per month for Business Central Essentials or Premium against 210 USD for Finance or Supply Chain Management (checked on 31 October 2026), but the licence price should not decide the product. Business Central suits small and mid-sized organizations with standard finance, inventory, projects and light manufacturing. Finance and Operations suits multi-entity organizations with deep supply chain, production or multi-country finance needs. Choose on fit, then budget the licences.

Solzet implements both: see Dynamics 365 Business Central and Dynamics 365 Finance and Operations. If you also run Customer Engagement, the integration between CRM and ERP is designed by the same team.

When does per-user licensing make a custom-built CRM the better route?

Per-user licensing is the right model when most users work deeply in the product and benefit from what Microsoft keeps adding. It becomes the wrong model when you are paying full licences for many people who use a handful of screens, when the process is unusual enough that you customise around the product rather than with it, or when you need to own the code, the data and the hosting outright.

In those cases a custom-built CRM on React, Node.js, PostgreSQL or .NET carries no per-user licence at all, but it brings other obligations: hosting, maintenance, security patching and an owner for its whole life. The build versus licence decision guide sets out the rule, the guide to what it really costs to build a CRM covers the cost drivers, and Custom CRM Development describes how Solzet delivers it.