In development MRC 574123

Dynamics 365 Project Operations: Unify product receipt and item requirement posting

This feature posts a purchase order product receipt and the consumption of its linked project item requirement in one transaction. It applies when automatic item consumption is enabled or when you select Consume immediately while posting the product receipt. Both updates succeed

Dynamics 365 Project Operations 03 Horizon

DIGITAL SKILL WORKS LTD / 12 PANES

GA / disclosure March CY2027
Preview September CY2026
Platforms Web

What it is

Dynamics 365 Project Operations: Unify product receipt and item requirement posting is a Microsoft 365 roadmap item published via Microsoft Release Communications. Current status: In development.

What it does

This feature posts a purchase order product receipt and the consumption of its linked project item requirement in one transaction. It applies when automatic item consumption is enabled or when you select Consume immediately while posting the product receipt. Both updates succeed together, or the system rolls them both back when an error occurs. The posting flow prevents duplicate project posting and preserves existing behavior for batch posting and cancellation or correction flows. This combined posting can only be triggered from product receipt posting. The feature is available for public preview in version 10.0.49 and is off by default. It applies to Project Operations connected with ERP and Project Operations for manufacturing deployment types.

Why you should care

Board

Track as Horizon signal; decide whether it changes Wave 0 priority or stays on the watchlist.

CISO

Confirm identity, data access, and overshare exposure before enabling for broad cohorts.

CFO

Map licence or consumption impact to the frozen value case; avoid seat spray.

Adoption

Pilot with a named cohort and measure changed work, not vanity clicks.

Suggested action

Wave 0 first: Security → GRC → Cost & Value → Licence → Adoption. Add to Horizon watchlist with an owner. Pilot only after Steady controls for the affected surface are in place.

12 Panes: 03 Horizon

Communication needed

  • Security: Assess exposure, Conditional Access, and agent/tool permissions.
  • GRC: Update AI/agent register and evidence path; confirm DPIA triggers if personal data is in scope.
  • FinOps: Forecast seat or credit impact; align to frozen value case.
  • Adoption: Plan cohort messaging, clinics, and success measures.
  • Comms: One story for board and staff — what changes, what does not, who owns risk.

Benefits

  • May improve productivity on a specific Microsoft 365 surface when permissions and data quality allow.
  • Roadmap visibility helps Horizon planning without guessing dates.

Risks

  • Status and dates change; treat MRC as directional, not a contract.
  • Enabling without Steady controls can amplify overshare or cost leakage.
  • Preview or rolling features can change behaviour; fence exploration on Pane 12 Frontier.

Source

  • MRC id: 574123
  • Status: In development
  • Products: Dynamics 365 Project Operations
  • GA / disclosure: March CY2027
  • Preview: September CY2026
  • Platforms: Web
  • Cloud instances: Worldwide (Standard Multi-Tenant)
  • moreInfoUrls: —
  • Open on Microsoft 365 Roadmap

Microsoft Release Communications / Microsoft 365 Roadmap (AI at Work). Content is subject to Microsoft API Terms of Use. Dates and status change; verify in the official roadmap before acting.

Back to roadmap intel