Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users by admins, makers, or analysts | 
Mar 9, 2026 |
May 29, 2026 |
Business value
Service managers, dispatchers, and back‑office teams regularly analyze schedules, work orders, assets, and service history to make operational decisions. By bringing Microsoft 365 Copilot directly into the Field Service web experience, users can ask natural‑language questions about their Dataverse data, quickly navigate records, and access organizational knowledge without switching tools.
This capability reduces time spent searching across systems, improves decision quality during planning and scheduling, and provides a governed entry point for AI across Field Service operations. It also allows organizations to standardize how AI is introduced, leveraging Microsoft 365 Copilot and custom agents within existing security and compliance boundaries.
Feature details
Microsoft 365 Copilot is available within Field Service model‑driven web apps, bringing conversational AI directly into the back‑office experience. When you open the Microsoft 365 chat from the Copilot pane, you can ask questions in natural language about Dataverse data, including work orders, assets, accounts, bookings, and service history. Copilot understands your application context and can navigate you to relevant records and views.
Out of the box, the Dataverse Q&A capability allows schedulers and service managers to ask questions like “Which work orders are at risk today?” or “Show assets with repeated failures this quarter,” with responses grounded in organizational data. In addition, organizations can bring their own Microsoft 365 agents, including agents built with Copilot Studio, and make them available within the same chat pane. This enables custom scenarios such as policy guidance, operational playbooks, KPI explanations, or domain‑specific service logic without building custom UI.
This feature is web‑only and intended for back‑office users working in Field Service model‑driven apps. It's enabled by an admin through existing Power Apps configuration and follows standard Microsoft 365 Copilot governance. No Field Service–specific customization is required; administrators and makers can use published Power Apps documentation to enable and customize the experience.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.