Insights · Knowledge, not a service
The field-operations application of the Customer Engagement family. Built on the FieldOne scheduling engine acquired in 2015. Two licence types — Dispatcher for the back office and Frontline Worker for technicians.
What is Dynamics 365 Field Service?
Microsoft Dynamics 365 Field Service is Microsoft's cloud-based field-operations application. It orchestrates the full lifecycle of on-site work — from incident creation through scheduling, dispatch, technician execution, parts logistics and customer signature.
Functionally it includes:
Field Service runs on Dataverse and integrates natively with Customer Service (case-to-work-order), Sales (opportunity-to-service-contract), Business Central or Finance (parts and invoicing).
Predecessor & history
Microsoft's field-service offering did not grow organically. In 2015 Microsoft acquired FieldOne Systems, a third-party field-service-management product running on the Dynamics CRM platform. FieldOne was rebranded to Field Service and made a first-class Dynamics 365 application with the 2016 rebrand.
Milestones:
Customers from older FieldOne or early Field Service deployments have a documented migration path — most upgrade work is around mobile-app rework, since the technician app has changed substantially.
Licensing tiers
Unlike Sales and Customer Service, Field Service uses a split licensing model that distinguishes between dispatchers and technicians. All prices: list prices, net, per user per month, annual commitment. As of May 2026.
| Licence | List price | What's included |
|---|---|---|
| Field Service (Dispatcher) | approx. EUR 95/user/month | Full back-office functionality: schedule board, schedule assistant, work-order configuration, asset management, agreements, reporting. For dispatchers, planners, service managers. |
| Field Service Frontline Worker | approx. EUR 20/resource/month | Reduced licence for technicians: receive work orders, capture time and parts, photos, signature. No back-office configuration. Replaces the older "Field Service Resource" licence. |
| Resource Scheduling Optimization | add-on, approx. EUR 30/user/month | AI-based optimisation engine — minimises travel, balances workload, respects skills and SLAs. Typically purchased for the dispatcher group, not all users. |
Attach licence: if you already have Customer Service Enterprise or Sales Enterprise, you can attach Field Service Dispatcher at a reduced price (approx. EUR 25/user/month).
Use cases
Field Service is less suitable for pure office-based service teams (use Customer Service), for very small technician teams (under 5 resources) without dispatch needs, or for project-based on-site work where Project Operations fits better.
If you want Field Service implemented
This page frames the terminology and licensing. If you want Field Service configured, migrated or extended, here is the right place: Microsoft Dynamics 365 Field Service — service page. There you will find our approach, references and price indications for discovery, implementation and dispatcher coaching.
Frequently asked questions
Two licence types: Dispatcher / full user at approx. EUR 95/user/month for back-office planning and configuration; Field Service Frontline Worker at approx. EUR 20/resource/month for technicians who use the mobile app to receive work orders, capture time and parts. The split keeps the technician cost low while giving dispatchers full functionality.
Field Service contains case-related entities (Incident Type, Asset) but no full case-management workspace. Many setups have Customer Service for inbound triage and Field Service for on-site dispatch. The two apps share Dataverse data natively — a case converts to a work order with one click.
Field Service integrates natively with Azure IoT, Connected Field Service and Connected Customer Service. Sensor data triggers work orders before a customer reports an issue. Typical for elevator, HVAC and industrial-equipment vendors who want to move from reactive to predictive service.
FieldOne was a third-party field-service product acquired by Microsoft in 2015 and rebranded as Field Service. Its scheduling engine is the foundation of today's Resource Scheduling Optimization. The acquisition is why Field Service exists as a separate app rather than a Customer Service extension.
6–12 months from discovery to go-live. The technician mobile app, asset hierarchy, scheduling rules and parts handling all need careful design. With Resource Scheduling Optimization, IoT integration or multi-country setup, more typically 9–18 months.
30 min introduction
Which licensing mix? Which dispatch optimisation? Which IoT integration? Let's talk.
