New: Odoo and Dynamics 365 cost calculators.Estimate your costs

Microsoft Dynamics 365 Field Service: pricing, features, and SME fit

As of October 2026, list price is $105 USD or $142.50 CAD per user per month, paid yearly (CAD plus tax). License map, features, and a first rollout.

Dynamics 365Dynamics 365 & Power Platform14 min readUpdated 22 sources

Key takeaways

  • Onsite service application: work orders, dispatch, mobile technicians, assets, inventory, agreements, billing, and analytics.
  • Réactif: break-fix after a case, call, email, or portal request.
  • Created from cases, sales orders, emails, phone calls, agreements, portals, or IoT data.
  • Schedule board: manual dispatch by location, availability, skills, and priority.

Microsoft Dynamics 365 Field Service overview

A Microsoft Dynamics 365 Field Service overview starts with the job it is built for. Microsoft Learn describes it as the application for delivering onsite service at customer locations, combining workflow automation, scheduling, and a mobile app. Dynamics 365 for field services, field service for Dynamics 365, and MS Dynamics 365 Field Service are the same product under the names buyers type into search.

The documented capabilities (fonctionnalités Dynamics 365 Field Service) are work orders, scheduling and dispatch, communication tools, a mobile app, Copilot summaries and natural-language questions, asset management, preventive maintenance, inventory purchasing and returns, billing, time tracking, and analytics. Named roles are customer service agents, service managers, dispatchers, field technicians, and inventory managers. Agents, managers, dispatchers, and inventory managers primarily use the browser. Technicians use the mobile app.

It installs on a Power Platform environment that has a Dataverse database and Enable Dynamics 365 apps turned on. A free trial installs the app automatically. After purchase, the environment type can be changed to production. Because the records sit on Dataverse, a service account can connect to the rest of a Dynamics 365 estate, including sales orders that become installs and cases that become work orders.

Field service CRM in Dynamics 365 means those customer and job records share one database. It is field service business software for companies that send people to a site, with a schedule board for dispatch and a license per person who needs the app. Companies that only answer calls and emails are looking at Dynamics 365 Customer Service, which is a separate product covered later on this page.

  • Onsite service application: work orders, dispatch, mobile technicians, assets, inventory, agreements, billing, and analytics.
  • Browser for agents, managers, dispatchers, and inventory managers. Mobile app for technicians.
  • Installs on Power Platform with a Dataverse database. A trial can move to a production environment after purchase.
  • Same product whether the search says Dynamics 365 Field Service, Dynamics 365 for field services, or field service for Dynamics 365.

Type de service in Dynamics 365 Field Service

The search type de service Dynamics 365 Field Service maps to four service delivery models in Microsoft’s French and English documentation. Many organizations combine them. The French names are réactif, préventif, prédictif, and basé sur des projets.

Réactif is reactive break-fix. A customer calls, a case or a phone call becomes a work order, and a dispatcher books a technician. Préventif is preventive maintenance based on an agreement (basé sur un accord). The agreement generates scheduled work so a dispatcher does not raise every visit by hand. Prédictif is predictive maintenance driven by IoT (piloté par l’IoT), often discussed as Connected Field Service, where device data can open work before the customer calls. Basé sur des projets is multistage project-based work (multi-étapes), the pattern used when an install or upgrade has several visits, skills, and parts lists.

Pick the model from the work you already sell. A shop with emergency callouts and a handful of maintenance contracts can go live on réactif plus préventif. Add prédictif when assets already send telemetry you trust. Use the project model when one sale creates a chain of site visits. Microsoft’s overview treats these as operating patterns on the same work-order record, and the Field Service license is the same whichever mix you run.

  • Réactif: break-fix after a case, call, email, or portal request.
  • Préventif: agreement-based maintenance that generates work on a schedule.
  • Prédictif: IoT-driven maintenance (Connected Field Service).
  • Basé sur des projets: multistage work such as installs and upgrades.

Work orders, from request to invoice

The work order is the record dispatchers, technicians, and billing share. Microsoft documents creation from cases, sales orders, emails, phone calls, service agreements, web portals, or IoT data. Details on the order include tasks, parts, billable labor, and required characteristics such as skills.

A work order incident is a template package of recommended service tasks, products, services, and characteristics used to populate a work order faster. A boiler breakdown, a preventive visit, and a two-day install should each have an incident type so staff do not rebuild the parts list on every call. Agreements are the preventive source: the contract holds the schedule, and Field Service raises the work orders.

The board can schedule work orders, and it can also schedule sales orders, projects, and custom tables. When the technician finishes, time, parts, and services on the order are what billing uses. You can invoice inside Field Service, or post the outcome to Business Central when that integration is turned on. Until actuals are recorded, finance is still looking at a job that has not hit the books.

