Last updated: November 5, 2026
By ZapAI Team
Dynamics 365 Project Operations is Microsoft’s project-based business app inside the wider Microsoft Dynamics 365 family. It runs project sales, planning, resourcing, time, expense and billing in one place. It comes in two current deployment types, Core and Integrated with ERP, lists at $135 per user per month with a 20-seat minimum, and has three agents in preview. For a lot of smaller firms, Business Central Projects is the cheaper and better fit.
Dynamics 365 Project Operations is a Microsoft app for project-based firms that links deals, resource scheduling, time and expense, and project billing. It deploys as Core, alongside another ERP, or Integrated with ERP on Dynamics 365 Finance, at $135 per user monthly.
Most pages about Project Operations read like a brochure. Quote to cash. One platform. Happy consultants. Sure. But the questions we hear from consulting, engineering and professional services firms are blunter, and they usually start with money. Do we really need 20 licenses? Can our Business Central setup do this already? Which deployment type are we buying, and can we change our minds later?
That’s what this guide answers. Every product fact below was checked against Microsoft Learn, Microsoft’s pricing page, and the November 2026 Dynamics 365 Licensing Guide. Opinions are labeled as ZapAI practice. And with Ignite running November 17 to 20, expect us to refresh this page.
What Is Dynamics 365 Project Operations?
It’s a Dataverse app for companies that sell time, expertise and project deliverables. Project Operations covers the full project lifecycle, from a project quote through staffing, time and expense capture, approvals and invoicing, with project accounting either in Dynamics 365 Finance or in another ERP.
Think of it as four tools sharing one data model. Project sales borrows from Dynamics 365 Sales, with project quotes, contracts and price lists. Planning builds a work breakdown structure. Resourcing uses Universal Resource Scheduling, the same engine behind Field Service. Billing turns approved actuals into proforma invoices, and in the integrated version into posted customer invoices and recognized revenue.
Who’s it for? Firms where people are the inventory. Consultancies, engineering firms, architects, agencies. If your margin depends on utilization, bill rates and how fast approved hours become invoices, you’re the target customer.
Who isn’t? A 15-person shop billing simple hourly work. Different tool.
Which Deployment Type Fits, Core or Integrated with ERP?
Choose Core if another ERP keeps the books and you want Project Operations for sales, planning, resourcing, time and proforma invoicing. Choose Integrated with ERP when Dynamics 365 Finance should handle customer invoices, project accounting and revenue recognition. A third type covers stocked and production order projects.
Microsoft renamed these in October 2025, when Project Operations Lite became Project Operations Core and Project Operations for resource and non-stocked scenarios became Project Operations Integrated with ERP, per the change log in the Dynamics 365 Licensing Guide. Older partner pages still use the old names. Don’t let that confuse you.
| Deployment type | Where accounting happens | What it adds | Best fit |
|---|---|---|---|
| Project Operations Core | Your current ERP or accounting system | Project sales, Project for the web planning, pricing, resourcing, time, basic expense, budgets, subcontracting, proforma invoices | Firms keeping their ERP, including Business Central, NetSuite or another system |
| Integrated with ERP | Dynamics 365 Finance | Everything in Core, plus full expense with receipt OCR, customer-facing invoicing and revenue recognition | Services firms on Finance, or moving to it |
| Project Operations for manufacturing | Finance and Supply Chain Management | Production orders, stocked materials with inventory, full invoicing and revenue recognition | Engineer-to-order and project manufacturing |
Capabilities come from Microsoft’s guide to determining your deployment type. That same page says one environment can run stocked and production order scenarios in one legal entity and resource-based work in another, so a US plant and a UK services arm can share a tenant.
Read its last note twice. There’s no out-of-box supported migration of data between deployment types. Moving later means custom scripts, custom mapping and manual cleanup. So this decision is close to permanent.
Core has a clear job description. Microsoft’s Project Operations Core overview says to use it with a third-party ERP or accounting system that handles sales taxes, exchange rates, expense reimbursements and non-project expenses. Proforma invoices get reviewed in Project Operations and then sent to that system for processing, and somebody, either your partner or an AppSource vendor, has to build or sell the integration that carries them across. Plan for it.
Existing Finance customers on the older Project management and accounting module have a path too. From version 10.0.43, Microsoft’s move to the modern architecture guidance lets a legal entity finish old projects while new ones are created in Dataverse. Once you create a new project in Dataverse, you can’t opt out.
How Much Does Project Operations Cost in 2026?
List price is $135 per user per month, paid yearly, with a 20-seat minimum purchase. Team Members, for people who only enter time and expenses and approve them, cost $8. Copilot Credits for agents are extra, and attach pricing depends on which license a user already holds.
Microsoft’s Project Operations pricing page shows the $135 figure and says Copilot Credits aren’t included and must be bought separately to use the agents, along with an Azure subscription. The rest comes from the October 2026 Dynamics 365 Licensing Deck.
| License, US list, billed yearly | Price, November 2026 | Notes |
|---|---|---|
| Project Operations | $135 per user per month | 20-seat minimum purchase |
| Project Operations attach on a Finance, SCM, Commerce or HR base | $30 per user per month | Finance base plus attach comes to $240 |
| Team Members | $8 per user per month | Submit and approve time, expense and materials |
| Sales Enterprise, Field Service or Customer Service attach on a Project Operations base | $20 per user per month | For users who need both apps |
| Copilot Credits | Sold separately | Needed for the Time Entry, Expense and Approvals agents |
Each tenant also gets one production environment and one Tier 2 sandbox, plus 90 GB of Dataverse or operations database capacity, per the licensing guide, which matters if you planned on separate test and training environments. Check yours.
Licensing traps we see
- The 20-seat floor. Ten project managers still pay for 20 licenses, or $32,400 a year at list.
- No attach on Business Central. The deck’s base and attach table shows no Project Operations attach price for Business Central Essentials or Premium users, so a Business Central shop pays the full $135.
- Base goes to the priciest app. A user who needs Finance and Project Operations carries Finance as the base license at $210, then Project Operations as a $30 attach.
- Over-licensed consultants. Microsoft’s guide says users who create and approve project timesheets only need Team Members.
- Agent costs. Credits are a separate meter.
That fourth point is where budgets quietly bloat. A 60-person consultancy where 45 people only log hours and expenses needs full licenses for account managers, project managers, resource managers and project accountants. Everyone else can sit on Team Members. Our Finance licensing guide on roles, attach rules and enforcement explains how Microsoft checks role assignments, and the same logic is worth applying here before you sign.
When Is Business Central Projects Enough?
For most firms under roughly 50 billable people, one legal entity and straightforward T&M or fixed fee work, Business Central Projects is enough. Project Operations earns its price when resource scheduling across a large bench, multidimensional bill rates, deal pipelines or Finance-grade revenue recognition become daily problems.
That threshold is our opinion. Microsoft doesn’t publish one.
Business Central already does real project accounting. Its project management documentation covers project tasks and planning lines, resource allocation and prices, time sheets posted to project journals, budgets against actuals, WIP methods for correct financial statements, and invoicing when work is done or on an invoicing schedule. Projects come with Essentials, which lists at $80 per user, as our Business Central pricing breakdown shows.
| Need | Business Central Projects | Project Operations |
|---|---|---|
| Project accounting and WIP | Built in, posts straight to the general ledger | Integrated with ERP posts through Finance, Core hands off to your ERP |
| Time entry | Time sheets tied to project tasks | Time entry grid, mobile, Team Members app, Time Entry Agent preview |
| Resource scheduling | Resource capacity and allocation | Schedule board, resource requests, skills matching, soft and hard bookings |
| Pricing | Resource and item prices | Multidimensional pricing by role, organizational unit and other dimensions |
| Project sales | Quotes and orders | Project opportunities, quotes and contracts with estimates |
| Billing | Invoices from planning lines or schedules | T&M backlog, fixed price milestones, progress billing in Integrated |
| Minimum spend | No seat minimum listed | 20 seats at $135 |
Stay on Business Central if these sound familiar.
- Your finance team is three people and the ERP already works.
- Fewer than 30 people get scheduled.
- Bill rates come from a resource card, not a matrix of role, region and client.
- A spreadsheet or Planner board handles staffing without drama.
- Pipeline lives in a CRM you like.
Look harder at Project Operations when resource managers spend every Monday juggling 80 consultants across 40 projects in a spreadsheet nobody trusts, when you price by role and region, or when one revenue recognition policy has to hold across several legal entities. A hybrid also exists. Core can sit on top of Business Central, sending proforma invoices to it for posting. Microsoft doesn’t ship that integration, so partners build or sell it. Price that bridge early. If the real question is which ERP, read our Business Central vs Dynamics 365 Finance comparison first.
How Does It Fit With Finance, Sales, Field Service and Planner?
Finance is the accounting backbone in Integrated with ERP. Sales supplies the opportunity and quote model. Field Service connects work orders to projects through an out-of-box integration. Planner premium plans replaced the standalone Project for the web app, while Project Operations keeps its own planning.
Dynamics 365 Finance
In the integrated deployment, Project Operations runs in Dataverse and Finance runs in its own environment, linked by dual-write maps. Approved actuals flow to Finance as integration journals, where project accounting, revenue recognition and customer invoice posting happen. Full Project Operations users get Operations Activity level rights in Finance and Supply Chain Management, per the licensing guide. A controller doing full Finance work still needs a Finance license, in our reading. Our Dynamics 365 Finance consultants handle that side.
Dynamics 365 Sales
Project Operations includes project opportunities, quotes and contracts on the Sales data model. If the same team also sells products or subscriptions and wants forecasting and sequences, add Sales Enterprise as a $20 attach. Our Dynamics 365 Sales pricing guide compares the tiers.
Dynamics 365 Field Service
Microsoft’s Field Service integration with Project Operations links work orders to projects, which act as the financial container. Technician time and material usage flow into Project Operations, go through the same pricing and approval rules as everyone else’s entries, and become actuals and then proforma invoices for review. It supports three setups. All four apps together. Field Service with Finance and SCM, using embedded project forms. Or Field Service and Project Operations without Finance, for firms on another ERP. Task dates sync one way only, from project to work order. Our Field Service guide explains why Finance customers should design for this path now.
Planner and Project for the web
Here’s where it gets muddy. Microsoft’s Planner team retired Project for the web as a standalone app in August 2025, and premium plans now live in Planner, per the Planner blog post on the transition. That post never mentions Project Operations. Meanwhile, Project Operations documentation still describes planning with Project for the web, and the November 2026 licensing guide still lists Project for the Web as a Project Operations use right. In practice, your work breakdown structure lives inside Project Operations either way.
When is Planner enough? Internal projects. No billing, no bill rates, no revenue. Planner premium plans handle tasks, dependencies and timelines well, and they’re far cheaper than 20 Project Operations seats.
How Do Time, Expense and Resource Scheduling Work?
Team members log time and expenses against projects and tasks, a project approver approves them, and approved entries become cost and sales actuals. Resource managers staff demand through resource requests and the schedule board, booking named people by skill and availability.
Time first. Consultants enter time in a weekly grid, on mobile, or in the Project Operations Team Member app. Microsoft’s Team Member app page lists time entry, expense entry in the Core deployment, material usage and approvals. At $8, that app is where most of your staff will live.
Expenses split by deployment. Core includes basic expense. Integrated with ERP adds full expense management with receipt OCR, which runs through Finance’s expense module and its policies.
Resourcing is where Project Operations pulls away from lighter tools. A project manager adds generic roles to the team, those roles create resource requirements, and a resource manager either books a named person or proposes one for the project manager to accept. Soft bookings reserve someone without consuming capacity. Hard bookings consume it. The schedule board shows availability across the bench, filtered by skills, role and organizational unit.
Our practice view. Most resourcing pain is data, not software. Skills that nobody maintains, roles that mean different things in different offices, calendars that ignore vacation. Fix those first.
How Does Project Billing Work?
Each project contract line carries a billing method, either time and material or fixed price. T&M lines bill approved actuals from a billing backlog on a date-based invoice schedule. Fixed price lines bill milestones, generated periodically or created by hand, and Integrated with ERP adds progress billing by percentage complete.
Contracts drive everything here. A project contract can mix lines, so one engagement might carry a fixed fee for discovery, T&M for build work and a separate expense line. Per Microsoft’s guide to invoice schedules on project contract lines, these are the rules that matter.
- T&M schedules use an invoice frequency. The transaction cutoff falls the day before each invoice run.
- Fixed price milestones must add up to the contracted value of the line, or the contract line shows an error.
- Milestones can only be created on lines a project is mapped to.
- Progress billing needs Project Operations Dataverse version 4.124 or later, Finance 10.0.42 or later, and a feature switched on in Finance.
In Core, the process stops at a confirmed proforma invoice that your ERP turns into the real one. In Integrated with ERP, Finance posts the customer invoice, applies accounting rules and runs revenue recognition. That’s a big difference for any firm with audited financials, percentage-of-completion revenue or intercompany billing, because it decides whether your controller trusts Project Operations numbers directly or reconciles two systems at every month-end close.
Test your three hardest contracts in a sandbox before you sign anything. Seriously.
What Copilot and Agent Features Are Available Now?
Copilot for project offers task plan generation, risk assessments, status reports and a chat assistant. Three agents, the Time Entry Agent, Expense Agent and Approvals Agent, are production-ready previews that need Copilot Credits and an Azure subscription. None were generally available as of November 5, 2026.
Copilot for project comes first. Per Microsoft’s Copilot for project overview, it can generate up to 100 tasks from a project name and description, suggest risks and mitigations, and draft internal or external status reports. It’s on by default for existing tenants. Two catches. Risk assessments and status reports need logged actuals first, and some regions require consent to move data across regions.
Agents are a different animal.
| Agent | Status, November 2026 | What it does | Deployment types |
|---|---|---|---|
| Time Entry Agent | Production-ready preview | Drafts time entries and reminds people to log hours, in the grid or in Teams | Core and Integrated with ERP |
| Approvals Agent | Production-ready preview | Classifies time, expense and material entries against your policy documents | Core and Integrated with ERP |
| Expense Agent | Production-ready preview | Turns receipts from a shared mailbox, mobile app or in-app upload into expense lines and reports | Integrated with ERP and manufacturing |
Setup isn’t trivial. The Time Entry Agent setup guide requires Project Operations version 4.140.0.239 or later, a feature flag, publishing from Copilot Studio, and turning on 13 Power Automate flows in a set order. If you create the recommended dedicated agent user, Microsoft lists Power Automate Free, Teams Enterprise and a Microsoft 365 E5 license for it, mainly for Outlook calendar access. Budget an afternoon. Maybe two.
Approvals is the interesting one. Per the Approvals Agent overview, you upload policy documents for time, expense and materials, org-wide or per project. The agent marks each entry Ready for approval or Needs review. A Classify and auto approve mode exists too, and Microsoft itself says to test the agent thoroughly before using it, which is fair warning for any firm whose invoices depend on those approvals. We’d keep humans approving for the first few billing cycles.
Expense Agent details sit in the Expense Agent overview. Note the scope. It doesn’t apply to Core.
Sources conflict on status. A 2025 release plan entry listed agent-led time, expense and approvals with a September 2025 general availability date. Microsoft Learn, the pricing page and the licensing guide’s paid preview appendix all still call them previews. We follow the current pages. Credit costs per action aren’t published on the Project Operations pages we checked, so see our Copilot Studio pricing guide for how credit packs work, and our Copilot use cases across Dynamics 365 for where AI pays off elsewhere.
What Should You Plan for in Implementation?
Plan for the deployment decision, data design and integrations before configuration. Integrated with ERP means a Finance environment, dual-write and Finance setup alongside Project Operations. Core means building the handoff to your ERP. Either way, pricing dimensions, roles and contract structures decide whether the system works.
Since February 2026, new customers can’t create projects in Lifecycle Services for Finance or Project Operations and use the Power Platform admin center instead, per Microsoft’s environment provisioning guidance. Integrated provisioning also involves linking the Finance and Dataverse environments, running the Project Operations dual-write maps, and confirming security on the dual-write app user, and provisioning alone can take up to six hours. Not hard. Easy to get wrong.
What we’d sort out first, as ZapAI practice.
- Pick the deployment type in writing, with finance and delivery leaders both signing, since you can’t migrate between types later.
- Design pricing dimensions. Role, organizational unit, maybe region. Keep it small.
- Map your five most common contract shapes to contract lines and billing methods.
- Decide who gets full licenses and who gets Team Members, role by role.
- Clean resource data, including roles, skills, calendars and cost rates.
- Pilot one practice or region for a full billing cycle, invoices included.
- Add agents last.
Costs depend on scope. Our Dynamics 365 implementation cost guide shows what drives the number.
How Do You Decide If Project Operations Fits?
Count your full users, check your ERP, and test your hardest contracts. If fewer than 20 people need full licenses and Business Central already runs your books, start with Business Central Projects. If you’re on Finance or heading there, Integrated with ERP is usually the right deployment.
- At least 20 people need full rights, or you accept paying for 20.
- Resource managers schedule 50 or more billable people across several projects.
- Bill rates vary by role, unit, region or customer.
- Project quotes need estimates and margin before you win them.
- You bill a mix of T&M, fixed price milestones and progress billing.
- Revenue recognition rules matter to auditors.
- Finance is your ERP, or will be within two years. If yes, choose Integrated.
- Another ERP stays put, and someone owns the Core integration to it.
- Field technicians do project work. Then the Field Service integration matters.
- You can wait for agents to reach general availability.
Fewer than four checks? Business Central Projects, or Business Central plus Planner, will likely serve you better. Six or more, and Project Operations deserves a proper evaluation.
What Could Change After Ignite 2026?
Agent status and credit rates are the likeliest changes. Ignite runs November 17 to 20, 2026, in San Francisco. Treat this page’s preview labels as a snapshot and expect a refresh in late November, once we’ve checked what Microsoft actually ships against the Learn pages, the pricing page and the next licensing guide.
Watch three things. Whether the Time Entry, Expense and Approvals agents reach general availability. Whether Microsoft publishes per-action credit rates for them. And whether Project Operations documentation adopts Planner naming. Also remember the roadmap moved. Since September 2026, Dynamics 365 changes appear on the AI at Work roadmap instead of release plans, and Release Planner retires by November 15, 2026, per Microsoft’s announcement of the always-on roadmap. Our guide to the release wave changes explains how to plan updates now.
Wrapping Up
Put simply, Project Operations fits project-based firms with a big bench, complex pricing and contracts, and either Finance or a committed ERP integration behind it. It costs $135 per user with a 20-seat floor, and its agents are still previews. Smaller firms with simple billing are usually better served by Business Central Projects. Pick the deployment type carefully. You can’t easily switch.
ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric and AI consulting firm in Irving, Texas, working with businesses across Dallas-Fort Worth and nationwide. Our Business Central consultants set up projects, time sheets and WIP for firms that don’t need more. Weighing Project Operations? Talk to us about a Project Operations fit review, and we’ll map your users, contracts and ERP before recommending a deployment type.
Questions Teams Ask About Project Operations
How much does Dynamics 365 Project Operations cost per user?
$135 per user per month, billed yearly, with a 20-seat minimum purchase. Team Members licenses for time and expense entry cost $8. Users who hold a Finance base license can add Project Operations as a $30 attach.
What’s the difference between Core and Integrated with ERP?
Core stops at proforma invoices and sends them to your existing ERP. Integrated with ERP adds Dynamics 365 Finance for customer invoicing, project accounting, full expense management and revenue recognition.
Can we switch deployment types later?
Not easily. Microsoft says there’s no out-of-box supported data migration between deployment types. Moving takes custom scripts, mapping and manual work, so treat the choice as long term.
Is Business Central Projects a replacement for Project Operations?
For smaller firms, usually yes. Business Central handles project tasks, planning lines, time sheets, WIP and project invoicing inside the ERP, starting with Essentials. It lacks Project Operations’ schedule board, multidimensional pricing and project sales depth.
Do consultants who only log time need a full license?
No. Microsoft’s licensing guide says users who create and approve project timesheets only need a Team Members license, which also covers expense submission and approvals.
Are the Project Operations agents generally available?
Not as of November 5, 2026. The Time Entry, Expense and Approvals agents are production-ready previews, they need Copilot Credits and an Azure subscription, and the Expense Agent works only with Integrated with ERP and manufacturing deployments.
Does Project Operations work with Business Central?
Yes, through the Core deployment, with Business Central as the ERP. Microsoft doesn’t ship a native connector, so partners build or sell the integration, and Business Central users pay full Project Operations pricing with no attach discount.