Dynamics 365 Field Service — Pricing, Plans & What's Included

Dynamics 365 Field Service is a commercial Dynamics 365 application for onsite service operations, because it brings work orders, dispatching, scheduling, technician execution, service asset context, and mobile field updates into one service-management system. It is best suited for organizations that send technicians, crews, or contractors to customer locations or equipment sites.

Dynamics 365 Field Service includes capabilities for field service work order management, scheduling and dispatch, technician-facing mobile work, and service account, asset, and maintenance context. It is intended to help teams plan, assign, execute, and complete onsite service jobs in a connected Dynamics 365 environment.

Dynamics 365 Field Service licensing does not automatically include implementation, configuration, data migration, integrations, user training, third-party tools, hardware, carrier services, or non-Microsoft add-ons, because those are separate services or products. Other Dynamics 365 apps such as Sales, Customer Service, Finance, or Supply Chain Management are also not included unless separately licensed.

Dynamics 365 Field Service is the standard commercial Field Service license, while Dynamics 365 Field Service Attach is only for customers that already have a qualifying Dynamics 365 base offer. The Attach SKU should not be used unless eligibility is confirmed, because the qualifying base license is not included with the Attach purchase.

A commercial customer should consider Dynamics 365 Field Service Device only when the deployment involves device-based or shared-device scenarios that match Microsoft’s current use rights. Field Service Device is a separate SKU from the standard Field Service and Field Service Attach SKUs, so IT Partner should confirm the assignment model and access limits in the current Microsoft Product Terms before purchase.

No trial SKU is listed for Dynamics 365 Field Service in the commercial source offer set. If you need a proof of concept, IT Partner can help evaluate whether a limited paid pilot, existing tenant evaluation, or Microsoft-provided trial route is available for your scenario.

The commercial offer set includes one-month and one-year term options for Dynamics 365 Field Service, Field Service Attach, and Field Service Device. Three-year term options are listed for Dynamics 365 Field Service and Field Service Attach with available monthly, annual, or triennial billing depending on the selected SKU; no three-year Field Service Device option is listed in the provided source set.

You can generally add licenses during an active CSP subscription term, because added seats are commonly co-termed to the existing subscription. Reductions and cancellations are more restricted after the applicable cancellation window and are usually handled at renewal or within Microsoft’s permitted change period, so IT Partner should confirm the current CSP new commerce rules before you commit.

Cancellation flexibility depends on the subscription term and Microsoft CSP new commerce rules, because longer commitments normally trade flexibility for term stability. A one-month term is typically the most flexible option, while annual and multi-year terms usually limit cancellation or seat reduction after the allowed cancellation window; confirm the exact timing with IT Partner before ordering.

At renewal, the subscription can typically be continued, adjusted, or allowed to expire based on the CSP renewal settings and Microsoft’s current rules. Renewal is the best time to reduce seats, change term strategy, or reassess whether full Field Service, Attach, or Device licensing is still the right mix.

Yes, a properly coordinated CSP partner transfer can be completed without user downtime, because the customer tenant and Dynamics 365 environment remain in Microsoft’s cloud and are not migrated to a new tenant. IT Partner should align subscription replacement timing, license assignment, and renewal dates so users keep access during the transition.

Moving CSP management to IT Partner does not move your tenant data, because the data stays in your existing Microsoft tenant and Dynamics 365 environment. The Microsoft-published price for the same SKU and commitment is not changed by the administrative partner transfer, but your final quote can still reflect billing terms, taxes, promotions, or partner services, so confirm the order details before switching.

Dynamics 365 Field Service does not automatically include Microsoft Teams licensing, because Teams is licensed separately through Microsoft 365 or other eligible offers. If your field service process requires Teams collaboration, chat, meetings, or frontline communication, confirm that the users already have the required Teams rights.

Dynamics 365 Field Service may surface Microsoft AI or Copilot experiences depending on Microsoft availability, tenant configuration, region, and licensing rules, but the provided commercial SKU data does not list a separate Copilot entitlement. Treat Copilot as a capability to validate before purchase, because Microsoft can require specific licenses, admin enablement, data settings, or regional availability.

Dynamics 365 Field Service runs in the Dynamics 365 and Power Platform ecosystem, but the license does not automatically cover every possible Dataverse capacity, Power Platform extension, connector, storage, or integration requirement. IT Partner should review your work order volume, mobile usage, integrations, environments, and data-retention needs before finalizing the licensing design.

Dynamics 365 Field Service uses Microsoft cloud identity and application security controls such as Microsoft Entra ID access, role-based permissions, and Dynamics 365/Dataverse security concepts. Security should be designed around dispatcher, technician, manager, administrator, and integration roles, because overbroad access can expose customer, asset, schedule, and service history data unnecessarily.

Dynamics 365 Field Service is delivered through Microsoft’s cloud compliance framework for Dynamics 365 and Power Platform, but compliance suitability depends on your tenant region, data model, configurations, integrations, and industry obligations. Regulated commercial buyers should validate data residency, audit, retention, encryption, access control, and any sector-specific requirements with IT Partner and Microsoft’s current compliance documentation.

You should start by mapping service processes, work order types, assets, resources, territories, schedules, mobile requirements, and integrations, because licensing alone does not configure the system. Data migration, implementation, training, and integration work are not automatic license entitlements, so plan them as a separate project with IT Partner.

A government organization should not assume the commercial SKU is appropriate, because GCC and GCC High are separate government cloud offerings with different eligibility, compliance, residency, and operational boundaries. The source pack lists Government availability, but this FAQ is for commercial customers; government buyers should confirm whether Commercial, GCC, or GCC High is required before purchasing.

Nonprofit and education availability is listed in the source pack, but eligible organizations should not default to the commercial offer if charity or education licensing is available and appropriate. Nonprofits should confirm charity eligibility and any grant or discounted licensing context, while education customers should confirm whether faculty, staff, student, or shared-device use rights apply before ordering.