Exam objective 3.3 focuses on how mobile technology and the Internet of Things (IoT) let field technicians fix problems before they break the customer's equipment. This matters because passing MB-910 means understanding how Dynamics 365 Field Service moves beyond 'wait for a customer to call and complain' to a world where machines phone home with their own symptoms.
Jump to a section
A simple way to picture Mobile App, IoT, and Connected Field Service
A hospital's fleet of ambulances is a perfect analogy for Connected Field Service. Each ambulance is a field technician's van, equipped with tools and a paramedic (the technician). Dispatchers at the hospital manage the fleet.
Instead of waiting for a 911 call, imagine every ambulance has a 'heart monitor' for every hospital bed in the city — an Internet of Things (IoT) sensor on a patient. That sensor constantly beams the patient's heart rate, blood pressure, and oxygen levels to the ambulance's dashboard. The dashboard runs a mobile app that shows the patient a dispatcher oversees in real time. When the sensor detects a dangerous irregular heartbeat, the system doesn't just sound an alarm in the hospital; it automatically creates a 'service case' in the ambulance's navigation app, identifies the nearest ambulance with the right defibrillator and paramedic speciality, and dispatches them proactively. The paramedic arrives before the patient even feels the chest pain. The ambulance is no longer reactionary — it's predictive. The mobile app on the paramedic's tablet shows the patient's full history, vital signs, and the exact protocol to follow, all synced live. This maps precisely to how IoT sensors on factory equipment, the cloud, and the Field Service mobile app work together in Dynamics 365 to prevent breakdowns before they cost a factory a day of production.
Let's build this from the ground up. Imagine a vending machine company that sells fizzy drinks. Historically, the vending machine sits there until a customer puts money in and gets nothing — then they call customer support. The company sends a technician the next day, only to discover a simple loose wire that stopped the machine for hours. That's reactive service: fixing things after they break. It loses money in lost sales and angers customers.
Dynamics 365 Field Service, combined with IoT and a mobile app, flips this to proactive service. Here is how it works, one layer at a time.
First, the 'Internet of Things' (IoT) refers to everyday physical objects — like vending machines, wind turbines, or MRI scanners — that have a small computer chip and a sensor inside. That sensor measures something: temperature, vibration, power usage, door status. The chip has a cellular or Wi-Fi connection that sends that measurement — called a 'telemetry signal' — to the cloud (Microsoft Azure, in this case). The vending machine's sensor might report: 'Motor RPM dropping, 20% below normal operating range.'
Second, Azure IoT Hub is the dedicated mailbox that receives millions of these telemetry signals simultaneously from thousands of machines. It doesn't just dump them in a pile; it routes each signal to the right service. If the motor RPM is slightly low, it might just log a note. If it's critically low (the motor is about to seize), the IoT Hub triggers a rule: 'Create a Field Service case for machine ID VM-5432 with priority 'Critical'.
Third, this triggers Connected Field Service, a module within Dynamics 365 that connects IoT signals directly to service processes. The moment that critical signal arrives, Dynamics 365 automatically:
Creates a work order (a digital job ticket) with the exact machine ID, error code, and location.
Checks the technician schedule for the nearest available technician with the right skills (maybe only 'Senior Vending Technician' can fix motors).
Books the technician's time slot.
Generates a list of required spare parts based on the error code and reserves them from the warehouse.
Fourth, the Field Service Mobile App is the tool the technician uses. When the technician gets the assignment on their phone or tablet, the app shows:
A map with the street address and route.
The customer's name, contract history, and which parts they already paid for.
The exact error code from the IoT sensor and a step-by-step repair checklist.
The option to scan the machine's barcode with the phone camera to confirm they are at the right place.
A button to capture the customer's electronic signature when the job is done.
The ability to log time and mileage automatically.
Fifth, everything syncs automatically. The moment the technician closes the work order in the app, the inventory system deducts the spare parts, the invoice is generated in the finance system (Dynamics 365 Finance), and the customer receives an automatic text message: 'Your machine is fixed. Technician John left at 2:45 PM.'
Before this system existed, companies used paper forms, phone calls, and fax machines. A technician might drive two hours only to realise they needed a part that was back at the warehouse. Schedules were kept on whiteboards. Customer complaints were handled one crisis at a time. This system replaces all that with a single, real-time flow from machine to technician to billing.
Key terms defined:
IoT (Internet of Things): physical devices with sensors and internet connectivity sending data to the cloud.
Telemetry: raw data from sensors (e.g., 'temperature: 85 degrees').
Cloud: a giant network of remote servers (Microsoft's data centres) that store and process data.
Work order: a digital instruction to a field technician describing what to fix, where, and when.
Connected Field Service: the specific Dynamics 365 feature that turns IoT telemetry into service tasks automatically.
Mobile App: the Field Service app installed on a smartphone or tablet that the technician uses on the job.
1. Device Sends Telemetry
An IoT sensor on equipment (e.g., a wind turbine gearbox) measures temperature every 5 minutes and sends a data packet (telemetry) to the cloud via a cellular chip. This is an automatic, continuous process — no human touches the sensor.
2. Azure IoT Hub Receives Signal
The telemetry arrives at Azure IoT Hub, a Microsoft service that can handle millions of signals per second. The hub checks the device ID (e.g., 'Turbine_12') and forwards the data to the right destination — here, Dynamics 365 Field Service.
3. Connected Field Service Evaluates Rules
Inside Dynamics 365, a rule fires: 'If gearbox oil temperature > 85 degrees, create a work order.' The system automatically creates the work order with asset details, estimated duration, and required skill level.
4. System Books the Best Technician
The scheduling engine in Field Service checks which technicians are available, closest, and have the right certification. It assigns the job to that technician and sends a push notification to their mobile app.
5. Technician Accepts and Prepares Offline
The technician opens the Field Service Mobile App, sees the job details, and taps 'Accept'. The app downloads the full work order, parts list, maps, and customer history to the device for offline access.
6. On-Site Execution and Completion
The technician scans the asset barcode at the site, follows the repair instructions, snaps a photo of the fix, collects a digital signature, and marks the work order as 'Complete'. All this happens even if the device is offline.
7. Automatic Sync and Back-End Updates
When the technician's device reconnects to the internet, the mobile app syncs changes. The work order status updates to 'Completed', inventory parts are deducted, a billing invoice is generated, and the customer receives a satisfaction survey.
Meet Maria, a field service technician for 'AeroWind', a company that maintains large wind turbines in Scotland. AeroWind has 200 turbines, each with over 50 IoT sensors measuring blade pitch, gearbox oil temperature, vibration in the main bearing, and wind speed.
Here is what Maria's day looks like with Connected Field Service.
At 6:00 AM, Maria wakes up and checks her company-issued phone. The Field Service Mobile App already shows her first job. The system didn't wait for a turbine to break. At 3:17 AM, an IoT sensor on Turbine 12 detected that the gearbox oil temperature was 8 degrees above normal threshold. The Azure IoT Hub flagged this as 'high prediction of imminent gearbox failure within 48 hours if not serviced.' The Connected Field Service engine automatically created a 'Preventive Maintenance Work Order' with priority 'High'.
The app shows Maria:
Customer: GreenGrid Energy.
Turbine ID: T-12, located at coordinates (lat/long with a satellite photo).
Issue: Gearbox oil temperature high. Likely cause according to the AI model: blocked oil filter.
Required part: Oil filter Kit part number 882-AC, already reserved at the depot 20 miles away.
Estimated repair time: 2.5 hours.
Procedure: a step-by-step guide with torque settings for bolts.
Maria taps 'Accept'. The app automatically logs her acceptance time, navigates to the 20-mile depot to pick up the part, then to the turbine. At the turbine, she scans the barcode on the turbine tower with her phone camera. The app verifies she is at the correct asset and completes a mandatory safety checklist (hard hat, harness, weather check). She fixes the blocked oil filter — it took an hour, not the predicted 2.5. She taps 'Complete', takes a photo of the new filter installed, captures the site manager's signature on the screen, and adds a note: 'Found small twig debris in filter — cleaned cooling intake too.'
The app syncs. The work order closes. The inventory system deducts 'Oil Filter Kit 882-AC' from stock. The spare parts inventory automatically triggers a reorder since stock dropped below the minimum level. The finance system creates a 'no charge' invoice because this is under warranty. The customer receives a satisfaction survey via text message.
Meanwhile, back at AeroWind's office, the service manager opens the Dynamics 365 dashboard. She sees a map of all 200 turbines. Green ones are healthy. Yellow ones have low-priority notes. One turbine is red — Turbine 12 — and it just turned green after Maria's fix. She can see that Maria completed the job 30 minutes faster than the average technician for that task.
The IT professional (or Dynamics 365 administrator) who set this up had to:
Configure the Azure IoT Hub to receive telemetry from the specific brand of turbine sensors (often using JSON data format).
Define rules in Connected Field Service: e.g., 'If gearbox oil temperature > 85 degrees for more than 10 minutes, create a work order with severity 2.'
Map the IoT signal fields to Dynamics 365 fields (e.g., 'SensorDeviceID' maps to 'Asset Number').
Set up the mobile app configuration so Maria sees only the fields relevant to a wind turbine technician.
Test the end-to-end flow: sensor -> IoT Hub -> work order creation -> mobile app notification -> parts reservation.
This is not science fiction. It is a standard configuration available in Dynamics 365 today.
The MB-910 exam tests topic 3.3 with a specific pattern. You will see roughly 3-5 questions about mobile capabilities and Connected Field Service. The exam loves testing your ability to distinguish between 'reactive' and 'proactive' service, and which system does what.
What the exam explicitly tests:
The definition of IoT and Connected Field Service and how they relate. A typical question: 'Which Dynamics 365 capability uses IoT signals to automatically schedule a service visit before equipment fails?' Answer: Connected Field Service.
The purpose of the Field Service Mobile App. A typical question: 'What tool does a field technician use to view their scheduled jobs, capture signatures, and log time?' Answer: The Field Service Mobile App.
The difference between a work order and an incident type. A work order is the overarching job. Incident types are pre-defined sets of tasks, parts, and skills for common problems (e.g., 'Oil filter replacement incident type' includes filter part number, labor time estimate, and safety check). The exam loves asking which is which.
What the technician can do in the mobile app without internet connection. The app has offline capabilities: it can cache work orders, parts catalogs, and maps so the technician can still use it underground or in a remote Scottish valley. When the device reconnects, it syncs automatically. The exam will ask: 'If a technician is in a basement with no signal, can they still check their next job?' Yes, if the work order was downloaded before going offline.
The role of Azure IoT Hub. The exam may not ask deeply technical questions, but you must know it is the 'gateway' that collects data from IoT devices and sends it to Dynamics 365. A trap: they might say 'Which Microsoft product collects IoT data?' Answer: Azure IoT Hub, not Dynamics 365 itself.
The difference between predictive maintenance (what IoT enables) and preventive maintenance (scheduled by calendar). Predictive maintenance uses real-time sensor data to predict failure. Preventive maintenance happens every 6 months regardless of sensor data. The exam will give a scenario and ask: 'Is this predictive or preventive?'
Common traps to recognise:
Trap 1: 'The mobile app replaces the need for a back-end system.' Wrong. The mobile app relies on Dynamics 365 backend; it is a front-end tool.
Trap 2: 'IoT requires a technician to manually read the sensor.' Wrong. IoT sensors transmit without human intervention.
Trap 3: 'Connected Field Service is only for large enterprises.' Wrong. It scales to small operations too.
Trap 4: 'The mobile app only works online.' Wrong. It has offline mode.
Key definitions to memorise:
IoT: devices with sensors sending data over the internet.
Connected Field Service: the Dynamics 365 module that reacts to IoT data to create service actions.
Field Service Mobile App: the technician's on-site tool.
Predictive maintenance: fixing something before it breaks based on data.
Connected Field Service automatically creates a work order when an IoT sensor detects a problem, so no human has to call it in.
The Field Service Mobile App works offline — the technician can view, edit, and complete work orders without an internet connection.
Azure IoT Hub is the gateway that collects telemetry from sensors and routes it to Dynamics 365 for processing.
Predictive maintenance uses real-time sensor data to predict failure before it happens, while preventive maintenance runs on a fixed calendar schedule.
The technician uses the mobile app to scan barcodes, capture signatures, log time, and take photos — all synced automatically with the back-end.
A work order is the overall job; incident types are pre-defined templates for common repair tasks that include parts and steps.
IoT sensors measure things like temperature, vibration, and power usage, and send that data to the cloud without anyone pressing a button.
When a work order is completed in the app, inventory is automatically updated and billing is triggered.
These come up on the exam all the time. Here's how to tell them apart.
Connected Field Service
Back-end module in Dynamics 365 that processes IoT data and creates work orders.
Runs on cloud servers and is managed by IT administrators.
Does not have a user interface for field technicians.
Including scheduling logic, inventory integration, and billing rules
Field Service Mobile App
Front-end application installed on the technician's smartphone or tablet.
Runs on the technician's device and works offline.
Used by field technicians to view, accept, and complete jobs.
Including barcode scanning, signature capture, and navigation
Predictive Maintenance
Triggered by real-time sensor data indicating an imminent failure.
Uses IoT telemetry to predict when a machine will break.
No fixed schedule; maintenance happens only when data suggests it is needed.
Including checking gearbox temperature trending upward
Preventive Maintenance
Scheduled on a calendar basis (e.g., every 90 days or 1000 operating hours).
Does not rely on sensor data; uses elapsed time or usage counters.
Has a fixed recurring schedule regardless of actual machine condition.
Including changing oil every 6 months regardless of oil quality
Work Order
The overall job record that includes dates, location, customer details, and status.
Can contain multiple incident types (e.g., replace filter AND check oil).
Is what the technician sees in the mobile app as a single job.
Including: Work Order #12345 for Turbine 12 at GreenGrid Energy
Incident Type
A re-usable template for a specific repair task (e.g., 'Oil Filter Replacement').
Includes predefined tasks, required parts, estimated labor time, and skill level.
Cannot exist on its own; it must be part of a work order.
Including: Incident Type 'Oil Filter Replacement' with part #882-AC and 1.5 hours labour
Azure IoT Hub
Microsoft's cloud service for receiving telemetry from IoT devices.
Handles device authentication, message routing, and scaling to millions of devices.
Is not aware of business processes like invoicing or technician scheduling.
Including: receiving temperature readings from 50,000 turbines
Dynamics 365 Field Service
Microsoft's business application for managing service operations.
Handles work orders, scheduling, inventory, and billing.
Does not directly collect sensor data but receives processed signals from IoT Hub.
Including: creating a work order for a turbine with high temperature
Mistake
IoT means all devices are connected to the same network as my home Wi-Fi.
Correct
IoT devices usually connect to the internet via cellular networks (like a 4G chip), or low-power networks (LoRaWAN), not necessarily local Wi-Fi.
People assume 'internet' means Wi-Fi, but industrial IoT devices are often in remote locations and use cellular networks.
Mistake
If the Field Service Mobile App shows a job offline, the technician cannot complete it.
Correct
The app can cache the work order and let the technician complete it offline. The app syncs when connectivity returns.
Many assume 'cloud app' means always-online, but Dynamics built the app specifically for areas with patchy reception.
Mistake
Connected Field Service and the Field Service Mobile App are the same thing.
Correct
Connected Field Service is the back-end module that processes IoT data and triggers workflows. The Mobile App is the front-end tool the technician uses.
The names are similar ('Field Service' appears in both) and it is easy to conflate back-end logic with front-end interface.
Mistake
The technician must manually update inventory after using a part.
Correct
When the technician completes a work order in the mobile app and selects a part used, the inventory system deducts it automatically.
People assume manual data entry is required because that is how older paper-based systems worked.
Mistake
IoT sensors can only send data, not receive commands.
Correct
Many IoT sensors can receive commands from the cloud, e.g., to reboot a machine or adjust a valve.
The word 'sensor' implies passive measurement, but many modern IoT devices are 'actuators' that can act on commands.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
No. You need Dynamics 365 Field Service licenses. The IoT sensors and Azure IoT Hub are additional services, but your technicians only need a smartphone or tablet with the Field Service Mobile App installed.
Yes, partially. The app can cache work orders and parts data while the technician has Wi-Fi, then work entirely offline in the field. The sync will happen the next time the device connects to any network.
No. Azure IoT Hub is a separate Azure service. Dynamics 365 Connected Field Service integrates with it, but you pay for them separately.
No, the Field Service Mobile App runs on a standard smartphone (iPhone or Android) or tablet. A laptop is not required for field work.
Not by default, but you can configure it. Dynamics 365 can send automated SMS or email notifications to the customer when a technician is on the way, but the system does not make a phone call unless you connect it to a telephony service.
Yes, as long as the equipment can send telemetry data in a standard format (like JSON or MQTT) over the internet. The Azure IoT Hub can ingest data from any manufacturer.
You've finished Mobile App, IoT, and Connected Field Service. Continue through the MB-910 study guide to build a complete picture of the exam.
Done with this chapter?