ChangeIntel IT change radar
Public mode

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

Some sources, documents or advisories need attention: 274/275 feeds/APIs · 469/469 docs · 7/9 advisories · checked 20:03 UTC Customize Public modeDiscuss ChangeIntel on Discord

Recorded 5 Nov 2026 at 17:01 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.

Microsoft 365 roadmapMicrosoft 365 roadmap

Dynamics 365 Field Service: Plan asset maintenance using time, actual usage, and service sequences

Business value Organizations can maintain assets according to how the equipment ages, how much it is actually used, and which service activities have already been completed. A flexible maintenance schedule helps avoid servicing lightly used equipment too often while reducing the risk that heavily used equipment operates beyond its required maintenance interval. Usage-based schedules connect maintenance directly to meter readings recorded for the individual asset. This allows work to be driven by actual operating hours, mileage, cycles, production counts, or another tracked measure rather than by an estimated calendar interval alone. Combining scheduling methods in one plan supports more consistent execution of manufacturer guidance, internal reliability standards, and contractual maintenance commitments. Feature detail Define maintenance activities against the actual usage of an asset by specifying recurring service intervals on its meter. For example, require an oil change after every 150 operating hours or an inspection after every configured number of miles, cycles, or units produced. As new readings are recorded, the asset's accumulated usage determines when the next maintenan…

What changed

  1. Preview target: Not stated → October CY2026 · Availability target: Not stated → February CY2027
  2. Preview target: October CY2026 → Not stated · Availability target: February CY2027 → Not stated
  3. Preview target: Not stated → October CY2026 · Availability target: Not stated → February CY2027
  4. Preview target: October CY2026 → Not stated · Availability target: February CY2027 → Not stated
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 (58)

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

  1. 5 Nov 2026 · 17:01:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  2. 4 Nov 2026 · 15:02:25 UTC Preview targetNot stated → October CY2026
  3. 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → February CY2027
  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=571665
  9. 4 Nov 2026 · 15:02:25 UTC SummaryBusiness value → Business value Organizations can maintain assets according to how the equipment ages, how much it is actually used, and which service activities have already been completed. A flexible maintenance schedule helps avoid servicing lightly used equipment too often while reducing the risk that heavily used equipment operates beyond its required maintenance interval. Usage-based schedules connect maintenance directly to meter readings recorded for the individual asset. This allows work to be driven by actual operating hours, mileage, cycles, production counts, or another tracked measure rather than by an estimated calendar interval alone. Combining scheduling methods in one plan supports more consistent execution of manufacturer guidance, internal reliability standards, and contractual maintenance commitments. Feature detail Define maintenance activities against the actual usage of an asset by specifying recurring service intervals on its meter. For example, require an oil change after every 150 operating hours or an inspection after every configured number of miles, cycles, or units produced. As new readings are recorded, the asset's accumulated usage determines when the next maintenan…
  10. 4 Nov 2026 · 13:26:53 UTC Preview targetOctober CY2026 → Not stated
  11. 4 Nov 2026 · 13:26:53 UTC General availability targetFebruary CY2027 → Not stated
  12. 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  13. 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
  14. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  15. 4 Nov 2026 · 13:26:53 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571665 → No longer listed in this observation
  16. 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
  17. 4 Nov 2026 · 13:26:53 UTC SummaryBusiness value Organizations can maintain assets according to how the equipment ages, how much it is actually used, and which service activities have already been completed. A flexible maintenance schedule helps avoid servicing lightly used equipment too often while reducing the risk that heavily used equipment operates beyond its required maintenance interval. Usage-based schedules connect maintenance directly to meter readings recorded for the individual asset. This allows work to be driven by actual operating hours, mileage, cycles, production counts, or another tracked measure rather than by an estimated calendar interval alone. Combining scheduling methods in one plan supports more consistent execution of manufacturer guidance, internal reliability standards, and contractual maintenance commitments. Feature detail Define maintenance activities against the actual usage of an asset by specifying recurring service intervals on its meter. For example, require an oil change after every 150 operating hours or an inspection after every configured number of miles, cycles, or units produced. As new readings are recorded, the asset's accumulated usage determines when the next maintenan… → Business value
  18. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  19. 4 Nov 2026 · 11:04:04 UTC Preview targetNot stated → October CY2026
  20. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → February CY2027
  21. 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  22. 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
  23. 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
  24. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  25. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571665
  26. 4 Nov 2026 · 11:04:04 UTC SummaryBusiness value → Business value Organizations can maintain assets according to how the equipment ages, how much it is actually used, and which service activities have already been completed. A flexible maintenance schedule helps avoid servicing lightly used equipment too often while reducing the risk that heavily used equipment operates beyond its required maintenance interval. Usage-based schedules connect maintenance directly to meter readings recorded for the individual asset. This allows work to be driven by actual operating hours, mileage, cycles, production counts, or another tracked measure rather than by an estimated calendar interval alone. Combining scheduling methods in one plan supports more consistent execution of manufacturer guidance, internal reliability standards, and contractual maintenance commitments. Feature detail Define maintenance activities against the actual usage of an asset by specifying recurring service intervals on its meter. For example, require an oil change after every 150 operating hours or an inspection after every configured number of miles, cycles, or units produced. As new readings are recorded, the asset's accumulated usage determines when the next maintenan…
  27. 4 Nov 2026 · 10:01:18 UTC Preview targetOctober CY2026 → Not stated
  28. 4 Nov 2026 · 10:01:18 UTC General availability targetFebruary CY2027 → Not stated
  29. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  30. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  31. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  32. 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571665 → No longer listed in this observation
  33. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
  34. 4 Nov 2026 · 10:01:18 UTC SummaryBusiness value Organizations can maintain assets according to how the equipment ages, how much it is actually used, and which service activities have already been completed. A flexible maintenance schedule helps avoid servicing lightly used equipment too often while reducing the risk that heavily used equipment operates beyond its required maintenance interval. Usage-based schedules connect maintenance directly to meter readings recorded for the individual asset. This allows work to be driven by actual operating hours, mileage, cycles, production counts, or another tracked measure rather than by an estimated calendar interval alone. Combining scheduling methods in one plan supports more consistent execution of manufacturer guidance, internal reliability standards, and contractual maintenance commitments. Feature detail Define maintenance activities against the actual usage of an asset by specifying recurring service intervals on its meter. For example, require an oil change after every 150 operating hours or an inspection after every configured number of miles, cycles, or units produced. As new readings are recorded, the asset's accumulated usage determines when the next maintenan… → Business value
  35. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  36. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  37. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  38. 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=571665 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=571665
  39. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  40. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  41. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM571665
  42. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  43. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  44. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  45. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  46. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  47. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  48. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  49. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  50. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  51. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  52. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  53. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  54. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  55. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  56. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  57. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  58. 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 11 Nov 20:03 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current

No accounts or analytics; your preferences stay in your browser. Information, not advice. ChangeIntel is an independent tool and is not affiliated with or endorsed by Microsoft, Apple, Google, Broadcom (VMware), Jamf, Oracle, Mozilla, or any other vendor it covers. Product names are trademarks of their owners. Built by Evotec.