Written with AI assistance.
What is Dynamics 365 Field Service?
Dynamics 365 Field Service supports the planning and follow-up of work at customer locations. Work orders connect assignments, sites, equipment and resource requirements.
Dispatchers can consider availability and skills when assigning work. Technicians can record completed work and supporting documentation in the mobile workspace, depending on the organisation's configuration.
The solution is relevant when service, maintenance, inspections or installations require coordination of people and equipment. Before implementation, describe the workflow, responsibilities and documentation requirements.
The original demonstration transcript is available in the Norwegian version of this FAQ.
Ask a question or share what helped you.
Field Service | Questions and answers
Because status changes in the mobile app are used to calculate working hours, travel time, and the basis for invoicing. Entering them afterwards involves guesswork.
Field Service | Questions and answers
Field Service | Questions and answers
What can technicians do in the mobile app without network coverage?
Field Service | Questions and answers
Why should technicians record time and parts on the work order?
Field Service | Questions and answers
Field Service | Questions and answers
An agreement that automatically generates work orders according to a schedule, with agreed content and pricing.
The Field Service app has an offline mode, so work can continue in basements, tunnels, and mountainous areas. Here’s what works—and what requires a little planning.
Because it forms the basis for invoicing, inventory management, and profitability per job. Entering data after the fact is always inaccurate.
The work order is the central record in Field Service. It describes what needs to be done and where, and forms the basis for both planning and invoicing.
When a breakdown costs significantly more than a planned inspection, and when equipment failures are predictable. Not all equipment meets both criteria.
Microsoft replaced twice-yearly release waves with continuous roadmap publication. Customer processes needed to track status from development through rollout to launch.
Sales and Service Agent became generally available in Microsoft 365 Copilot. Dynamics described MCP actions across sales, service, field work and projects.
Service Agent became generally available across Dynamics 365 and Microsoft 365. Workforce Engagement Management connected demand, staffing and quality work.
Gartner found nearly five hours saved per seller each week, but many organisations did not reinvest the time. Dynamics wave 1 described connections across customer insight, sales, service and field work.
Microsoft published April news for manufacturing, Power Platform, Planner and Power BI. Together, the releases show how automation and analytics can support field work when project accountability, data quality and human control are clear.
Share a question or reflection.
Be the first to contribute.