Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.
Cite this versionField-level log (70)
Up to 100 recent field edits are shown; older edits may be outside retention.
- 16 Nov 2026 · 02:39:04 UTC General availability targetNot stated → November CY2026
- 16 Nov 2026 · 02:39:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
- 16 Nov 2026 · 02:39:04 UTC Source coverage: microsoft-365-roadmapCurrent
- 16 Nov 2026 · 02:39:04 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items → No longer listed in this observation
- 16 Nov 2026 · 02:39:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 16 Nov 2026 · 02:39:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=570857
- 16 Nov 2026 · 02:39:04 UTC SummaryOrganizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work. → Organizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work. With this capability, Field Service Work Orders can be connected to a project that serves as the financial container for the work. Technicians continue to plan and execute through Field Service, while supported labor, material, expense, and other costs are captured against that project for centralized cost tracking. This gives organizations a consistent way to manage non-billable field work and understand its total cost without requiring a customer contract simply to connect the Work Order to a project.
- 16 Nov 2026 · 01:34:04 UTC General availability targetNovember CY2026 → Not stated
- 16 Nov 2026 · 01:34:04 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
- 16 Nov 2026 · 01:34:04 UTC Source coverage: merill-message-center-archiveCurrent
- 16 Nov 2026 · 01:34:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
- 16 Nov 2026 · 01:34:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=570857 → No longer listed in this observation
- 16 Nov 2026 · 01:34:04 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
- 16 Nov 2026 · 01:34:04 UTC SummaryOrganizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work. With this capability, Field Service Work Orders can be connected to a project that serves as the financial container for the work. Technicians continue to plan and execute through Field Service, while supported labor, material, expense, and other costs are captured against that project for centralized cost tracking. This gives organizations a consistent way to manage non-billable field work and understand its total cost without requiring a customer contract simply to connect the Work Order to a project. → Organizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work.
- 16 Nov 2026 · 01:23:36 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 5 Nov 2026 · 18:04:05 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 5 Nov 2026 · 17:01:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 4 Nov 2026 · 15:02:25 UTC General availability targetNot stated → November CY2026
- 4 Nov 2026 · 15:02:25 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
- 4 Nov 2026 · 15:02:25 UTC Source coverage: microsoft-365-roadmapCurrent
- 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
- 4 Nov 2026 · 15:02:25 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 4 Nov 2026 · 15:02:25 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=570857
- 4 Nov 2026 · 15:02:25 UTC SummaryOrganizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work. → Organizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work. With this capability, Field Service Work Orders can be connected to a project that serves as the financial container for the work. Technicians continue to plan and execute through Field Service, while supported labor, material, expense, and other costs are captured against that project for centralized cost tracking. This gives organizations a consistent way to manage non-billable field work and understand its total cost without requiring a customer contract simply to connect the Work Order to a project.
- 4 Nov 2026 · 13:26:53 UTC General availability targetNovember CY2026 → Not stated
- 4 Nov 2026 · 13:26:53 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
- 4 Nov 2026 · 13:26:53 UTC Source coverage: merill-message-center-archiveCurrent
- 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
- 4 Nov 2026 · 13:26:53 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=570857 → No longer listed in this observation
- 4 Nov 2026 · 13:26:53 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
- 4 Nov 2026 · 13:26:53 UTC SummaryOrganizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work. With this capability, Field Service Work Orders can be connected to a project that serves as the financial container for the work. Technicians continue to plan and execute through Field Service, while supported labor, material, expense, and other costs are captured against that project for centralized cost tracking. This gives organizations a consistent way to manage non-billable field work and understand its total cost without requiring a customer contract simply to connect the Work Order to a project. → Organizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work.
- 4 Nov 2026 · 13:10:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 4 Nov 2026 · 11:04:04 UTC General availability targetNot stated → November CY2026
- 4 Nov 2026 · 11:04:04 UTC Source coverage: merill-message-center-archiveCurrent → Not collected
- 4 Nov 2026 · 11:04:04 UTC Source coverage: microsoft-365-roadmapCurrent
- 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
- 4 Nov 2026 · 11:04:04 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 4 Nov 2026 · 11:04:04 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=570857
- 4 Nov 2026 · 11:04:04 UTC SummaryOrganizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work. → Organizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work. With this capability, Field Service Work Orders can be connected to a project that serves as the financial container for the work. Technicians continue to plan and execute through Field Service, while supported labor, material, expense, and other costs are captured against that project for centralized cost tracking. This gives organizations a consistent way to manage non-billable field work and understand its total cost without requiring a customer contract simply to connect the Work Order to a project.
- 4 Nov 2026 · 10:01:18 UTC General availability targetNovember CY2026 → Not stated
- 4 Nov 2026 · 10:01:18 UTC Source coverage: microsoft-365-roadmapIncomplete → Not collected
- 4 Nov 2026 · 10:01:18 UTC Source coverage: merill-message-center-archiveCurrent
- 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items → No longer listed in this observation
- 4 Nov 2026 · 10:01:18 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/en-us/microsoft-365/roadmap?id=570857 → No longer listed in this observation
- 4 Nov 2026 · 10:01:18 UTC Link: Dynamics 365 Field Service/roadmap?topic=Dynamics%20365%20Field%20Service&period=all#items
- 4 Nov 2026 · 10:01:18 UTC SummaryOrganizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work. With this capability, Field Service Work Orders can be connected to a project that serves as the financial container for the work. Technicians continue to plan and execute through Field Service, while supported labor, material, expense, and other costs are captured against that project for centralized cost tracking. This gives organizations a consistent way to manage non-billable field work and understand its total cost without requiring a customer contract simply to connect the Work Order to a project. → Organizations often use the same field teams for both customer work and internal operational work, such as maintenance, inspections, or asset-related activities that are not billed to an external customer. These scenarios still require scheduling, technician execution, and accurate tracking of the labor, materials, and other costs associated with the work.
- 4 Nov 2026 · 07:16:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 3 Nov 2026 · 10:16:39 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 3 Nov 2026 · 09:13:39 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 28 Oct 2026 · 08:37:56 UTC Link: Microsoft roadmap entryhttps://www.microsoft.com/microsoft-365/roadmap?id=570857 → https://www.microsoft.com/en-us/microsoft-365/roadmap?id=570857
- 26 Oct 2026 · 18:49:55 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 26 Oct 2026 · 17:48:57 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 26 Oct 2026 · 06:24:14 UTC Link: Microsoft 365 Message Center Archive by Merill Fernandohttps://mc.merill.net/message/RM570857
- 25 Oct 2026 · 20:06:13 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 25 Oct 2026 · 18:13:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 24 Oct 2026 · 11:31:34 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 24 Oct 2026 · 09:51:08 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 23 Oct 2026 · 09:33:49 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 23 Oct 2026 · 08:31:50 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 22 Oct 2026 · 18:42:24 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 22 Oct 2026 · 17:41:25 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 21 Oct 2026 · 20:45:25 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 21 Oct 2026 · 19:44:24 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 18 Oct 2026 · 14:54:30 UTC Link: Dynamics 365/roadmap?topic=Dynamics%20365&period=all#items
- 15 Oct 2026 · 14:22:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 15 Oct 2026 · 13:21:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 15 Oct 2026 · 12:20:54 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 15 Oct 2026 · 11:19:54 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete
- 14 Oct 2026 · 11:54:40 UTC Source coverage: microsoft-365-roadmapIncomplete → Current
- 14 Oct 2026 · 11:22:42 UTC Source coverage: microsoft-365-roadmapCurrent → Incomplete