Home / crm-business-applications / Microsoft Dynamics 365 Field Service Functional Consultant (MB-240) / Cheat Sheet
Microsoft Dynamics 365 Field Service Functional Consultant (MB-240)

MB-240 Cheat Sheet

MB-240 Rewarded Configuring Field Service Records Correctly — Not Building Custom Solutions

MB-240 and its Field Service Functional Consultant certification were retired on 30 June 2026, with no successor named by Microsoft. This sheet serves existing holders and consultants still learning Field Service configuration: the lightest built-in record wins.

Check Your Readiness →
Among the harder certs
Avg: Not published by Microsoft
Pass: 750 / 1000
Most candidates understand Microsoft Dynamics 365 Field Service Functional Consultant (MB-240) concepts — and still fail. This exam tests how you apply knowledge under pressure.

MB-240 Domain Map (final outline, 18 September 2025)

Stems read like implementation tickets: a customer business rule such as a one-hour minimum charge, a banned technician or a quarterly service, and you pick the setting or record that delivers it without code. Passing standard was 700/1000; Microsoft never published the question count.

  1. 01
    Configure Field Service (20–25%) — security roles, territories, characteristics and ratings, product types, minimum charges, resource types, crews, NTE, Remote Assist
  2. 02
    Work orders and customer assets (25–30%) — system vs. sub-status, booking status, incident types, agreements, inspections, assets and functional locations
  3. 03
    Schedule and dispatch (15–20%) — URS, requirements, schedule assistant, fulfillment preferences, multi-day allocation, resource preferences, geocoding
  4. 04
    Mobile app (5–10%) — mobile app module, offline profile, booking status, service reports, geofencing, push notifications
  5. 05
    Inventory and purchasing (5–10%) — warehouses, adjustments vs. transfers, PO receipts, RMA vs. RTV, used products
  6. 06
    Power Platform (5–10%) — main and quick view forms, system views, custom pages, automated cloud flows, solutions

Wrong instinct vs correct approach

On-site repair labour is billed hourly, but every visit must be charged at least one hour
✕ Wrong instinct

Create the repair as an inventory product with a fixed price

✓ Correct approach

Set the product type to service, then set a minimum charge amount and duration on its price list item. Only services are priced by duration; inventory products move warehouse stock and are priced per unit.

One customer bans a specific technician who must stay available to other customers in the territory
✕ Wrong instinct

Remove the technician from the territory

✓ Correct approach

Add a restricted resource preference on that customer's account, which excludes the technician from schedule assistant results only for that customer. Territories filter scheduling views and never act as security or per-customer exclusions.

Quarterly chiller servicing must create work orders two weeks ahead and bill a fixed monthly fee
✕ Wrong instinct

Create recurring work orders manually and invoice after each visit

✓ Correct approach

Create an agreement, move it out of Estimate to Active, add a booking setup with quarterly recurrence and lead time, and a separate invoice setup recurring monthly. Visit and invoice schedules run independently.

Technicians see customer assets online, but the asset list is empty once they lose signal
✕ Wrong instinct

Add read privileges to the technician security role

✓ Correct approach

Access is clearly fine because records load online. Add customer assets to the mobile offline profile with filters tied to the technician's bookings, so only needed rows sync and the device stays fast.

Know these cold

  • ▸ Assign the Field Service security role and its field security profile together
  • ▸ A resource only matches a skill requirement once rated on that characteristic
  • ▸ Not-to-exceed records warn on total spend; price lists only set unit prices
  • ▸ Primary incident type sets requirement duration and skills; extra incident types do not extend it
  • ▸ Inspections attach through service task types, never directly to a work order type
  • ▸ Functional locations model sites and rooms; customer assets model equipment linked to them
  • ▸ Fulfillment preferences limit arrival windows; multi-day allocation spreads one long job across days
  • ▸ Enable a custom table for scheduling instead of building a scheduling app
  • ▸ RMA records the customer return first; RTV ships the item back to the vendor
  • ▸ Remote Assist one-time calls give guests a browser link with no licence or app

Can you answer these without checking your notes?

In this scenario: "On-site repair labour is billed hourly, but every visit must be charged at least one hour" — what should you do first?
Set the product type to service, then set a minimum charge amount and duration on its price list item. Only services are priced by duration; inventory products move warehouse stock and are priced per unit.
In this scenario: "One customer bans a specific technician who must stay available to other customers in the territory" — what should you do first?
Add a restricted resource preference on that customer's account, which excludes the technician from schedule assistant results only for that customer. Territories filter scheduling views and never act as security or per-customer exclusions.
In this scenario: "Quarterly chiller servicing must create work orders two weeks ahead and bill a fixed monthly fee" — what should you do first?
Create an agreement, move it out of Estimate to Active, add a booking setup with quarterly recurrence and lead time, and a separate invoice setup recurring monthly. Visit and invoice schedules run independently.

Common Exam Mistakes — What candidates get wrong

Adding a new work order system status for a reporting label

System statuses (Unscheduled through Posted or Canceled) are fixed because automation depends on them. Create a sub-status such as Awaiting Parts mapped to one system status. Technicians change booking status, which rolls up to the work order.

Treating a Completed work order as financially final

Completed means the work is done; Posted locks the work order and finalises billing, usually after back-office review. Agreement invoice setup runs on its own recurrence, so a fixed monthly fee invoices even in months without a visit.

Blaming the schedule assistant before checking working hours and geocodes

A resource with no working hours template has no availability, and an address without latitude and longitude breaks travel and distance sorting. Then check territory, characteristic ratings and resource preferences, since any one can silently filter resources out.

Using a crew when the team changes from job to job

A crew books fixed members together; a pool assigns a specific member later; a requirement group template finds a matching combination per job and is often attached to an incident type. Crew leader management cascades status from the leader.

Moving van stock with two inventory adjustments

An inventory transfer decreases the source warehouse and increases the destination, such as a technician van, in one audited transaction. Adjustments correct one location after counts or damage. Stock rises only on a purchase order receipt, never on approval.

Resources to help you pass Dynamics 365 Field Service MB-240 on your first attempt

MB-240 is retired, but its Field Service judgement still matters on projects. Check your configuration instincts.