For a 40-person HVAC company, a useful first incident set is three templates: no-heat emergency (two hours of labor, a standard parts kit, a gas-ticket skill), annual agreement visit (checklist plus filter), and new-equipment startup (two bookings, commissioning task, serial asset). That is configuration work, and it is the difference between a dispatcher typing each job and a form that already knows the skills and parts.

  • Created from cases, sales orders, emails, phone calls, agreements, portals, or IoT data.
  • Carries tasks, parts, billable labor, and required characteristics.
  • Incident types are templates of tasks, products, services, and characteristics.
  • The same scheduling tools can book work orders, sales orders, projects, and custom tables.

Entités Dynamics 365 Field Service

Entités Dynamics 365 Field Service are the Dataverse tables staff and integrations read. Microsoft’s work-order architecture lists Work Order, Account (the service account), Service Agreement, Customer Asset, Work Order Incident, Resource Requirement, Bookable Resource, Booking, Booking Timestamp, Booking Journal, Product Catalog, Inventory, and Purchasing.

Account is the customer site or billing customer. Customer Asset is the equipment at that site. Service Agreement holds the preventive contract. Work Order Incident is the template. Resource Requirement says which skills and how much time the job needs. Bookable Resource is the person, crew, or facility that can be booked. Booking is the time slot on the board. Booking Timestamp and Booking Journal record status changes and time. Product Catalog, Inventory, and Purchasing cover parts, truck stock, purchase orders, and returns.

A booking with no resource requirement cannot be matched on skills. A product that never enters inventory cannot decrement a truck. A work order with no service account has nowhere to send the invoice. When a Business Central sync fails, check those empty records and the Premium and same-tenant gates covered later on this page. Name these tables in workshops using both the English labels and the word entités, because Canadian teams often train from the French docs and the English app at the same time.

Core Dynamics 365 Field Service records (Microsoft Learn architecture)
RecordWhat it holdsWho touches it first
Account (service account)Customer and service locationService agent or sales
Customer AssetEquipment installed at the siteInventory or service manager
Service AgreementPreventive contract and visit scheduleService manager
Work Order IncidentTemplate of tasks, products, services, and characteristicsService manager
Work OrderThe job: tasks, parts, labor, characteristicsAgent or agreement process
Resource RequirementSkills and time the job needsDispatcher
Bookable ResourcePerson, crew, or facility that can be bookedDispatcher or admin
Booking, timestamp, journalScheduled slot, status history, and timeDispatcher and technician
Product, inventory, purchasingParts catalog, stock, purchase orders, and returnsInventory manager

Microsoft field service dispatch software: board, assistant, and RSO

Microsoft field service dispatch software inside this product has three levels. Dispatchers can schedule manually on the schedule board, with the schedule assistant, or automatically with the Resource Scheduling Optimization add-on. The board shows work orders, sales orders, projects, and custom tables. Location, availability, skills, and priority are the inputs those tools use.

The schedule board is drag-and-drop assignment for a person watching the day. The schedule assistant recommends a resource for one job. Resource Scheduling Optimization (RSO) is the paid add-in, priced by the number of resources whose schedules are optimized. Microsoft prices it with a single-tenant assumption. RSO can run overnight, intraday (the documented example is every 30 minutes), for one resource, as a simulation, or for emergency priority jobs.

As of October 2026, RSO lists at $30 USD or $40.70 CAD per resource per month, paid yearly. Canada prices are plus applicable tax. A 10-technician crew that optimizes every resource adds $300 USD or $407 CAD per month on top of user licenses. A team with stable territories and few emergency inserts can stay on the board and the assistant. Add RSO when travel, overtime, or missed windows are coming from manual routing across mixed skills and territories. Book a Flectic scoping call to count which resources you will optimize before that add-on lands on the order.

Scheduling analytics sit on the same CRM records: bookings, travel, skills, and work-order status. Use them to see utilization and how often emergency work bumps the plan. They do not replace a finance report. Copilot can answer natural-language questions about this data. The Scheduling Operations Agent for dispatchers is listed on the product page as in preview, so treat automated dispatch agents as optional and separate from the RSO add-on price.

  • Schedule board: manual dispatch by location, availability, skills, and priority.
  • Schedule assistant: a recommendation for a single job.
  • RSO: paid optimization per resource, including overnight, intraday, single-resource, simulation, and emergency runs.
  • RSO list as of October 2026: $30 USD or $40.70 CAD per resource per month, paid yearly. Canada plus tax.

Application mobile Dynamics 365 Field Service

The application mobile Dynamics 365 Field Service is included in the Field Service license at no extra charge. It runs on iOS, Android, and Windows 10 or later, and it is a customizable model-driven Power Platform app. Technicians update the booking, tasks, time, parts, and notes on the work order from the site.

