Project Operations deployment types

Dynamics 365 Project Operations is offered in three distinct deployment types, each targeting a different project services scenario. They aren't interchangeable — picking the wrong one means rebuilding later. Understanding the three at the start of any project-services Dynamics initiative saves significant time and licence churn.

The three deployments.

• Project Operations — Lite (PO Lite) — for opportunity-to-cash on Dataverse only.
• Project Operations — Resource and Non-Stocked / Production-Based — for organisations needing tighter integration with Finance & Operations.
• Project Operations — Finance and Operations Integrated — for organisations on F&O with full ERP-grade project management.

The naming has shifted over recent waves; current branding emphasises the underlying scenarios rather than the deployment names directly. Microsoft documents the three shapes consistently.

PO Lite — Dataverse only. Best for:

• Smaller professional services firms.
• Project-centric work without complex ERP needs.
• Organisations on the CE-side of Dynamics 365 (Sales, Customer Service).
• Time-tracking, project billing, basic revenue recognition.

What it offers:

• Project planning (tasks, schedule, resources).
• Time and expense entry.
• Project quotes and contracts.
• Invoicing via sales orders or directly.
• Basic revenue and cost reporting.

What it doesn't offer:

• Deep inventory integration.
• Complex revenue recognition standards (ASC 606 multi-element).
• Advanced manufacturing-style WIP and cost accounting.
• Multi-currency consolidation at scale.

Licensing: priced per user; Dataverse-only deployment cheaper and simpler.

Resource and Non-Stocked-Based. Best for:

• Mid-market and enterprise services firms.
• Organisations needing F&O for finance but project management on the CE side.
• Hybrid scenarios where parts of operations are on F&O.

Architecture:

• Project, resource, time entry on Dataverse (CE side).
• Project accounting, revenue recognition, billing on F&O.
• Dual-write integration syncs between.

The advantage: front-line teams use a CE-style modern UX while finance gets F&O-grade accounting. The cost: integration complexity; dual-write maintenance.

F&O Integrated (full ERP). Best for:

• Large project-driven manufacturers.
• Engineer-to-order, build-to-order businesses.
• Organisations on F&O for everything; want projects integrated into the broader ERP.

Architecture:

• Project module within F&O itself.
• Full integration with inventory, production, procurement.
• Project ledger, cost categories, WIP, revenue recognition all in F&O's project sub-ledger.

Capabilities:

• Manufacturing projects (the project consumes BOMs and produces output).
• Construction-style projects (long-lead, milestone-based).
• Government contracting (DCAA / FAR compliance).
• Multi-LE projects (entities collaborating on one project).

This is the heaviest deployment but the most capable for complex scenarios.

Picking between them.

• Pure services with simple needs → PO Lite.
• Services with F&O finance integration → Resource and Non-Stocked.
• Manufacturing or complex projects on F&O → F&O Integrated.

If unsure, lean toward the lighter option — upgrading is non-trivial, but starting too heavy is operational overkill.

Migration between deployments. A common scenario: company starts with PO Lite, grows, decides to integrate with F&O. Migration is possible but involves:

• Re-platforming project schedules.
• Re-establishing financials in F&O.
• Re-training teams.
• Data conversion.

Plan months for a real migration, not weeks. The decision to deploy on the right type from the start saves significant cost later.

Common cross-deployment concepts.

• Project — the core entity.
• Project task / WBS — work breakdown structure.
• Project resource — people assigned to the project.
• Time entry / expense entry — actuals.
• Project contract — billing arrangement (fixed-price, T&M, milestone).
• Project invoice — billing to customer.
• Project actuals — committed costs and revenue.

These exist in all three but vary in depth.

Resource scheduling. All deployments include resource scheduling:

• Resource Scheduling Optimization (RSO) — ML-driven resource matching.
• Schedule board — manual assignment.
• Resource fulfillment — bookings on the project.

Field Service and Project Operations share scheduling infrastructure; an organisation running both gets unified scheduling.

Time entry. Universal pattern:

• Resource enters time against project / task daily or weekly.
• Manager approves.
• Time posts to project actuals — flowing to billing and revenue recognition.

PO Lite has a simpler time entry surface; F&O Integrated has additional time entry features (multiple time categories, regulatory timekeeping).

Common pitfalls.

• Wrong deployment chosen at start. Cost of correction high.
• Integration complexity underestimated. Dual-write reliability work is real ops effort.
• Configuration sprawl. Every customer's slightly different; managing varied configs across many customers is heavy for partners.
• Licensing confusion. Three deployments → multiple SKUs and add-ons; getting licensing right takes specialist help.
• Roadmap misalignment. Some features land in one deployment before others; planning around current capability matters.

Strategic positioning. Microsoft's investment is across all three, but the most innovation lands in the integrated deployments (Resource/Non-Stocked and F&O). PO Lite remains supported for the simpler scenarios but doesn't always get newest features first.

Choose deployment based on actual business needs, not aspirations. Start lighter, upgrade only with concrete evidence of need. The deployment choice is one of the biggest decisions in any Project Operations project — give it the analysis it deserves.