Field Service and Field Service Contractor licences

What it does

Field Service is sold as two named-user licences: the full Dynamics 365 Field Service licence, and Dynamics 365 Field Service Contractor, which carries a subset of the same features and is aimed at third-party technicians. Both are ordinary Microsoft 365 subscriptions assigned per user, and neither one on its own gives anybody access to anything.

Key facts

Learn names exactly two SKUs — Dynamics 365 Field Service and Dynamics 365 Field Service Contractor — and describes Contractor only as "a subset of the core features and capabilities for third-party technicians". The actual feature split lives in the Dynamics 365 Licensing Guide PDF, not on Learn.
Buying is done in the Microsoft 365 admin center under Billing > Licenses, searching for Dynamics 365 Field Service. Nothing about the purchase forces you to pick the right split up front, so people over-buy full licences routinely.
A licence is one of three things a user needs. The other two are membership of the environment (directly or via a security group) and at least one security role. Miss either and the user gets an access error that looks like a licensing fault but isn't.
Predefined roles are Field Service - Administrator, Field Service - Dispatcher, Field Service - Resource, Field Service - Inventory Purchase, plus IoT - Administrator and IoT - Endpoint User. None of them are licence-aware — assigning Field Service - Dispatcher to an unlicensed user changes nothing about entitlement.
Frontline workers each need a Field Service licence. The Quick Set Up: Frontline Workers form on the Get started page creates the bookable resources and sets characteristics, territories, time zone, security roles, field security profiles and mobile offline profile in one pass.
Bookable resources of type Account or Contact represent people outside your organisation with no system access. They cost no licence, but they also can't sign in, so they can't use the Field Service mobile app or update their own bookings.
Universal Resource Scheduling comes with Field Service automatically — schedule board, requirements, bookings, schedule assistant. Resource Scheduling Optimization does not; that's a separately priced add-on.
Evaluation is a 30-day trial that needs no admin rights, on its own tenant and URL. It is not a path to production.
Guides and Remote Assist stop being available after 31 December 2026, which matters if a deal was scoped around a mixed-reality bundle sitting alongside Field Service.

When to use / skip

Everybody doing delivery work in Field Service — dispatchers, service managers, technicians who touch work orders on the mobile app — needs a Field Service licence of some flavour. The real question is who gets full versus Contractor, and who needs no Dynamics licence at all.

Contractor is worth pursuing when a meaningful share of your workforce is genuinely third-party: subcontracted engineers who receive bookings, do the work, complete tasks and go away again, without touching agreements, inventory, purchase orders or the schedule board. If the "contractors" are actually badged staff on a different payroll, or if they raise their own work orders and manage stock on a van, you'll end up buying full licences anyway and the exercise wasted a month.

Skip the licence question entirely for people who only look. Read access to Field Service data does not require a Dynamics 365 licence, so a service manager who lives in a Power BI report, or a back-office user who reads work order status in a Power Apps canvas app, is not a Field Service user.

Configuration decisions

Which personas are Contractor and which are full — and get the feature boundary in writing from Microsoft or your LSP before you commit, because Learn will not tell you.
Whether subcontracted labour is modelled as licensed users or as Contact/Account bookable resources. That choice decides whether they get the mobile app at all, and it's expensive to reverse once bookings exist.
Whether environment access is controlled by a Microsoft Entra security group or by adding users individually. Groups are the only sane option once you're over a few dozen technicians.
Whether you use the predefined Field Service roles as-is or copy them. Copies are safer for upgrades but you inherit maintenance of the privilege set.
How licence assignment is driven day to day: manual in the admin center, group-based licensing, or a joiner-mover-leaver process. Field workforces churn.

Gotchas

Contractor's feature subset isn't documented publicly. Assume nothing about inventory, agreements, purchase orders or RSO being included, and treat any assumption you can't source as a commercial risk on the deal.
Removing a licence in the admin center leaves the Dataverse user record, its security roles and its bookable resource in place. The user simply stops being able to write. Nothing tells the dispatcher, and the resource keeps showing on the schedule board.
Users can hold a Field Service licence and still be blocked, because the security role is missing or they were never added to the environment. Check all three before raising anything with Microsoft.
Contact and Account resources look free and flexible, right up to the point somebody asks why the subcontractor can't see their jobs on a phone. Non-user resources have no sign-in.
Trials expire after 30 days, extend once, and die after 14 days of inactivity with no reactivation. Any configuration built there and not exported is gone.

Consultant notes

Do the licence-count exercise against personas, not headcount. Dispatchers, schedulers, inventory owners and service managers are all full licences; the population you can genuinely move to Contractor is usually smaller than the client hopes.
Tell the client plainly that Microsoft publishes the entitlement structure on Learn and the detail in a PDF that changes with each licensing guide release. Point them at the guide rather than repeating figures from a slide deck.
Demo the access failure. Show a licensed user with no security role hitting the same error as an unlicensed one — it kills a whole class of support tickets later.
Before go-live, reconcile assigned licences against active bookable resources. The gap in both directions is always interesting: unlicensed resources on the board, and licensed leavers still costing money.

Worth another look when the licensing guide is refreshed, or if Microsoft ever documents the Contractor feature subset on Learn.