★ First page of Microsoft's 100,000-partner directory, sorted by responsiveness✓ Microsoft Solutions Partner — Security, Modern Work, Infrastructure, App Innovation, Data & AI · Support Services designation● Microsoft partner since 2006◆ 1,100+ organizations under management
Home/Services/Business Applications and Automation/Dynamics 365 Field Service Implementation
Implementation

Dynamics 365 Field Service Implementation

Dynamics 365 Field Service Implementation is a 5-week, $4,950 fixed-price engagement that stands up Field Service in one Dataverse environment of one tenant (standard scope: up to 500 users) and hands it over working: work order types and incident types, bookable resources with skills and territories, the dispatcher schedule board with map view and schedule assistant, the Field Service mobile app for a pilot group of technicians, customer assets and agreements with recurring preventive-maintenance bookings, inventory basics (warehouses, truck stock, products used), and Resource Scheduling Optimization only where you have licensed the add-in. Licensing prerequisites are stated before kickoff; Microsoft license and metered charges (Field Service and Contractor licenses, the Resource Scheduling Optimization add-in, Dataverse capacity) are yours, not part of the fee.

Timeline 5 weeksService owner Roman SotnikDynamics 365DataversePower Apps

What this engagement is

Dynamics 365 Field Service is Microsoft's application for organizations that send people to customer sites: a work order lifecycle, a dispatcher schedule board, a technician mobile app, customer assets and service agreements, and inventory for parts carried on trucks. It runs on Dataverse in a Power Platform environment, so what you configure in the first five weeks is also the foundation every later customization, report and integration builds on. Getting that foundation right is the whole point of this engagement. We configure, we do not code. The scope is the standard Field Service feature set set up for your business: work order types, incident types with service tasks and the products and services they consume, priorities, substatuses and territories; bookable resources (employees, contractors, crews and equipment) with characteristics, proficiency ratings, roles, work hours and home locations; the schedule board with the tabs, filters, booking statuses and map view your dispatchers need, and the schedule assistant that proposes qualified, available resources with travel time; the Field Service mobile app with an offline profile, tested on your technicians' devices; customer assets and functional locations at service locations, and agreements that generate recurring work orders and bookings for preventive maintenance; and inventory basics (warehouses including truck stock, inventory journals, products used and returned on work orders). Resource Scheduling Optimization is the automated optimizer that schedules many bookings at once against goals such as travel time and utilization. It is a separately licensed add-in, priced by the number of resources optimized, and at the time of writing is limited to one active instance per tenant. We deploy and configure it only where you hold the license; otherwise the schedule board and schedule assistant remain the dispatcher's tools and the optimizer can be added later without rework. Licensing is stated before kickoff, not discovered during it. Dispatchers, service managers, administrators and employed technicians need a Dynamics 365 Field Service license; third-party technicians who only need a subset of the capabilities can use the Field Service Contractor license. We confirm the list against Microsoft's current licensing guide and your existing bundles so you do not repurchase what you already own. Microsoft licenses and metered charges stay yours. The engagement closes with a pilot on real work orders, training for dispatchers and technicians, an administrator handover and documentation of every setting we changed. Data migration of historical work orders, ERP or accounting integration, Connected Field Service (IoT), custom development and organization-wide rollout waves are excluded here and quoted separately, and we say so at the scoping call rather than at week four.

Success criteria

01A dispatcher can create a work order from an incident type, see the service tasks, products and services it carries, and book it to a qualified, available resource from the schedule board or the schedule assistant.
02Bookable resources carry the agreed skills, proficiency ratings, roles, work hours, territories and home locations, and the schedule board map view shows them against the day's bookings.
03A pilot group of technicians completes the work order lifecycle on the Field Service mobile app, including offline capture of service tasks, products used, notes and customer signature, and the data syncs to Dataverse.
04Customer assets and functional locations are recorded for the service locations in scope, and at least one agreement generates recurring work orders and bookings on the approved schedule.
05Warehouses, truck stock and inventory journals are configured so products used on a work order decrement the correct inventory.
06Where licensed, Resource Scheduling Optimization is deployed, scoped and has completed scheduled runs against the agreed goal.
07Your administrators receive documentation of every configured setting, security role assignment and mobile offline profile, and have completed the handover session.