Inspections are published templates attached to service task types, then added to work orders. On mobile, file attachments default to 3 MB per file unless an admin changes the limit, and only the latest response set is kept for a task. Plan photos and PDFs around that default before go-live, or raise the limit on purpose.

Offline access requires an administrator-configured offline profile. Microsoft says the refreshed mobile experience does not currently support working offline. If crews lose signal in basements, plants, or rural routes, test the mobile build you will deploy and keep an offline profile for the experience that still supports it. The older pattern of trimming sync with filters still matters, because a profile that pulls every account and product will stall a phone.

Every person who opens the app needs a user account, a Field Service or Field Service Contractor license, environment access, and a security role. The Field Service - Resource role can view and update only work orders assigned to that worker, which is the right scope for most technicians. Contractors can be added as Microsoft Entra B2B collaboration users.

  • Included with the license on iOS, Android, and Windows 10 or later.
  • Inspection attachments default to 3 MB per file. Only the latest response set is kept.
  • Offline needs an admin-configured offline profile. The refreshed mobile experience does not currently support offline.
  • Resource role limits a worker to assigned work orders.

Capabilities that change the weekly schedule

Feature checklists hide the operating choices. Four capabilities change a service week: complete work orders before travel, a schedule someone can defend, parts that leave the truck on the job, and a status the customer can see. Each one is configuration, and each one fails if the records in the entity list are thin.

First-time completion depends on history, the asset, required characteristics, an inspection, and the parts on the order. Schedule density depends on clean territories and skills, then on the assistant or RSO when the board gets noisy. Truck stock depends on inventory products consumed against a mobile warehouse before the job is billed. Customer updates depend on communication tools on the work order, plus IoT alerts when equipment is instrumented.

Microsoft’s product page cites a Forrester Consulting Total Economic Impact study from December 2023. The composite organization in that study shows 346% ROI, $42.65 million in benefits over three years, and payback in under six months. For a 20 to 100 person company, judge the purchase on license mix, travel, and how agreements replace manual job entry.

Two 2026 product limits belong in the business case. Dynamics 365 Guides and Remote Assist will no longer be available after December 31, 2026, so a multi-year plan should not depend on those mixed-reality apps. The Scheduling Operations Agent is in preview. Custom agents are built in Copilot Studio. The pricing page says an Azure subscription is required to use agents, and Copilot Credits are sold separately for prebuilt and custom agents.

  • Work-order completeness, skills, inspections, and truck stock support first-time completion.
  • Board and assistant first. RSO when routing across territories is the cost problem.
  • Forrester December 2023 composite: 346% ROI, $42.65 million over three years, payback under six months. Microsoft’s composite organization, separate from a 20 to 100 person case.
  • Guides and Remote Assist end after December 31, 2026. Scheduling Operations Agent is in preview.

Inventory, purchasing, and returns

Field Service includes inventory for technicians and trucks: warehouses (including mobile truck-stock warehouses), adjustments, transfers, and consumption of products on work orders, plus purchase orders and returns. Products have to be set to the Inventory product type before they participate. When a technician uses a part, stock on that warehouse drops, and posted actuals carry the cost to the job.

This is the field edge of stock, and it is a different engine from Dynamics 365 Supply Chain Management or the inventory ledger in Business Central. Distribution, landed cost, and multi-site planning stay in the ERP. Field Service should consume and request parts, then hand quantities and cost to that ledger. Item availability in Field Service through virtual tables requires Field Service and Business Central in the same tenant.

A practical split for a 25-truck electrical contractor: the truck is a mobile warehouse, the shop is a static warehouse, and Business Central remains the stock ledger if Premium service integration is on. Transfers replenish the truck. The work order consumes the breaker or the sensor. Returns follow the purchasing path inside Field Service. If the part is never set to the Inventory product type, the technician can type a name and finance never sees a quantity move.

  • Static and mobile warehouses, adjustments, transfers, and work-order consumption.
  • Products must use the Inventory product type.
  • Purchase orders and returns stay in Field Service.
  • Pair with Business Central or Supply Chain Management when you need a full stock ledger. Same-tenant virtual tables expose Business Central item availability.

Copilot in Dynamics 365 Field Service

Copilot in Field Service summarizes work orders and answers natural-language questions. The work order summary has to be enabled by an admin, generates per user, respects that person’s security role, and shows in a side pane on the work order or booking. That is the practical win for a technician who inherits a long history, or a dispatcher drafting an update.

Prebuilt and custom agents are a separate spend. Copilot Credits are sold as pay-as-you-go or prepaid commit, and prepaid commit units can save up to 20%. Microsoft does not list a per-credit price on the Field Service pricing page, so budget the model, and confirm the credit price at checkout. An Azure subscription is required to use agents. The Scheduling Operations Agent is in preview.

