Dynamics 365 SCM 10.0.49: mandatory features to check before October

Dynamics 365 Supply Chain Management 10.0.49 reaches the auto-update window in October 2026. I would use the remaining time to compare Microsoft’s mandatory feature list with the way the system is actually configured and used today.

Microsoft identifies 10.0.49 as build 10.0.2790, with self-update general availability in September 2026 and auto-update general availability in October 2026. Some features are on by default and can still be disabled. Others become mandatory, which means administrators can no longer turn them off. Microsoft also removes some capabilities from Feature management. Microsoft documents these states in the 10.0.49 release notes.

The practical job is to identify which of those changes touch your processes and whether the current production setup depends on a different feature state.

10.0.49 upgrade triage: classify the change, check where it is used, compare today’s production state, and test the business outcome before rollout. Original Beyond ERP diagram.

Start with the mandatory features you actually use

Microsoft lists 12 features becoming mandatory in 10.0.49. They cover Asset Management, inventory and warehouse management, production control, sales and rebate processes. The list includes Advanced quality management, several Inventory Visibility integrations, Dispense management, direct-delivery date recalculation and vendor-rebate capabilities. The complete list is in Microsoft’s 10.0.49 release notes.

The feature name alone does not tell you the business risk. I would take a few real process examples into the release review.

Advanced quality management. If you use advanced quality processes around receipt, production or inventory handling, run the normal quality scenarios through the 10.0.49 sandbox. For example, create the transaction that normally triggers quality activity, process the inspection or disposition step, and confirm that downstream inventory status and warehouse work still behave as expected. If the feature is disabled in production today, that becomes a priority investigation because the option to leave it disabled is going away.

Inventory Visibility integrations. Microsoft lists ATP integration, reservation offset integration, transaction integration and warehouse-item enablement among the mandatory features. If your order promising or external inventory process uses Inventory Visibility, use representative items and warehouses to compare the quantities and availability seen by the consuming process before and after the upgrade. A useful test is an item with demand, supply and reservations changing during the scenario, rather than a clean item with a static balance.

Recalculate delivery dates upon creation of direct delivery. For businesses using direct delivery, create a representative sales order and purchase order flow and compare the resulting delivery dates with the current production behaviour. Include cases where supplier lead time, requested dates or transport assumptions matter. The point is to confirm that customer-facing dates and any dependent planning or integration logic still produce an acceptable result.

Vendor rebate features. If vendor rebates are in use, test the rebate deal through the transaction and settlement path used in production. Microsoft lists consolidation of vendor invoices for the same vendor in vendor rebate deals and posting vendor rebate outputs to purchase order vendors as mandatory features. An illustrative regression case would use a vendor with multiple qualifying purchase transactions and then check the generated rebate output, vendor assignment and posting result against the expected accounting treatment.

These are test examples, not statements that every customer uses those processes or that 10.0.49 will change every result. They show the level at which I would test a mandatory feature: start from a real transaction, follow it through the business process and compare the outcome with the current estate.

For each applicable feature, I would also record the legal entities affected, current production setting, integrations, extensions, batch jobs, security roles, process owner and fallback. A feature deliberately disabled today deserves attention first because 10.0.49 removes that production choice.

The same check applies to capabilities removed from Feature management. Microsoft describes those as becoming permanent parts of Supply Chain Management. The 10.0.49 release notes show those Feature management changes. If the switch disappears, the support plan needs another recovery route.

Keep Dynamic work classification separate

Dynamic work classification is not mandatory in 10.0.49. Microsoft still labels it Production Ready Preview, while 10.0.49 turns it on by default. It can still be disabled. Microsoft documents that status on the 10.0.49 page.

Microsoft’s Dynamic work classification documentation says the feature requires Supply Chain Management 10.0.48 or later and uses Power Fx formulas at runtime. A rule can change the work pool, default work priority, location directive codes and work classes when work is created. It can use data from the work and related load, shipment, wave and transportation appointment records.

A warehouse example is carrier-based prioritisation. Work could be created with the normal template values, then a Power Fx rule could assign a different work pool or priority when the load is associated with a particular carrier or shipping condition. If the carrier changes later, the rule can be configured to classify the work again.

Microsoft’s release-plan entry explains that the feature can reduce the number of static work templates and location directives needed.

Review the rule with the work template

When Power Fx changes work values at runtime, I would review the rule and work template together. Otherwise support teams can look at a template and still miss the reason a work header received a particular pool, priority, directive code or work class.

Microsoft documents two details that belong in the regression pack. Blank() keeps the original template value, while an empty string clears it. Template grouping also needs to match the classification logic. If the rule classifies by zone, for example, the grouping needs to stop conflicting zones from being combined on one work header. Microsoft covers both behaviours in the Dynamic work classification guidance.

For each rule, keep the purpose, associated templates, inputs, fields it can override, fallback behaviour, reclassification setting, owner and regression scenarios together. Microsoft provides a Preview action for checking a rule against existing work. I would use it as a quick check, then run the full process through wave processing, work creation and mobile execution.

Test load changes as well as work creation

If load-update reclassification is enabled, test the initial work and then change the relevant load data.

Microsoft supports disabling load-update reclassification or running it synchronously, and notes that synchronous processing can introduce a brief wait while associated work headers are processed. The load-update options are documented here.

Use representative volumes. Include work where picking has started or staging is underway. The formula can return the intended value and still create an awkward warehouse result if the classification changes after people or automation have acted on the original work.

What I would want before production

For each applicable 10.0.49 change, I would want the current production setting, the affected process, the dependencies around it, the regression result and a fallback that still works when feature deactivation is unavailable.

Microsoft introduced Dynamic work classification in 10.0.48 as a production-ready preview under Feature management. The 10.0.48 release notes record that starting point. In 10.0.49 it becomes on by default while keeping the preview label.

Before the October auto-update window, the useful evidence is simple: show which mandatory changes apply, show how the process behaves in 10.0.49, and show what the team will do if the result is not acceptable.