Microsoft Dynamics 365 Finance and Operations Pricing The Split That Drives Your Cost

Dynamics 365 F&O is two apps, not one - and that drives the price

The single most important fact about Microsoft Dynamics 365 Finance and Operations pricing is that F&O is not a single SKU. Microsoft split the older Finance and Operations product into two separately licensed applications: Dynamics 365 Finance and Dynamics 365 Supply Chain Management. They run on the same codebase and share data, but each is licensed, priced, and entitled independently. Together they form Microsoft's enterprise ERP core.

What this means for your budget: a user who works in both financials and supply chain is not licensed once - they need rights to both apps. Microsoft handles this through a base-plus-attach mechanic (covered below), so the combined per-user cost lands between one and two full licenses, not at 2x the headline. Understanding this split is the difference between an accurate TCO and a number that surprises you at renewal.

This guide stays strictly on pricing: the $210/$300 tiers for each app, how base-plus-attach combines them, Copilot Credit metering, the storage and environment costs most vendor pages skip, when Business Central is the cheaper fit, and three worked TCO scenarios. For feature depth on each application, see our Dynamics 365 Finance guide and our standalone Supply Chain Management pricing breakdown.

Dynamics 365 F&O pricing at a glance (2026)

All figures below are Microsoft USD list pricing, per user per month, billed yearly. Finance and Supply Chain Management carry identical list pricing - $210 for the base tier and $300 for Premium - because they sit at the same license level in the Dynamics 365 family. Actual pricing varies by currency, country, partner, and volume, and must be quoted through a Cloud Solution Provider (CSP) partner or volume-licensing channel. The table also shows the recurring cost lines that most per-seat summaries omit: Team Members, the attach rate, combined F&O bundles, additional storage, and the Tier 2 sandbox.

Premium tiers add advanced planning and analytics capabilities, higher capacity and storage entitlements, and 1,000 Copilot Credits per user per month (tenant-pooled) that power prebuilt and custom agents. Team Members licenses - at $8 per user/month - cover read access, approvals, and lightweight task entry, and they are the single most underused cost lever in F&O license mixes.

What the Finance license covers vs the SCM license

The two licenses cover different functional ground, which is why a combined ERP rollout typically needs both. The Dynamics 365 Finance license covers the financial backbone: general ledger, accounts payable and receivable, budgeting, cash and bank management, fixed assets and asset leasing, cost accounting, financial reporting, electronic invoicing, tax calculation, and globalization and localization for multi-country operations.

The Dynamics 365 Supply Chain Management license covers operations: warehouse management (including the mobile app), inventory management and Inventory Visibility, procurement and sourcing, master planning (including Planning Optimization and DDMRP), manufacturing and production (discrete, process, and lean), transportation management, landed cost, product information management, engineering change management, and quality management.

The practical split: your finance and accounting team needs Finance; your operations, warehouse, procurement, and planning team needs SCM; and power users who span both - a CFO who reviews inventory valuation, a plant controller who owns cost accounting tied to production - need combined rights. That last group is where the base-plus-attach mechanic matters most.

The Dynamics 365 F&O modules list: Finance and SCM, broken out

Because Finance and Operations is two licensed apps, the modules list splits along the same line. There is no single 'F&O modules' bundle you license at one price - you assemble capability from Finance modules, SCM modules, and the Team Members tier, and the license mix determines the bill. The table below enumerates the modules each app ships with at the base and Premium tiers so you can map job roles to the modules that justify a full-user seat versus a $8 Team Members seat.

A few patterns help with sizing. The Finance module set is heavier on GL, tax, consolidation, and compliance (electronic invoicing, multi-country globalization); the SCM module set is heavier on execution (warehouse, manufacturing, procurement, planning). Premium upgrades do not unlock new modules in most cases - they upgrade planning and analytics depth within existing modules and add the tenant-pooled Copilot Credits that power agents across both apps. For deeper feature detail per app, see our Dynamics 365 Finance guide and our Supply Chain Management pricing breakdown.

The split that drives your cost: base plus attach, not 2x base

Dynamics 365 uses a base-plus-attach licensing model. Every full-access user needs one base license - the first, highest-priced qualifying app they use. Additional Dynamics 365 apps bolt on as attach licenses at a reduced rate. Attach licenses require a qualifying base license; you cannot buy an attach without the base. Microsoft documents this as the standard pattern across most Dynamics 365 full-user licensing because it gives a single user cost-effective rights to multiple apps.

