Connected Field Service and IoT

Connected Field Service is the part of Dynamics 365 Field Service that bridges physical equipment in the world to the work-order system. Instead of waiting for a customer to call and report a problem, the equipment itself reports its state — temperature, vibration, error codes, usage — and the system decides whether to dispatch a technician, attempt remote resolution, or alert proactively before a fault becomes an outage.

The data flow.

1. Equipment (HVAC units, industrial machinery, medical devices, refrigeration, vehicle fleets) emits telemetry — typically via cellular, WiFi, or LoRa to a cloud endpoint.
2. Azure IoT Hub (or another IoT platform) ingests, authenticates, and routes the messages.
3. Stream Analytics or custom code processes the stream — thresholds, anomaly detection, ML model scoring.
4. Alerts are raised when a condition matches — temperature out of range, vibration above tolerance, error code emitted, predicted failure within N days.
5. Connected Field Service receives alerts and decides what to do: try remote resolution (send a command back to the device), schedule a preventive work order, escalate to dispatch, notify a customer.

Connected Field Service in the agent's view. Inside the Field Service application, alerts appear as IoT alerts linked to customer assets. Agents (or automated rules) can:

• Acknowledge — record awareness of the alert.
• Take action remotely — execute commands sent back to the device (restart, reset thresholds, run diagnostics).
• Create a work order — dispatch a technician with the right skills, parts, and context.
• Mark as false positive — feedback that improves anomaly-detection models.

Anomaly detection. Beyond rule-based thresholds (temperature > 80°C), Connected Field Service supports ML-based anomaly detection trained on the equipment's normal patterns. The model spots deviations a fixed threshold would miss — gradual drift, intermittent spikes, multi-variable correlations.

Preventive vs reactive. The big shift Connected Field Service enables: instead of dispatching a technician after a failure, predict failure before it happens and dispatch preventively. Customers see fewer outages; service organisations see better first-time-fix rates because the right parts arrive with the technician.

Remote-first resolution. Many "problems" are resolvable without a site visit — restart a device, adjust a setting, recalibrate. Connected Field Service automates the remote attempt first; only escalates to dispatch if remote fails. For some service organisations, remote resolution diverts 30–50% of would-be work orders, saving substantial cost.

Customer asset hierarchy. Equipment installed at customer sites is modelled as a customer asset with hierarchy: parent equipment, child sub-assemblies, components. Telemetry attaches at the appropriate level. Maintenance history accumulates per asset.

Integration with the broader stack. Connected Field Service plays with:

• Customer Service — customer-raised cases combine with IoT alerts on the same equipment.
• Sales — predictive maintenance contracts up-sell from service contracts.
• Supply Chain — spare-part demand is forecast from predicted failures.
• Customer Insights — equipment usage patterns inform marketing and product roadmap.

Implementation reality. Connected Field Service requires real IoT capability on the equipment side — sensors, connectivity, telemetry pipeline. For equipment that doesn't yet have IoT, the program needs an OT (operational technology) project alongside the IT project. The IT side is the easy part.

Licensing. Connected Field Service is sold alongside Dynamics 365 Field Service; Azure IoT costs are billed separately by Azure consumption.