CRM

Dynamics 365 Field Service: the guide to managing field operations

Dynamics 365 Field Service: the guide to managing field operations

A technician who arrives without the right part, a customer called back three times to set a time slot, a service report re-keyed in the evening at the office, an invoice issued two weeks after the visit: for an SMB or mid-sized company that sells installation, maintenance or after-sales service, these frictions are costly. According to Aquant’s 2026 benchmark, based on data from 161 service organizations, unsuccessful visits account for a median of 25% of total service cost, and up to 44% in the lowest-performing organizations.

Microsoft Dynamics 365 Field Service was designed to manage this cycle end to end, from the customer request to invoicing. Based on the official Microsoft Learn documentation and public pricing, this guide describes what the application actually covers, how scheduling and technicians’ work are organized, what AI changes, how much the licenses cost and how to run the rollout without losing control of your KPIs.

Why managing field operations has become a margin issue

Field service concentrates several costs that are hard to see in a standard dashboard: travel time, repeat trips for the same fault, inventory tied up in vehicles, invoicing delays. The benchmark published by Aquant in February 2026 (nearly 30 million service events analyzed) gives useful orders of magnitude:

  • First-time fix rate: 77% on average, 88% for the best organizations and 60% for the lowest performers.
  • Average time to resolution: 4.5 days on average, 2.5 days for the best and 10 days for the lowest.
  • Remote resolution: about one request in five could be handled without sending a technician.

In other words, the gap between an average service organization and a high-performing one comes down mainly to the quality of information available before the technician leaves: diagnosis, equipment history, parts, skills. That is precisely the role of field service management software such as Field Service, provided it is connected to the rest of the information system.

What Dynamics 365 Field Service covers, from request to invoice

Microsoft describes Field Service as an application that combines workflow automation, scheduling algorithms and mobility. It is built on Dataverse, the same data platform as Dynamics 365 Sales and Dynamics 365 Customer Service. The lifecycle documented on Microsoft Learn has four stages.

1. Creating the work order

A work order can originate from a customer case, a sales order, an email, a phone call, a service agreement, a web portal or a connected-device alert. It groups the tasks to perform, the planned parts, the billable work and the required skills, and it is linked to a customer site and to the equipment concerned.

2. Scheduling

The dispatcher assigns work orders to available resources: employed technicians, subcontractors or equipment. This can be done manually, with a semi-automated assistant or fully automatically (see the next section).

3. Execution in the field

On the mobile app, the technician finds the address, instructions, equipment history and tasks. They take photos, capture a signature, record the parts used and close the work order or request a follow-up.

4. Closing and invoicing

On closing, the equipment history and inventory levels are updated automatically, and an invoice is generated for the parts and labor used. When accounting is kept in Business Central, invoicing can be delegated to the ERP (see below).

Around this cycle, the application also manages customer assets (history of installed equipment), inventory (stock carried in vehicles, purchase requests, purchase orders, product returns) and agreements. Agreements automatically generate work orders and invoices at a defined frequency and over a defined period: quarterly elevator maintenance or a weekly inspection visit, for example. Each agreement is linked to a single customer site, so a multi-site customer requires several agreements.

Scheduling and optimization: sending the right person at the right time

Scheduling is the operational core of Field Service. The schedule board displays resources and jobs on a map, with routes and real-time traffic, and lets you reassign a job by drag and drop. The schedule assistant suggests the time slots and technicians that match the skills, territory and availability.

For larger teams, Microsoft offers Resource Scheduling Optimization (RSO), a paid add-on that automatically assigns multiple jobs to the best-suited resources. According to the Microsoft Learn documentation, RSO:

  • pursues ranked objectives, such as reducing travel time, maximizing resource utilization, prioritizing urgent jobs or scheduling as early as possible;
  • takes into account required skills, location, territory, the time windows promised to the customer and deadlines;
  • can run on a schedule (overnight, for example), be triggered by a flow, or run during the day every 30 minutes;
  • leaves the final say to the dispatcher, who adjusts the result on the schedule board.

The price of RSO depends on the number of resources whose schedule is optimized: Microsoft France lists €26.00 excl. VAT per resource per month (public price checked on November 11, 2026). For an SMB managing about ten technicians over a limited territory, the schedule board and the assistant are often enough; RSO makes sense when the volume of daily jobs makes manual scheduling too slow or too costly in mileage.

Maintenance agreements fit into this logic: automatically generated preventive work orders can be included in the RSO scope to optimize routes.

