MB-240
Microsoft Dynamics 365 Field Service Functional Consultant
Microsoft Dynamics 365 Field Service Functional Consultant Exam Guide
Exam MB-240 validated whether a Dynamics 365 Field Service functional consultant could translate service requirements into configured applications, work orders, schedules, mobile processes, inventory operations, and Power Platform improvements. Microsoft now identifies the exam, certification, and renewal assessment as retired, so the first decision is not how to book MB-240 but whether your goal is historical preparation, role capability, or a current replacement credential. This guide helps you choose that path, prioritize the former exam objectives, and build practical Field Service knowledge without relying on obsolete exam assumptions.
Is MB-240 still available?
Microsoft states that Exam MB-240 and its related certification and renewal assessment were retired on June 30, 2026. That status changes the sensible preparation decision: do not treat older booking instructions or legacy exam pages as evidence that a new appointment can be scheduled. Use the current Microsoft Credentials pages to identify the related certification requirements instead.
The exam page describes MB-240 as retired, while the legacy certification page says that the earlier version of the Microsoft Certified: Dynamics 365 Field Service Functional Consultant Associate credential is no longer available. These notices should take precedence over older articles, course listings, search results, or third-party question banks.
For a candidate studying Field Service for work, the retired blueprint remains useful as a skills checklist. For a candidate seeking a current Microsoft credential, begin at Microsoft’s Dynamics 365 credentials catalogue and inspect the current Field Service or related functional-consultant options before paying for training or planning an exam.
What should a candidate do first?
Confirm the target outcome. If you need to perform Field Service implementation work, use the MB-240 objectives as a structured learning plan and validate the current product documentation as you study. If you need a transcript credential, stop and verify the active certification path instead of assuming that MB-240 can still be taken.
What did the certification validate?
The credential was aimed at functional consultants who implement solutions for the field-service lifecycle. The role included scheduling resources against customer requirements, matching skills, locations, and availability, equipping frontline workers with useful information and tools, and building service histories for customer assets.
This is broader than learning isolated menu paths. A consultant had to connect business requirements with configuration choices, operational processes, user roles, mobile work, inventory, and related Dynamics 365 and Power Platform capabilities. The practical test of readiness is whether you can explain how a service request becomes completed work and recorded asset history.
Microsoft’s role guidance also describes collaboration with project managers, developers, and solution architects. That makes solution boundaries part of the preparation problem: know which requirement belongs in standard configuration, which needs a broader platform decision, and which should be clarified with the implementation team.
Who was the intended audience?
The intended candidate was a Dynamics 365 Field Service functional consultant. Microsoft’s legacy guidance recommended one to three years of experience as a functional consultant implementing Dynamics 365, but that guidance belongs to the legacy certification context rather than a current admission rule for a replacement credential.
The role is a strong fit for people gathering requirements, configuring Field Service, mapping service processes, supporting dispatchers and technicians, and coordinating changes across a Dynamics 365 implementation. A beginner can still use the objectives, but should expect to learn the operational concepts before attempting advanced configuration exercises.
What skills did MB-240 measure?
The published MB-240 blueprint grouped the work into six technical domains: configuring Field Service applications; managing work orders and customer assets; scheduling and dispatching work orders; managing the Field Service mobile app; managing inventory and purchasing with the built-in inventory system; and implementing Microsoft Power Platform.
The percentages below are the official domain labels and should be read as study-priority signals, not as a promise about a future exam. Because MB-240 is retired, use them to organize historical knowledge or job preparation rather than to predict a current assessment.
Configure field service applications (20–25%) covered administration, resources and scheduling, service agreements, booking setups, and related Field Service settings. Manage work orders and customer assets (25–30%) covered the central service records, incident types, bookings, and asset history. Schedule and dispatch work orders (15–20%) focused on matching work to suitable resources and managing dispatch decisions.
Manage the Field Service mobile app (5–10%) addressed installing, configuring, and adapting the mobile experience. Manage inventory and purchasing by using the built-in inventory management system (5–10%) covered inventory operations and purchasing. Implement Microsoft Power Platform (5–10%) connected Field Service implementation work with platform capabilities and integrations.
Which domain deserves the most attention?
Start with Manage work orders and customer assets (25–30%), then move to Configure field service applications (20–25%). Together, those domains establish the records, settings, and lifecycle decisions that the other areas depend on. Do not study the percentages as bare rankings; the domain labels describe the actual work you must understand.
Next, study Schedule and dispatch work orders (15–20%) as an operational application of your configuration knowledge. Finish the first pass with the mobile, inventory and purchasing, and Power Platform domains, each of which carries a smaller published range but can expose gaps in an otherwise strong implementation model.
How should you study the Field Service process?
Study the lifecycle before memorizing configuration names. A useful sequence is requirement discovery, work-order creation, incident and task definition, resource matching, booking and dispatch, technician execution in the mobile app, inventory or purchasing action, completion, and customer-asset history. At every stage, ask which record changes and which user needs the information.
Microsoft describes work orders as central to Field Service operations. Its official learning path also covers configuration, work-order management, agreements, and mobile customization. Treat that sequence as a working model: configure the foundation, follow a work order through delivery, automate recurring service through agreements, and then adapt the mobile experience.
This approach prevents a common error: learning a feature without understanding why it exists. For example, a booking is not simply a calendar entry; it represents the assignment of a resource to service work. An agreement is not merely a recurring record; it supports scheduled generation of work orders, bookings, and invoices according to customer expectations.
What should you document while studying?
Create a process table with five columns: business requirement, Field Service record or setting, user responsible, expected outcome, and unresolved design question. Populate it with scenarios such as scheduled maintenance, emergency repair, technician skill matching, unavailable inventory, and a customer asset requiring repeat service.
Then draw the relationships between work orders, incident types, bookings, resources, products, locations, agreements, and customer assets. The purpose is not to reproduce a user interface. It is to make dependencies visible so that a configuration choice can be tested against the complete service process.
How can you prepare the configuration domain?
For Configure field service applications (20–25%), practice explaining how administrative settings, resources, scheduling, service agreements, and booking setups support a customer’s operating model. Begin with the desired service process, then identify the minimum configuration needed to make that process reliable and understandable to dispatchers and technicians.
Separate global or administrative decisions from process-specific records. Ask what controls the organization’s service behavior, what defines a resource, what determines how a booking is created, and what an agreement should generate. This prevents configuration by trial and error and gives you a defensible reason for each choice.
Use a scenario such as a maintenance provider serving several locations. Define the service territory, resource capabilities, working arrangements, booking expectations, and recurring agreement terms before opening the application. Then test whether a generated work order contains enough information for dispatch and execution.
Do not treat AI-enabled experiences or Copilot references as a substitute for core configuration knowledge. Microsoft says candidates should understand uses for Microsoft 365 Copilot in Field Service, but the underlying records, lifecycle, and business rules still determine whether an AI-assisted experience is useful.
Configuration mistakes to avoid
A frequent mistake is starting with the schedule board before defining the resource model. Another is creating recurring work manually when an agreement is intended to generate work orders, bookings, and invoices on an expected schedule. A third is accepting default settings without checking how they affect work-order creation, booking, technician instructions, or customer-asset history.
For each practice scenario, record the requirement that the setting satisfies and one side effect that must be tested. If you cannot state both, your understanding is probably still feature-based rather than implementation-based.
How should you master work orders and customer assets?
Manage work orders and customer assets (25–30%) was the largest published MB-240 domain. Prepare by following a work order from creation through completion and by connecting the service event to the affected customer asset. Your notes should distinguish the purpose of the work order, incident type, booking, product or service, and asset history.
Use incident types as reusable definitions of common service work rather than treating every work order as a blank form. Consider what tasks, products, services, characteristics, or instructions a repeated incident should provide. Then test whether a dispatcher can assign the work and whether a frontline worker can complete it without reconstructing the requirement from memory.
Customer assets deserve equal attention. A service history is valuable only when the service activity is associated with the right asset and customer context. Practice tracing previous work, installed equipment, and future maintenance decisions from the asset record. If your scenario cannot answer what was serviced, where, and why, the design is incomplete.
Include exception paths: a work order changes scope, a technician cannot complete a task, a required product is unavailable, or the wrong asset was selected. These cases reveal whether statuses, ownership, instructions, and related records have been designed coherently.
A practical work-order exercise
Write a short requirement for a repair visit. Identify the customer, location, asset, incident, required skill, expected duration, parts, technician action, and completion evidence. Configure or model the records needed to support it, then review the result from three perspectives: dispatcher, technician, and service manager.
Repeat the exercise for planned maintenance generated through an agreement. Compare what is common between the two work orders and what should be controlled by the agreement or incident definition. This comparison builds the judgment needed to avoid unnecessary duplication.
How do you study scheduling and dispatch?
Schedule and dispatch work orders (15–20%) requires more than knowing how to place a booking. Practice matching customer requirements with resource skills, location, availability, and the operational constraints represented in the scenario. Explain why one resource is a better match than another and what trade-off the dispatcher is making.
Start by translating the requirement into scheduling criteria. A customer may require a particular skill, service territory, time window, or asset familiarity. Only after identifying those criteria should you consider the available resources and bookings. This order of reasoning is more reliable than choosing a resource first and rationalizing the choice afterward.
Use the schedule board as a decision surface, not as the entire subject. Study how a dispatcher sees demand, resource capacity, bookings, and conflicts. Then test changes: the preferred technician is unavailable, travel makes a booking impractical, or the customer changes the appointment requirement.
Record the result of each scheduling decision. A useful note says which constraint was satisfied, which constraint was relaxed, and what follow-up action is required. This prepares you for scenario questions and for real implementation conversations without depending on live exam content.
Dispatch pitfalls
Do not equate availability with suitability. A free resource may lack the required skill or be poorly located. Do not ignore the difference between scheduling a work order and completing the work. A booking must support an executable assignment, while the work order must retain the service requirement and outcome.
Also avoid designing for the perfect case only. A robust process defines what happens when no resource matches every criterion. That may require a dispatcher decision, a customer conversation, a revised time window, or an escalation—not an unsupported assumption that the system will resolve the conflict automatically.
What should you practice in the Field Service mobile app?
Manage the Field Service mobile app (5–10%) is a smaller published domain, but it represents the frontline experience. Study how forms, views, and the site map expose the information technicians need to review, update, and complete work. The correct design is driven by field tasks, not by copying every back-office field onto a mobile screen.
Walk through the technician’s sequence: receive assigned work, review location and asset context, inspect instructions, record progress, consume or identify products, capture completion details, and move the work toward closure. At each step, note whether the user needs to read, create, edit, or confirm information.
Use the official learning path’s mobile module to structure this practice. Then compare the mobile experience with dispatcher and administrator requirements. A field worker should not have to understand the whole data model to complete a visit, while the system should still preserve the information needed for service history and operational reporting.
Mobile design checks
Check whether the most important information is visible at the point of action, whether views support the technician’s daily queue, and whether the form reflects the actual completion process. Check also whether a customization creates confusion by exposing fields that are irrelevant or by hiding information needed to make a safe service decision.
If you cannot access a practice environment, perform a paper walkthrough instead. Label each screen or record action and identify what would be configured, what would be governed by security, and what would require validation with frontline users.
How should inventory and purchasing fit the study plan?
Manage inventory and purchasing by using the built-in inventory management system (5–10%) should be studied as part of service execution, not as a separate warehouse topic. Connect products, locations, technician needs, replenishment, and purchasing decisions to the work order that creates the demand.
Use a shortage scenario. A technician needs a part, the preferred location does not have it, and the visit cannot proceed without a decision. Map the possible operational responses and identify which records must reflect the part requirement, movement, consumption, or purchase. The objective is to understand the flow of information and accountability.
Microsoft’s learning path specifically includes inventory management within its work-order module. That is a useful reminder that inventory affects whether a work order can be completed and whether the customer-asset history accurately represents the service delivered.
Inventory mistakes to avoid
Do not study product catalog concepts without tracing their effect on a real job. Do not assume that recording a part on a work order automatically answers every purchasing or stock question. Verify how the organization expects inventory to be represented, where the part is held, and how consumption or replenishment should be recorded.
Keep a separate list of terms that your organization uses differently from the application. Functional consultants often lose time when business language and system terminology appear identical but refer to different processes.
Where does Power Platform enter the exam scope?
Implement Microsoft Power Platform (5–10%) was one of the published MB-240 domains. Prepare by understanding how Field Service fits into the wider platform and how integrations or extensions support a requirement. The goal is not to memorize unrelated platform features; it is to choose an appropriate implementation approach and explain its effect on the Field Service process.
Microsoft identifies integration areas including Microsoft Power Platform, Dynamics 365 Customer Service, Microsoft 365 apps, Dynamics 365 Remote Assist, and Dynamics 365 Guides. Build a simple integration map showing the business event, source system, destination experience, data involved, and owner responsible for support.
Use the functional-consultant boundary as a study filter. For every proposed enhancement, ask whether standard Field Service configuration already meets the requirement, whether a platform capability is appropriate, and what must be designed or tested by developers or solution architects. This keeps customization purposeful and reduces the risk of solving a process problem with unnecessary complexity.
A useful platform decision exercise
Take one requirement from your work-order scenario, such as notifying a customer, updating a related service process, or presenting information to a frontline worker. Describe the standard Field Service behavior first. Then outline a platform-based enhancement only if a clear gap remains, including the trigger, data, security implications, failure handling, and test case.
This exercise develops implementation judgment rather than feature recall. It also makes collaboration easier because you can state precisely what the functional design must accomplish before asking another specialist to build or integrate it.
Which Microsoft Learn resources should you use?
Use the official MB-240 study guide and exam page as the authority for the historical scope, then use the intermediate-level Implement Microsoft Dynamics 365 Field Service learning path for structured product study. The path contains four modules covering configuration, work-order management, agreements, and customization of the Field Service Mobile application.
The learning path lists familiarity with Microsoft Dynamics 365 applications as a prerequisite. Treat that as a foundation check: if model-driven applications, records, security, or Power Platform concepts are unfamiliar, resolve those gaps before spending most of your time on Field Service-specific configuration.
Microsoft’s broader Dynamics 365 credentials catalogue links role-based certifications and relevant learning content. Because MB-240 is retired, use that catalogue to check what credential currently corresponds to your career objective. Do not assume that a legacy course code or an old certification page describes the active route.
How to read the study guide efficiently
Read the skills-measured table first and turn each domain into a checklist. Use the linked learning resources to fill conceptual gaps, but return to the checklist after every module. For each objective, write one explanation, one configuration or design exercise, and one failure case.
The study guide notes that Microsoft updates exams periodically and that the English version is updated first. That advice matters especially when using archived MB-240 material: distinguish historical objectives from current product behavior and confirm active credential information before making a scheduling decision.
What is a practical study roadmap?
A sound roadmap moves from process understanding to configuration, then to execution, integration, and review. Because MB-240 is retired, the roadmap below is for Field Service capability-building or historical objective coverage; it is not a promise that completing it qualifies you for a current exam.
Start by writing a service scenario and a glossary of its terms. Map the work-order lifecycle and customer-asset history. Next, study administration, resources, scheduling, booking setups, and agreements. Then work through dispatch, mobile execution, inventory, purchasing, and Power Platform decisions. Finish by testing the entire scenario from requirement to completed service record.
Stage one: establish the operating model
Define the customer types, service locations, assets, recurring obligations, emergency work, resources, skills, and availability rules in your scenario. Draw the lifecycle and identify the information each participant needs. This stage gives every later configuration exercise a reason and a testable outcome.
Stage two: build the service foundation
Study Field Service administration, resources, scheduling concepts, booking setups, incident types, and agreements. For each item, connect the setting or record to a business requirement. Validate that the design can create or organize work without forcing dispatchers to recreate standard information manually.
Stage three: execute and dispatch work
Run the work-order scenario through scheduling and dispatch. Test a good match, a conflict, an unavailable resource, and a changed customer requirement. Then review the same assignment as a technician using the mobile process and as a manager reviewing service history.
Stage four: extend and troubleshoot
Add an inventory shortage and one Power Platform or connected-application requirement. Document the data flow, ownership, security questions, and expected failure behavior. Troubleshoot from the business outcome backward: identify where the process stopped, which record lacks information, and which configuration or integration decision caused the gap.
Stage five: perform a readiness review
Close the notes and explain each domain aloud using your own scenario. You should be able to justify configuration choices, distinguish related records, describe dispatch trade-offs, and identify when collaboration with a developer or solution architect is needed. Any explanation that depends on memorized labels rather than a process example deserves another practical exercise.
What exam details were documented?
The historical MB-240 study guide states that a score of 700 or greater was required to pass. Microsoft listed the exam languages as English, Japanese, German, French, Spanish, Portuguese (Brazil), Italian, and Chinese (Simplified), and noted that price depended on the country or region where the exam was proctored.
Those details should not be used to plan a new MB-240 appointment because Microsoft now marks the exam as retired. If you are reviewing archived records or comparing historical study material, retain the distinction between documented exam information and current availability.
Microsoft recommended registering with a personal MSA account because exam records associated with an organizational work or school account could be lost and unrecoverable if the candidate left that organization. That warning is relevant to Microsoft certification administration generally, but it does not restore access to a retired exam.
The study guide also described an exam sandbox, a free practice assessment, accommodation requests, and additional time when the exam was not available in a preferred language. These were preparation or administration resources documented for the exam; confirm current applicability with Microsoft before relying on any of them for another credential.
What about renewal?
Microsoft’s renewal page says the Field Service Functional Consultant Associate certification, related exam, and renewal assessments were retired on June 30, 2026. The page also explains that renewal assessments were intended to demonstrate currency with Field Service updates, but that historical renewal process should not be confused with an active route for this retired credential.
What are the most costly preparation mistakes?
The largest mistake is preparing to schedule a retired exam without checking Microsoft’s current status. The next is studying only interface steps while ignoring the work-order lifecycle, asset history, resource constraints, mobile execution, and integration boundaries. A third is treating practice questions or recalled material as a substitute for understanding implementation decisions.
Avoid using leaked questions, exam dumps, or memorization claims. They cannot establish that you can configure a working service process, and they do not provide a reliable basis for a current credential decision. Use official objectives, Microsoft Learn content, documented scenarios, and hands-on validation instead.
Do not give equal study time to every topic without considering dependencies. Work orders and application configuration form the operating foundation; scheduling, mobile work, inventory, and platform extensions make more sense when that foundation is clear. At the same time, do not ignore the smaller domains, because a real implementation crosses all of them.
Finally, do not confuse the legacy certification page with a current prerequisite list. The legacy page lists MB-200 and MB-240 as required exams for that earlier certification version, while current certification requirements must be checked through Microsoft’s active credentials catalogue.
A final self-check
You are ready to move from reading to validation when you can take an unfamiliar service requirement and identify the required records, configuration areas, resource constraints, technician experience, inventory implications, integration choices, and test outcomes. If you can name a feature but cannot explain its place in the process, keep studying the scenario rather than collecting more terminology.
What should you do next?
First, verify the current Microsoft Dynamics 365 certification catalogue and confirm whether your target is a live credential or Field Service implementation capability. Second, save the official MB-240 study guide as a historical scope reference. Third, complete the Microsoft Learn Field Service path and build one end-to-end scenario that you can configure, explain, and troubleshoot.
If your objective is employment or project readiness, turn the roadmap into a working portfolio: a process map, configuration rationale, dispatch decision record, mobile task flow, inventory exception, and integration design. If your objective is certification, use the catalogue’s current requirements rather than scheduling against an archived exam page.
Keep your study notes version-aware. Microsoft updates product and assessment content, and the MB-240 pages contain retirement notices. Recheck official pages immediately before committing time or money to a credential route. That final verification is the practical decision that protects your preparation from becoming tied to an unavailable exam.
Conclusion
MB-240 remains a useful map of the Field Service functional-consultant role, but Microsoft’s published retirement notice means it should not be treated as an available exam. Use its domains to learn the complete service process: configure the application, manage work and assets, dispatch suitable resources, support technicians, control inventory, and extend the solution responsibly. Then confirm the active Microsoft credential path before scheduling anything. That combination of process practice and current-source verification is more dependable than memorizing an obsolete blueprint.
Related exams
- 77-725 exam — Microsoft Word 2016 Core: Document Creation, Collaboration and Communication (MOS)
- 77-727 exam — Excel 2016: Core Data Analysis, Manipulation, and Presentation
- 77-728 exam — Excel 2016 Expert: Interpreting Data for Insights
- 77-731 exam — Outlook 2016: Core Communication, Collaboration and Email Skills
- AZ-120 exam — Planning and Administering Microsoft Azure for SAP Workloads
- AZ-400 exam — Microsoft Azure DevOps Solutions