What you receive

✓Scoping call and written confirmation of fit with the standard scope (one tenant, one environment, up to 500 users), the pilot technician group and the five-week plan.
✓Licensing prerequisite map: who needs the Dynamics 365 Field Service license, who qualifies for the Field Service Contractor license, whether Resource Scheduling Optimization is in scope, and the Dataverse capacity check; licenses themselves remain your purchase.
✓Environment foundation: Field Service installed in the agreed Dataverse environment, Field Service settings, business units and security roles (administrator, dispatcher, resource) assigned to your users, and map settings configured for geocoding and travel time.
✓Work order configuration: work order types, incident types with service tasks, products and services, priorities, substatuses, service territories, service and billing accounts, product catalog and price lists loaded from the templates we provide.
✓Resource configuration: bookable resources for employees, contractors, crews and equipment, characteristics and proficiency ratings, resource roles, work hour calendars, organizational units and home locations.
✓Schedule board configuration: board tabs per dispatcher or territory, filters, booking statuses with colors, map view, schedule assistant defaults and travel time behavior.
✓Field Service mobile app: app module reviewed for your work order process, offline profile defined and tested, push notifications verified, and installation guidance for iOS, Android and Windows devices.
✓Assets and agreements: customer assets and functional locations loaded for the service locations in scope, agreement templates with booking setups for recurring preventive maintenance, and invoice setups enabled or disabled as you decide.
✓Inventory basics: warehouses including per-technician truck stock, inventory journals for transfers and adjustments, and products used and returned on work orders.
✓Resource Scheduling Optimization, where licensed: add-in deployed from the Power Platform admin center, optimization scope and goal defined, schedules configured and the first runs reviewed with dispatchers.
✓Pilot on live work orders with the pilot technician group, tuning of booking statuses, incident types and offline profile against real use.
✓Training: one dispatcher and service manager session, one technician mobile session and one administrator handover, each with a recording if you want one.
✓Configuration documentation and a closeout report against the success criteria.

How the work unfolds

1. Discovery and licensing

Scoping call with your service manager and lead dispatcher: work order flow, resource types, territories, assets under agreement, parts handling and devices. We issue the licensing prerequisite map and the reference-data templates (accounts, products and price lists, resources and skills, territories, assets, agreements).

2. Environment foundation

Install Field Service in the agreed Dataverse environment, configure Field Service settings, business units, security roles and map settings; verify Dataverse capacity and that the licensed users can sign in with the right roles.

3. Work orders and resources

Configure work order types, incident types with service tasks, products and services, priorities, substatuses, territories and accounts; load the product catalog and price lists; create bookable resources with skills, proficiency ratings, roles, work hours and home locations.

4. Schedule board and mobile

Build the schedule board tabs, filters, booking statuses and map view; set schedule assistant and travel time defaults; review the mobile app module, define and test the offline profile on the pilot group's devices; deploy and scope Resource Scheduling Optimization where licensed.

5. Assets, agreements and inventory

Load customer assets and functional locations, build agreement templates with booking setups and decide on invoice setups; configure warehouses, truck stock, inventory journals and products used and returned.

6. Pilot

Run the pilot technician group on live work orders for at least one week of real dispatch; tune incident types, booking statuses, offline profile and board filters against what dispatchers and technicians actually do.

7. Training and handover

Deliver the dispatcher, technician and administrator sessions, hand over configuration documentation and the closeout report, and remove our access unless you ask us to stay.

Prerequisites

→A Microsoft 365 tenant with a Power Platform environment (or capacity to create one) in which Dynamics 365 Field Service can be installed; one environment is in scope.
→Dynamics 365 Field Service licenses for dispatchers, service managers, administrators and employed technicians, and Field Service Contractor licenses for third-party technicians where you use them, assigned before phase 2. Resource Scheduling Optimization is required only if the optimizer is in scope. We can supply the licenses through our direct CSP relationship or advise on your agreement; license costs are not part of the service fee.
→Administrative access to your tenant through granular, time-bound GDAP that you approve (never standing global admin), plus a Field Service administrator role in the environment in scope.
→Reference data returned in our templates: accounts and service locations, products and price lists, resources with skills and work hours, territories, customer assets and the agreements you want generated automatically.
→A named decision-maker (usually the service manager) available for a weekly review, a lead dispatcher for board design, and a pilot group of technicians with iOS, Android or Windows devices for the mobile phase.
→Agreement on what the work order lifecycle looks like today, including any paper or spreadsheet process the app replaces.

