Dynamics 365 Field Service Integration Retires: What Replaces It?

Quick answer. As of October 2026, Microsoft says both the Data Integrator templates for Dynamics 365 Field Service and the Field Service integration with finance and operations applications stop after February 28, 2027, and, according to Microsoft Learn’s Field Service feature deprecations page, the capability “is transitioning to the Field Service and Project Operations integration”, so an estate posting work orders into Finance and Supply Chain Management has to choose a deployment model, license the user who installs the new integration for Project Operations, and cut over before that date. According to Microsoft Learn, the model decides where inventory lives (Field Service keeps it without Finance; Finance owns it in the integrated model, where Field Service inventory management is disabled), and Microsoft’s setup page asks you to uninstall the legacy integration before enabling the new one, so the order is model, then license and prerequisites, then a tested cutover. In GCC, GCC High and DoD, Microsoft’s Field Service government table, dated August 28, 2026, lists the Field Service and Project Operations integration as not available, so a government-cloud estate plans its path from what its cloud lists today and rechecks the table.

At month end, the controller expects the labor and parts your technicians used on work orders to be in the ledger as journals, and no one on the finance side thinks about the integration that puts them there. Then a Microsoft notice says that integration stops on a fixed date, with no extension language, and names a replacement that is not the same shape. This guide sets out which of the two retiring mechanisms your estate runs, what the replacement moves, what it needs before it can be installed, the order of work before February 28, 2027, and what to do if your cloud does not list the replacement.

What stops on February 28, 2027, and what keeps working until then

If you plan for one retirement and your estate runs the other, the inventory is wrong before it starts, because two different mechanisms end on the same day. The first is the older template-based link. Microsoft Learn’s list of removed or deprecated platform features for finance and operations states: “The Data Integrator templates for Dynamics 365 Field Service will no longer be available after February 28, 2027”. The same entry states: “This integration works by synchronizing work orders, agreements, inventory, and projects between Field Service and Supply Chain Management.” Its stated reason: “This functionality is scheduled to be replaced by a simpler, more integrated Field Service experience.”

The second is the newer, dual-write based integration. Microsoft Learn’s Field Service feature deprecations page, in a notice dated December 1, 2025, states: “The Field Service integration with finance and operations applications won’t be available after February 28, 2027. This capability is transitioning to the Field Service and Project Operations integration.” According to Microsoft Learn’s page on the Field Service integration with finance and operations applications, “The integration relies on the enabled dual-write framework and the mappings to ensure that transactions use a common understanding of critical core concepts.” That page also says what it does for the ledger: “Field Service transactions (work order product and work order service records) create parallel transactions on their respective finance and operations project in the form of journals.” The same deprecations page lists a separate Field Service family date, Guides and Remote Assist after December 31, 2026, which is its own retirement and not part of this one.

How the two are built differs, and that matters for the inventory. According to Microsoft Learn’s Data Integrator page, “The Data Integrator (for Admins) is a point-to-point integration service used to integrate data into Dataverse.” Template names are how you find it in an estate; one example, from Microsoft Learn’s page on synchronizing work orders to sales orders, is “The Work orders to Sales orders (Field Service to Supply Chain Management) template is used to run synchronization.”

What keeps working until the date is also stated, with conditions. According to Microsoft Learn’s Field Service feature deprecations page, “Environments that already have the integration enabled retain access and can continue until February 28, 2027.” New installs are already closed: “Starting with the Field Service 8.8.139.398 release, the Install Finance and Operations toggle isn’t available in environments where the finance and operations integration isn’t already installed or configured.” On what deprecation means, the same page states: “The feature or capability continues to work and is fully supported until it’s officially removed.” And after the date: “After removal, the feature or capability no longer works.”

This guide’s own planning rule, not Microsoft’s: find which of the two mechanisms you run (or whether you run both), list every template or map in use, and name the financial and inventory records each one moves, before anyone chooses a replacement model.

What the Field Service and Project Operations integration changes