Use Copilot on language-heavy work: recap, customer wording, and questions about bookings and assets. Keep a person on schedule changes and on anything that becomes an invoice. Credits and Azure are capacity costs on top of the $105 or $50 user license, in the same way RSO sits on top of the user license.

  • Work order summary is admin-enabled, per user, and limited by security role.
  • Natural-language questions run against Field Service data the user can already see.
  • Agents need Copilot Credits plus an Azure subscription. Prepaid commit can save up to 20%.
  • Scheduling Operations Agent is in preview.

Dynamics 365 Field Service pricing in the US and Canada

Dynamics 365 Field Service pricing as of October 2026 is published as yearly list prices. Microsoft says displayed prices are informational and the checkout price can differ by currency, country, and region. Canada list prices are shown plus applicable tax. Month-to-month prices without an annual commitment are not on the pricing page. A 30-day trial is available at no charge, and Learn says you can start it without admin privileges.

Two licenses exist. The standard Field Service license includes all core features. Field Service Contractor is a subset of core features for third-party technicians. The public comparison grid text does not list which rows the Contractor license drops. The Field Service pricing page notes that some items apply in the mobile app for that plan. Every user still needs an account, a license, environment access, and a security role.

Microsoft positions Field Service Contractor for third-party technicians. The Field Service - Resource role is a security limit on a license, not a cheaper SKU: it can view and update only work orders assigned to that worker. Confirm with Microsoft before you buy a full seat for every employee. Dispatchers, service managers, and inventory managers use the browser on the board, agreements, and purchasing, so a typical map puts them on the full license. Contractors can be added as Microsoft Entra B2B collaboration users.

Worked example, using October 2026 list prices and these assumptions: 2 dispatchers and 1 service manager on the full license, 4 internal technicians on the full license, 6 third-party technicians on Contractor, and RSO for 10 resources. US monthly list is 7 × $105 plus 6 × $50 plus 10 × $30, which is $1,335 per month, or $16,020 per year, before tax and before Copilot Credits. The same mix in Canada is 7 × $142.50 plus 6 × $67.80 plus 10 × $40.70, which is $1,811.30 CAD per month plus applicable tax, or $21,735.60 CAD per year plus tax. Drop RSO and the US list falls to $1,035 per month ($12,420 per year). Canada without RSO is $1,404.30 CAD per month plus tax. Book a Flectic license-map call to place dispatchers, technicians, and subcontractors on full seats, Contractor seats, and RSO, and to flag Customer Service and Business Central Premium when those licenses are still extra.

A smaller crew, same price list: 1 dispatcher and 3 internal technicians on the full license, 2 contractors, and no RSO. That is 4 × $105 plus 2 × $50, or $520 USD per month ($6,240 per year). In Canada it is 4 × $142.50 plus 2 × $67.80, or $705.60 CAD per month plus tax. FastTrack for Dynamics 365 includes Field Service, but eligibility requires a minimum annual Dynamics 365 spend on a new deployment plus a qualified Solutions Partner. Microsoft does not publish that dollar minimum on the eligibility page.

  • Full license: $105 USD or $142.50 CAD per user per month, paid yearly.
  • Contractor: $50 USD or $67.80 CAD per user per month, for third-party technicians.
  • RSO: $30 USD or $40.70 CAD per optimized resource per month.
  • Checkout can differ by currency, country, and region. Canada prices are plus applicable tax.
Field Service list prices as of October 2026, paid yearly
ItemUSDCAD (plus applicable tax)Basis
Field Service (full)$105.00$142.50Per user per month, paid yearly. All core features.
Field Service Contractor$50.00$67.80Per user per month, paid yearly. Subset for third-party technicians.
Resource Scheduling Optimization$30.00$40.70Per optimized resource per month, paid yearly. Single-tenant pricing assumption.
Field Service trial$0See Canadian checkout30 days. Learn says you can start it without admin privileges.

Dynamics 365 Customer Service versus Field Service

Dynamics 365 Customer Service is a separate product from Field Service. People search d365 customer service, customer service Microsoft Dynamics 365, and Microsoft Dynamics 365 for customer service on the same buying cycle because both sit under the Dynamics 365 name and the Enterprise list price matches Field Service. Customer Service covers cases and contact-center work. Field Service covers onsite work orders, the schedule board, truck inventory, and the technician app.

As of October 2026, US list prices paid yearly are Customer Service Professional $50, Enterprise $105, and Premium $195 per user per month. Canada list prices, plus applicable tax, are $67.80, $142.50, and $264.60. Dynamics 365 Contact Center is another license at $110 USD or $149.20 CAD per user per month, paid yearly. Enterprise at $105 USD matches the Field Service full license and remains a Customer Service license. A person who works in both apps needs a license for each app they use.