Applied to F&O: a user who needs both Finance and SCM licenses one app as their base and attaches the other at the discounted attach rate. Their combined cost is base price plus a lower attach price - not two full base prices. Per Microsoft partner documentation, the attach to a qualifying base lands around $30 per user/month (commonly cited in the $20-$30 range), so a combined F&O full user costs roughly $240 - not $420. This is the single biggest pricing lever for mid-market buyers on the platform, and the one most vendor pages skip because Microsoft does not publish attach pricing on its public pricing pages.

Where to find the real number: attach pricing, capacity entitlements, and minimums live in the Dynamics 365 Licensing Guide and Product Terms, not on the public pricing pages. You confirm the current attach rate through a Microsoft partner or your CSP at quote time. The implication for budgeting is clear: never estimate a combined F&O user at 2x $210. Estimate at base plus attach, and check whether your existing license estate already entitles a user to a base you can attach to.

Finance Premium vs base: what the extra $90 buys

Finance Premium and SCM Premium each add $90 per user/month over the base tier ($300 minus $210). The question is not whether that is a lot of money - it is - but whether the capabilities it unlocks are used by that specific seat. Premium is not a faster or more reliable version of base; it is a functional superset aimed at planning, advanced analytics, and AI agents.

The decision driver is functional, not price. Most full users - GL accountants, AP/AR clerks, warehouse leads, buyers, production schedulers - stay productive on the base $210 tier in either app. Premium is reserved for the small set of users who actually drive planning, advanced analytics, or Copilot agents: a finance director running business performance planning, a demand planner creating and editing forecasts, or anyone operationalizing Copilot agents for reconciliation or procurement.

Copilot Credits deep-dive: the F&O consumption ramp

Copilot Credits are the consumption unit that powers prebuilt and custom agents across Dynamics 365 and the Power Platform. A single credit represents one interaction between a user and a Copilot agent - counted when the agent generates a response, calls a tool, or runs a flow step. As of the November 2025 licensing update, every Premium tier (Finance Premium and SCM Premium) includes 1,000 Copilot Credits per user per month, pooled at the tenant level, that meter agents for reconciliation, cash-flow forecasting, collections, demand planning, and procurement scenarios. Base tiers do not include credits.

Two budgeting implications follow. First, because credits are tenant-pooled, a small number of heavy agent users can draw down the pool that came with your Premium seats - so the credit math is an organizational run-rate question, not a per-seat ceiling. Second, once the included pool is exhausted, additional credits bill on pay-as-you-go (PAYG) metering at $0.01 per credit, or you can pre-purchase packs of 25,000 credits for $200 per month (roughly $0.008 per credit). At the PAYG rate, a tenant that burns through a 25,000-credit pack overage pays $250 instead of the $200 pre-purchase price - so forecasting matters once you move past the included pool.

The math to model in year one: 1,000 included credits per Premium seat is worth $10 at the PAYG rate. A 25-Premium-seat tenant therefore starts with 25,000 tenant-pooled credits per month - exactly one pre-purchase pack's worth. If your roadmap leans on custom Copilot agents for finance close or supply-chain exceptions, treat the included pool as a buffer and forecast PAYG or pre-purchase overage alongside the license line. Premium is the gateway to agents; the credit pool and PAYG rate are the operating cost inside that gateway.

Hidden costs beyond the seat: storage, environments, and API

Per-seat pricing is only part of a Dynamics 365 F&O bill. Three recurring cost lines routinely surprise buyers because they meter against usage rather than headcount, and because Microsoft's included entitlements are tighter than the legacy Dynamics AX on-premises era implied. Model these from day one or they surface as a renewal shock.

Database storage overage is the largest hidden line. F&O stores transactional data in Azure SQL / Dataverse-backed databases, and additional production database capacity beyond the per-tenant entitlement bills at roughly $40 per GB per month, with non-production (sandbox) database capacity at roughly $30 per GB per month. File and blob storage (attachments, documents, images) is materially cheaper - commonly around $2 per GB per month - but the database line is the one that compounds as transaction volume and years-in-production grow. Archival and data retention policy is a real cost lever here, not a nice-to-have.

Environments are the second line. Every production rollout needs at least one Tier 2 sandbox for user-acceptance testing, and the Tier 2 Standard Acceptance Testing environment lists at roughly $1,417 per month (about $16,200 per year) as a standalone SKU - on top of the user licenses. Dev/test Tier 1 environments are cheaper or included depending on the program, but UAT and pre-production Tier 2+ environments are licensed SKUs. The third line is API and capacity metering: heavy integrations, dual-write throughput, and Power Automate flows that call F&O data can consume Power Platform request entitlements and, beyond them, pay-as-you-go API meters. None of these show up on a per-seat quote.