Who does what

IT Partner

  • Run discovery, issue the licensing prerequisite map and the reference-data templates.
  • Install and configure Field Service in the one environment in scope as listed under deliverables.
  • Load the reference data you return in our templates and validate it in the app.
  • Deploy and scope Resource Scheduling Optimization where you have licensed it.
  • Run the pilot, deliver the three training sessions and the administrator handover, and provide configuration documentation and the closeout report.

Your team

  • Purchase and assign the Field Service, Contractor and (where in scope) Resource Scheduling Optimization licenses and hold the Dataverse capacity the environment needs.
  • Return reference data in the templates by the agreed dates and make process decisions at the weekly review.
  • Provide the pilot technicians, their devices and time for the mobile pilot and training sessions.
  • Approve the schedule board design, incident types and agreement templates before the pilot.
  • Own the environment, its backups and administration after handover.

What's not included

✕Microsoft license and metered charges: Dynamics 365 Field Service and Field Service Contractor licenses, the Resource Scheduling Optimization add-in, Dataverse storage and capacity add-ons, and any Azure resources are billed by Microsoft, not by IT Partner.
✕Migration of historical work orders, bookings, invoices or time entries from a previous system; quoted separately once we see the export.
✕Integration with Dynamics 365 Business Central, other ERP or accounting systems, or third-party dispatch and telematics tools; our Dynamics 365 Business Central integration development service covers that case separately.
✕Connected Field Service (IoT Hub or IoT Central alerts creating work orders), Dynamics 365 Remote Assist and Guides rollouts, and Dynamics 365 Customer Service case management.
✕Custom development: plug-ins, custom Power Apps component framework controls, Power Automate flows beyond the standard Field Service flows, custom Power BI reports and Power Pages customer or contractor portals.
✕Device procurement, enrollment and app protection policies; our Intune setup services cover enrollment and app protection separately.
✕Additional environments (for example a separate development and test pipeline), additional tenants, and organization-wide training waves beyond the three sessions included.
✕Ongoing administration after handover; available on an hourly basis or through a managed arrangement.

Limitations & technical notes

!Standard scope: one tenant, one Dataverse environment and up to 500 users. Larger estates, more environments or more than the pilot technician group on mobile are quoted in writing after the scoping call.
!Resource Scheduling Optimization is configured only where you hold the add-in license. At the time of writing Microsoft licenses it per optimized resource and allows one active instance per tenant; we verify this against Microsoft's current licensing guide at kickoff rather than assume it from this page.
!Licensing facts on this page (Field Service and Contractor licenses, Guides and Remote Assist inclusion) reflect Microsoft's documentation at the time of writing; Microsoft updates its licensing guide monthly and the prerequisite map we issue at kickoff is the binding version.
!The mobile phase covers one pilot group on the Field Service mobile app with one offline profile. Further technician waves reuse that configuration and are scheduled as follow-on work.
!Map view, geocoding and travel time depend on the map provider Microsoft enables for Field Service and on addresses in your data being geocodable; we flag records that fail geocoding rather than fix the source data.
!The 5-week duration assumes reference data arrives in our templates on time, licenses are assigned before phase 2 and the pilot group is available; delays on those move the timeline, not the price.

Frequently asked questions

What exactly does the implementation configure?

One Dynamics 365 Field Service deployment in one Dataverse environment of one tenant: work order types, incident types with service tasks, priorities and substatuses; bookable resources with skills, proficiency ratings, roles, work hours and territories; the schedule board with map view, filters, booking statuses and the schedule assistant; the Field Service mobile app with an offline profile for a pilot group of technicians; customer assets, functional locations and agreements with recurring booking setups; and inventory basics (warehouses, truck stock, inventory journals, products used on work orders). Resource Scheduling Optimization is configured only where you hold the add-in license.