If the replacement is treated as a new connector for the same flow, the first surprise is where the money is interpreted. According to Microsoft Learn’s page on deployment models and inventory, when an admin enables the Field Service and Project Operations integration, “Project Operations becomes the system that financially interprets work order activity.” Microsoft Learn’s overview of the Field Service integration with Project Operations describes the aim: “The out-of-the-box integration between Microsoft Dynamics 365 Field Service and Dynamics 365 Project Operations provides a supported mechanism for connecting field execution with project financials.” The same overview states: “The result is a continuous financial pipeline: from work order to project and contract line, to proforma invoice, to posted invoice in Finance.”

For the technicians, Microsoft describes little change. According to Microsoft’s release plan entry, Connect Field Service to finance and operations, “Technicians can continue using Field Service without any changes to their workflows.” According to the companion entry, Link work orders to projects for unified financials, you can “Link work orders and agreements in Field Service directly to projects in Project Operations.” Both entries show general availability on January 30, 2026. Microsoft Learn now states on the first entry: “As of October 2026, this content is archived and no longer maintained.” A later change may therefore appear on Microsoft’s roadmap rather than on these pages.

The overview on Microsoft Learn names three ways an organization can use the integration, and they are three different designs, not three installation options:

• “Field Service, Project Operations, Finance, and Supply Chain Management, which deliver full end-to-end service, project, and financial orchestration.”
• “Field Service, Finance, and Supply Chain Management, without using the Project Operations application.”
• “Field Service and Project Operations, without using Finance and Supply Chain Management.”

Of the last pattern, the overview adds: “This approach can be used for integration to other ERP solutions or for direct execution and management purposes.”

Inventory is where the model choice bites. The page on deployment models and inventory describes two named models. For Project Operations Core (Lite) without Finance, it states: “In this model, Project Operations manages project financials and invoicing. Field Service remains the system of record for inventory.” For Integrated Project Operations with Finance, it states: “In this model, Finance becomes the system of record for inventory and accounting. Field Service inventory management is disabled.” Compare that with the retiring path: according to Microsoft Learn’s page on the finance and operations integration, “When you enable the finance and operations integration from the Field Service Settings, Dynamics 365 Supply Chain Management becomes the system of record for inventory.”

This guide’s own planning rule, not Microsoft’s: choose the model by where inventory and financial posting must live after the move, not by which one installs fastest, and write down which system owns inventory before and after, so no one discovers the change during a close.

Prerequisites and the license line for the Field Service and Project Operations integration

A replacement that cannot be installed on the day of cutover is not a plan, and the blocking items for this integration are licensing and versions, not configuration. According to Microsoft Learn’s page on setting up the Field Service integration with Project Operations, “To download and install the Dynamics 365 Field Service and Project Operations integration package, the installing user must have at least one Project Operations license.” The overview repeats the condition in its description of the model without the Project Operations application: “The user who installs the integration must have a Project Operations license.” Both statements name the user who installs the integration; neither says every Field Service user needs one, and this guide does not either.

That setup page also names a second owner to plan for: “The Field Service and Project Operations Integration package includes a flow that runs regularly under the user who installs the package.” That makes the installing account an operational dependency, so review its licensing for that flow and decide who owns the account after go-live.

The setup page lists these prerequisites, among others:

• “You have Field Service minimum version 8.8.142.0.”
• “You have Project Operations minimum version 4.162.0.0.”
• “If you have the Field Service integration with finance and operations applications (legacy), uninstall it.”
• “If you want to integrate with Dynamics 365 finance and operations, configure dual-write integration.”

That last condition means dual-write stays in the picture for any model that posts to Finance, which fits Microsoft’s general direction on the older service: according to Microsoft Learn’s Data Integrator page, “We highly recommend customers start using dual-write, which provides tightly coupled, bidirectional integration between finance and operations apps and Dataverse.” What dual-write changes in Dataverse is a broader integration question, covered in Microsoft integration during an ERP or CRM migration.

This guide’s own planning rule, not Microsoft’s: put the Project Operations license for the installing user, the owner of the recurring flow and the two version upgrades into the budget and the change calendar before the design is signed. This guide states no price and no license SKU; confirm both with Microsoft’s licensing guide.

The order of work before February 28, 2027

