Microsoft retired Exam MB-240, Dynamics 365 Field Service Functional Consultant, on June 30, 2026, along with the related certification route. This article retains its original MB-240 title and permalink as a historical record of the capabilities the exam assessed; it is not an active booking or passing guide. Dynamics 365 Field Service remains an active business application, and the work of scheduling technicians, managing customer assets, tracking parts and documenting service visits remains relevant even though the assessment is no longer offered.
The best way to understand the former MB-240 scope is to follow a service request from first contact through dispatch, on-site work and a verified outcome. Imagine a company maintaining refrigeration equipment at retail stores. A customer reports that a unit is failing, and the organization must select a qualified technician, reserve a replacement part, arrange an appropriate time window, record the inspection and establish whether the asset is safe to return to service. This workflow exposes the operational decisions behind Field Service configuration more clearly than an old exam-day question list.
Microsoft’s archived MB-240 guide covered application configuration, work orders and customer assets, scheduling and dispatch, the Field Service mobile app, inventory and purchasing, and Power Platform integration. Those topics are historically accurate for the retired certification, but their old weights and scheduling instructions should not be used to prepare for an imaginary active MB-240 exam. Readers seeking a current Microsoft credential should review the live certification catalog and the requirements of the specific business application role they intend to demonstrate.
Work orders describe the service obligation
A work order is a record of what needs to be done, where, why and under which service conditions. It can be created from a direct request, a customer service case, a maintenance agreement or another approved process. Its status needs to mean something operational: created, scheduled, in progress, completed or closed should match the real service team’s behavior. An automatically advanced status is not proof that equipment was repaired or that a customer accepted the result.
For the refrigeration case, document the asset, reported symptom, service location, contact details, requested outcome, priority and any required safety precautions. Choose an appropriate incident type and include the expected tasks and products if those are part of the organization’s configuration. The team may also need entitlement or warranty information, but it should not invent coverage when it is missing. An accurate work order allows dispatchers and technicians to understand the job without exposing unnecessary customer information.
Field Service configurations can have different requirements for a service account depending on the work order type and the environment’s supported capabilities. Some account-centered processes use the service account to supply address, billing and territory defaults; other permitted work order types can provide context through other fields. A consultant should verify the selected type’s actual rules rather than assume every work order universally requires the same customer account field. Test both an account-based job and any permitted alternative using synthetic records.
The related historical Field Service functional-consultant credential reflected implementation responsibilities around these service records. Its retirement does not make the work order lifecycle obsolete. The professional skill is to match the application to a legitimate service process, validate permissions and document exceptions, whether or not that skill is currently assessed by an exam.
Scheduling is a constrained matching problem
Dispatch is not simply dragging a work order into an empty calendar slot. A successful assignment may depend on technician skills, required certifications or safety training, territory, location, working hours, equipment, travel time and parts availability. A worker who appears free may still be unsuitable for the job. The scheduling process needs to make constraints visible so the dispatcher can choose a workable appointment rather than an attractive but impossible calendar arrangement.
Create a test resource with refrigeration skills and another with only general maintenance experience. Add an urgent work order requiring the specialist and observe which assignments are permitted or suggested under the configured rules. Then make the specialist unavailable and record the dispatcher’s choices: change the time window, escalate, arrange another qualified worker or notify the customer. An organization should define who can make those decisions and what message must be sent when the original appointment cannot be kept.
The schedule board, scheduling assistant and optional optimization features can support resource planning, but they do not guarantee every proposed route is physically or commercially workable. A technician may need secure site access, specialist equipment or a customer escort that is not fully represented in the optimization inputs. A reliable operational plan includes those dependencies and provides a method for manual exception handling and recorded approval.
Customer assets and service history connect visits over time
A customer asset record gives field work a durable context. The same refrigeration unit may have an installation record, warranty status, service history, replaced components and recurring failure patterns. The accuracy of identifiers matters: when two similar units exist at one store, a technician must record work against the correct asset rather than a generic location. A history assigned to the wrong unit can affect future maintenance decisions and conceal a repeated safety issue.
In the test scenario, create an asset with a synthetic serial number and associate two prior maintenance visits. The new work order should reference the same equipment and reveal the relevant service context. After repair, confirm the asset’s history records the observed failure, performed tasks and parts consumed without duplicating earlier activity. A work order can close successfully while an asset record remains stale; that mismatch is precisely what an acceptance test should detect.
Agreements can create recurring inspections or preventive-maintenance work. A recurrence rule should reflect the contract’s timing and the operational reason for the visit, not simply generate a large number of appointments. If an asset is out of service, the next preventive visit may need a different procedure. Test the agreement’s scheduling behavior, billing expectations and responsibility for canceled or rescheduled visits before using it in production.
Parts and inventory require proof of consumption
Field technicians depend on stock that may be held at a warehouse, a service vehicle or another permitted location. Reserving a part for a work order is different from confirming that it has been picked up, installed or returned. An inventory process should preserve that distinction so the organization can reconcile physical quantities with what the service history claims was used. If the technician discovers that the selected part is incompatible, a replacement or return needs an authorized record rather than an untracked adjustment.
For the refrigeration visit, reserve a replacement controller and record its expected inventory source. Simulate the technician using one item, returning a defective component and not using the second part initially requested. Reconcile those movements against the work order products and the stock records. A correct parts workflow should explain why an item became unavailable to other jobs and when unused stock returned to saleable or serviceable status.
Purchasing may be required when no suitable part exists. The dispatcher needs to know the promised supplier date and whether that date permits a customer appointment. An automatically generated purchase request is not proof that a vendor has accepted the order. Communicate the uncertainty and record a follow-up service plan. A service business that books a repair while its critical replacement item is on backorder will create avoidable missed appointments unless that dependency is handled.
The technician mobile experience must work under field conditions
The Dynamics 365 Field Service mobile app allows frontline workers to review bookings, inspect work orders and update status or service information while on the move. The environment’s access configuration and offline profile determine what information is available and what can be synchronized later. A consultant should never infer that every field remains immediately synchronized when a technician is offline. Connectivity, permissions and app configuration affect what the worker can see or change.
An authorized lab can simulate a technician arriving at a customer site, reviewing instructions and recording findings. Where the configured experience permits offline work, disconnect a test device and observe which details remain available, what edits can be staged, and how the application behaves on reconnection. Use synthetic customer data and avoid photographing real private premises. Verify that completion notes, photos or parts updates reach the intended records after synchronization instead of assuming that a local “saved” message establishes successful server acceptance.
Mobile errors have operational consequences. If a technician cannot see the booking, the issue may involve resource assignment, access role, app selection, synchronization or record status. A support handoff should describe the device, app version, affected booking and observed behavior without copying customer secrets. A useful workflow offers a safe escalation or follow-up work order when the original job cannot be completed in one visit.
Accessibility and safety remain important. Field workers may use the application with gloves, poor connectivity or tight appointment windows. Forms and task checklists should support accurate recording rather than encourage hurried guesses. If a required hazard check has not been completed, the system should not silently present the job as safe or finished simply because all ordinary fields have values. Product configuration must reflect organizational policy and the real hazards of the service work.
Use automation and connected services within approved boundaries
Field Service can connect with Power Platform and other Dynamics 365 applications. A customer-service case may result in a work order; a completed visit may trigger a notification or reporting process. These integrations require clear ownership of data and event meaning. An automation that creates a duplicate work order every time a case is edited can multiply costs and confusion. Test idempotency, failure handling and the workflow for correcting an erroneous event before allowing the process to run broadly.
Microsoft Copilot features can assist with summarizing work-order context where supported and authorized, but a generated summary is not an independent verification of what happened. Service managers should be able to identify which records informed a summary, whether sensitive information was handled appropriately, and how a worker can correct an inaccurate description. Field-service accountability remains with the organization and its personnel even when an assistant proposes language or a next step.
Adjacent customer-service processes may involve case intake, service-level commitments and communications before a technician is dispatched. The field visit and customer-service case have different operational purposes, so their statuses and ownership should be mapped deliberately. A case closed by a customer-service agent does not automatically prove that an asset was repaired; the linked service record and acceptance criteria should support that conclusion.
Assess current Field Service skills with end-to-end tests
For a complete practice project, define one refrigeration failure and follow it through request, work-order creation, qualification-based scheduling, parts reservation, technician mobile action, customer-asset history and closing review. Use a permitted sandbox. Record the expected state for every step, then introduce an exception: the technician is unavailable, the part is missing, the visit is interrupted or the synchronization fails. Each case should demonstrate who decides the next action and what evidence proves that the service process remains consistent.
Do not treat a successful booking as the end of the exercise. Confirm that the work was performed by an appropriate resource, that installed parts are accounted for, that the mobile record synchronized as expected, and that the receiving customer or service supervisor can see an accurate outcome. If an exception remains, keep it open with an owner and a next step. A technically complete field-service implementation is one that supports real operational decisions without losing traceability or authorization.
MB-240 is retired and cannot be used as an active 2026 exam-preparation target. Anyone seeking a current credential should consult Microsoft’s live certification catalog rather than assume a direct exam successor exists. The durable value of this historical guide is the workflow reasoning behind Dynamics 365 Field Service: creating valid work orders, matching resources, managing assets and parts, capturing field evidence and closing the service obligation accurately.