Ever had to call a customer and walk back a delivery date you already confirmed? Not fun. And usually nobody actually did anything wrong. Somewhere in the system, a planning run quietly reshuffled the material or capacity backing that promise, and nobody noticed until it was too late.
That’s the problem this post is about. In “Smarter Demand Planning,” the last post in this series, we talked about getting better at predicting what customers will want. This time we’re looking at the other half of the equation: once you know what’s needed, can you actually trust the plan that gets it there? Dynamics 365 Supply Chain Management, or SCM, is Microsoft’s cloud ERP, or enterprise resource planning system, for finance and operations. Two 2026 release wave 1 investments there are aimed squarely at that question.
The idea in one minute 💡
- Confirmed Capable-to-Promise (CTP) Protection, a new addition to Planning Optimization, stops the system from quietly stealing material or capacity from an order you already promised a customer.
- In-memory supply planning makes the underlying planning engine faster, so requirement changes show up as near-real-time insight instead of showing up tomorrow.
- Together, they mean fewer broken promises and faster reaction when something in the supply chain shifts.
The problem: promises that don’t stay promised 📒
Here’s a scenario every planner knows. A customer calls, you check availability, and using capable-to-promise, or CTP (the calculation that checks real material and capacity availability before quoting a date), you confirm a delivery date. Good news, right?
Except then a planning run happens. Maybe a bigger, newer order comes in. Without anything stopping it, the system can reallocate the material or capacity you already committed to that first customer, in favor of the new one. Nobody did this on purpose. It’s just standard supply planning logic doing its job: optimizing for the whole picture, not remembering which orders a human already gave their word on.
The result: planners spend time re-confirming or re-negotiating dates that should have been settled, and customers lose a little trust every time a “confirmed” date turns out not to be.
Confirmed CTP Protection: keeping your word ✅
This is exactly the gap that Confirmed Capable-to-Promise (CTP) Protection closes. When it’s turned on, Planning Optimization protects the material and capacity tied to sales order lines with a confirmed CTP delivery date, across every level of the bill of materials, not just the finished item. Those reservations are locked in place during future planning runs, so a newer order can’t quietly bump an earlier promise out of the way.
Under the hood, this builds on a related capability already documented as “keep supply for confirmed demand,” which lets a planner flag a master plan so that once a sales line has an open status and a confirmed ship date, its entire supply chain (planned orders, routes, capacity reservations, even on-hand inventory pegging) stays put through subsequent planning runs. Microsoft’s own diagrams show how this holds up even when multiple orders share the same component or when separate supply branches feed different confirmed lines.
Practically, this means less firefighting. Fewer “wait, why did my date move?” conversations. And a lot more confidence that when your team tells a customer a date, that date is going to hold. Nobody has to babysit the plan to make sure it does.
As of today, this is in public preview (available since June 1, 2026), with general availability expected in September 2026. If you want to try it ahead of go-live, ask your partner about enabling it now.
In-memory planning: closer to real time ⏳
The second piece is less visible but just as important: how fast the planning engine itself works. Microsoft describes in-memory supply planning as giving “the performance and scalability to get near real-time insights into requirement changes” for material requirements planning (MRP, the calculation that figures out what to buy or make, and when) and production scheduling.
In plain terms: the gap between “something changed” and “the plan reflects it” keeps shrinking. That matters because a plan is only as useful as how current it is. A planner reacting to a stale plan is reacting to yesterday’s problem, not today’s.
What this means for you ☕
Put these two together and the theme is reliability. CTP protection keeps the commitments you’ve already made intact. Faster, in-memory planning means when something genuinely does need to change, you see it sooner and can react before it becomes a customer-facing issue instead of after.
Thank you for reading!
Next up in the series, post #4: Warehouses Get an AI Upgrade, a look at how AI is starting to change what happens on the warehouse floor.
Sources
- Overview of Dynamics 365 Supply Chain Management 2026 release wave 1: Microsoft Learn
- Planning investment area: Microsoft Learn
- Protect confirmed CTP dates with Planning Optimization: Microsoft Learn
- Keep supply for confirmed demand in Planning Optimization: Microsoft Learn
- 2026 release wave 1 plans for Microsoft Dynamics 365, Microsoft Power Platform, and Copilot Studio offerings: Microsoft Dynamics 365 Blog
Interested in learning more? Below are some of my latest posts:
Leave a Reply