Technician mobility, connected devices and AI

A mobile app included in the license

The Field Service mobile app runs on iOS, Android and Windows, and it is included in the Field Service license at no extra cost. Built on the Power Platform, it can be customized like the rest of Dynamics 365. Technicians use it to view their bookings on a map, record their time, carry out inspections, scan barcodes, view data from connected equipment and produce their service reports.

Offline mode, essential in basements, rural areas or industrial sites, is enabled through an offline profile configured by the administrator (tables, filters, sync frequency). A point to watch: as of the documentation’s last update (September 2026), Microsoft states that the new mobile experience does not yet support offline work. The choice of mobile experience must therefore reflect actual field conditions.

Connected Field Service: from corrective to predictive maintenance

With Connected Field Service, equipment data flows in through Azure IoT Hub. Rules define the thresholds that trigger an alert, for example a temperature that exceeds a given value. The alert then follows a guided process: creating a case for remote diagnosis, then, if the problem cannot be solved remotely, creating a work order that the technician finds on their mobile device. Repeated alerts from the same device are grouped automatically to avoid duplicates. This is a direct lever on the share of requests that could be handled without a site visit.

Copilot and agents

Microsoft Learn lists several Copilot features in Field Service (documentation updated in July 2026):

  • work order summaries on demand (status, priority, related activities, next steps);
  • updating a work order by text or voice from the mobile app (in preview): status, times, tasks, product lines;
  • creating inspection templates from PDFs or images;
  • natural-language questions about data, help filling in forms and supervision of tasks proposed by agents.

On its pricing page, Microsoft specifies that prebuilt agents and custom agents built in Copilot Studio require Copilot credits, purchased in addition to licenses. The scheduling operations agent is listed there in preview. For a project, it is wise to distinguish generally available features from those in preview before building them into critical processes.

Licenses and costs: what to budget for

The public prices listed by Microsoft France (checked on November 10, 2026, excluding VAT, annual commitment) are as follows:

Profile License Public price What the license covers
Dispatcher, service manager, employed technician Dynamics 365 Field Service €91.00 excl. VAT per user per month Web, mobile and Microsoft 365 access, scheduling and dispatch, maintenance agreements, returns, Copilot for work orders, technician performance analytics
Subcontracted technician Dynamics 365 Field Service Contractor €43.30 excl. VAT per user per month Limited access, designed to assign and track external technicians
High-volume teams Resource Scheduling Optimization Add-on: €26.00 excl. VAT per resource per month Automatic multi-job scheduling
Advanced AI use Copilot credits Based on consumption Running prebuilt agents and Copilot Studio agents

Microsoft notes that these prices are indicative and may vary by currency, country and purchasing channel. Two remarks for building a realistic budget:

  • Think by profile: not everyone involved needs the full license. Subcontractors may qualify for the Contractor license, and users who only view data may qualify for other license types. Our article on optimizing Dynamics 365 licenses explains this approach.
  • Anticipate end of support: the pricing page still mentions access to Dynamics 365 Guides and Remote Assist, but Microsoft Learn states that support for these two mixed-reality applications ends on December 31, 2026. It is better not to build a new process on them.

Integrations: Business Central, Microsoft 365 and reporting

Field Service and Business Central

For an SMB that manages its accounting and inventory in Dynamics 365 Business Central, Microsoft offers a native, bidirectional integration. Technicians and dispatchers work in Field Service; once the work order is completed, the parts and hours consumed flow into Business Central as project journal lines, for posting and invoicing. Statuses are aligned: a “Completed” work order in Field Service becomes “Finished” in Business Central, ready to be posted.

Points to know before getting started, according to the Microsoft Learn documentation:

  • the integration requires a connection to Dataverse, enabling the integration with Dynamics 365 Sales and installing the “Field Service Integration” app from the Marketplace;
  • the “Project and service” option, which also synchronizes service orders, service items and customer assets, requires the Business Central Premium experience;
  • invoicing must be done on one side only: the documentation recommends disabling invoice creation in Field Service when Business Central handles invoicing;
  • item availability can be displayed in Field Service through a virtual table, provided both applications are in the same tenant.

If you are considering a move to Business Central, our guide to migrating to Business Central covers the method, the steps and the pitfalls to avoid.

Microsoft 365: a scope that has changed

According to Microsoft Learn, the Field Service integrations with the Outlook add-in, the Teams app, Viva Connections and Planner are deprecated and no longer supported since October 30, 2025. It is therefore useful to check, during scoping, which integrations are actually available rather than relying on older demos.