Minimum commitments and deployment options

Historically, Dynamics 365 Finance carried a 20-full-user minimum purchase requirement under volume licensing, with Team Member and Activity licenses not counting toward the floor. Recent Microsoft licensing changes have relaxed that floor and CSP (Cloud Solution Provider) deals are explicitly exempt from the 20-user minimum. Treat the 20-user number as a volume-licensing legacy that may or may not apply to your deal - your partner confirms it at quote time, not a hard rule to budget against.

Deployment options for F&O are cloud-native by default: Microsoft hosts the production and sandbox environments, and updates ship on a first-party cadence. Self-service environments and Tier 2+ sandboxes are add-on cost lines above the user licenses. F&O does not have an on-premises tier in the way the older AX 2012 did; if you need on-prem or disconnected ERP, that is a Business Central conversation, not an F&O one - see the Business Central crossover below and our BC vs Finance and Operations comparison.

Dynamics 365 F&O pricing in the USA: what US buyers actually pay

The $210 base / $300 Premium figures in this guide are Microsoft's published US dollar list pricing, and US buyers should treat them as the ceiling on the license line, not the invoice. In the USA, Dynamics 365 Finance and Operations is sold almost exclusively through the Cloud Solution Provider (CSP) channel and Microsoft volume-licensing partners - you do not buy it directly from a public price list. CSP partners can apply margin-based discounts and offer monthly billing flexibility, while Enterprise Agreements (EA) kick in for larger US estates and unlock better unit pricing plus Microsoft co-funding. The result is that a well-negotiated US deal commonly lands 10-25% below list on licenses.

Where US budgets diverge from list pricing is the implementation and TCO line, not the license. For US-based organizations, Dynamics 365 F&O implementation in 2026 typically ranges from $150,000 to over $1,000,000 depending on company size, industry complexity, and customization - and the rule of thumb in the US channel is that implementation runs roughly 3-5x the annual licensing cost for an enterprise-grade deployment. Migrating from a legacy system (SAP ECC, Oracle, JD Edwards, or Dynamics AX 2009/2012) adds a data-cleanup and refactoring line, with AX-to-F&O upgrades commonly falling in the $120,000-$500,000 range. Most US projects take 6-12 months to go live. The practical implication: budget the license line against the list tiers above, but model the implementation line against your complexity, not your headcount.

Two US-specific factors move the number. First, regulatory scope: US enterprises in finance, manufacturing, and distribution often need SOX, GAAP, and IRS-aligned controls, tax-engine integration, and custom financial reporting - each adds configuration cost. Industry complexity (advanced costing and BOMs in manufacturing, omnichannel inventory in retail, warehouse automation in distribution) can raise implementation cost by 20-40%. Second, partner location: US-based or US-focused partners bill higher hourly rates but typically deliver faster alignment with US regulations and lower long-term risk. Choosing the right partner is the single largest implementation-cost lever for US buyers - more than any license discount.

Business Central vs F&O: the cost crossover and when to step up

Business Central is Microsoft's SMB ERP and is dramatically cheaper per seat: Essentials at $80 per user/month, Premium at $110 per user/month, and Team Members at $8. F&O starts at $210 base / $300 Premium, with a combined F&O seat at roughly $240. On a pure per-seat basis, F&O is roughly 2x to 2.2x the cost of BC Premium, so BC is the cheaper ERP at almost every headcount - until capability, not cost, forces the move.

The crossover is functional, not numeric. F&O earns its premium when you need capabilities BC cannot deliver at scale: multi-entity financial consolidation across many legal entities, advanced process and lean manufacturing, advanced warehousing with inbound/outbound clustering and mobile execution at scale, Planning Optimization and DDMRP, high transaction throughput, and deep globalization for many countries. A common rule of thumb in the partner channel: BC fits companies up to roughly 200-300 full users with standard operations, while F&O is the right floor for complex, multi-national, or high-volume manufacturers. Below that line, BC Premium at $110 usually delivers more value per dollar than F&O at $240 combined.

Pricing by company size: 5-user, 25-user, and 100-user scenarios

Per-seat pricing scales linearly, but the right license mix - and the proportion of Team Members versus full users, and base versus Premium - changes dramatically with company size. A 5-user finance-led company has a very different mix than a 100-user manufacturer. The table below shows illustrative license-only annual costs at three sizes, holding the attach at $30, base at $210, Premium delta at $90, and Team Members at $8.

