Connected Field Service combines Dynamics 365 Field Service with Internet of Things (IoT) technology to help businesses monitor connected devices and equipment remotely. By collecting device data and identifying potential issues, organisations can move from reactive break-fix service towards preventive and predictive maintenance.
With Connected Field Service, IoT devices can send data to the cloud, where rules can identify conditions that require attention. The resulting IoT alerts can be viewed in Dynamics 365 Field Service and, where appropriate, converted into work orders that can be scheduled and assigned to technicians.
Table of Contents
- What is Connected Field Service?
- How Does Connected Field Service Work?
- Connected Field Service Architecture
- How IoT Alerts Work in Connected Field Service
- Benefits of Connected Field Service
- Connected Field Service and Predictive Maintenance
- Connected Field Service vs Reactive Field Service
- Azure IoT Hub and Dynamics 365 Field Service
- What Happened to Azure Time Series Insights?
- How to Deploy Connected Field Service with Azure IoT Hub
- Security and Permissions
- Who Can Benefit from Connected Field Service?
- How Dynamics Square UK Can Help
- Bottom line
- Frequently Asked Questions
What is Connected Field Service?
Connected Field Service is a solution that integrates IoT devices and equipment with Dynamics 365 Field Service. It enables service organisations to monitor assets remotely, detect potential faults and take action before an equipment failure causes significant disruption.
Instead of relying only on customers or technicians to identify equipment problems, connected devices can continuously provide information about equipment conditions. When the data meets a configured condition or threshold, an IoT alert can be created in Dynamics 365 Field Service.
The alert can then be reviewed by service teams and converted into a work order when field service intervention is required.
How Does Connected Field Service Work?
Connected Field Service uses a combination of IoT devices, Azure services and Dynamics 365 Field Service to move device information from connected equipment into field service processes.
The typical data flow includes:
IoT devices and sensors collect information from connected equipment.
The device data is sent to Azure IoT Hub.
Azure Stream Analytics can analyse incoming device data and identify conditions that meet configured rules.
Relevant faults or conditions can generate an IoT alert.
Azure services such as Service Bus and Logic Apps can transfer information between Azure and Dynamics 365.
The IoT alert appears in Dynamics 365 Field Service.
The service team can review the alert and convert it into a work order when required.
The work order can then be scheduled and assigned to a field technician.
This architecture allows device data to become part of the wider field service workflow rather than remaining isolated within an IoT platform.
Connected Field Service Architecture
The Connected Field Service architecture can include several Microsoft Azure and Dynamics 365 components. The exact configuration depends on the organisation's IoT environment and service requirements.
IoT Devices and Sensors
Connected equipment can contain sensors that collect information such as temperature, pressure, vibration or other operational measurements.
Azure IoT Hub
Azure IoT Hub acts as a cloud gateway for communicating with connected devices. It can receive device data and provide device management and security capabilities.
Azure Stream Analytics
Azure Stream Analytics can process device data as it enters IoT Hub and identify conditions based on configured rules and thresholds.
Service Bus
Azure Service Bus can queue information and help transfer faults between Azure services and Dynamics 365. It can also support reliable message delivery and retries.
Logic Apps
Azure Logic Apps can connect Azure services with Dynamics 365 and other applications. In a Connected Field Service architecture, Logic Apps can apply integration logic, map information and trigger actions in Dynamics 365.
Dynamics 365 Field Service
Dynamics 365 Field Service provides the service management layer where teams can manage IoT alerts, customer assets, cases, work orders, resources and technicians.
Microsoft's current Connected Field Service architecture documents IoT devices and Edge, IoT Hub, Stream Analytics, Service Bus, Logic Apps, IoT alerts and the Connected Field Service model-driven app as key components.
How IoT Alerts Work in Connected Field Service
An IoT alert represents device information that may require attention from the service team.
For example, a temperature sensor on a piece of equipment could report a temperature above an acceptable threshold. The configured IoT rules can identify the condition and create an alert in Dynamics 365 Field Service.
Service teams can then review the alert and determine whether further action is required. An IoT alert can be converted into a work order, allowing the issue to move into the standard field service scheduling and technician assignment process.
Microsoft currently documents the ability to create IoT alerts from incoming IoT messages and convert those alerts into work orders in Dynamics 365 Field Service.
Benefits of Connected Field Service
Proactive Maintenance
Connected Field Service can help service teams identify potential equipment problems before they develop into major failures. This supports a shift from reactive maintenance towards proactive and predictive service.
Reduced Equipment Downtime
Continuous monitoring can help identify abnormal equipment conditions earlier, allowing service teams to investigate and address potential problems before they result in extended downtime.
Faster Service Response
When an IoT alert is converted into a work order, service teams can use Dynamics 365 Field Service processes to schedule and assign the required technician.
Better Resource Allocation
IoT and asset information can provide additional context when service teams decide how and when to respond to an issue. This can help dispatchers consider equipment condition alongside technician skills, availability and location.
Improved Customer Experience
Remote monitoring can help service organisations identify issues earlier and respond before customers experience a major equipment failure.
Data-Driven Service Operations
IoT devices generate operational data that can be analysed to identify patterns, recurring issues and potential areas for improvement in service delivery.
Microsoft identifies predictive maintenance, improved customer experience, resource allocation, cost reduction and data-driven insights among the key benefits of Connected Field Service.
Connected Field Service and Predictive Maintenance
Predictive maintenance uses equipment condition and operational data to identify potential failures before they occur.
With Connected Field Service, IoT devices can continuously monitor equipment and send readings to the cloud. When data indicates a potential problem, an IoT alert can be generated and reviewed by the service team.
This approach can reduce dependence on fixed maintenance schedules and help organisations respond according to the actual condition of their assets.
Connected Field Service vs Reactive Field Service
| Reactive Field Service | Connected Field Service |
|---|---|
| Customer or technician identifies the issue | Connected equipment can identify abnormal conditions |
| Service request is raised after a problem occurs | IoT alerts can identify potential issues earlier |
| Maintenance is often performed after failure | Supports preventive and predictive maintenance approaches |
| Limited equipment condition data may be available | IoT data provides additional asset information |
| Technician response starts after the service issue is reported | IoT alerts can initiate a service workflow |
Azure IoT Hub and Dynamics 365 Field Service
Azure IoT Hub provides the connection between IoT-enabled equipment and the cloud-based service architecture. Dynamics 365 Field Service provides the business application where service teams manage assets, alerts, cases, work orders and technicians.
The integration allows organisations to connect equipment data with operational field service processes rather than managing IoT monitoring and service management as separate activities.
What Happened to Azure Time Series Insights?
If your existing Connected Field Service content or implementation refers to Azure Time Series Insights for the device readings chart, that information needs to be updated.
Microsoft confirms that the device readings chart in Connected Field Service is no longer available because it relied on Azure Time Series Insights, which was retired on 7 July 2024.
Therefore, references to the old Time Series Insights-based device readings experience should not be presented as a current Connected Field Service capability.
How to Deploy Connected Field Service with Azure IoT Hub
The deployment process depends on the organisation's Azure and Dynamics 365 environment. Microsoft's current setup guidance includes the following major steps:
Deploy Connected Field Service and the required Azure resources.
Create an IoT provider instance.
Set up the IoT endpoint.
Authorise the required Azure application connection.
Configure device rules.
Start the required Azure Stream Analytics jobs.
Dynamics 365 Field Service must be installed, and the required security roles and Azure resources need to be configured before completing the Connected Field Service setup.
Security and Permissions
Connected Field Service requires appropriate security roles because different users manage different parts of the IoT and field service process.
For example, an IoT Administrator can register IoT devices, connect IoT data with Field Service and manage business processes based on IoT alerts.
Organisations should review their Dynamics 365 Field Service security roles and apply permissions according to the responsibilities of administrators, dispatchers, technicians and other users.
Microsoft's current Field Service documentation continues to provide dedicated security roles for Connected Field Service and IoT administration.
Who Can Benefit from Connected Field Service?
Connected Field Service can be useful for organisations that manage equipment or assets that can be monitored through IoT devices.
Common use cases include:
Manufacturing equipment monitoring
HVAC and building equipment
Industrial machinery
Connected appliances
Energy and utilities equipment
Medical and specialist equipment
Vehicles and connected assets
The suitability of Connected Field Service depends on the availability of useful sensor data, the service model, asset requirements and the organisation's existing technology architecture.
How Dynamics Square UK Can Help
Implementing Connected Field Service involves more than connecting an IoT device to Dynamics 365. The solution may require Azure configuration, IoT data processing, security roles, alert rules, integration workflows and Dynamics 365 Field Service configuration.
Dynamics Square UK can help businesses plan and implement Dynamics 365 Field Service solutions, including IoT integration, asset management, work order processes and service operations.
Our consultants can also help review your existing Field Service and Azure environment and identify the appropriate approach for connecting equipment data with service processes.
Contact Dynamics Square UK to discuss your Connected Field Service and Dynamics 365 requirements.
Bottom line
Connected Field Service brings IoT data and Dynamics 365 Field Service together to help organisations monitor equipment, identify potential issues and take action through established service processes.
By connecting IoT devices with Azure and Dynamics 365 Field Service, organisations can move beyond a purely reactive break-fix approach and support preventive and predictive maintenance strategies.
With the current Connected Field Service architecture, IoT alerts can be reviewed in Dynamics 365 and converted into work orders when service intervention is required. This creates a direct connection between equipment condition and field service operations.
Dynamics Square UK can help you assess, implement and optimise Dynamics 365 Field Service and Connected Field Service according to your business and technical requirements.
Contact our Dynamics 365 consultants to discuss your Field Service and IoT requirements.
Frequently Asked Questions
Connected Field Service integrates IoT technology with Dynamics 365 Field Service to monitor connected devices and equipment, identify potential issues and support proactive or predictive maintenance.
IoT devices send equipment data to Azure services such as IoT Hub. Rules can identify conditions that require attention, generate IoT alerts in Dynamics 365 Field Service and, where appropriate, convert those alerts into work orders.
Azure IoT Hub provides communication between connected devices and the cloud. It receives device data and supports device management and security within the Connected Field Service architecture.
Yes. An IoT alert can be converted into a work order in Dynamics 365 Field Service. The work order can then be scheduled and assigned to a field technician.
Connected Field Service can support proactive maintenance, earlier issue detection, improved service response, better resource allocation, reduced downtime and data-driven service operations.
.png&w=3840&q=75&dpl=dpl_5qzySE1sFePcB71x9JXqJrPChMNo)