Field Service Mobile Copilot Moves Toward Questions About Past Work
Microsoft’s roadmap gives two examples of the intended interaction: “What is the work history of this asset?” and “Who worked on this job last?” Those are retrieval questions. A technician preparing for a visit could ask for relevant history without manually finding and opening each record, provided the eventual feature can access the records needed to answer.
The description also says organizations will be able to extend the experience with custom experiences and agents for frontline and back-office users. It does not specify how an administrator would build or enable those extensions, which Dataverse tables standard Q&A will cover, or whether chat answers will include links back to records. Those details will determine how useful the feature is in a deployment with customized Field Service data.
Roadmap item 571663 is marked In development. It lists Targeted Release, Worldwide (Standard Multi-Tenant), and Android, iOS, and Desktop as platforms, with general availability estimated for February 2027. Microsoft describes roadmap dates as estimates subject to change. Neither the platform list nor the release target is a deployment notice for a particular tenant.
Existing Field Service Mobile Copilot Skills Solve Different Tasks
Field Service technicians already have documented Copilot functions in the mobile app. Microsoft Learn describes a work-order summary that brings together context about a booking, and a separate AI-powered work-order-update preview that takes a technician’s description of completed work and recommends field changes for review. The planned chat adds an open-ended question-and-answer workflow to that picture; it should not be confused with either existing skill.
The update preview illustrates why the distinction matters. It recommends changes to a defined set of fields, including booking status and times, service-task completion, product quantities, and service durations. The technician confirms suggested updates before they are applied. Roadmap item 571663 describes answers to questions, but makes no equivalent promise that its chat will change records.
Microsoft Learn also documents how administrators enable the existing refreshed mobile experience: a user with Field Service–Administrator permissions opens the Field Service Mobile app module in a browser, goes to Settings > Mobile settings > Features, turns on New mobile experience, then saves and publishes the app. That experience can be assigned to everyone or limited to users with the Field Service – New Mobile Experience security role; its documented minimums are mobile app version 2408.2 and solution version 8.8.122.6. These are requirements for the refreshed experience, not confirmed prerequisites or enablement steps for the forthcoming chat.
Desktop and Offline Listings Need Feature-Specific Confirmation
The roadmap’s Desktop listing deserves a careful reading alongside Microsoft’s current mobile documentation. Microsoft Learn says the refreshed mobile experience is unavailable in the Windows app, which instead shows the classic Unified Interface. It also says users working offline fall back to that classic experience. Those statements describe the refreshed experience as documented today; they do not settle how roadmap item 571663 will behave on desktop or without a connection.
For teams that send technicians to sites with poor connectivity, this is a practical planning boundary. Microsoft documents offline data synchronization for the Field Service mobile app, but its current documentation says the new mobile experience does not support working offline. Until Microsoft publishes chat-specific requirements, administrators should avoid promising that a technician will be able to question Dataverse data through Copilot at an offline job site.
Access is another detail to verify at release. Microsoft’s documentation for the Field Service web app says its Copilot answers depend on data the signed-in user can access. That is useful context for reviewing technician permissions and record quality, but the web app’s roles, licensing, and configuration instructions are not established requirements for this separately planned mobile chat.
What This Means for Field Service Administrators
Keep current mobile Copilot decisions separate from the February 2027 chat plan. An organization can assess its existing summaries and update preview now, while treating conversational Q&A as a future capability whose rollout instructions have yet to be published.
- Keep roadmap item 571663 on the deployment watchlist; its February 2027 general-availability date is an estimate.
- Identify the asset-history and prior-job questions technicians actually need answered, and check whether the relevant records are maintained in Dataverse.
- Use the documented refreshed-experience settings only for capabilities available there today; they are not instructions for enabling the planned chat.
- Before a chat rollout, confirm supported app versions, platforms, permissions, licensing, regions, languages, and offline behavior in feature-specific documentation.
- Test answers against records that technicians can inspect once the feature becomes available, especially where a wrong account, asset, or work order would change the next service decision.
Copilot chat could make Field Service history easier to reach in the moment a technician needs it. The decision point for administrators is the eventual feature documentation and tenant rollout: that is when Microsoft can turn the roadmap’s examples into a supported mobile workflow.