Demand planning in Dynamics 365 Supply Chain
Microsoft's Demand Planning module — statistical forecasting, collaboration, scenarios, and the path from forecast to MRP.
Demand Planning is Dynamics 365 Supply Chain Management's modern forecasting module, built natively on the Power Platform with embedded AI. It replaces an older, less-loved Demand Forecasting tool with a cleaner UX and a real planner workspace.
The model. A demand plan is structured around dimensions — typically item, location, customer or channel, and time bucket — and measures — historical sales, statistical forecast, collaborative forecast, final consensus forecast. Planners work in a grid that pivots across the dimensions, much like a planning spreadsheet, but backed by versioning, audit, and AI.
Data inputs. Historical sales transactions flow in from F&O. External signals (marketing campaigns, promotional plans, weather, macroeconomic indicators) can be loaded as additional measures through Dataverse or Power Automate. Open orders, planned orders, and inventory positions are pulled live from F&O for sanity checks.
Statistical forecasting. Built-in forecasting models include moving averages, exponential smoothing, ARIMA, and ML-based ensembles. Planners run the engine for a horizon, evaluate accuracy against held-out history (MAPE, WAPE), and select the best-fit model per item-location. The system can also recommend a model per series.
Collaboration. Sales and operations planning (S&OP) requires multiple stakeholders to contribute. Demand Planning supports collaborative inputs — sales teams override the statistical forecast for known opportunities; marketing layers campaign uplifts; finance applies budget alignment. Each contribution is tracked and the final consensus is calculated.
Scenarios. Planners can clone a baseline forecast into what-if scenarios — promotional uplift, supply constraint, market expansion — and compare side by side without disturbing the production plan.
Outputs. The final consensus forecast publishes to F&O as forecast lines that feed master planning (the supply-side engine). Forecast lines respect time fences, lead-time offsets, and consumption rules so MRP doesn't double-count actual orders against the forecast.
Workflow. Built-in approval workflow routes the published forecast through configurable approvers before it lands in F&O.
Reporting. Power BI templates ship with the module, covering forecast accuracy, bias, drift, and consensus variance.
Where it stops. Sophisticated S&OE (sales and operations execution), causal modelling, or supply-side scenario engines often combine Demand Planning with a third-party tool. For mid-market manufacturing and distribution, the built-in module is fully sufficient.
Related guides
- Master planning groups in Dynamics 365 Supply ChainHow master planning groups configure replenishment behaviour per item in F&O — coverage groups, item allocation keys, and the policies that shape MRP.
- Master planning runs in Dynamics 365 Finance and OperationsWhat master planning actually does in F&O — the regenerative vs net change run, planned orders, action messages, and how the engine produces a supply plan.
- Planning Optimization in Dynamics 365 Supply ChainHow Planning Optimization replaced the legacy MRP engine — in-memory architecture, scalability, scope, and migration considerations.
- Alerts and notifications in Dynamics 365 FinanceHow F&O's alert framework surfaces important events — alert rules, due-date triggers, change events, delivery to action centre and email.
- Batch jobs and batch groups in Dynamics 365 FinanceHow F&O's batch framework runs background processing — batch jobs, batch groups, schedules, server allocation, and operational monitoring.