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 · 6/9 advisories · checked 20:03 UTC Customize Public modeDiscuss ChangeIntel on Discord

Recorded 23 Oct 2026 at 08:31 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: 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 23 Oct 2026 at 08:14 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 (12)

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

  1. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  2. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  3. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  4. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  5. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  6. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  7. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  8. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  9. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  10. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  11. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  12. 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