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 16 Nov 2026 at 01:23 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: Generate maintenance work orders within a configurable lead window

Business value Organizations can turn upcoming maintenance requirements into executable Field Service work without requiring planners to monitor every asset and create each work order manually. Generating work at a controlled point before it is due gives dispatchers time to secure technicians, skills, parts, and customer access while avoiding an unnecessarily large backlog of work created too far in advance. This connects long-range maintenance planning with day-to-day service execution and helps ensure that a valid maintenance requirement becomes actionable at the right time. Feature detail Configure a lead window that determines how far in advance an upcoming maintenance event should create a work order. When a scheduled or predicted event enters that window, generate the corresponding Field Service work order for the customer asset. Carry the relevant maintenance context into the generated work, including the maintenance activity and the information required to prepare and schedule service. Depending on the configured maintenance definition, this can include tasks, products, services, required skills, and expected duration. Work-order generation can operate from maintenance due…

What it said

Roadmap ID
571666
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, Preview
Platforms
Desktop, 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 16 Nov 2026 at 00:16 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 (60)

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

  1. 16 Nov 2026 · 01:23:36 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  2. 5 Nov 2026 · 18:04:05 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  3. 5 Nov 2026 · 17:01:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  4. 4 Nov 2026 · 15:02:25 UTC Preview targetNot stated → October CY2026
  5. 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → February CY2027
  6. 4 Nov 2026 · 15:02:25 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  7. 4 Nov 2026 · 15:02:25 UTC Source coverage: microsoft-365-roadmapCurrent
  8. 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
  9. 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  10. 4 Nov 2026 · 15:02:25 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571666
  11. 4 Nov 2026 · 15:02:25 UTC SummaryBusiness value → Business value Organizations can turn upcoming maintenance requirements into executable Field Service work without requiring planners to monitor every asset and create each work order manually. Generating work at a controlled point before it is due gives dispatchers time to secure technicians, skills, parts, and customer access while avoiding an unnecessarily large backlog of work created too far in advance. This connects long-range maintenance planning with day-to-day service execution and helps ensure that a valid maintenance requirement becomes actionable at the right time. Feature detail Configure a lead window that determines how far in advance an upcoming maintenance event should create a work order. When a scheduled or predicted event enters that window, generate the corresponding Field Service work order for the customer asset. Carry the relevant maintenance context into the generated work, including the maintenance activity and the information required to prepare and schedule service. Depending on the configured maintenance definition, this can include tasks, products, services, required skills, and expected duration. Work-order generation can operate from maintenance due…
  12. 4 Nov 2026 · 13:26:53 UTC Preview targetOctober CY2026 → Not stated
  13. 4 Nov 2026 · 13:26:53 UTC General availability targetFebruary CY2027 → Not stated
  14. 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  15. 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
  16. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  17. 4 Nov 2026 · 13:26:53 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571666 → No longer listed in this observation
  18. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
  19. 4 Nov 2026 · 13:26:53 UTC SummaryBusiness value Organizations can turn upcoming maintenance requirements into executable Field Service work without requiring planners to monitor every asset and create each work order manually. Generating work at a controlled point before it is due gives dispatchers time to secure technicians, skills, parts, and customer access while avoiding an unnecessarily large backlog of work created too far in advance. This connects long-range maintenance planning with day-to-day service execution and helps ensure that a valid maintenance requirement becomes actionable at the right time. Feature detail Configure a lead window that determines how far in advance an upcoming maintenance event should create a work order. When a scheduled or predicted event enters that window, generate the corresponding Field Service work order for the customer asset. Carry the relevant maintenance context into the generated work, including the maintenance activity and the information required to prepare and schedule service. Depending on the configured maintenance definition, this can include tasks, products, services, required skills, and expected duration. Work-order generation can operate from maintenance due… → Business value
  20. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  21. 4 Nov 2026 · 11:04:04 UTC Preview targetNot stated → October CY2026
  22. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → February CY2027
  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=571666
  28. 4 Nov 2026 · 11:04:04 UTC SummaryBusiness value → Business value Organizations can turn upcoming maintenance requirements into executable Field Service work without requiring planners to monitor every asset and create each work order manually. Generating work at a controlled point before it is due gives dispatchers time to secure technicians, skills, parts, and customer access while avoiding an unnecessarily large backlog of work created too far in advance. This connects long-range maintenance planning with day-to-day service execution and helps ensure that a valid maintenance requirement becomes actionable at the right time. Feature detail Configure a lead window that determines how far in advance an upcoming maintenance event should create a work order. When a scheduled or predicted event enters that window, generate the corresponding Field Service work order for the customer asset. Carry the relevant maintenance context into the generated work, including the maintenance activity and the information required to prepare and schedule service. Depending on the configured maintenance definition, this can include tasks, products, services, required skills, and expected duration. Work-order generation can operate from maintenance due…
  29. 4 Nov 2026 · 10:01:18 UTC Preview targetOctober CY2026 → Not stated
  30. 4 Nov 2026 · 10:01:18 UTC General availability targetFebruary CY2027 → Not stated
  31. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  32. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  33. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  34. 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571666 → No longer listed in this observation
  35. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
  36. 4 Nov 2026 · 10:01:18 UTC SummaryBusiness value Organizations can turn upcoming maintenance requirements into executable Field Service work without requiring planners to monitor every asset and create each work order manually. Generating work at a controlled point before it is due gives dispatchers time to secure technicians, skills, parts, and customer access while avoiding an unnecessarily large backlog of work created too far in advance. This connects long-range maintenance planning with day-to-day service execution and helps ensure that a valid maintenance requirement becomes actionable at the right time. Feature detail Configure a lead window that determines how far in advance an upcoming maintenance event should create a work order. When a scheduled or predicted event enters that window, generate the corresponding Field Service work order for the customer asset. Carry the relevant maintenance context into the generated work, including the maintenance activity and the information required to prepare and schedule service. Depending on the configured maintenance definition, this can include tasks, products, services, required skills, and expected duration. Work-order generation can operate from maintenance due… → Business value
  37. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  38. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  39. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  40. 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=571666 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=571666
  41. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  42. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  43. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM571666
  44. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  45. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  46. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  47. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  48. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  49. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  50. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  51. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  52. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  53. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  54. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  55. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  56. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  57. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  58. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  59. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  60. 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