A brief, honest history of Field Service and why it still matters to your project
Picture a service desk not so long ago. A customer rings, someone writes the job on a carbon-copy sheet, and a dispatcher looks at a wall planner and works out from memory who might be free. The engineer gets the job by phone, by radio or by a fax to the depot, and the invoice goes out days later, provided the sheet survives the van.
Dynamics 365 Field Service was built to replace that world, and many organisations have moved on. The product’s history still matters, though, for a practical reason: the system you run, or the advice you follow, may have been shaped by an earlier version of it.
From FieldOne Sky to a first-party app
The product didn’t start at Microsoft. FieldOne built FieldOne Sky, with work orders, a schedule board, dispatcher and agent roles, and a mobile app on Resco’s Woodford framework that worked offline and synced when it found a signal. It ran as a solution inside Dynamics CRM, and it captured field work as data rather than handwriting.
Microsoft acquired FieldOne in July 2015; FieldOne Sky became today’s Dynamics 365 Field Service. Microsoft rebuilt it as a first-party application, with Dataverse underneath and the Power Platform around it. The work order, the schedule board and the offline-first mobile app all trace back to that original design, while much of the rest has been rebuilt and reworked several times since.
What has come and gone
Today’s product would surprise those early users. Copilot in Dynamics 365 Field Service summarises work orders, inspections give technicians structured checklists, and the Scheduling Operations Agent, still in preview, suggests optimised schedules for dispatchers to review. The mobile app is now a model-driven app on the Power Platform, included in the Field Service licence.
Features leave, too. The legacy Field Service Mobile app, configured through Woodford, was retired in June 2022, and its Woodford solutions are deprecated. The Field Service add-in for Outlook, the Field Service app for Teams, and the Viva Connections and Planner integrations lost support after October 2025. Dynamics 365 Guides and Remote Assist, the mixed reality tools once promoted alongside Field Service, reach end of support at the end of 2026.
Why the history matters to your project
Three things tend to follow a system through the years. The first is old advice: blog posts, forum answers and internal wikis written for a version of the product that no longer exists, some recommending features Microsoft has since retired. The second is customisation built before the platform caught up, such as a home-made inspection table, a hand-rolled job summary or a mobile layout designed for the old app. The third is the bill, because each of those is something you pay to maintain, test and carry through every update, often for a job the product now covers as standard.
The fix is a regular, unglamorous audit. List every customisation, plug-in, flow and integration, note when and why it was built, and check it against Microsoft’s current documentation and its Field Service deprecations page. Decide whether to keep each one, replace it with the standard feature or retire it, and treat any advice older than your current release as a lead to check rather than an answer. If you’re starting fresh, the lesson is simpler: begin on the current release and build only what the product genuinely can’t do.
How Proximo 3 helps
We’ve watched this product grow up. Our team has worked on this stack since Microsoft Dynamics CRM 3.0, and in field service since before Microsoft had a field service product. That history is practical rather than nostalgic, because it tells us which design decisions age well.
We build every new implementation on the current release, so you start without a legacy design to carry. We track what Microsoft is adding and retiring and design with it in mind, so you aren’t paying to build something the platform is about to make redundant. Our co-founder Mark Christie wrote the book on Dynamics 365 Field Service (Apress), and it’s out in November.