Buy Customer Service Professional when agents handle cases and you do not need the enterprise tier. Buy Field Service when someone has to go to the building. A common 20 to 100 person mix is three case agents on Customer Service Professional and a field crew on Field Service. Three Professional seats add 3 × $50 = $150 USD per month, or 3 × $67.80 = $203.40 CAD per month plus tax, on top of the Field Service example above. Add Contact Center only when you are buying that contact-center license, at $110 USD or $149.20 CAD per user per month.

Cases still matter to field teams. Field Service can create a work order from a case, so many companies keep a small Customer Service footprint for the phone and email queue and Field Service for the visit. The $105 Enterprise price is the Customer Service license and does not include the schedule board. The schedule board is on the Field Service license.

Customer Service and Contact Center list prices as of October 2026, paid yearly
LicenseUSD per user per monthCAD per user per month, plus taxWhat it is for
Customer Service Professional$50.00$67.80Case management at the lower tier
Customer Service Enterprise$105.00$142.50Higher Customer Service tier. Same USD list as Field Service, separate product.
Customer Service Premium$195.00$264.60Top Customer Service tier
Contact Center$110.00$149.20Contact center license, separate from Field Service
Field Service full$105.00$142.50Onsite work orders, scheduling, inventory, technician app

Business Central and the Premium gate

Business Central integrates with Field Service in two documented ways: project management only, or project and service management together. Service-management integration requires the Business Central Premium experience and cannot be enabled alone. If the goal is to invoice field work from Business Central service orders, Premium is the requirement. Project-only integration is the path when you are pushing project tasks and you are not turning on service management.

The integration needs a Dataverse connection, Dynamics 365 Sales integration enabled, and the Field Service Integration app from Marketplace. Item availability in Field Service via virtual tables requires Field Service and Business Central in the same tenant. Those are setup gates, and they are easy to miss after the Field Service licenses are already purchased.

Decide the ERP path before you design invoicing. Companies that bill from Field Service itself can go live on work orders, price lists, and posted actuals, then add Business Central when the books move. Companies that already post service invoices in Business Central should confirm Premium before they promise technicians that parts and labor will land on a Business Central service order. Finance and Supply Chain Management are a different estate. Use them when that is already the ledger, and keep Field Service as the onsite edge.

  • Project-only integration, or project plus service management.
  • Service-management integration requires Business Central Premium and cannot be enabled alone.
  • Requires Dataverse, Sales integration, and the Field Service Integration app.
  • Virtual-table item availability requires the same tenant.

When Field Service fits a 20 to 100 person company

Field Service fits when onsite work is a revenue line with repeatable visits: maintenance contracts, inspections, installs, and warranty repair. The trigger is operational, not a logo preference. If agreements, skills, and truck stock already exist on whiteboards or in a shared inbox, the work order, the schedule board, and the mobile app replace that stack.

It fits cleanly when customer records should stay on Dataverse next to Sales or Customer Service, or when Business Central will take the project or the service invoice. License math for a mixed crew is predictable from the tables above. Keep RSO, Copilot Credits, and Customer Service Enterprise for the phase where you have a measured need for each one.

Hold off when field work is a few jobs a month handled by office staff. Customer Service, a jobs list in Business Central, or a lighter suite such as Odoo will cover occasional site visits with less license surface. Hold off on RSO until a dispatcher can show travel or missed windows that the board cannot fix. Microsoft positions Contractor for third-party technicians. Confirm with Microsoft before you buy a full seat for every employee.

A practical decision rule: count people who dispatch, people who only run assigned jobs, and subcontractors. Price the full seats, the Contractor seats, and RSO only for resources you will optimize. Then ask whether service invoices must post to Business Central. If they must, Premium is in the ERP budget, separate from the Field Service user price.

  • Fits recurring onsite work: agreements, inspections, installs, warranty.
  • Fits when Sales, Customer Service, or Business Central should share the customer record.
  • Skip it when site visits are rare. Skip RSO until manual dispatch is the measured problem.
  • Price full seats, Contractor seats for subcontractors, and Premium only if Business Central must run service orders.

Dynamics 365 Field Service and the Odoo alternative

Flectic implements Dynamics 365 and Odoo, so the comparison starts from the work, the ledger, and the license surface. Dynamics 365 Field Service is the stronger fit when the crew already works in Microsoft 365, when you need agreements, a schedule board, RSO, incident templates, and the Business Central service path, and when you accept per-user pricing at the October 2026 lists.