Two patterns dominate. First, Team Members grow as a share of the mix as company size grows: a 5-user company may have zero Team Members (everyone is a full user), while a 100-user company often runs 20-40 Team Members for warehouse floor, shop floor, and field roles - each one a $96/year seat instead of a $2,520/year full user. Second, the Premium footprint stays a minority of full users at every size: roughly 20-25% of full seats, reserved for planners and agent drivers, not the whole population.

Three worked F&O TCO scenarios (small, mid, large)

These are illustrative annual TCOs built on Microsoft list pricing and the attach math above - not quotes. Your actual number depends on the Finance/SCM user split, Premium footprint, attach rate, negotiated discount, number of environments, storage volume, and Copilot consumption. We model three sizes so you can see how environments and storage become a larger share of the bill as you scale.

Small scenario (5 users): a finance-led company with no supply-chain operations - a services firm or holding company. Four users on Finance base, one on Finance Premium for planning. No Tier 2 sandbox in year one (a single Tier 1 dev environment suffices), modest storage. Mid scenario (25 users): a manufacturer or distributor needing both Finance and SCM. Most full users are combined (base plus attach); five sit on Premium; one Tier 2 sandbox for UAT. Large scenario (100 users): a multi-site manufacturer with heavy warehousing and 20 Team Members on the floor, a fuller Premium footprint, two Tier 2 sandboxes, and meaningful storage overage.

3-year TCO: a worked 50-user Dynamics 365 F&O example

The TCO number that matters is cumulative, not the first-year invoice. A common striking-distance question is the total cost of ownership for Dynamics 365 Finance and Operations over a realistic planning horizon - and the right way to model it is licenses times three years, plus one-time implementation, plus recurring environments and storage across all three. The worked example below holds the assumptions constant - base at $210, Premium delta at $90, combined attach at ~$240, Team Members at $8, one Tier 2 sandbox at ~$16,200/year, and a mid-range US implementation - so you can see where the dollars land over time.

The shape of a 3-year F&O TCO is dominated by recurring licenses and the one-time implementation line, not by storage or environments. In this 50-user example, the three-year license line (roughly $400,000 at list before any discount) plus a mid-range implementation ($400,000) accounts for the vast majority of the cumulative spend; the Tier 2 sandbox ($48,600 over three years) and modest storage overage are rounding error by comparison. That is the strategic insight: negotiating the license line (right-sizing Team Members, limiting Premium, securing a CSP/EA discount) and controlling implementation scope move the 3-year TCO far more than chasing storage savings. Figures are USD list, illustrative, and exclude Copilot pay-as-you-go overage.

Dynamics 365 F&O pricing negotiation tips

List pricing is the ceiling, not the invoice. The difference between a well-negotiated F&O deal and a default one is often 10-25% on the license line and far more on implementation - but only if you negotiate the right levers. The single highest-leverage move is right-sizing the license mix before you sign: auditing actual job roles against Finance, SCM, combined, Premium, and Team Members SKUs, and defaulting light users to the $8 Team Members tier rather than a $210 full-user seat. A company that converts 20 read-only users from base to Team Members saves roughly $48,000 per year at list.

Beyond mix, four levers move the number. First, channel choice: CSP deals suit organizations below roughly 250 users because they offer monthly billing flexibility and partner margin-based discounts, while Enterprise Agreements (EA) suit 250+ seat estates and unlock better unit pricing plus Microsoft co-funding for implementation. Second, commitment length: three-year terms consistently unlock better attach rates and Microsoft funding than annual. Third, timing: Microsoft's fiscal year ends June 30, and partners carry quarter-end and year-end incentives that make late-June and December the most negotiable windows. Fourth, separate licenses from implementation: bundling them with one partner hides margin in the implementation line and weakens your leverage on both.

What a real Flectic estimate covers (and what list pricing cannot)

List pricing answers 'what does Microsoft charge per seat.' It does not answer 'what will this cost my company' because the variables that move your number - the Finance/SCM user split, the right Premium footprint, negotiated attach and volume discounts, environment tier, storage volume, and implementation scope - are partner-specific. That is the gap we close.

As a dual-platform partner implementing both Dynamics 365 and Odoo, Flectic sizes F&O license mix against actual job roles rather than defaulting every full user to the most expensive SKU. We model the Copilot Credit run-rate against your agent roadmap, forecast storage and environment costs into year two and three, and pressure-test whether Business Central or F&O is the right floor before you commit. Our AI-accelerated delivery is designed to deliver up to 3x faster than a traditional ERP rollout, which changes the implementation line of your TCO, not just the license line. The goal is a number you can defend at renewal, with no surprise attach charges.

Frequently asked questions