Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 274/275 feeds/APIs · 469/469 docs · 7/9 advisories · checked 20:03 UTC Customize Public modeDiscuss ChangeIntel on Discord

Recorded 4 Nov 2026 at 13:10 UTC. This is what ChangeIntel recorded, including the title, summary, facts and links. It is not a statement of the source's current position. See the latest record.

Dynamics 365 Field Service: Expand your service offering through subcontractors without the onboarding overhead

Business value Subcontractors commonly communicate completion through an emailed service report or a message describing the work performed. Dispatchers then have to find the correct assignment, interpret the report, update the booking and work order, and copy important closeout details into Field Service. This manual process delays operational visibility, creates inconsistent service history, and can leave completed bookings or work orders open. Service teams can setup an agent to process subcontractor service reports to prepare a coordinated booking and work-order closeout. This supports faster reconciliation of external work and helps keep scheduling status, operational records, and service history consistent. Feature detail An agent in Dynamics 365 Field Service processes supported emails and service reports, identifies the applicable Field Service work order and active booking, and prepares a coordinated closeout proposal. The proposal can include supported booking and work-order status changes together with completion details extracted from the submission, such as the completion summary, work performed, notes, recommendations, requirements, requested follow-up, actual complet…

What it said

Roadmap ID
571672
Status
In development
General availability target
February CY2027
Preview target
October CY2026
Products
Dynamics 365 Field Service
Clouds
Worldwide (Standard Multi-Tenant)
Release phases
Preview
Platforms
Desktop, Web
Added to the roadmap
24 Sep 2026 22:58 UTC
Last changed
25 Sep 2026 22:37 UTC

Source evidence when recorded

Microsoft 365 roadmap
IncompleteRead 4 Nov 2026 at 12:05 UTC

Coverage describes the sources at this observation. A complete read then does not establish their current position.

Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (43)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  2. 4 Nov 2026 · 11:04:04 UTC Last changed24 Sep 2026 22:58 UTC → 25 Sep 2026 22:37 UTC
  3. 4 Nov 2026 · 11:04:04 UTC Preview targetNot stated → October CY2026
  4. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → February CY2027
  5. 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  6. 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
  7. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items → No longer listed in this observation
  8. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  9. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571672
  10. 4 Nov 2026 · 11:04:04 UTC SummaryBusiness value → Business value Subcontractors commonly communicate completion through an emailed service report or a message describing the work performed. Dispatchers then have to find the correct assignment, interpret the report, update the booking and work order, and copy important closeout details into Field Service. This manual process delays operational visibility, creates inconsistent service history, and can leave completed bookings or work orders open. Service teams can setup an agent to process subcontractor service reports to prepare a coordinated booking and work-order closeout. This supports faster reconciliation of external work and helps keep scheduling status, operational records, and service history consistent. Feature detail An agent in Dynamics 365 Field Service processes supported emails and service reports, identifies the applicable Field Service work order and active booking, and prepares a coordinated closeout proposal. The proposal can include supported booking and work-order status changes together with completion details extracted from the submission, such as the completion summary, work performed, notes, recommendations, requirements, requested follow-up, actual complet…
  11. 4 Nov 2026 · 10:01:18 UTC Last changed25 Sep 2026 22:37 UTC → 24 Sep 2026 22:58 UTC
  12. 4 Nov 2026 · 10:01:18 UTC Preview targetOctober CY2026 → Not stated
  13. 4 Nov 2026 · 10:01:18 UTC General availability targetFebruary CY2027 → Not stated
  14. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  15. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  16. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  17. 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571672 → No longer listed in this observation
  18. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
  19. 4 Nov 2026 · 10:01:18 UTC SummaryBusiness value Subcontractors commonly communicate completion through an emailed service report or a message describing the work performed. Dispatchers then have to find the correct assignment, interpret the report, update the booking and work order, and copy important closeout details into Field Service. This manual process delays operational visibility, creates inconsistent service history, and can leave completed bookings or work orders open. Service teams can setup an agent to process subcontractor service reports to prepare a coordinated booking and work-order closeout. This supports faster reconciliation of external work and helps keep scheduling status, operational records, and service history consistent. Feature detail An agent in Dynamics 365 Field Service processes supported emails and service reports, identifies the applicable Field Service work order and active booking, and prepares a coordinated closeout proposal. The proposal can include supported booking and work-order status changes together with completion details extracted from the submission, such as the completion summary, work performed, notes, recommendations, requirements, requested follow-up, actual complet… → Business value
  20. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  21. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  22. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  23. 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=571672 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=571672
  24. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  25. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  26. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM571672
  27. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  28. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  29. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  30. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  31. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  32. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  33. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  34. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  35. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  36. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  37. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  38. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  39. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  40. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  41. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  42. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  43. 14 Oct 2026 · 11:22:42 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 11 Nov 20:03 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current