Odoo is the stronger fit when you want field tasks, timesheets, CRM, and accounting on one subscription and your visits do not need the Field Service scheduling add-on or the Contractor license split. Choose it when the Microsoft license stack (Field Service, plus Customer Service, plus RSO, plus Premium) is larger than the operating problem.

Stay on an existing CRM or ITSM suite when that system already runs the customer record and the cost of moving outweighs dispatch features. For a greenfield service company, compare technician count, agreement volume, truck stock, and whether invoices post in Business Central before you pick a logo. Flectic scopes both platforms against that list.

  • Choose Field Service for Microsoft 365 crews that need agreements, dispatch depth, and a Business Central path.
  • Choose Odoo when a single subscription and simpler field tasks match the work.
  • Stay put when another CRM already owns the customer record and the service process.
  • Compare seats, agreements, truck stock, and the invoice destination before buying.

Tutoriel Dynamics 365 Field Service: first usable phase

This tutoriel Dynamics 365 Field Service is the sequence we use for a first usable phase. Flectic sets the timeline for that phase in the written scope, with a fixed price. It follows Microsoft’s own setup order: environment, licenses and roles, incident types, scheduling, mobile, inspections, and the invoice handoff. Scope it long enough for a service manager and a dispatcher to rehearse, and short enough to avoid turning on RSO, agents, and IoT in the same release.

Start with a Power Platform environment that has Dataverse and Enable Dynamics 365 apps. The 30-day trial installs Field Service for a pilot. After purchase, change the environment type to production. Assign each person an account, a full or Contractor license, environment access, and one security role. Predefined roles are Field Service - Resource, Dispatcher, Administrator, and Inventory Purchase, plus IoT - Administrator and IoT - Endpoint User. Resource sees assigned work orders only. The Dispatcher role runs the schedule board, and Inventory Purchase covers purchasing and returns of parts. Administrator configures the app.

Build a handful of work order incidents for the jobs you sell most. Create bookable resources with territories and characteristics. Schedule with the board and the schedule assistant. Put technicians on the mobile app, confirm whether your build is the refreshed experience, and set an offline profile only on the experience that supports offline. Publish one inspection on a service task type and test a photo under the 3 MB default. Close the loop by invoicing in Field Service or, when Business Central service orders are required, by completing the Premium integration: Dataverse, Sales integration, and the Field Service Integration app, same tenant if you need item availability.

Leave RSO, Copilot Credits, and Connected Field Service for a later phase unless a measured bottleneck is already on the table. FastTrack may be available for eligible new Dynamics 365 spend with a qualified Solutions Partner. The eligibility page does not publish the spend minimum, so confirm that with Microsoft before you plan around it.

  • Environment with Dataverse, then licenses, then security roles.
  • Incident types, resources, characteristics, board, and schedule assistant.
  • Mobile app, inspection template, 3 MB attachment default, offline profile only where the app build supports it.
  • Invoice in Field Service, or post through Business Central Premium when service-order sync is required.
  • Defer RSO, agents, and IoT until the first phase is in daily use.

How Flectic can help

Flectic implements Dynamics 365 for companies of 20 to 100 people in the US and Canada, including Field Service for teams that schedule technicians and bill site work. Flectic sends a written proposal with a fixed price for each phase before work starts. Read how Flectic implements Dynamics 365, then book a free discovery call to start.

