Dynamics 365 Project Operations, Licensing, Pricing & SME Fit

What Dynamics 365 Project Operations actually is

Dynamics 365 Project Operations is the application Microsoft built for project-based organizations—consulting, professional services, engineering services, and any business that sells, staffs, delivers, and bills work as projects. Microsoft's product overview describes it as bringing sales, resourcing, project management, and finance teams together in a single application. It evolved from Dynamics 365 Project Service Automation (PSA), which reached end of support on October 1, 2024 and end of life in March 2025 (Microsoft Learn, PSA overview).

It exists as a separate application, rather than only as a module inside Business Central, because of depth. Project Operations adds specialized capabilities a general ERP does not ship with: project-based sales with multidimensional pricing, Universal Resource Scheduling shared with Dynamics 365 Field Service, Microsoft Project for the Web as the planning engine, subcontracting with three-way match invoicing, and flexible proforma plus customer-facing invoicing. Where Business Central Projects is project accounting bolted to an ERP ledger, Project Operations is a full front-to-back project business application (Microsoft Learn, Universal Resource Scheduling overview).

It is sold in the Dynamics 365 family, runs on Microsoft Dataverse for sales/planning/resourcing/delivery, and in its Integrated deployment connects to Dynamics 365 Finance (and optionally Supply Chain) for GL, revenue recognition, and WIP—typically via dual-write. Flectic implements it alongside Business Central and Odoo, and we are explicit about which platform is the right fit for a given SME, because the wrong choice is expensive. For the lighter project-accounting path, see our Business Central Jobs & Projects guide.

Dynamics 365 Project Operations licensing and pricing (2026)

Project Operations is licensed at $135.00 per user per month, paid yearly, with a free trial available, according to the official Microsoft pricing page (verified August 2026). That base license covers the front-office project lifecycle end to end: deal management, work planning, resourcing, project execution, subcontracting, and billing and proforma features.

The base license specifically covers deal management (multiple contract types, lead-to-contract, CPQ for services), work planning (scheduling, Gantt and Kanban, estimates and budgets, templates), resourcing (skills management, requests, booking reconciliations, workforce planning), project execution (time, expense, and material usage, mobile apps, policies and rules, budget tracking and earned value), subcontracting (capacity planning, vendor onboarding, goods and services delivery, three-way match invoicing), and billing and proforma features (unbilled and billed backlog, not-to-exceed limits, invoice review, edits, and adjustments).

List price alone is not how most multi-app Dynamics customers actually buy. Microsoft's base-and-attach model means the first Dynamics 365 app on a named user is charged at full price (the base), and additional qualifying apps can be attach licenses at a lower rate. Partner licensing guides commonly cite Project Operations attach in the roughly $20–$30 per user/month range when the user already holds a qualifying base license such as Sales Enterprise, Customer Service Enterprise, Field Service, or Finance—exact attach eligibility and price must be confirmed against the current Dynamics 365 Licensing Guide and Product Terms for your agreement (AlphaBOLD 2026 licensing guide; SA Global; Rand Group).

Light users—consultants who only enter time and expenses, update their own resource competencies, or apply for open project positions—often fit the Dynamics 365 Team Members license rather than a full Project Operations seat. Team Members is a named-user subscription for lightweight scenarios; for Project Operations the designated experience is Project Resource Hub. Partner pricing guides consistently list Team Member at about $8 per user/month; Microsoft Learn documents the use-rights boundary, and using Team Member for full project-manager work is out of compliance (Microsoft Learn, Team Members license; Rand Group).

Two TCO gotchas still catch SMEs. First, AI agents for time, expense, and approvals run on Copilot Credits (pay-as-you-go or prepaid Commit Units) and require an Azure subscription—they are not included in the $135 base license (Microsoft Project Operations pricing page). Second, partner explainers commonly note a minimum purchase of full-user licenses for Project Operations (often cited as 20 seats); treat that as a commercial constraint to verify in Product Terms before you model a ten-person pilot (Rand Group; Dynamics Square).

Worked example for a mid-size professional services firm (list prices, illustrative—not a quote): 10 project managers / engagement leads on full Project Operations at $135 = $1,350/month. Thirty billable consultants who only submit time and expenses on Team Member at about $8 = $240/month. Combined named-user software ≈ $1,590/month before Copilot Credits, Finance attach (if Integrated), Power Platform capacity, and implementation. If those same 40 people all took full PO seats, list software alone would be 40 × $135 = $5,400/month—license mix is usually where SMEs win or lose the TCO case.

Deployment types: Core, Integrated, stocked vs non-stocked

