Dynamics 365 Field Service is licensed across three user-type SKUs in 2026: full users at $105/user/month list (Base, first user of the application), Attach users at $20/user/month list (second-and-subsequent users whose primary D365 app is something else), and Contractor users at $50/user/month list (limited to specific Field Service capabilities for external technicians). Team Member access is available at $8/user/month for read-mostly visibility. The IoT alert and connected-asset entitlement is bundled with Field Service Base — it is not a separate SKU but a feature within the per-user licence. The biggest commercial fact for Field Service buyers in 2026: most enterprises deploying Field Service also run D365 Customer Service for case management, making the Attach pricing structure ($20 vs $105 = 5x) the single largest licence-cost lever. Customer Service Base + Field Service Attach is materially cheaper than Field Service Base for every user whose primary day-to-day surface is case management.
Field Service user-type SKUs in 2026
Dynamics 365 Field Service follows the D365 Base / Attach / Team Member model with a Field-Service-specific Contractor SKU. Pricing in 2026:
| User type | 2026 list price | Functional scope | When to use |
|---|---|---|---|
| Field Service (Base) | ~$105/user/month | Full Field Service + IoT + Connected Field Service | Users whose primary application is Field Service (dispatchers, schedulers) |
| Field Service (Attach) | ~$20/user/month | Same functional scope as Base | Users whose Base is Customer Service / Sales / SCM |
| Field Service Contractor | ~$50/user/month | Limited Field Service for external technicians | Third-party contractors performing field work on your behalf |
| Team Members | ~$8/user/month | Read-mostly; limited write to ~10 entities | Internal headcount needing visibility |
The Base vs Attach decision is the largest cost lever for the typical Field Service deployment. Service-organisation populations are typically structured as dispatchers (whose primary app is Field Service — Base), case-management agents (whose primary app is Customer Service, with Field Service as the secondary view — Attach), and technicians (Base or Contractor depending on employment status). Customers who default everyone to Base routinely overpay by 50–70% on the case-management agent portion of the population.
Field Service Contractor: scoped for external technicians
The Field Service Contractor SKU is specifically designed for external technicians who perform work on the customer’s behalf but are not internal employees. Contractor licensing at $50/user/month is materially cheaper than the $105 Base, but is functionally bounded: Contractors cannot create work orders, cannot modify scheduling configurations, cannot access certain customer-record entities, and are scoped to their assigned work-order surface.
The procurement implication: customers running mixed internal/external technician fleets should explicitly classify each user as employee or contractor and license accordingly. The audit trap is the inverse — customers using Contractor licences for internal employees to capture the lower price. Microsoft Verification will surface the employment classification mismatch through HR-system reconciliation, with recovery economics that compound across the audit lookback.
IoT and Connected Field Service: bundled, not separate
One of the meaningful 2024-2026 simplifications: IoT alerts, connected-asset telemetry, and the broader Connected Field Service surface are bundled into the Field Service Base licence at no incremental cost. Customers who deployed Field Service before this consolidation may carry a separate ‘Connected Field Service’ SKU that is no longer required — renewal is the moment to remove it.
The IoT entitlement scope: device telemetry ingestion, alert routing, automated work-order creation from telemetry, and the Azure IoT Hub backplane required to support the integration. The Azure IoT Hub consumption itself is separate Azure consumption and applies to MACC commit — the entitlement under Field Service covers the licence, not the underlying Azure consumption.
Resource Scheduling Optimization add-on
Resource Scheduling Optimization (RSO) is a Field Service add-on at ~$170/scheduler/month that drives AI-based scheduling across the technician fleet — route optimisation, skill-match, SLA-aware dispatch. RSO is per-scheduler, not per-technician, so for a 40-technician operation with 2 dispatchers, the RSO cost is 2 × $170 = $340/month, not 40 × anything.
The decision: RSO is materially valuable for technician fleets >25 technicians per scheduler where manual scheduling is operationally infeasible. For smaller operations or simpler topologies, the RSO premium often does not deliver proportional savings — the buyer-side analysis should compute the dispatch-hour saving and the SLA-improvement value against the RSO cost before defaulting in.
EA negotiation levers for Dynamics 365 Field Service
- Base-vs-Attach audit at user level. Audit every Field Service user against the user’s primary D365 application. Case-management agents using Field Service as a secondary surface should be on Attach not Base.
- Contractor-vs-Base classification. External technicians should be on Contractor licensing at $50; internal technicians belong on Base at $105. Audit the classification against HR records before renewal.
- Connected Field Service legacy SKU removal. Customers with pre-2024 Connected Field Service add-ons should remove them at renewal — the entitlement is now bundled into Field Service Base.
- RSO right-sizing. RSO is per-scheduler not per-technician. Customers who priced RSO across the full technician fleet are quoting against the wrong unit.
- Team Member operational-access audit. Field Service Team Member assignments performing work-order creation, dispatch, or technician operations create audit exposure. Reclassify to the correct entitlement before Microsoft surfaces it.
- IoT-Hub MACC inclusion. The Azure IoT Hub consumption underlying Connected Field Service applies to MACC commit — capture in MACC sizing rather than letting it land outside.
Anonymised case study: $540K Field Service renewal reduction
A 1,400-technician HVAC service enterprise carried 1,400 Field Service Base licences ($176K/month), 180 Contractor licences ($9K/month), 64 dispatcher seats on Field Service Base ($8K/month), 11 RSO licences priced across schedulers, and a residual Connected Field Service add-on for 800 technicians ($16K/month). We audited. Base-vs-Attach: 220 service-coordinator seats with Customer Service primary surface re-classified to Attach — $224K annualised reduction. Contractor classification: 280 technicians correctly on Contractor licensing were over-classified to Base — correction back to Contractor saved $185K annualised. Connected Field Service add-on removal: legacy add-on terminated at renewal — $192K annualised reduction. RSO right-sizing: 11 RSO licences scoped to 8 actual dispatcher seats — $6K annualised reduction. Combined annualised renewal reduction: $540K against the LSP proposal. The customer also captured $115K Azure consumption headroom into MACC commit through the IoT Hub re-allocation but that landed in the Azure renewal not the D365 line item.
D365 Field Service licensing is one of the most operationally complex D365 deployments — the mix of employee and contractor technicians, dispatcher overhead, and IoT bundling creates multiple overpayment paths if not audited explicitly. Pair the Field Service audit with the D365 Commerce and D365 Marketing analyses, the broader 2026 EA tier-collapse landscape, and the license-optimization advisory that drives the user-level rebuild.