What is Dynamics 365 Field Service?

Dynamics 365 Field Service is Microsoft's application for organisations that send technicians or engineers to a customer site to perform work. Typical customers are equipment manufacturers running maintenance contracts, facilities-management firms, utilities, telecoms, medical-device service teams, and home-service businesses — anywhere a work order, a person, a vehicle, and an asset at a customer location have to line up in time and space.

Where it fits

Field Service is one of the CRM-lineage Dynamics 365 apps, running on the same Dataverse as Sales, Customer Service, Marketing, and Customer Insights. The shared platform matters because the field service business rarely stands alone: a case opened in Customer Service becomes a work order in Field Service, an asset installed by Sales gets serviced by Field Service, and the technician's arrival photo lands on the same customer timeline as the sales conversation.

In the market, Field Service competes primarily with ServiceNow Field Service Management, Salesforce Field Service, IFS Field Service Management, and specialised products like ServiceMax (for equipment manufacturers). It wins on integration into Microsoft 365 and Dynamics 365, on the maturity of its scheduling engine, and on the fact that IoT-connected scenarios (Azure IoT feeding work orders) are a first-class capability rather than a partner add-on.

Work orders

The central object is the work order, generated from a case, a phone-logged incident, a preventive maintenance schedule, an IoT alert, or a customer portal request. It carries the customer, the asset being worked on, the location (with geocoded coordinates), the products and services required, the estimated time, the skills needed, priority, SLA, and a status lifecycle that runs Scheduled → Travelling → On Site → Complete → Posted.

Work orders can be simple (one visit, one technician) or complex (multi-day, multi-technician, with dependencies between tasks). Requirement groups model the "one person to unload the equipment plus two more to install it plus a certified electrician to sign it off" scenario without contorting the data model — see crew jobs and multi-resource bookings for the scheduling side of that same scenario. Complex assets with parent-child structure of their own are covered in asset hierarchies.

An incident type template configures the standard work: the tasks, the parts, the skills, and the estimated duration for a "boiler service" or a "meter replacement". Work orders created from an incident type inherit all of it and can be tuned per booking.

Scheduling

A configurable schedule board lets dispatchers drag work orders onto technicians. Filters, colour codes, capacity views, and heat maps make the day's plan legible; conflict detection prevents double-booking.

The schedule assistant finds available slots for a single work order against skills, working hours, travel time, and stock — the answer to "when could Emma fit this in this week". It's used both by dispatchers picking up ad-hoc bookings and by self-service portals letting customers pick their own slot.

Resource Scheduling Optimization (RSO) is the optional engine that plans the whole day for the whole fleet — an NP-hard combinatorial problem of routes, skills, time windows, SLA priorities, and travel time. RSO can be run on demand, on a schedule, or continuously; it typically lifts productive time on a fleet by 5–15% over hand-scheduling. It carries its own licence.

Mobile app

Technicians work from a first-class mobile app that runs on iOS and Android, online and offline. Offline is the key word: field crews spend a serious portion of the day in low- or no-coverage zones, and an app that only works online is not usable.

The app carries the day's bookings, navigation to each site, customer history, asset records including previous work orders on that asset, knowledge articles, parts inventory on the truck, and the forms to record time on and off, parts used, photos of the work, customer signatures, and inspection results. Custom forms are built with the same Power Apps designer used for the model-driven Dataverse apps.

Location tracking on the mobile app feeds real-time arrival estimates back to dispatch and to the customer. Vehicle information (odometer, fuel) can be recorded per visit for fleet compliance.

Connected assets and IoT

A hierarchical customer asset model tracks equipment installed at customer sites — parent asset, sub-components, serial numbers, warranty status, maintenance history, technical specs. Warranty and contract entitlements attach to the asset, so the right terms apply to any work on it.

IoT integration through Azure IoT or Connected Field Service lets devices raise alerts that automatically generate work orders — the "the boiler is going to fail" scenario. Anomaly detection on the device data can decide whether to dispatch a technician, order a spare part in advance, or attempt a remote reset first. When a remote fix works, the incident closes without a truck roll — the highest-margin outcome in field service.

Copilot in Field Service summarises the work order for a technician on arrival, drafts the completion notes from the technician's spoken summary, and finds relevant knowledge articles inside the mobile app.

Inventory and parts

Truck-stock inventory is tracked per resource. Parts consumed on a job decrement the truck's stock and trigger replenishment against warehouse master data. Non-stock parts are ordered to the customer site or the local depot with lead-time visibility.

For manufacturers, serialised parts and batch tracking carry through, so warranty claims and recall notices tie back to the specific unit installed at a specific site.

Integration to Business Central or Dynamics 365 Supply Chain Management makes the warehouse master data the source of truth; Field Service becomes the consumption layer.

Customer experience

Customers receive arrival windows, real-time technician tracking (an ETA that updates as the technician moves), and post-job surveys (via Customer Voice or an external tool). A self-service portal built with Power Pages lets customers log requests, see the status of open work, and pick appointment slots.

