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 (65)
Up to 100 recent field edits are shown; older edits may be outside retention.
- 4 Nov 2026 · 15:02:25 UTC Last changed30 Sep 2026 23:31 UTC → 28 Oct 2026 23:04 UTC
- 4 Nov 2026 · 15:02:25 UTC Preview targetNot stated → December CY2026
- 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → December CY2026
- 4 Nov 2026 · 15:02:25 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
- 4 Nov 2026 · 15:02:25 UTC Source coverage: microsoft-365-roadmapCurrent
- 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items → No longer listed in this observation
- 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 4 Nov 2026 · 15:02:25 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573239
- 4 Nov 2026 · 15:02:25 UTC SummaryBusiness value → Business value Technicians do not always record booking completion at the moment work ends. They may update the booking later because of connectivity, customer-facing responsibilities, or end-of-day administration. When the later administrative action replaces the booking End Time, the recorded duration can extend beyond the work that was actually performed and affect downstream journals, time entries, labor costs, actuals, and work-order completion reporting. Field Service administrators can choose whether completion by the booked resource automatically changes the booking End Time. Organizations whose technicians complete bookings later can preserve the existing or explicitly supplied work end, helping booking duration and downstream time and cost records remain aligned with when the work occurred. Feature detail Use the organization-level Set End Time on booked resource completion setting in Field Service settings to control the automatic End Time update. With the setting set to Yes , which is the default, current behavior is preserved. When the booked resource completes a booking without supplying End Time, Field Service sets End Time to the completion time and recalculates Du…
- 4 Nov 2026 · 13:26:53 UTC Last changed28 Oct 2026 23:04 UTC → 30 Sep 2026 23:31 UTC
- 4 Nov 2026 · 13:26:53 UTC Preview targetDecember CY2026 → Not stated
- 4 Nov 2026 · 13:26:53 UTC General availability targetDecember CY2026 → 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=573239 → 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 Technicians do not always record booking completion at the moment work ends. They may update the booking later because of connectivity, customer-facing responsibilities, or end-of-day administration. When the later administrative action replaces the booking End Time, the recorded duration can extend beyond the work that was actually performed and affect downstream journals, time entries, labor costs, actuals, and work-order completion reporting. Field Service administrators can choose whether completion by the booked resource automatically changes the booking End Time. Organizations whose technicians complete bookings later can preserve the existing or explicitly supplied work end, helping booking duration and downstream time and cost records remain aligned with when the work occurred. Feature detail Use the organization-level Set End Time on booked resource completion setting in Field Service settings to control the automatic End Time update. With the setting set to Yes , which is the default, current behavior is preserved. When the booked resource completes a booking without supplying End Time, Field Service sets End Time to the completion time and recalculates Du… → Business value
- 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 4 Nov 2026 · 11:04:04 UTC Last changed30 Sep 2026 23:31 UTC → 28 Oct 2026 23:04 UTC
- 4 Nov 2026 · 11:04:04 UTC Preview targetNot stated → December CY2026
- 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → December CY2026
- 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=573239
- 4 Nov 2026 · 11:04:04 UTC SummaryBusiness value → Business value Technicians do not always record booking completion at the moment work ends. They may update the booking later because of connectivity, customer-facing responsibilities, or end-of-day administration. When the later administrative action replaces the booking End Time, the recorded duration can extend beyond the work that was actually performed and affect downstream journals, time entries, labor costs, actuals, and work-order completion reporting. Field Service administrators can choose whether completion by the booked resource automatically changes the booking End Time. Organizations whose technicians complete bookings later can preserve the existing or explicitly supplied work end, helping booking duration and downstream time and cost records remain aligned with when the work occurred. Feature detail Use the organization-level Set End Time on booked resource completion setting in Field Service settings to control the automatic End Time update. With the setting set to Yes , which is the default, current behavior is preserved. When the booked resource completes a booking without supplying End Time, Field Service sets End Time to the completion time and recalculates Du…
- 4 Nov 2026 · 10:01:18 UTC Last changed28 Oct 2026 23:04 UTC → 30 Sep 2026 23:31 UTC
- 4 Nov 2026 · 10:01:18 UTC Preview targetDecember CY2026 → Not stated
- 4 Nov 2026 · 10:01:18 UTC General availability targetDecember CY2026 → 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=573239 → 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 Technicians do not always record booking completion at the moment work ends. They may update the booking later because of connectivity, customer-facing responsibilities, or end-of-day administration. When the later administrative action replaces the booking End Time, the recorded duration can extend beyond the work that was actually performed and affect downstream journals, time entries, labor costs, actuals, and work-order completion reporting. Field Service administrators can choose whether completion by the booked resource automatically changes the booking End Time. Organizations whose technicians complete bookings later can preserve the existing or explicitly supplied work end, helping booking duration and downstream time and cost records remain aligned with when the work occurred. Feature detail Use the organization-level Set End Time on booked resource completion setting in Field Service settings to control the automatic End Time update. With the setting set to Yes , which is the default, current behavior is preserved. When the booked resource completes a booking without supplying End Time, Field Service sets End Time to the completion time and recalculates Du… → 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
- 29 Oct 2026 · 00:08:33 UTC Last changed30 Sep 2026 23:31 UTC → 28 Oct 2026 23:04 UTC
- 29 Oct 2026 · 00:08:33 UTC Release phasesGeneral Availability → General Availability, Preview
- 29 Oct 2026 · 00:08:33 UTC Preview targetOctober CY2026 → December CY2026
- 29 Oct 2026 · 00:08:33 UTC General availability targetFebruary CY2027 → December CY2026
- 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=573239 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=573239
- 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/RM573239
- 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