Sources

  1. Dynamics 365 Field Service is Microsoft’s application for delivering onsite service at customer locations, combining workflow automation, scheduling, and a mobile app.

    learn.microsoft.comChecked high
  2. Four service delivery models: reactive break-fix, preventive agreement-based maintenance, predictive IoT-driven maintenance, and multistage project-based work. Many organizations combine them. Documented capabilities include work orders, scheduling and dispatch, communication tools, a mobile app, Copilot summaries and natural-language questions, asset management, preventive maintenance, inventory purchasing and returns, billing, time tracking, and analytics.

    learn.microsoft.comChecked high
  3. Named roles are customer service agents, service managers, dispatchers, field technicians, and inventory managers. Agents, managers, dispatchers, and inventory managers primarily use the browser. Technicians use the mobile app. Work orders can be created from cases, sales orders, emails, phone calls, service agreements, web portals, or IoT data, with tasks, parts, billable labor, and required characteristics. Dispatchers schedule on the schedule board, with the schedule assistant, or with Resource Scheduling Optimization. The board can schedule work orders, sales orders, projects, and custom tables.

    learn.microsoft.comChecked high
  4. French names for the four models: réactif (break-fix), préventif (basé sur un accord), prédictif (piloté par l’IoT), and basé sur des projets (multi-étapes), with features including ordres de travail, planification, application mobile, actifs, inventaire, and facturation.

    learn.microsoft.comChecked high
  5. Core tables include Work Order, Account (service account), Service Agreement, Customer Asset, Work Order Incident, Resource Requirement, Bookable Resource, Booking, Booking Timestamp, Booking Journal, Product Catalog, Inventory, and Purchasing. A work order incident is a template of recommended service tasks, products, services, and characteristics.

    learn.microsoft.comChecked high
  6. As of October 2026, US list prices paid yearly: Field Service $105 per user per month, Field Service Contractor $50 per user per month, Resource Scheduling Optimization $30 per resource per month. Microsoft assumes a single tenant for RSO. Checkout price can differ.

    microsoft.comChecked high
  7. As of October 2026, Canada list prices paid yearly, plus applicable tax: Field Service $142.50 CAD per user per month, Contractor $67.80 CAD, Resource Scheduling Optimization $40.70 CAD per resource per month. Displayed prices are informational and checkout can differ by currency, country, and region.

    microsoft.comChecked high
  8. Two licenses: standard with all core features, and Field Service Contractor as a subset for third-party technicians. 30-day trial with no admin privileges required to start. Guides and Remote Assist will no longer be available after December 31, 2026.

    learn.microsoft.comChecked high
  9. The pricing-page comparison text does not itemize which feature rows the Contractor license excludes. Microsoft describes Contractor as a subset for third-party technicians, and a footnote says some items apply in the mobile app for that plan. Copilot Credits are pay-as-you-go or prepaid commit, and prepaid commit units can save up to 20%. An Azure subscription is required to use agents.

    microsoft.comChecked high
  10. Every user needs a user account, a Field Service or Field Service Contractor license, environment access, and a security role. Contractors can be added as Microsoft Entra B2B collaboration users.

    learn.microsoft.comChecked high
  11. Predefined security roles: Field Service - Resource, Dispatcher, Administrator, and Inventory Purchase, plus IoT - Administrator and IoT - Endpoint User. The Resource role can view and update only work orders assigned to that worker.

    learn.microsoft.comChecked high
  12. The mobile app for iOS, Android, and Windows 10+ is included at no extra charge and is a customizable model-driven Power Platform app. Offline access requires an administrator-configured offline profile. The refreshed mobile experience does not currently support working offline.

    learn.microsoft.comChecked high
  13. Inspections are published templates attached to service task types, then added to work orders. On mobile, file attachments default to 3 MB per file unless an admin changes the limit, and only the latest response set is kept for a task.

    learn.microsoft.comChecked high
  14. Resource Scheduling Optimization is priced by the number of resources optimized and can run overnight, intraday (documented example: every 30 minutes), for one resource, as a simulation, or for emergency priority jobs.

    learn.microsoft.comChecked high
  15. Field Service installs on a Power Platform environment with a Dataverse database and Enable Dynamics 365 apps turned on. A free trial installs the app automatically. After purchase the environment type can be changed to production.

    learn.microsoft.comChecked high
  16. Business Central integrates for project management only, or for project and service management together. Service-management integration requires the Business Central Premium experience and cannot be enabled alone. Setup needs a Dataverse connection, Dynamics 365 Sales integration, and the Field Service Integration app. Item availability via virtual tables requires the same tenant.

    learn.microsoft.comChecked high
  17. As of October 2026, Customer Service US list prices paid yearly: Professional $50, Enterprise $105, Premium $195 per user per month. Contact Center $110 per user per month. Enterprise matches Field Service list price and is a separate product.

    microsoft.comChecked high
  18. As of October 2026, Customer Service Canada list prices paid yearly, plus applicable tax: Professional $67.80 CAD, Enterprise $142.50 CAD, Premium $264.60 CAD per user per month. Contact Center $149.20 CAD per user per month.

    microsoft.comChecked high
  19. Forrester Consulting Total Economic Impact study (December 2023) of a composite organization, as cited on the Field Service product page: 346% ROI, $42.65 million in benefits over three years, and payback in under six months. Scheduling Operations Agent is in preview. Custom agents are built in Copilot Studio.

    microsoft.comChecked high
  20. FastTrack for Dynamics 365 includes Field Service. Eligibility requires a minimum annual Dynamics 365 spend on a new deployment plus a qualified Solutions Partner. Microsoft does not publish the dollar minimum on the eligibility page.

    learn.microsoft.comChecked high
  21. Field inventory supports static and mobile truck-stock warehouses, adjustments, transfers, and consumption on work orders. Products must be the Inventory product type. Purchasing and returns are supported.

    learn.microsoft.comChecked high
  22. Work order summary must be admin-enabled, is generated per user, respects the security role, and appears in a side pane on the work order or booking.

    learn.microsoft.comChecked high

Frequently asked questions

What are the types de service in Dynamics 365 Field Service?

Microsoft documents four service delivery models, and many organizations combine them. In the French documentation they are réactif (break-fix), préventif (basé sur un accord), prédictif (piloté par l’IoT), and basé sur des projets (multi-étapes). English names are reactive, preventive agreement-based maintenance, predictive IoT-driven maintenance, and multistage project-based work. They share the same work-order app and the same Field Service license.

Quelles sont les fonctionnalités de Dynamics 365 Field Service?

The fonctionnalités Microsoft lists are work orders (ordres de travail), scheduling and dispatch, communication tools, a mobile app, Copilot summaries and natural-language questions, asset management, preventive maintenance, inventory purchasing and returns, billing, time tracking, and analytics. Dispatchers and managers use the browser. Technicians use the mobile app, which is included with the license. Resource Scheduling Optimization, Copilot Credits, and the Scheduling Operations Agent are separate from that core list.

What is a Microsoft Dynamics 365 Field Service overview?

It is Microsoft’s cloud application for onsite service at customer locations, combining workflow automation, scheduling, and a mobile app. Work can start from a case, sales order, email, phone call, agreement, portal, or IoT signal, and it is carried on a work order with tasks, parts, billable labor, and required skills. As of October 2026 the full license lists at $105 USD or $142.50 CAD per user per month, paid yearly, with the CAD amount plus applicable tax. The app runs on Power Platform with Dataverse.

What are the entités in Dynamics 365 Field Service?

Core records in the work-order architecture are Work Order, Account (service account), Service Agreement, Customer Asset, Work Order Incident, Resource Requirement, Bookable Resource, Booking, Booking Timestamp, Booking Journal, Product Catalog, Inventory, and Purchasing. A work order incident is a template of tasks, products, services, and characteristics. Bookable Resource is who can be scheduled, and Booking is the slot on the board.

Is Dynamics 365 Field Service the same product as Dynamics 365 Customer Service?

They are separate products. Customer Service covers cases and, with its own license, contact-center work. Field Service covers onsite work orders, scheduling, field inventory, and the technician app. As of October 2026, Customer Service Enterprise and Field Service both list at $105 USD or $142.50 CAD per user per month, paid yearly. A person who uses both apps needs a license for each one. Customer Service Professional lists at $50 USD or $67.80 CAD, Premium at $195 USD or $264.60 CAD, and Contact Center at $110 USD or $149.20 CAD.

How much does Dynamics 365 Field Service cost in the US and in Canada?

As of October 2026, paid yearly, the full license is $105 USD or $142.50 CAD per user per month. Field Service Contractor is $50 USD or $67.80 CAD per user per month. Resource Scheduling Optimization is $30 USD or $40.70 CAD per optimized resource per month. Canada prices are plus applicable tax, and Microsoft says the checkout price can differ by currency, country, and region. A 30-day trial is available, and Learn says you can start it without admin privileges.

What is the difference between the full Field Service license and Field Service Contractor?

The full license includes all core features and lists at $105 USD or $142.50 CAD per user per month, paid yearly, CAD plus applicable tax. Contractor lists at $50 USD or $67.80 CAD per user per month, paid yearly, CAD plus applicable tax, and Microsoft positions it as a subset of core features for third-party technicians. The Field Service pricing page comparison text does not itemize which rows Contractor drops, and a footnote on that pricing page says some items apply in the mobile app for that plan. The Resource role is a security limit on a license, not a cheaper SKU. Confirm with Microsoft before you buy a full seat for every employee. Contractors can be added as Microsoft Entra B2B users.

Does the Field Service mobile app work offline?

The mobile app for iOS, Android, and Windows 10 or later is included with the Field Service license. Offline access requires an administrator-configured offline profile. Microsoft says the refreshed mobile experience does not currently support working offline, so crews who lose signal need to test the build they will ship. Inspection file attachments default to 3 MB per file unless an admin changes the limit, and only the latest response set is kept for a task.

Is there a tutorial for the work-order lifecycle from creation to invoice?

Yes. Install Field Service on a Dataverse environment with Dynamics 365 apps enabled, assign a full or Contractor license and a security role, and create incident types for your common jobs. Dispatch on the schedule board or with the schedule assistant, update the booking in the mobile app, complete an inspection, then invoice in Field Service or post to Business Central. Service-order integration requires Business Central Premium and cannot be enabled on its own.

Do I need Business Central Premium to invoice field work from Field Service?

You can invoice from Field Service itself without Business Central. You need Business Central Premium when you turn on service-management integration so field work posts as Business Central service. That integration cannot be enabled alone. The other documented path is project management only. Either path needs a Dataverse connection, Dynamics 365 Sales integration, and the Field Service Integration app. Item availability through virtual tables also requires both apps in the same tenant.

More on the blog: Choosing an ERP or CRM