SLA management tracks response and resolution commitments per customer or asset. Missed SLAs escalate through configurable rules; kept SLAs feed the customer's account manager for renewal conversations.

Contract and billing

Agreements model recurring service — a monthly boiler check, a quarterly compliance inspection — and generate work orders on the agreed cadence with the agreed pricing. The agreement carries the SLA, the included parts, and the labour rates.

Billable work rolls up to invoice: labour hours, parts consumed, and travel per the agreement terms. Billing flows out to Business Central, Dynamics 365 Finance, or a third-party ERP through standard integrations. For services businesses running Project Operations alongside Field Service, project accounting picks up the profitability roll-up.

Licensing

Sold per user. Two main SKUs plus a specialised one:

Field Service — the standard licence for technicians, dispatchers, and admins. Covers all functionality on the desktop and mobile app.

Field Service Contractor — a lower-cost licence for third-party contractors who need mobile access to receive and complete work orders but no dispatch or admin capability.

Frontline Worker — a device-based option for high-volume technician fleets where per-user pricing doesn't fit the economics.

Resource Scheduling Optimization carries a separate add-on licence. Copilot for Field Service is licensed as part of Field Service Enterprise or as an add-on.

Attach licensing lets users who already hold another Dynamics 365 app add Field Service at a reduced base price — common in equipment-manufacturer deployments where the same seats run Sales and Field Service.

When Field Service is the wrong fit

Field Service is aimed at enterprise dispatch — dozens to thousands of technicians, connected assets, IoT, complex agreements. Below that scale, or in adjacent scenarios, other tools usually win:

• Under ~10 technicians running simple jobs. ServiceTitan (trades), Jobber (small services), and Housecall Pro (home services) are up and running in a day. Field Service can serve this too, but the setup burden and licence cost only pay off when the scheduling problem is real.
• Pure services firms (audit, consulting, agency work). Billable time and expenses without physical assets or trucks belong in Project Operations, not Field Service. The two apps look similar on the surface and are frequently confused — see Field Service vs Project Operations for the split.
• Fleet-management-first operations. Where the job is optimising the fleet itself (fuel, safety, telematics), Samsara, Verizon Connect, or Geotab are the primary system and Field Service is at best a secondary consumer.
• Committed ServiceMax on Salesforce. Equipment manufacturers deeply invested in ServiceMax for asset-heavy service management rarely see a payback from switching — the migration is expensive and ServiceMax has decades of vertical depth.
• No Microsoft footprint at all. No Sales, no Customer Service, no BC or F&O, no Microsoft 365 adoption — the shared-Dataverse advantage disappears and specialists usually deliver more per licence dollar.

The tell that Field Service is the right platform: the customer already runs Dynamics 365 or Microsoft 365 heavily, has more than a handful of technicians, cares about scheduling optimisation as a distinct problem, and either has connected assets today or is planning to.

First-time buyer checklist

Answer these before signing an order form:

1. Technician count and dispatcher count. Two very different licence categories. Contractors get their own cheaper SKU.
2. RSO or hand-scheduling. Resource Scheduling Optimization is a separate add-on. It typically lifts productive time 5–15% on a real fleet; below ~20 technicians the payback is longer and hand-scheduling is defensible.
3. Copilot. Bundled with Field Service Enterprise or added on top. Decide the plan (which flows, which surfaces) before licensing.
4. Mobile. Which OSes, which devices, and — critically — how much offline time per day? Confirm the offline design covers the actual coverage gaps, not just the demo.
5. Assets and IoT. Are we tracking customer-installed equipment? If yes, plan the asset model and inheritance rules early — it is the hardest thing to retrofit. If IoT-triggered work orders are in scope, budget for Azure IoT alongside Field Service licences.
6. Inventory. Truck stock only, or full warehouse integration back to Business Central / F&O? Decide the source of truth for parts before rollout.
7. Agreements and billing. Do we run recurring service (maintenance contracts)? Agreements generate work orders on cadence; without them, everything is ad-hoc. Where does invoicing happen — BC, F&O, or a third-party ERP?
8. Customer experience. Real-time technician tracking, arrival window notifications, self-service booking — which are on day one, which are later? A Power Pages portal is a separate licence and a separate implementation project.
9. SLA and warranty. How are commitments per customer or per asset represented today? Get the taxonomy right before it is enforced by the system.
10. Change management. Technicians are often the last group in the org to accept a new system. Involve them in mobile form design; a mobile experience they resent is the number-one reason field-service projects fail.

Microsoft's FastTrack team and a specialist Field Service partner can pressure-test all of this. The point is to have the answers before licences are bought, not after.

Where to go next

Follow a job through the work order lifecycle, plan a fleet with Resource Scheduling Optimization, and equip technicians with the Field Service mobile app. Connected Field Service and IoT covers the device-triggered scenarios. If you are unsure whether this or Project Operations is the right app, Field Service vs Project Operations draws the line. The scheduling and asset-maintenance model here is the same one behind heavy-maintenance verticals like Dynamics 365 for railways, Dynamics 365 for shipping and maritime, and Dynamics 365 for airlines, where the work order is a maintenance check rather than a customer visit.