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: Support multiple warehouse assignments for field technicians

Field technicians often source parts from more than one warehouse. Limiting a technician to a single warehouse can make it harder to reflect how materials are actually sourced across field operations. With this capability, administrators can assign multiple warehouses to a Bookable Resource and designate a preferred/default warehouse for the applicable legal entity. When a technician records material consumption, the warehouse can be automatically populated based on the Work Order legal entity and the technician’s configured default warehouse for that legal entity, while still allowing the technician to select another applicable warehouse when needed. This reduces manual selection for technicians, helps ensure materials are recorded against the correct warehouse and legal entity, and gives organizations more flexibility to reflect how inventory is actually managed across field operations. This capability is supported in the Integrated deployment type with Project Operations, where Field Service works with Finance and Supply Chain Management through Dual-write.

What it said

Roadmap ID
570858
Status
In development
General availability target
November CY2026
Preview target
Not stated
Products
Dynamics 365 Field Service
Clouds
Worldwide (Standard Multi-Tenant)
Release phases
General Availability
Platforms
Web
Added to the roadmap
24 Sep 2026 22:58 UTC
Last changed
25 Sep 2026 22:37 UTC

Source evidence when recorded

Microsoft 365 roadmap
IncompleteRead 5 Nov 2026 at 15:56 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 (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 Last changed24 Sep 2026 22:58 UTC → 25 Sep 2026 22:37 UTC
  3. 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → November 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=570858
  9. 4 Nov 2026 · 15:02:25 UTC SummaryField technicians often source parts from more than one warehouse. Limiting a technician to a single warehouse can make it harder to reflect how materials are actually sourced across field operations. → Field technicians often source parts from more than one warehouse. Limiting a technician to a single warehouse can make it harder to reflect how materials are actually sourced across field operations. With this capability, administrators can assign multiple warehouses to a Bookable Resource and designate a preferred/default warehouse for the applicable legal entity. When a technician records material consumption, the warehouse can be automatically populated based on the Work Order legal entity and the technician’s configured default warehouse for that legal entity, while still allowing the technician to select another applicable warehouse when needed. This reduces manual selection for technicians, helps ensure materials are recorded against the correct warehouse and legal entity, and gives organizations more flexibility to reflect how inventory is actually managed across field operations. This capability is supported in the Integrated deployment type with Project Operations, where Field Service works with Finance and Supply Chain Management through Dual-write.
  10. 4 Nov 2026 · 13:26:53 UTC Last changed25 Sep 2026 22:37 UTC → 24 Sep 2026 22:58 UTC
  11. 4 Nov 2026 · 13:26:53 UTC General availability targetNovember CY2026 → 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=570858 → 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 SummaryField technicians often source parts from more than one warehouse. Limiting a technician to a single warehouse can make it harder to reflect how materials are actually sourced across field operations. With this capability, administrators can assign multiple warehouses to a Bookable Resource and designate a preferred/default warehouse for the applicable legal entity. When a technician records material consumption, the warehouse can be automatically populated based on the Work Order legal entity and the technician’s configured default warehouse for that legal entity, while still allowing the technician to select another applicable warehouse when needed. This reduces manual selection for technicians, helps ensure materials are recorded against the correct warehouse and legal entity, and gives organizations more flexibility to reflect how inventory is actually managed across field operations. This capability is supported in the Integrated deployment type with Project Operations, where Field Service works with Finance and Supply Chain Management through Dual-write. → Field technicians often source parts from more than one warehouse. Limiting a technician to a single warehouse can make it harder to reflect how materials are actually sourced across field operations.
  18. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  19. 4 Nov 2026 · 11:04:04 UTC Last changed24 Sep 2026 22:58 UTC → 25 Sep 2026 22:37 UTC
  20. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → November CY2026
  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=570858
  26. 4 Nov 2026 · 11:04:04 UTC SummaryField technicians often source parts from more than one warehouse. Limiting a technician to a single warehouse can make it harder to reflect how materials are actually sourced across field operations. → Field technicians often source parts from more than one warehouse. Limiting a technician to a single warehouse can make it harder to reflect how materials are actually sourced across field operations. With this capability, administrators can assign multiple warehouses to a Bookable Resource and designate a preferred/default warehouse for the applicable legal entity. When a technician records material consumption, the warehouse can be automatically populated based on the Work Order legal entity and the technician’s configured default warehouse for that legal entity, while still allowing the technician to select another applicable warehouse when needed. This reduces manual selection for technicians, helps ensure materials are recorded against the correct warehouse and legal entity, and gives organizations more flexibility to reflect how inventory is actually managed across field operations. This capability is supported in the Integrated deployment type with Project Operations, where Field Service works with Finance and Supply Chain Management through Dual-write.
  27. 4 Nov 2026 · 10:01:18 UTC Last changed25 Sep 2026 22:37 UTC → 24 Sep 2026 22:58 UTC
  28. 4 Nov 2026 · 10:01:18 UTC General availability targetNovember CY2026 → 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=570858 → 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 SummaryField technicians often source parts from more than one warehouse. Limiting a technician to a single warehouse can make it harder to reflect how materials are actually sourced across field operations. With this capability, administrators can assign multiple warehouses to a Bookable Resource and designate a preferred/default warehouse for the applicable legal entity. When a technician records material consumption, the warehouse can be automatically populated based on the Work Order legal entity and the technician’s configured default warehouse for that legal entity, while still allowing the technician to select another applicable warehouse when needed. This reduces manual selection for technicians, helps ensure materials are recorded against the correct warehouse and legal entity, and gives organizations more flexibility to reflect how inventory is actually managed across field operations. This capability is supported in the Integrated deployment type with Project Operations, where Field Service works with Finance and Supply Chain Management through Dual-write. → Field technicians often source parts from more than one warehouse. Limiting a technician to a single warehouse can make it harder to reflect how materials are actually sourced across field operations.
  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=570858 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=570858
  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/RM570858
  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.