What to plan against is not a late start; it is a cutover that lands inside a close, with the old path already uninstalled and the new one holding transactions it cannot post. Microsoft’s own conditions set the order. The setup page on Microsoft Learn asks you to uninstall the legacy integration before the new one is enabled, so the cutover is a planned switch of paths, not a side-by-side overlap in one environment. And according to Microsoft Learn’s page on company alignment and legal entities, “If the service account and the company don’t match on a work order and the work order transactional records, transactions don’t synchronize until the discrepancy is resolved.”

The following sequence is this guide’s recommended order, not a sequence Microsoft publishes; it is built on the conditions quoted from Microsoft Learn’s Field Service feature deprecations page, the setup page and the deployment models page:

1. Inventory the current integration: which retiring mechanism, every template or map, and the journals and inventory records each one moves.
2. Choose the deployment model, and record which system owns inventory and posting before and after the move.
3. License the installing user for Project Operations, name the owner of the recurring flow, and schedule the Field Service and Project Operations version upgrades.
4. Configure the new integration in a sandbox, with service accounts and companies aligned and checked on sample work orders.
5. Reconcile at least one period of work order journals, old path against new, in the sandbox, and agree the differences with the controller.
6. Cut over outside a financial close: uninstall the legacy integration, enable the new one, and post a first set of live work orders under watch.
7. Retire the old path and its templates or maps, and record the date.

Existing environments keep the old integration until the date, so the window is real, but it closes for everyone at once: after removal, according to Microsoft Learn, the feature no longer works.

If your Field Service estate runs in GCC, GCC High or DoD

If you run Field Service in a US government cloud, read your cloud’s column before you plan the move to the Field Service and Project Operations integration, because Microsoft’s tables do not list the named replacement there. Microsoft Learn’s page on Dynamics 365 Field Service in US government clouds, dated August 28, 2026, states: “The following table lists which Field Service services are currently supported in each cloud.” In that table, the Field Service and Project Operations integration is marked Not Available in the GCC, GCC High and DoD columns, while Dynamics 365 Field Service itself is marked Available in all three. The same page states: “Microsoft continues to evaluate these services and capabilities for inclusion and updates in future releases.”

The broader table points the same way. Microsoft Learn’s Dynamics 365 US Government service description, last updated October 6, 2026, lists Dynamics 365 Project Operations in the GCC column only, with nothing in the GCC High and DoD columns, and tells readers to check back on a monthly basis. For the full app availability table and how to vet an implementer for these clouds, see Dynamics 365 implementation for government contractors.

What those tables do not say matters as much. As of their dates, Microsoft’s tables do not list the Field Service and Project Operations integration for these clouds; this guide does not say whether or when that changes, and the government table has no row for the retiring finance and operations integration, so this guide makes no claim about whether the legacy path runs in your cloud today. If you are still deciding whether Field Service fits a regulated field workforce in a government cloud at all, that is a separate question with its own checklist.

These options are this guide’s framing, not Microsoft’s advice, and none is presented as Microsoft’s recommendation:

• Raise the gap with Microsoft through your account team, and record the answer with its date.
• Keep posting work order costs to Finance through an integration the estate builds on Microsoft mechanisms your cloud lists, designed and tested before the date.
• Move the financial step to a manual or batch process for an interim period, with its control owner named.

This guide’s own planning rule: read your cloud’s column first, and if the replacement is not in it, choose one of the options by name before the date, with an owner and a dated record of what Microsoft’s tables showed when you chose.

When this guide is the wrong starting point

Before you start, check whether your estate needs this work at all; some estates need a different piece of work instead:

• Your Field Service does not post to Finance and Supply Chain Management through either retiring mechanism. Then nothing in this guide applies to you.
• You use dual-write table maps between Field Service and Supply Chain Management only for records such as warehouses, customer assets or purchase orders. The retirement notices name the integration and the templates; Microsoft Learn’s page on integrating Field Service and Supply Chain Management carries no retirement notice as of its read date, and this guide does not say those maps change or continue.
• You are already planning to replace your ERP or to leave Field Service. Then the model choice follows that program, not this date.
• The real question is which third-party integration product or partner to use. That is a product decision this guide does not make.

What to ask of whoever moves the integration with you

Whoever does this work with you, inside the organization or outside it, hold it to these criteria, stated as what they should be able to show you:

• Which retiring mechanism they found, and every template or map in it.
• The deployment model chosen, and where inventory and financial posting live after it.
• Who holds the installing license, and who owns the recurring flow.
• The company alignment check on service accounts and work orders.
• One reconciled period of work order journals, old path against new, before cutover.
• The date the old path was retired.
• In a government cloud, the dated reading of your cloud’s column and the option chosen, with its owner.
• The configuration and the runbook, handed to your own team to keep.

No firm or product is named or compared in that list.

How i3solutions answers

i3solutions has delivered Dynamics 365 integration engagements for regulated enterprises across healthcare, defense and aerospace manufacturing, and financial services. For this retirement, the work is a project, with embedded specialists where your team needs them, that inventories the current Field Service integration, designs the move to the Field Service and Project Operations integration or, in a government cloud, the integration path your cloud supports, builds and configures it, and reconciles it before cutover. i3solutions builds Dynamics 365 integrations using named Microsoft mechanisms including Dataverse, dual write, virtual tables, Azure Logic Apps, Azure Service Bus, and Power Automate connectors. Delivery is senior and US-based. i3solutions has been a Microsoft Partner with 30 years of enterprise technology delivery experience and has delivered 1,500+ Microsoft engagements across aerospace and defense, financial services, and health sciences. An i3solutions project engagement does not by itself include ongoing support of what it delivers, which i3solutions scopes separately as Application Managed Services, and it is not a replacement for the internal team, open-ended scope expansion, or vendor lock-in.

For how this fits the wider Dynamics 365 estate, see Dynamics 365 development services.

Key Takeaways

Every takeaway is drawn from Microsoft Learn’s Field Service feature deprecations page, its list of removed or deprecated platform features for finance and operations, and its Project Operations integration and government pages cited in this guide, all re-read on drafting day, except where a line says it is this guide’s own rule:

• Two mechanisms end after February 28, 2027: the Data Integrator templates for Field Service and the dual-write based Field Service integration with finance and operations applications.
• Microsoft names one replacement for the capability: the Field Service and Project Operations integration.
• The user who installs it needs a Project Operations license, and the legacy integration is uninstalled first.
• The deployment model decides whether Field Service or Finance owns inventory.
• Microsoft’s Field Service government table lists the Field Service and Project Operations integration as not available in GCC, GCC High and DoD.
• This guide’s own rule: choose the model first, license and upgrade next, then reconcile and cut over outside a close.

Frequently Asked Questions

Are the Field Service Data Integrator templates being retired?

Yes. According to Microsoft Learn, the Data Integrator templates for Dynamics 365 Field Service will no longer be available after February 28, 2027. Microsoft Learn says that integration works by synchronizing work orders, agreements, inventory, and projects between Field Service and Supply Chain Management.

What is the difference between the Data Integrator templates and the dual-write Field Service integration, and do both end in February 2027?

They are two mechanisms, and both end. According to Microsoft Learn, the Data Integrator is a point-to-point integration service used to integrate data into Dataverse, and the Field Service integration with finance and operations applications relies on the enabled dual-write framework. Microsoft Learn states that the Data Integrator templates for Field Service will no longer be available after February 28, 2027, and that the Field Service integration with finance and operations applications won’t be available after February 28, 2027 and is transitioning to the Field Service and Project Operations integration.

Do we need a Project Operations license to move to the Field Service and Project Operations integration?

The installing user does. According to Microsoft Learn, to download and install the Dynamics 365 Field Service and Project Operations integration package, the installing user must have at least one Project Operations license, and the package includes a flow that runs regularly under the user who installs it.

Where does inventory live after we move to the Field Service and Project Operations integration?

It depends on the deployment model. According to Microsoft Learn, in Project Operations Core (Lite) without Finance, Field Service remains the system of record for inventory; in Integrated Project Operations with Finance, Finance becomes the system of record for inventory and accounting, and Field Service inventory management is disabled.

Is the Field Service and Project Operations integration available in GCC High?

Not according to Microsoft’s table as of its date. According to Microsoft Learn’s page on Field Service in US government clouds, dated August 28, 2026, the Field Service and Project Operations integration is Not Available in GCC, GCC High and DoD, and Microsoft continues to evaluate these services and capabilities for inclusion and updates in future releases.