Dynamics 365 Field Service

Dynamics 365 Field Service is Microsoft first-party field service application, sitting in the enterprise half of this category rather than the trades half. It is not a product a two-truck contractor buys: entry list pricing is 105.00 per user per month paid yearly, and the application runs on Dataverse and Power Platform, so a buyer is taking on a platform as well as an app. The natural buyer already runs Dynamics 365 elsewhere.

Microsoft documents four distinct service delivery models out of the box, which is unusual breadth: reactive break-fix, preventive work generated from agreements, predictive work driven by IoT signals through Connected Field Service, and project-based work via Project Operations. Work orders can originate from cases, sales orders, email, agreements, web portals or IoT devices. The schedule board supports manual drag-and-drop dispatch, a scheduling assistant, or fully automated assignment through Resource Scheduling Optimization, which Microsoft documents as a separate add-on rather than an included feature. Routing is bundled into that scheduling optimisation rather than sold as a standalone engine, with resources and jobs shown on a map alongside live traffic.

The strongest differentiator is the Business Central integration. Microsoft publishes the actual table mappings, which is rare: project lines to work order products and services, Business Central service orders to Field Service work orders, service items to customer assets, and Business Central locations to Field Service warehouses. Invoicing happens on the Business Central side. The catch is licensing: the deeper Project and Service integration mode requires Business Central Premium, because service management features are not available on Essentials.

• Offline is the honest weak point. Microsoft contradicts itself. The live mobile overview frames offline as something an administrator configures, and states plainly that the refreshed mobile experience does not currently support working offline. Other Microsoft-owned surfaces, including the docs source mirror and a Learn training module, describe offline as on by default. Microsoft also maintains a dedicated offline profile best practices and limitations page plus troubleshooting pages for missing offline data, which tells you offline needs deliberate engineering rather than a switch.
• Mobile is included in the Field Service licence at no extra charge on iOS, Android and Windows 10 and later.
• Quoting, SLA management and a documented Field Service API were not verifiable on any Microsoft page opened during research. They are recorded as unknown, not absent.

Good fit: organisations already standardised on Microsoft, particularly those running Business Central as the ERP and wanting completed work orders to flow into it for invoicing without custom middleware. Also a good fit where service work spans several delivery models at once, for example a manufacturer running contract-based preventive maintenance alongside reactive calls and IoT-triggered work. Teams that already have Power Platform skills in house will get far more out of it than teams that do not, because the mobile app is a model-driven Power Apps app and customisation happens at that layer.

Poor fit: small contractors. At 105.00 per user per month on an annual commitment, plus a Dataverse dependency and a likely Resource Scheduling Optimization add-on for real automated scheduling, the landed cost is far above the trades products in this category. It is also a poor fit for crews that genuinely work with no signal for hours at a time, at least until Microsoft resolves the inconsistency between its offline documentation and its statement that the newer mobile experience does not support offline. Verify offline behaviour against your specific target release before committing.

Typical use cases: equipment manufacturers servicing an installed base, utilities dispatching outage and maintenance work, medical device field engineering, facilities and HVAC maintenance organisations, and in-home care scheduling. Microsoft names these industries in its own documentation.