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: 273/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 23:12 UTC Customize Public modeDiscuss ChangeIntel on Discord

Recorded 4 Nov 2026 at 13:10 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: Process subcontractor photos, completion documents, and inspection results

Business value Subcontractors often document completed work through photos, service reports, inspection forms, certificates, and other files. When those documents remain only in a shared mailbox, service teams must manually download, interpret, organize, and reconnect them with the work they support. Important completion evidence and inspection findings can be difficult to find when a customer, dispatcher, auditor, or future technician needs them. Processing subcontractor completion documents as part of the closeout keeps evidence and supported findings connected to the Field Service work. This improves traceability, reduces document-handling effort, and preserves a more complete operational history. Feature detail The Subcontractor Agent processes supported attachments received with a subcontractor submission, including photos, PDFs, service reports, inspection documents, and other supported completion files. It associates those files with the relevant Field Service work so authorized users can find the evidence from the operational record rather than searching the mailbox. The agent can use supported document content when preparing the closeout proposal. For an inspection or tas…

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
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 (41)

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

  1. 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  2. 4 Nov 2026 · 11:04:04 UTC Preview targetNot stated → October CY2026
  3. 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → February CY2027
  4. 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
  5. 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
  6. 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
  7. 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  8. 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571674
  9. 4 Nov 2026 · 11:04:04 UTC SummaryBusiness value → Business value Subcontractors often document completed work through photos, service reports, inspection forms, certificates, and other files. When those documents remain only in a shared mailbox, service teams must manually download, interpret, organize, and reconnect them with the work they support. Important completion evidence and inspection findings can be difficult to find when a customer, dispatcher, auditor, or future technician needs them. Processing subcontractor completion documents as part of the closeout keeps evidence and supported findings connected to the Field Service work. This improves traceability, reduces document-handling effort, and preserves a more complete operational history. Feature detail The Subcontractor Agent processes supported attachments received with a subcontractor submission, including photos, PDFs, service reports, inspection documents, and other supported completion files. It associates those files with the relevant Field Service work so authorized users can find the evidence from the operational record rather than searching the mailbox. The agent can use supported document content when preparing the closeout proposal. For an inspection or tas…
  10. 4 Nov 2026 · 10:01:18 UTC Preview targetOctober CY2026 → Not stated
  11. 4 Nov 2026 · 10:01:18 UTC General availability targetFebruary CY2027 → Not stated
  12. 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
  13. 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
  14. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
  15. 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=571674 → No longer listed in this observation
  16. 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
  17. 4 Nov 2026 · 10:01:18 UTC SummaryBusiness value Subcontractors often document completed work through photos, service reports, inspection forms, certificates, and other files. When those documents remain only in a shared mailbox, service teams must manually download, interpret, organize, and reconnect them with the work they support. Important completion evidence and inspection findings can be difficult to find when a customer, dispatcher, auditor, or future technician needs them. Processing subcontractor completion documents as part of the closeout keeps evidence and supported findings connected to the Field Service work. This improves traceability, reduces document-handling effort, and preserves a more complete operational history. Feature detail The Subcontractor Agent processes supported attachments received with a subcontractor submission, including photos, PDFs, service reports, inspection documents, and other supported completion files. It associates those files with the relevant Field Service work so authorized users can find the evidence from the operational record rather than searching the mailbox. The agent can use supported document content when preparing the closeout proposal. For an inspection or tas… → Business value
  18. 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  19. 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  20. 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  21. 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=571674 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=571674
  22. 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  23. 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  24. 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM571674
  25. 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  26. 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  27. 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  28. 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  29. 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  30. 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  31. 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  32. 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  33. 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  34. 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  35. 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
  36. 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  37. 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  38. 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  39. 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
  40. 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
  41. 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 23:12 UTC · 273 of 275 readable · 271 fully read · documentation 469/469 current