Microsoft no longer frames Project Operations as a single product with cosmetic toggles. Deployment type is structural: it decides where project accounting lives, whether dual-write is in play, and whether you can manage stocked materials on projects. Microsoft Learn currently steers buyers with a deployment questionnaire toward Project Operations Core, Project Operations Integrated with ERP, or Project Operations for manufacturing (Microsoft Learn, Determine your deployment type).

Project Operations Core (what many older guides still call Lite) runs sales process for projects, Project for the Web planning, multidimensional pricing, unified resource management, time and basic expense, material usage, budgeting and time-phased forecasting, subcontracting, and proforma invoicing for project-manager review—on Dataverse. It is the right path when finance stays in a third-party ERP (or you are not ready for Dynamics 365 Finance) and you need modern project sales and delivery without ripping out the GL.

Project Operations Integrated with ERP adds full expense with receipt OCR, proforma and customer-facing invoicing, and revenue recognition, with Finance (and dual-write) in the loop. Dual-write creates a bi-directional, near-real-time bond between Dataverse and Finance/Supply Chain so project actuals, contracts, and accounting stay aligned without a custom integration program (Microsoft Learn; partner dual-write project-billing write-ups).

Stocked versus non-stocked (resource-based) is the other axis buyers confuse with deployment type. Non-stocked/resource-based scenarios fit pure professional services: labor, expenses, and non-inventory materials. Stocked/production-order scenarios add inventory, production orders, and project materials that hit the warehouse—historically stronger in manufacturing-oriented Project Operations for manufacturing, with modern integrated deployments also supporting stocked products when the right features and dual-write maps are enabled (Microsoft Learn, managed stocked products). Microsoft documents that stocked and non-stocked capabilities can coexist in one environment via legal-entity configuration.

There is no out-of-the-box migration between deployment types. Choosing Core when you actually need Integrated WIP and revenue recognition—or Integrated when you only needed Core—creates a re-platforming problem later. For an SME, the practical implication is that the $135/user/month license is never the whole cost picture: Core keeps finance elsewhere; Integrated adds Finance (and often dual-write program work) on top. Scope deployment type before you sign seats.

Project planning with Microsoft Project for the Web

Project planning in Project Operations uses Microsoft Project for the Web as its scheduling engine. Work is decomposed through work breakdown structures (WBS) that break a project into tasks, and each task carries scheduling detail: predecessors, effort estimates, and dependencies. The same structure supports Gantt and Kanban views, plus estimates and budgets that roll up to the project level, and reusable project templates.

Cost estimation is multidimensional. The WBS captures estimated cost and revenue across labor, materials, expenses, and fees, so a project manager can model a fixed-price engagement, a time-and-materials engagement, or a mixed contract on the same planning surface. Estimates flow into resourcing, billing, and earned-value tracking without re-keying.

For SMEs already in the Microsoft ecosystem, the Project for the Web foundation is a practical advantage: the planning surface is familiar to anyone who has used Microsoft Project, and it shares a data model with the rest of Project Operations, so a change to a task propagates to resource assignments, cost estimates, and the billing backlog without integration work. That is different from buying Project for the Web alone as a planner—without Project Operations you do not get the project sales, URS resourcing, proforma, and project accounting spine.

Resource management and Universal Resource Scheduling

Resource management in Project Operations covers skills management, resource requests, bookings and assignments, booking reconciliations, workforce planning, and utilization insights. The underlying engine is Universal Resource Scheduling (URS), the same scheduling platform Dynamics 365 Field Service uses, which means a project-based business that also runs field work can schedule on one system instead of two (Microsoft Learn, Universal Resource Scheduling overview).

Booking fulfillment runs in either Central mode, where a resource manager fulfills requests from a central team, or Hybrid mode, where project managers hold some booking authority. Central mode concentrates control with resourcing and is typical for larger professional-services teams; Hybrid mode distributes booking decisions and suits smaller, flatter teams. Booking reconciliations keep assignments aligned with confirmed bookings so utilization reporting stays accurate.

Workforce planning extends this to capacity: it surfaces resource demands against available capacity over a horizon, so a services director can see where the firm is over- or under-sold months ahead, not just this week. For an SME where a few unbilled consultants materially affect margin, that forward view is often the highest-ROI part of the license—and the reason pure project-accounting tools (or spreadsheet utilization) start to fail as headcount grows.

Time, expense, and material usage

Project execution captures time, expense, and material usage against the project and task structure from the WBS. Time entries carry the project, task, role, and billing type; expenses carry categories, receipt capture, and policy validation; material usage records consumables and billable items as they are applied. Mobile apps let consultants and field staff enter time and expenses from the job, with offline support for areas without coverage.