Which licenses do we need before you start?

A Dynamics 365 Field Service license for each dispatcher, service manager, administrator and employed technician who will use the app, and a Dynamics 365 Field Service Contractor license for third-party technicians who only need a subset of the capabilities. Resource Scheduling Optimization is a separate paid add-in licensed by the number of resources whose schedules are optimized. At the time of writing, Microsoft also includes Dynamics 365 Guides and Remote Assist with the Field Service license. We confirm the exact list against Microsoft's current licensing guide at kickoff; the licenses are purchased by you, through our CSP relationship or your existing agreement.

Is Resource Scheduling Optimization included?

Only where you have licensed it. Resource Scheduling Optimization is an add-in to Field Service, priced per optimized resource and limited to one active instance per tenant at the time of writing. If you hold it, we deploy it from the Power Platform admin center, define the optimization scope and goal, and schedule the first runs. If you do not, the schedule board and schedule assistant still give dispatchers skill-, territory- and travel-aware booking, and you can add the optimizer later without rework.

What does the price cover and what would make it higher?

$4,950 fixed covers the standard scope: one tenant, one Dataverse environment and up to 500 users, with the configuration listed on this page and no custom code. Larger estates, several environments, custom plug-ins or integrations are quoted in writing after the scoping call. Microsoft license and metered charges are yours: Field Service and Contractor licenses, the Resource Scheduling Optimization add-in and any Dataverse capacity beyond your entitlement.

How long does it take?

The planned duration is 5 weeks: discovery and environment foundation in week one, work orders and resources in week two, schedule board and mobile in week three, assets, agreements and inventory in week four, pilot, training and handover in week five. The plan assumes your reference data arrives in the templates we provide and a decision-maker is available for weekly reviews.

Do technicians need a special device or an MDM?

The Field Service mobile app runs on the Power Apps mobile app for iOS and Android, and on Windows. Any current smartphone or tablet works; a device management policy is not required for the app to function. If you want app protection or enrollment, our Intune setup services cover it separately and we sequence them before the technician pilot.

Can you migrate our existing work order history?

Not inside this fixed scope. We load your reference data (accounts, products, price lists, resources, territories, assets and agreements) from the templates we provide. Historical work orders, bookings and invoices from a previous system are a data migration quoted separately once we see the export, because volume and data quality drive the effort.

Does this connect to our ERP or accounting system?

No. Field Service generates work order products, services and (optionally) invoice records inside Dataverse, and we show you where they live. Pushing them into Dynamics 365 Business Central, another ERP or an accounting package is an integration project; our Dynamics 365 Business Central integration development service covers the Business Central case and other targets are quoted.

What about Connected Field Service, IoT alerts and Copilot?

Connected Field Service (IoT alerts creating work orders) is excluded because it depends on Azure IoT resources and device integration outside this scope. Copilot features inside Field Service follow Microsoft's availability and your licensing; where a feature is enabled for your region and license we show your dispatchers how to use it, but we do not promise specific Copilot capabilities on this page because they change.

Do you train our dispatchers and technicians?

Yes, within the engagement: one dispatcher and service manager session on the schedule board, work order lifecycle and agreements, one technician session on the mobile app using the pilot group's own work orders, and an administrator handover on settings, security roles and mobile offline profiles. Organization-wide rollout training beyond those sessions is quoted separately.

Who holds admin access while you work?

You do. We request granular, time-bound GDAP access that you approve, never standing global admin, plus a Field Service administrator role in the one environment in scope. Access is removed at handover unless you ask us to keep supporting the environment.

What happens after go-live?

You own everything we configured; it lives in your tenant and there is no lock-in. Customers who license through IT Partner receive break-fix support during business hours at no extra charge. Changes to the configuration after handover, new territories, further technician waves or the optimizer rollout are quoted or handled on an hourly basis.

Didn’t find your question?

Ask it here. A real engineer answers by email within one business day — and if it’s a good one, it becomes part of this page so the next person finds it.

Answered by a person, one time, to your inbox. Nothing you type here is published without a human reviewing and anonymizing it first.

Related services

$4,950 per project
5 weeks
Book a Field Service scoping call