Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.
Cite this versionField-level log (52)
Up to 100 recent field edits are shown; older edits may be outside retention.
- 4 Nov 2026 · 13:26:53 UTC Last changed25 Sep 2026 22:37 UTC → 24 Sep 2026 22:58 UTC
- 4 Nov 2026 · 13:26:53 UTC Preview targetOctober CY2026 → Not stated
- 4 Nov 2026 · 13:26:53 UTC General availability targetFebruary CY2027 → Not stated
- 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
- 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
- 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
- 4 Nov 2026 · 13:26:53 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571672 → No longer listed in this observation
- 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
- 4 Nov 2026 · 13:26:53 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
- 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 4 Nov 2026 · 11:04:04 UTC Last changed24 Sep 2026 22:58 UTC → 25 Sep 2026 22:37 UTC
- 4 Nov 2026 · 11:04:04 UTC Preview targetNot stated → October CY2026
- 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → February CY2027
- 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
- 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
- 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
- 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571672
- 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…
- 4 Nov 2026 · 10:01:18 UTC Last changed25 Sep 2026 22:37 UTC → 24 Sep 2026 22:58 UTC
- 4 Nov 2026 · 10:01:18 UTC Preview targetOctober CY2026 → Not stated
- 4 Nov 2026 · 10:01:18 UTC General availability targetFebruary CY2027 → Not stated
- 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
- 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
- 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
- 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
- 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
- 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
- 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 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
- 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM571672
- 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 14 Oct 2026 · 11:22:42 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete