A worker monitors a supply chain and inventory dashboard at a computer in a warehouse office.
Dynamics 365 Supply Chain Management planners have a long-standing complaint. A customer gets a delivery date from capable-to-promise (CTP), and then a later planning run quietly reshuffles the supply behind it. Microsoft's answer is a Planning Optimization feature called "Keep supply for confirmed demand." The roadmap entry (ID 578063) lists it as launched, with preview in June 2026 and general availability in September 2026.

The feature is meant to strictly preserve CTP customer commitments between planning runs. That is a bigger promise than keeping a date on a sales line. This guide covers what gets protected, how to turn it on, where the limits are, and what to watch for in performance.

A worker monitors a supply chain and inventory dashboard at a computer in a warehouse office. Why this matters​

A Microsoft Experience Dynamics 365 ideas post shows the pain was real. A customer described placing sales orders well in advance, with confirmed dates set through CTP. They said the promised date might not be met, because the system generated new proposals based on requirement dates. Microsoft's reply in that thread was that it had released a Planning Optimization feature to address the issue.

The roadmap's business pitch is that CTP commitments stay reliable, which prevents last-minute changes or manual fixes. The practical result is fewer planners hand-firming orders to hold a date.

What counts as "confirmed demand"​

A sales order line is confirmed demand when its Line status is Open order and its Confirmed ship date field is populated. The CTP calculation typically sets that date.

For confirmed demand, the system preserves these items across planning runs:

  • Planned orders.
  • Pegging for planned orders, released orders and on-hand inventory.
  • Routes and route jobs.
  • Capacity reservations.

Preservation applies across all BOM levels, so every derived requirement from a confirmed sales line is kept. Microsoft calls these "confirmed requirements."

Prerequisites​

  • Supply Chain Management version 10.0.48, build 10.0.2645.33 or later.
  • Planning Optimization in use.
  • The "Keep supply for confirmed demand in Planning Optimization" switch turned on in Feature management.

Microsoft's prerequisites list the version, build and Planning Optimization requirements above. The feature works with either Near real-time CTP or Batch CTP delivery date control. Microsoft says the supply chain is retained if you later change the delivery date control, as long as the confirmed ship date stays populated.

How to enable it​

Turning on the Feature management switch is not enough. You also choose the behavior per master plan or per run.

On a master plan​

  1. Go to Master planning > Setup > Plans > Master plans.
  2. Select or create a plan.
  3. On the General FastTab, set Keep supply for confirmed demand.

Yes preserves the full supply chain linked to confirmed sales lines, and planned orders in that chain aren't replanned. No is the default. With No, the system ignores confirmed requirements. Every planned order that isn't approved and sits outside the freezing time fence is replanned on each run.

This setting also drives non-interactive scenarios. Microsoft names CTP calculation, BOM explosion and finite-capacity scheduling.

On an interactive run​

  1. Go to Master planning > Master planning > Run > Master planning.
  2. On the Parameters FastTab, set Keep supply for confirmed demand to Yes or No.

The selected master plan supplies the default value.

Verify what a run actually did​

  1. Go to Master planning > Master planning (Workspace) > History.
  2. Select the run you want to inspect.
  3. On the Request FastTab, read the Keep supply for confirmed demand field.

Microsoft flags this as the first check when a confirmed date seems to have moved. A value of No means that run may have replanned supply that previously backed a confirmed line.

The on-hand inventory catch​

This is the detail most likely to cause surprises. By default, pegging from confirmed demand to received supply, meaning on-hand inventory, still follows the coverage group's Positive days setting. Suppose a confirmed sales line was pegged to a purchase order that you later received. If the line falls outside positive days, the next run can reallocate that inventory to earlier demand. This can happen even though the original line still has a confirmed ship date.

The fix is a coverage group parameter, Keep received supply outside positive days. You find it under Master planning > Setup > Coverage > Coverage groups, on the General FastTab.

  • No (default): confirmed demand is pegged to on-hand inventory only within positive days.
  • Yes: confirmed demand stays pegged to on-hand inventory regardless of positive days.

The parameter appears only when both Planning Optimization and the keep-supply feature are enabled. It takes effect only when the run has Keep supply for confirmed demand set to Yes.

Limits to know​

  • Dates still move. Action dates and futures update for all requirements, confirmed ones included.
  • Period coverage code. The feature doesn't respect the Period coverage code for confirmed supplies created between planning runs.
  • No substitution after confirmation. Planning won't swap a confirmed requirement for an alternate item, even if the alternate becomes available later.
  • Co-products and by-products. Sales demand for these isn't treated as confirmed, even with a confirmed ship date.

How it compares with other protections​

Approved planned orders and the freezing time fence already existed. They use different criteria.

ProtectionWhat it retains
Approved planned ordersPlanned orders with Approved status
Freezing time fencePlanned orders with a requirement date inside the fence
Keep supply for confirmed demandThe planned orders, pegging and other elements of a confirmed supply chain, whatever their requirement date or status

Microsoft's two worked examples​

Shared (period-grouped) components. Customer 1 orders five finished goods under CTP. Customer 2 orders five without CTP. Both draw on one grouped semi-finished planned production order. Because Customer 1's line is confirmed, the whole shared branch counts as confirmed. If Customer 2 cancels, only Customer 2's own finished-good planned order is removed. The shared branch stays, and its quantities aren't reduced.

Coverage by requirement. Two CTP-confirmed lines each have their own raw-material supply. One is a planned purchase order and the other is a released purchase order that was firmed earlier. If the second line is canceled, its planned production requirement goes away, but the released purchase order isn't removed. Planning doesn't re-peg it to other confirmed demand. Other unconfirmed demand can use it. If it stays unpegged and actions are enabled, it gets a Cancel action.

The takeaway is that protection follows the demand chain. Canceling an order does not automatically release everything it touched.

Performance and rollout advice​

Every planning run takes longer. The system has to identify confirmed lines, trace their supply chains across all BOM levels and preserve the related requirements. The cost depends on how many open sales lines have confirmed ship dates and how deep your BOMs are.

Microsoft's recommendations:

  • Use the feature with dynamic plans that CTP uses, ideally with a shorter coverage period.
  • Avoid static plans and long coverage time fences. Microsoft warns these can grow the confirmed requirements significantly and may cause timeouts.

Analysis: what admins should do​

This is my own assessment, not Microsoft guidance.

  • Pilot first. Enable the feature on a dynamic CTP plan and compare run durations before and after. Microsoft doesn't publish benchmarks, so your BOM depth and order volume will decide the result.
  • Audit coverage groups. If you receive purchased supply well ahead of need, the Positive days behavior is the likeliest cause of "my confirmed stock got taken" complaints.
  • Watch for rigidity. Protected supply is also supply that planning won't optimize. Heavy use of CTP confirmation on long horizons could lock in a plan that later demand would have improved.
  • Keep History in your troubleshooting routine. One field on the Request FastTab can settle whether a plan or run was the cause.

Microsoft's roadmap notes that release timelines can change. Feature availability in your tenant still depends on your version and your Feature management state. The roadmap lists Worldwide (Standard Multi-Tenant) and GCC as cloud instances.

 

References

  1. Dynamics 365 Supply Chain Management: Planning - Protect confirmed CTP dates with Planning Optimization Microsoft 365 Roadmap 2026-10-23T22:45:56.419010Z
  2. Microsoft Idea - Experience Dynamics 365 experience.microsoftcrmportals.com
  3. Keep supply for confirmed demand in Planning Optimization - Supply Chain Management learn.microsoft.com