Reporting

Field Service includes analytics on work orders, scheduling and customer relationships. To cross-reference this data with finance, contracts or customer satisfaction, most organizations add a Power BI layer fed by Dataverse.

Rolling out Field Service in an SMB or mid-sized company: method and KPIs

A successful Field Service project rarely starts with the tool. It starts with a precise map of a job’s journey, including its exceptions. Here is a five-step approach suited to the size of an SMB or mid-sized company:

  1. Map the actual flows: origin of requests, job types, skills, agreements, parts, invoicing rules. A Health Check assessment provides an objective starting point when tools are already in place.
  2. Make master data reliable: customer sites, installed equipment, parts catalog, technician skills. Without a clean reference base, neither scheduling nor equipment history can be used.
  3. Start with a pilot scope: one region, one equipment family or one agreement type, with manual or assisted scheduling before enabling automatic optimization.
  4. Equip and train technicians: test offline mode in the field, simplify mobile forms, plan adoption support.
  5. Connect the ERP and reporting once the process is stable, then extend gradually to the rest of the organization.

KPIs to track from the pilot onward:

  • first-time fix rate, to compare with the Aquant benchmark (77% on average);
  • time to resolution and adherence to promised time windows;
  • share of requests handled remotely;
  • technician utilization rate and travel time;
  • time between job completion and invoice.

At Activops, a firm specializing in Dynamics 365 since 2016, we support these projects from scoping to adoption, with particular attention to integration between field service, CRM and operations. Our Dynamics 365 Field Service integrator page presents our approach, and our implementation and integration offer details how a project unfolds.

Frequently asked questions

What is Dynamics 365 Field Service?
It is Microsoft’s application for managing on-site service. It covers work order creation, technician scheduling, the mobile app, parts inventory, maintenance agreements, equipment tracking and service invoicing.

How much does a Dynamics 365 Field Service license cost?
As of November 10, 2026, Microsoft France lists €91.00 excl. VAT per user per month for Dynamics 365 Field Service and €43.30 excl. VAT for the Contractor license intended for external technicians, with an annual commitment. Resource Scheduling Optimization and Copilot credits are billed on top.

Does the Field Service mobile app work without a network?
Yes, the mobile app can work offline once an administrator has configured an offline profile. According to Microsoft Learn (September 2026), however, the new mobile experience does not yet support this mode.

Can Field Service integrate with Business Central?
Yes. The native integration is bidirectional: parts and hours from completed work orders flow into Business Central for posting and invoicing. Synchronizing service orders and assets requires the Business Central Premium experience.

Is Resource Scheduling Optimization essential?
No. The schedule board and the schedule assistant are included. RSO, a paid add-on, makes sense when the volume of jobs makes manual scheduling too slow or too costly in travel.

Which KPIs should you track after rollout?
The most useful KPIs are the first-time fix rate, time to resolution, adherence to promised time slots, the share of requests handled remotely, technician utilization and the time between job completion and invoice.

Sources

  • Microsoft Learn, Overview of Dynamics 365 Field Service (French version), updated August 13, 2026 — learn.microsoft.com
  • Microsoft Learn, Overview of Resource Scheduling Optimization, updated March 24, 2026 — learn.microsoft.com
  • Microsoft Learn, Set up agreements to automatically generate work orders and invoices, updated August 28, 2026 — learn.microsoft.com
  • Microsoft Learn, Dynamics 365 Field Service mobile app overview, updated September 17, 2026 — learn.microsoft.com
  • Microsoft Learn, Create IoT alerts and convert IoT alerts into work orders, updated July 15, 2026 — learn.microsoft.com
  • Microsoft Learn, Copilot in Field Service overview, updated July 18, 2026 — learn.microsoft.com
  • Microsoft Learn, Integrate with Microsoft Dynamics 365 Field Service (Business Central), updated June 6, 2025 — learn.microsoft.com
  • Microsoft Learn, Overview of Field Service integrations (French version), updated March 7, 2026 — learn.microsoft.com
  • Microsoft Learn, Manage Field Service work orders with Microsoft 365 overview, updated September 9, 2026 — learn.microsoft.com
  • Microsoft, Dynamics 365 Field Service pricing (France), accessed November 10, 2026 — www.microsoft.com
  • Aquant, 2026 Field Service KPI Benchmark, February 2026 — aquant.ai

White paper: business-led transformation

Put a pragmatic strategy before the tools. Get the Activops white paper by email (in French).