Policies and rules validate entries before they hit actuals: approvers, cost limits, not-to-exceed checks, and required fields are enforced at submission. Budget tracking and earned-value reporting pull from the same actuals, so a delivery lead sees utilization, cost-to-complete, and margin in one view rather than reconciling spreadsheets. This is the operational layer that the BC Jobs module approximates with journal lines; Project Operations makes it the system of record.

For SMEs considering where AI cost lands, this is also where the Copilot agents sit. The time, expense, and approvals agents run on Copilot Credits and are designed to reduce the manual overhead of chasing submissions, grouping expenses, and routing approvals—the part of professional-services delivery that consumes the most non-billable time. Budget Copilot Credits the way you budget billable utilization: a small per-user base license surprise is less common than an unplanned Azure consumption line.

Proforma invoicing, customer invoicing, and WIP

Invoicing in Project Operations splits cleanly into proforma and customer-facing invoicing. Proforma invoices are the operational documents a project manager or engagement owner reviews before anything hits the ledger: they pull from billed and unbilled backlog, respect not-to-exceed limits, and support review, edits, and adjustments. Customer-facing invoicing is the financial document posted to the ERP for revenue recognition.

In Core deployments, Project Operations handles proforma invoicing and the customer invoice is produced by a connected ERP—which is why deployment choice drives finance scope. In the Integrated deployment with Dynamics 365 Finance, the same data flows through to the GL, accounts receivable, revenue recognition, and WIP accounting without re-keying (Microsoft Learn; Project Operations pricing page).

WIP, or work in process, is the accounting for costs incurred on a project before they are invoiced or recognized as revenue. For fixed-price engagements, WIP methods determine how cost is capitalized and recognized as the project completes; for time-and-materials work, WIP tracks unbilled effort. SMEs running project accounting inside Business Central should compare WIP methods carefully, because BC Jobs and Project Operations handle WIP at different depths, and the right answer depends on contract mix and revenue-recognition requirements. See our Business Central Jobs & Projects guide for the BC side of that comparison.

Project Operations vs Business Central Projects vs lighter tools

The most common scoping question for project-based SMEs is whether to run Dynamics 365 Project Operations, the Business Central Projects module (formerly Jobs), or stay on Project for the Web / spreadsheets until utilization and contract complexity force a platform. They serve different depths of project work; the decision rests on contract complexity, resourcing sophistication, finance requirements, and license budget—not brand preference.

Business Central Projects is the right fit when projects are primarily an accounting exercise: you need job ledger lines, WIP methods, job planning lines, and invoicing tied to the BC general ledger, and your resourcing is light. It is included with the BC license an SME likely already holds, which keeps cost predictable. Project for the Web alone is enough when the pain is schedule visualization and task ownership—not billing, utilization, or multi-dimensional project sales.

Project Operations is the right fit when delivery itself is the business: multidimensional pricing, Universal Resource Scheduling, earned-value tracking, subcontracting, and proforma-to-customer invoicing across complex contract types. A useful proxy: if the person buying the system is the head of delivery or a services director, Project Operations is usually in scope. If the buyer is the CFO or controller and projects are a finance workflow, BC Projects is usually enough. Flectic scopes both Dynamics 365 and Odoo for project-based SMEs across Canada, the UK, and the US, and we will tell you plainly when BC Projects, Odoo Project, or a third-party PSA is the better fit than Project Operations.

SME fit scorecard: go / no-go criteria and TCO gotchas

Use this scorecard before you buy seats. Project Operations is usually a go when three or more of these are true: you sell mixed contract types (T&M, fixed price, not-to-exceed, retainers) from the same system; utilization and skills-based staffing are board-level metrics; subcontractors are material to delivery capacity; proforma review is a weekly control, not an accounting afterthought; and you already run or plan Dynamics 365 Sales, Field Service, or Finance and want one Dataverse spine.

It is usually a no-go—or at least not yet—when projects are mostly job costing for a product business, headcount is small enough that a resource manager spreadsheet still works, finance will never leave a non-Microsoft ERP and you refuse dual systems, or the only requirement is task plans (then Project for the Web or BC Projects is cheaper and faster). Seat-cost fatigue is real across the Microsoft stack in 2026; open-source and mid-market ERPs compete hard on per-user math, so Project Operations has to earn its $135 with billable utilization and contract control—not feature checklists.

TCO gotchas to put on the first page of any business case: (1) base $135 is not the only line—attach, Team Member mix, Finance seats, dual-write implementation, and Copilot Credits stack; (2) minimum full-user purchase quantities can kill a small pilot—confirm Product Terms; (3) Core versus Integrated is a one-way-feeling architecture choice with no OOB migration; (4) Team Member is not a discount full user—overusing it for PMs creates compliance risk; (5) Field Service sharing URS is a win only if you actually run field work. Price the license mix you will run in year two, not the happy-path demo tenant.

Frequently asked questions