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 22 Oct 2026 at 17:41 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 it said

Roadmap ID
573239
Status
In development
General availability target
February CY2027
Preview target
October CY2026
Products
Dynamics 365 Field Service
Clouds
Worldwide (Standard Multi-Tenant)
Release phases
General Availability
Platforms
Android, Desktop, iOS, Web
Added to the roadmap
30 Sep 2026 23:31 UTC
Last changed
30 Sep 2026 23:31 UTC

Source evidence when recorded

Microsoft 365 roadmap
IncompleteRead 22 Oct 2026 at 17:32 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 (10)

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

  1. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  2. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  3. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  4. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  5. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  6. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  7. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  8. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  9. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  10. 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 08:58 UTC · 274 of 275 readable · 252 fully read · 18 waiting for GitHub's hourly limit · documentation 469/469 current