Public mode

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

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Recorded 4 Nov 2026 at 15:02 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: Preserve actual booking End Time when completion is recorded later

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…

What changed

  1. Preview target: Not stated → December CY2026 · Availability target: Not stated → December CY2026
  2. Preview target: December CY2026 → Not stated · Availability target: December CY2026 → Not stated
  3. Preview target: Not stated → December CY2026 · Availability target: Not stated → December CY2026
  4. Preview target: December CY2026 → Not stated · Availability target: December CY2026 → Not stated
  5. Release phases: General Availability → General Availability, Preview · Preview target: October CY2026 → December CY2026 · Availability target: February CY2027 → December CY2026
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 (65)

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

  1. 4 Nov 2026 · 15:02:25 UTC Last changed30 Sep 2026 23:31 UTC → 28 Oct 2026 23:04 UTC
  2. 4 Nov 2026 · 15:02:25 UTC Preview targetNot stated → December CY2026
  3. 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → December CY2026
  4. 4 Nov 2026 · 15:02:25 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  5. 4 Nov 2026 · 15:02:25 UTC Source coverage: microsoft-365-roadmapCurrent
  6. 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
  7. 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  8. 4 Nov 2026 · 15:02:25 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573239
  9. 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…
  10. 4 Nov 2026 · 13:26:53 UTC Last changed28 Oct 2026 23:04 UTC → 30 Sep 2026 23:31 UTC
  11. 4 Nov 2026 · 13:26:53 UTC Preview targetDecember CY2026 → Not stated
  12. 4 Nov 2026 · 13:26:53 UTC General availability targetDecember CY2026 → Not stated
  13. 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  14. 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
  15. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  16. 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
  17. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
  18. 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
  19. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  20. 4 Nov 2026 · 11:04:04 UTC Last changed30 Sep 2026 23:31 UTC → 28 Oct 2026 23:04 UTC
  21. 4 Nov 2026 · 11:04:04 UTC Preview targetNot stated → December CY2026
  22. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → December CY2026
  23. 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  24. 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
  25. 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
  26. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  27. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=573239
  28. 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…
  29. 4 Nov 2026 · 10:01:18 UTC Last changed28 Oct 2026 23:04 UTC → 30 Sep 2026 23:31 UTC
  30. 4 Nov 2026 · 10:01:18 UTC Preview targetDecember CY2026 → Not stated
  31. 4 Nov 2026 · 10:01:18 UTC General availability targetDecember CY2026 → Not stated
  32. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  33. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  34. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  35. 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
  36. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
  37. 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
  38. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  39. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  40. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  41. 29 Oct 2026 · 00:08:33 UTC Last changed30 Sep 2026 23:31 UTC → 28 Oct 2026 23:04 UTC
  42. 29 Oct 2026 · 00:08:33 UTC Release phasesGeneral Availability → General Availability, Preview
  43. 29 Oct 2026 · 00:08:33 UTC Preview targetOctober CY2026 → December CY2026
  44. 29 Oct 2026 · 00:08:33 UTC General availability targetFebruary CY2027 → December CY2026
  45. 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
  46. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  47. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  48. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM573239
  49. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  50. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  51. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  52. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  53. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  54. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  55. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  56. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  57. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  58. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  59. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  60. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  61. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  62. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  63. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  64. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  65. 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 16 Nov 11:47 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current