Dynamics 365 Field Service is a Microsoft application that helps companies organise and manage workers who go out to customers (like repair technicians, installation engineers, or maintenance crews). Instead of juggling paper schedules, sticky notes, and panicked phone calls, Field Service turns all that chaos into a calm, automatic system that knows who should visit which customer, when, and with which tools.
Jump to a section
A simple way to picture Introduction to Dynamics 365 Field Service
Your Gran’s kitchen, Sunday lunchtime. She’s got a handwritten list of what everyone wants: Uncle Dave’s extra-crispy roasties, your sister’s well-done beef, your dad’s gluten-free gravy. She’s the only cook, the oven is small, and the table is set for 1pm sharp. If she follows the list in order, the well-done beef takes so long that the roasties go cold. Uncle Dave complains. Your sister is hungry. The meal is a disaster.
Now imagine your Gran uses a smart ordering system. She types each person’s request into a tablet. The system instantly checks what’s in the fridge, how long each dish takes, which oven shelf is free, and who can wait another ten minutes. It suggests a new order: start the beef first, then the potatoes, leave the gluten-free gravy until last. It even sends a message to your phone saying ‘Your beef will be ready in 22 minutes.’ That’s Dynamics 365 Field Service.
The field service version is exactly the same, but instead of roast potatoes, you’re managing field engineers fixing broken printers, installing broadband, or repairing air conditioners. The system holds all the ‘recipes’ — engineer skills, parts in the van, travel time, customer priority — and calculates the perfect order of jobs. No more cold roasties. No more unhappy customers. Everyone gets served hot and on time.
Let’s break down what Dynamics 365 Field Service actually does. Think of any business that sends people to your home or office to fix something. A plumber, an internet cable installer, a photocopier repair person, a solar panel technician. That kind of work is called ‘field service’ because the worker goes out ‘in the field’ — not sitting behind a desk. Before software like Field Service existed, companies managed this work using paper forms, phone calls, and whiteboards. The dispatcher (the person who assigns jobs) would call an engineer, say ‘Go to 10 Acacia Road,’ and hope the engineer had the right spare parts and knew how to get there. It was messy. Customers were left waiting for hours, not knowing when someone would arrive.
Field Service fixes this mess with three big ideas:
Work Orders: A work order is a digital file that holds everything about one job. It contains the customer’s address, what needs fixing, which parts are needed, how long the job should take, and whether the customer has a service contract. When an engineer finishes the job, they update the work order on their mobile phone — marking what they did, which parts they used, and how the customer rated the service. The work order is the single source of truth for that job.
Scheduling: This is the brain of the system. Field Service uses a feature called the ‘Schedule Board’ — a big visual calendar that shows every engineer, every job, and every customer. The system can automatically suggest the best engineer for a job based on their skills (you wouldn’t send a boiler specialist to fix a laptop), their current location, and their availability. It even checks traffic and travel time. If a customer cancels, the system can reshuffle the entire day’s schedule in seconds. This replaces the frantic phone calls of a human dispatcher.
The Mobile App: Engineers don’t sit at a desk, so Field Service gives them a mobile app on their phone or tablet. Through this app, they can see their schedule for the day, navigate to the customer using maps, view the work order details, scan barcodes on spare parts, take photos of the completed job, get the customer’s digital signature, and mark the job as done. The app also works offline, so if the engineer drives through a tunnel or a remote area with no signal, they can still see their jobs and fill in data. When they get signal back, the data syncs automatically.
Why did Microsoft build this? Because field service is huge. Millions of people drive vans to fix things every day. Before Field Service, companies used sticky notes, Excel spreadsheets, and radio calls. All of that was slow and error-prone. Field Service automates the whole flow, from the moment a customer books a repair to the moment the engineer drives away. It also connects to other Microsoft tools, like Dynamics 365 Sales (for customer accounts), Dynamics 365 Customer Service (for call centre support), and Microsoft Entra ID (for security and login controls).
For the MB-910 exam, you need to remember that Field Service is all about ‘on-the-go’ work — it’s not for people in an office. The three pillars are Work Orders, Scheduling, and the Mobile App. Understand how they fit together, and you’ll be fine.
Customer Reports a Fault
A customer calls the service desk or submits a request online. This creates a record (often a ‘Case’ in Dynamics 365 Customer Service). This step captures what is broken and who needs help.
Create a Work Order
The service desk or dispatcher converts the case into a Work Order in Field Service. The work order includes the customer’s address, the problem description, the required skills (e.g., ‘HVAC certified’), and any spare parts needed. This moves the job from ‘just a conversation’ to ‘an actionable task’.
Schedule the Work Order
The dispatcher opens the Schedule Board. They see all available engineers, their current locations, and their shift times. They drag the work order onto the best engineer’s timeline. The system checks skill matches and travel time. The work order is now part of the engineer’s day.
Engineer Receives the Job on the Mobile App
The engineer gets a push notification on their phone. They open the Field Service mobile app and see the job details: address, contact name, description of the issue, and a parts list. The app shows a navigation button to open maps. The engineer drives to the site.
Engineer Completes the Job and Updates the Work Order
At the customer’s site, the engineer does the repair. They use the app to log what parts they used, take a photo of the completed work, get the customer’s signature, and mark the work order as ‘Completed’. This triggers the system to create an invoice (if set up) and close the loop.
Review and Reporting
Back in the office, the dispatcher (or manager) reviews the day’s completed work orders on a dashboard. They can see how many jobs were done on time, average customer satisfaction, and which parts are running low. This step helps the business improve over time.
Let’s walk through a real day at a company called ‘QuickFix IT Services’. QuickFix has 15 field engineers who visit businesses to fix broken servers, replace network cables, and set up new computers. Before Field Service, the dispatcher, Raj, would start his day with a pile of paper slips — each slip was a customer request. He would call each engineer on the phone, read the address, and hope the engineer wrote it down correctly. If a job got cancelled, Raj had to start a new round of calls. Customers often called to ask ‘Where is my engineer?’ and Raj had to guess. It was chaos.
With Dynamics 365 Field Service, Raj’s morning looks completely different. He opens the Schedule Board on his computer. He sees 15 coloured bars — one for each engineer — and a list of 22 jobs that came in overnight from the customer portal. The system has already matched each job to the right engineer based on their skills: for example, server repairs go to Sarah (certified server technician), while cabling jobs go to Mike (cabling specialist). The system also checked the engineers’ calendars — Sarah is fully booked, so the system suggests moving one of her routine maintenance visits to next week.
Raj’s actual workflow looks like this:
He reviews the suggested schedule and accepts it with one click. The system automatically sends each engineer a notification on their mobile app: ‘Your first job is at 9:15 AM at 42 High Street. Estimated travel time: 12 minutes.’
Sarah, the server engineer, opens her mobile app and sees her day: she has three jobs, each with full details — the customer’s contact name, the issue description (‘Server not booting after power cut’), and a list of recommended spare parts (a new power supply unit). She taps the navigation button and Google Maps opens, guiding her to the first customer.
At the customer site, Sarah scans the barcode on the server rack using her phone camera. The app pulls up the equipment history — this server had a similar issue two years ago. She replaces the power supply, takes a photo of the new part installed, and asks the customer to sign the digital screen. She marks the work order as ‘Completed’ and the system automatically invoices the customer based on their service contract. Sarah’s next job appears in her app automatically.
Meanwhile, a customer calls the office to say their internet is down. The call centre agent — using Dynamics 365 Customer Service — creates a new work order for a ‘network fault’. The system checks which engineer is nearest and free. It sees that Mike has just finished his cable job and is only 1.5 miles away. The system offers the job to Mike’s app. He accepts it. No phone call needed.
At the end of the day, Raj reviews a dashboard that shows: 19 out of 22 jobs completed on time, average customer satisfaction score 4.7 out of 5, and a note that two jobs are still open because they needed a part that wasn’t in stock. Raj orders those parts from within the system, and those jobs are automatically rescheduled for tomorrow.
This is the reality of Field Service. It replaces chaos with order. Raj is no longer a phone operator — he’s a supervisor making smart decisions. Engineers are happier because they have clear directions and fewer surprises. Customers are happier because they get accurate time windows and know exactly when the engineer will arrive.
The MB-910 exam tests exam objective 3.1 by asking you to identify the core capabilities of Dynamics 365 Field Service. The exam doesn’t require you to remember detailed configuration steps or pricing — it just wants you to know what the product does and when you would use it. Here is exactly what they test:
Work Orders: Expect a question that describes a scenario (e.g., ‘A technician needs to see a customer’s contact info, the problem description, and the list of parts required for a repair. Which record should they use?’). The answer is always ‘Work Order’. They might try to trick you by suggesting ‘Case’ (from Customer Service) or ‘Opportunity’ (from Sales). A case is a customer problem tracked by the call centre; an opportunity is a potential sale. A work order is specifically for field service tasks. Memorise that distinction.
Scheduling and the Schedule Board: The exam loves to ask what the Schedule Board does. The correct answer is: ‘It allows dispatchers to visually assign and optimise field service jobs to engineers.’ They might present options like ‘It tracks inventory levels’ or ‘It creates invoices’. Those are wrong. The Schedule Board is exclusively for scheduling people to jobs. Also remember that Field Service can do automatic scheduling (the system suggests the best engineer) and manual scheduling (the dispatcher drags and drops jobs).
The Mobile App: Expect a question about what the mobile app allows engineers to do. Common trap: listing features that are only available on the desktop version (like creating a new customer record from scratch). The mobile app is for viewing jobs, updating status, capturing signatures, scanning barcodes, and working offline. It is NOT designed for heavy data entry or administration.
Offline Capability: This is a favourite. The exam will ask whether the Field Service mobile app works without internet. The answer is yes — it has an offline mode that caches your schedule and lets you fill in data. When you reconnect, it syncs. The exam might contrast this with other Dynamics 365 apps that require constant connectivity.
Integration with Other Products: They test that Field Service connects to Dynamics 365 Sales and Dynamics 365 Customer Service. For example, a customer calls the service desk (Customer Service), a case is created, and then that case can be escalated to a field service work order. Similarly, salespeople can create a quote for installation services, and when the deal is closed, Field Service can automatically schedule the installation crew.
Common traps to watch for:
Confusing Field Service with Customer Service. Customer Service is for call centres answering phones and emails. Field Service is for engineers driving to sites. They work together but are different products.
Thinking the Schedule Board is part of the mobile app — it’s not. The Schedule Board is a desktop tool for dispatchers. The mobile app is for field engineers.
Assuming Field Service automatically generates invoices — it can, but only if you have the right integrations set up. The exam might say ‘Field Service automatically sends invoices to customers after a work order is completed.’ That’s partially true but oversimplified. The safer answer is that it tracks what was done, and then billing is handled by Dynamics 365 Finance or via integration.
Key definitions to memorise:
Work Order: The complete digital record of a field service job.
Schedule Board: The visual tool for dispatching and rescheduling engineers.
Field Engineer (or Technician): The person who goes to the customer site.
Mobile App: The phone/tablet tool used by field engineers to do their job.
Offline Mode: The ability to use the app without internet and sync later.
Dynamics 365 Field Service is designed specifically for businesses that send workers to customer sites to perform repairs, installations, or maintenance.
The three core components are Work Orders (the digital job file), the Schedule Board (for dispatching), and the Mobile App (for field engineers).
Work orders hold all job details: customer info, problem description, required parts, and completion notes.
The Schedule Board allows dispatchers to visually assign jobs to engineers, and can auto-suggest the best match based on skills, location, and availability.
The Field Service mobile app works offline — engineers can view jobs and fill in data without an internet connection, and it syncs automatically when connected.
Field Service integrates with Dynamics 365 Sales (for turning quotes into jobs) and Dynamics 365 Customer Service (for escalating call centre issues to field visits).
Field Service is not the same as Customer Service — one manages on-site work, the other manages phone and email conversations.
The mobile app is not a full admin tool — it is designed for job execution, not for creating new customer records or running reports.
These come up on the exam all the time. Here's how to tell them apart.
Work Order
Used specifically for field service jobs requiring an on-site visit
Contains details like engineer assigned, parts used, travel time, and customer signature
Created in Dynamics 365 Field Service module
Case
Used to track any customer interaction (phone, email, chat)
Contains conversation history, priority, and product details
Created in Dynamics 365 Customer Service module
Schedule Board
Desktop tool for dispatchers and managers
Shows all engineers and all jobs on a visual timeline
Used for assigning, rescheduling, and optimising the entire team's workload
Mobile App
Mobile tool for field engineers
Shows only the logged-in engineer's assigned jobs
Used for viewing job details, navigation, capturing completion data, and working offline
Dynamics 365 Field Service
Focuses on work that happens at the customer's location
Uses work orders, schedule board, and mobile app
Engineers are mobile workers, not desk-based
Dynamics 365 Customer Service
Focuses on communication with customers via phone, email, and chat
Uses cases, knowledge articles, and omnichannel queues
Agents work at a desk in a call centre or home office
Offline Mode (Mobile App)
Allows job viewing and data entry without internet
Data is stored locally on the device and synced later
Critical for basements, tunnels, and remote areas
Online Mode (Mobile App)
Requires constant internet connection
Data is saved directly to the cloud in real time
Works when the engineer has reliable mobile data or Wi-Fi
Mistake
Field Service is only for large companies with hundreds of engineers.
Correct
Field Service scales from a single self-employed plumber to a national utility company with thousands of field staff.
Beginners think Microsoft products are only for big corporations, but Dynamics 365 is designed to be modular — you can buy just Field Service and use it with a handful of users.
Mistake
The mobile app and the desktop application are identical in features.
Correct
The desktop version has admin tools, the Schedule Board, and reporting. The mobile app is a simplified version for field workers, focused on job execution.
People assume Microsoft builds one app that works everywhere, but field service has two distinct user types — dispatchers and engineers — and their tools are purposely different.
Mistake
Field Service replaces the need for any human dispatcher.
Correct
Field Service automates scheduling suggestions but still needs a human dispatcher to approve, override, or handle exceptions like emergency callouts.
There’s a common fear that AI completely replaces jobs, but the technology augments the dispatcher rather than eliminating them. The Schedule Board still needs human judgement.
Mistake
Work orders are the same as cases in Customer Service.
Correct
A case tracks a customer service interaction (like a phone call or email). A work order is a specific type of record used only for field service jobs that require an on-site visit.
Both terms sound similar and both exist within Dynamics 365, leading beginners to treat them as interchangeable. They serve different workflows.
Mistake
Field Service only works if you have an internet connection at all times.
Correct
The mobile app has a full offline mode that stores job data locally and syncs when a connection is restored.
People assume cloud software requires constant internet, but Microsoft deliberately built offline capability because field engineers often work in basements, tunnels, or remote areas with poor signal.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
No. Dispatchers and field engineers use different parts of the system. Dispatchers use the Schedule Board on a desktop. Engineers use the mobile app. Only a system administrator needs to set up users, permissions, and integrations.
Yes — but only the mobile app. The app caches your schedule, work orders, and customer data. You can fill in details offline. When you reconnect to the internet, everything syncs automatically. The desktop Schedule Board requires an internet connection.
Customer Service is for managing phone calls, emails, and chat with customers — it’s for a call centre. Field Service is for sending engineers to a physical location. They can be linked: a Customer Service case can become a Field Service work order.
It checks several factors: the engineer’s skill certifications (e.g., ‘electrical licence’), their current location, their remaining shift hours, and the travel time to the customer. It can suggest the best match automatically, or a dispatcher can manually override it.
Yes. You can buy a license for one user. The dispatcher and the technician can even be the same person — you would use the Schedule Board to plan your own day, and the mobile app to execute jobs. Microsoft does not require a minimum number of users.
Yes, partly. You can set up an ‘Inventory’ module in Field Service to track parts in a warehouse or at a technician’s van. The system can suggest which parts to take based on the work order. However, more complex inventory management may need Dynamics 365 Supply Chain Management.
You've finished Introduction to Dynamics 365 Field Service. Continue through the MB-910 study guide to build a complete picture of the exam.
Done with this chapter?