Field Service and Project Operations, natively connected: what it means for oil and gas

For years, companies that plan work as projects but execute it with field crews have run two systems that did not talk to each other. Project managers planned in one place. Dispatchers and technicians worked in another. Finance stitched the results together afterwards, usually in spreadsheets. Microsoft has now closed that gap: Dynamics 365 Field Service and Dynamics 365 Project Operations are connected out of the box, and since 31 July 2026 a project task can be turned directly into a work order.

This article explains what that means in plain terms, why it matters for oil and gas, and where we have done it before.

The two applications, one sentence each

Dynamics 365 Project Operations is where projects are sold, planned, staffed and billed: quotes, work breakdown structures, resource plans, time and expense, and invoicing, from deal to invoice.

Dynamics 365 Field Service is where the work gets done on site: work orders, a schedule board for dispatchers, a mobile app for technicians that works offline, asset and service history, parts and inventory.

Microsoft calls the combination a “project-based (multistage)” service model: “project managers plan and track project tasks, while dispatchers schedule and manage the related onsite work orders.” (Microsoft Learn, Overview of Dynamics 365 Field Service)

What the integration actually does

In Microsoft’s words, the integration “provides a supported mechanism for connecting field execution with project financials” and “connects work orders, project tasks, labor, materials, and financial transactions” using standard product features rather than custom code. (Field Service integration with Project Operations overview)

Here is the flow without the jargon:

• Every work order belongs to a project. The project is the financial container: it is where costs, revenue and billing rules live.
• Estimates flow forward. When a work order says “this job needs four hours and these parts”, those estimates appear on the project as planned cost.
• Actuals flow back. When the technician marks parts and labour as used, Project Operations prices them, a project manager approves them, and they become the project’s actual cost and revenue.
• Time follows the same path. Technicians submit time in Field Service; it lands in Project Operations for pricing and approval, and the approval status syncs back.
• Invoices are built from approved actuals as draft (proforma) invoices, ready for review. Where Dynamics 365 Finance is in place, the approved data posts to the ledger and the customer invoice is issued from there.
• New since July 2026: work orders from project tasks. Project teams can create a work order straight from a task, or link an existing one. Microsoft’s summary: “You can turn project tasks into executable Field Service work orders and bill only what matters.” Linking at task level also enables task-based billing, so one project can mix billing models. (Create work orders from project tasks, generally available 31 July 2026)

Scheduling and execution stay in Field Service. Project managers do not have to learn the schedule board, and dispatchers do not have to learn project accounting.

Why this is significant

Before the native integration, connecting the two applications meant a custom build: flows, functions, mapping tables, and a maintenance bill every time Microsoft shipped an update. Microsoft’s own reference architecture for a telecom operator shows what that looked like, with Power Automate and Azure Functions doing the plumbing. It worked, and it scaled to more than 300 project managers across 50 business segments, but it was bespoke. (Project Operations and Field Service integration reference architecture)

The out-of-the-box version removes most of that. Microsoft lists the benefits plainly: “reduce custom integration effort, improve consistency across costing and billing, strengthen visibility across service and project-driven work, and support more predictable financial and operational outcomes.”

It also comes in three configurations, so you do not need the full Microsoft finance stack to use it: Field Service with Project Operations and Finance; Field Service with Finance and a slim set of project screens; or Field Service with Project Operations alone, which Microsoft says “can be used for integration to other ERP solutions”. If you run SAP or another ERP, that last option is the relevant one. In that setup Field Service stays the system of record for inventory; with Finance, Finance takes over inventory and accounting. (Deployment models and inventory)

What it looks like in oil and gas

Microsoft’s stated priorities for the industry are to “digitize field work”, connect assets for predictive maintenance, and “predict unplanned downtime, optimize production”. (Microsoft: Oil and Gas Energy Solutions) The integration is the piece that connects that field work to the money. Some typical situations:

• Turnarounds and shutdowns. A turnaround is a project with hundreds of tasks and a hard end date. Each task becomes work orders for internal crews and contractors, and progress and cost roll up to the project daily instead of at the post-mortem.
• Capital projects and maintenance sharing the same crews. The same technicians work on a compressor upgrade (project) on Monday and a break-fix job (service) on Tuesday. One schedule board, one mobile app, and the hours land on the right cost object.
• Contractor cost control. Contractor labour and materials captured on work orders are priced and approved against the project before they reach an invoice, which is where most cost surprises used to hide.
• Well sites, terminals and pipeline assets. Recurring inspections run under service agreements, IoT alerts create work orders automatically, and asset history travels with the technician, offline if needed.
• Serialised parts and traceability. With Finance and Supply Chain Management, the serial and batch numbers a technician records flow through to finance, giving “full traceability from Field Service usage through Project Operations and into Finance”. Useful when an auditor asks which valve went where.

Features worth knowing about

• Work orders linked to projects and, since July 2026, to individual project tasks
• Estimates and actuals for labour and materials on the project, with approval workflows
• Time entries from the field, with approval status synced both ways
• Proforma invoicing in Project Operations; posted invoices and revenue recognition in Finance where used
• Two monitoring dashboards to find and fix stuck financial transactions (Monitor work order financial processing)
• Everything Field Service already brings: the schedule board and Resource Scheduling Optimization, the offline mobile app, asset and agreement management, and Copilot summaries of work orders

Where we come in

We are currently working inside a large integrated Field Service and Project Operations programme for a downstream oil and gas operator: portfolio, programme and project structures for capital and maintenance work, shift and calendar templates for round-the-clock plant operations, contractor and employee cost flows into project pricing, and scheduling performance at scale. We also documented how we built an external scheduling engine for Project Operations in a three-part technical series.

That experience is what we bring to a new implementation: which parts of the native integration to switch on, where it needs help, and how to roll it out to dispatchers and technicians who have a plant to run.

If you are planning a Field Service or Project Operations rollout, or already run one of the two and want to connect the other, book a free scoping call. We will look at how you plan, dispatch and bill work today and tell you honestly what the integration would and would not change.

Sources

• Microsoft Learn: Field Service integration with Project Operations overview
• Microsoft Learn: Create work orders from project tasks (2026 release wave 1)
• Microsoft Learn: Deployment models and inventory
• Microsoft Learn: Monitor work order financial processing
• Microsoft Learn: Project Operations and Field Service integration reference architecture
• Microsoft Learn: Overview of Dynamics 365 Field Service
• Microsoft Learn: Project Operations Core overview
• Microsoft: Oil and gas energy solutions