What is Dynamics 365 Project Operations?

Dynamics 365 Project Operations is Microsoft's professional-services automation (PSA) application — the system that runs an opportunity-to-cash flow for businesses that sell project work. Typical customers are consulting firms, marketing and creative agencies, IT services firms, engineering practices, and architecture firms. Project Operations sits deliberately across the CRM/ERP boundary because a services business needs both sides of the house tightly integrated: an opportunity in the sales funnel has to turn into a resourced project, and the hours consultants log against that project have to turn into revenue and cost postings in the ledger.

Where it fits

In the wider PSA market, Project Operations competes with Salesforce Services Cloud (Copado / Financial Force lineage), Microsoft Dynamics 365 successors like Certinia, Deltek, and specialist products like Kantata, Kimble (now Kantata), Replicon PSA, and Wrike / Smartsheet at the lighter end. It wins when the buyer already runs Microsoft business apps (Sales in front, F&O or Business Central at the back), when the deep Copilot integration matters, and when the shared Dataverse means an opportunity, a project, and an invoice can share the same account record without a middleware layer.

The line between Project Operations and simpler project management tools matters. Wrike, Smartsheet, and Microsoft Planner cover task management well but they are not PSAs — they don't touch billing, cost accounting, or revenue recognition. Project Operations is a PSA. If the business needs a WBS but not project accounting, it is over-scoped; if the business needs project accounting, task-tracker tools are under-scoped.

The three deployment modes

Project Operations is one product but operates in three modes depending on the customer's back office. The mode decides most of the architecture and much of the implementation cost.

Lite deployment — runs entirely on Dataverse, with financial postings integrated to Business Central, QuickBooks, Xero, or SAP via APIs. The right fit for SMB services firms whose financials sit in BC or a small-business accounting system. Fastest to deploy, cheapest to run, ceiling at moderate complexity.

Resource / non-stocked deployment — runs on the Finance and Operations stack with full F&O accounting integration. Time and expense post directly to F&O's general ledger through project accounting; there is no middleware. Right for services firms already on F&O or heading there; also right for large services firms whose complexity Lite cannot handle (multi-currency, multi-entity project accounting, IFRS 15 revenue recognition).

Stocked / production deployment — extends the F&O deployment with manufacturing and inventory. Right for firms that build and install physical goods as part of the project — engineering firms delivering equipment, construction firms with material take-offs, systems integrators building custom hardware plus services. Combines project services with deliverable goods on the same work order and the same project profit line.

The mode choice is not reversible without a re-implementation, so it deserves serious analysis at the start of a Project Operations engagement — not as an afterthought.

Opportunity to quote

Sales pursues an opportunity in the Sales app; when it's qualified as project work, a project quote is configured with phases, tasks, roles, hours, and billing terms. Billing types cover fixed-price, time-and-materials, capped T&M, milestone billing, and mixed contracts where different work streams inside one contract carry different terms.

The quote is priced from a rate card by role, seniority, and geography, adjusted with client-specific discounts and prepaid retainers, and reviewed through a configurable approval flow. On win, it converts to a project contract that carries the pricing, the milestones, the billing schedule, and the deliverables into project execution.

Project plan and WBS

A work breakdown structure (WBS) with tasks, dependencies, durations, effort estimates, and assignments. Baseline and current schedules are tracked separately so slippage against the baseline is visible.

Resourcing is done from a resource hub that shows availability, skills, location, cost rate, and current utilisation. Assignment can be by named resource (Emma is on this) or by generic role (a senior Java developer, to be named later). Generic assignments carry through the plan until they're replaced with real names, so the plan can be built before the resource conversations are finished.

For firms coming from Microsoft Project or Smartsheet, the WBS experience is different — simpler in some places (no Gantt-chart theatre), richer in others (integrated resource cost, integrated billing). The learning curve is short but the mental model shift matters.

Time and expenses

Consultants enter time on a weekly timesheet and expenses through receipts and policy-aware approvals — see expense management for the categories, policies, and reimbursement integration behind that. Both flow through workflow approval — the project manager first, then whatever additional approval the policy demands (an expense over a threshold routes to the finance director, mileage over a limit needs a business-purpose note).

Approved time and expenses post to the project for billing and cost. In Lite deployment, the postings flow to the connected finance system; in F&O deployments, they post directly to the general ledger, WIP, and project accounting through the F&O project posting framework.

Copilot in Project Operations speeds up time entry — draft a week's timesheet from the consultant's Teams meetings and calendar, review, adjust, submit. Not perfect on the first try, but a serious lift over a blank grid.

Billing

Invoicing runs at the cadence defined in the contract — monthly retainers, milestone billing, on-completion, on-approval, or scheduled instalments. Invoices can hold multiple billable types (T&M plus fixed-fee plus expense recovery) on a single invoice, with multiple currencies where the contract requires it.

Drafts are routed through review by the engagement partner, the client-partner, or finance — configurable — before posting to the back-office system for collection. Credit notes and re-billing follow the same flow in reverse.

Reporting

Built-in dashboards for project margin, resource utilisation, billable mix (billable vs non-billable hours), backlog, forecast vs actual, and cash forecast from open invoices. Practice-level reports roll up the individual projects into service line and firm KPIs.

The reporting depth is adequate for most services firms; deeper analytics ship as a Power BI app on top of Project Operations data in Dataverse or Fabric. Firms that need very rich portfolio management (predictive cash forecasting, capacity planning across a global practice) typically layer a specialist tool on top for the CFO reporting even while keeping Project Operations as the source of truth.

Integration

Project Operations shares Dataverse with Sales, Customer Service, and Field Service, so an opportunity in Sales flows through to a project and a client account carries the full history. Financial postings go to F&O directly (in F&O deployments) or to BC / third-party accounting via connectors (in Lite deployments).

Copilot across the Dynamics 365 family means a project manager can query pipeline, resource load, and billing status in natural language across apps. Power BI ties the operational data to whatever wider CFO reporting matters.

Licensing

Sold per user. Two SKUs plus a lightweight one:

Project Operations — the standard licence for project managers, resource managers, and consultants who need the full application.

Project Operations — Team Member — a lightweight licence for consultants who only need to submit timesheets and expenses. Priced substantially lower than the full licence; the right choice for the majority of a services firm's headcount.

Attach licensing lets Sales seats add Project Operations at a reduced price — common where account managers pursue and stay engaged on project work.

The short version

Project Operations is Microsoft's PSA. It runs the opportunity-to-cash flow for services firms. Three deployment modes (Lite on Dataverse, F&O for larger firms, Stocked for build-plus-services) — the choice decides the whole architecture. It fits Microsoft-shop services businesses well; it competes with specialist PSAs on capability and typically wins on integration into the wider Microsoft business apps stack.

Where to go next

The deployment-mode decision is expanded in Project Operations deployment types. Daily operation is covered in time and expense and resource management. For the two adjacent products people confuse it with, see Field Service vs Project Operations and Business Central Jobs vs Projects.