Dynamics 365 SCM Warehouse-to-LMS Integration: Preview December 2026, GA February 2027

Listed on the Microsoft AI at Work Roadmap under ID 576641 and documented in the Microsoft Learn release plan for Dynamics 365, the feature is currently in development. For enterprise IT administrators, solution architects, and warehouse operations leads, this roadmap update signals a more standardized way to pipe ground-truth warehouse execution data into specialized third-party workforce platforms—without having to hand-roll fragile custom middleware for every deployment mode.

The Rollout Timeline and Deployment Scope​

Before anyone starts clearing their December maintenance windows, it is worth remembering Microsoft's standard roadmap ground rules: roadmap dates and descriptions are planned estimates for commercial features and remain subject to change until general availability.

With that caveat in mind, Microsoft's roadmap entry outlines a clear schedule for roadmap ID 576641:

Perhaps the most important technical detail in Microsoft's feature description is the breadth of operational modes the integration framework is built to cover. According to the roadmap listing, the connection will support warehouse execution both with and without warehouse management processes, and it explicitly supports Warehouse management only mode.

Why does that matter? Because enterprise supply chains are rarely uniform. A single organization might run full-blown advanced warehouse management processes in a central fulfillment hub, basic execution in smaller regional depots, and Warehouse management only mode in facilities that serve third-party ERP systems. Having a single standard framework that spans all three operational contexts means architects will not have to invent separate labor-data extraction patterns for different facilities.

Section Summary: Roadmap item 576641 is slated for public preview in December 2026 and general availability in February 2027 for Worldwide Standard Multi-Tenant web environments, covering standard warehouse execution, operations without full warehouse management processes, and Warehouse management only mode.

What Dynamics 365 Already Does vs. What an External LMS Adds​

If you have administered Dynamics 365 Supply Chain Management for any length of time, you might be asking a fair rhetorical question: Doesn't the Warehouse management module already track worker tasks and labor standards?

It certainly does. According to Microsoft Learn documentation on managing warehouse workers, Supply Chain Management already records worker operations—such as picking, moving, and cycle counting on-hand inventory via the Warehouse Management mobile app—as "work." Administrators link warehouse work users to Human resources worker records, assign default warehouses and mobile device menus, and can turn on the Allow labor standards option per warehouse. Using the native Labor standards page, teams can define calculation methods to estimate how long specific picks or puts should take, compare estimated times against actual completion times on the All work page, use estimated times to automatically split and load-balance work, and review built-in reports like Labor by user and Labor by work transaction type.

However, as Microsoft Learn notes in its warehouse management overview, picking strategy is where labor cost concentrates, and high-volume distribution centers often rely on dedicated, third-party labor management systems that go far beyond basic expected-versus-actual work timers. In the roadmap description for ID 576641, Microsoft highlights several capabilities that dedicated external LMS platforms typically bring to the table when fed warehouse execution data:

• Engineered Labor Standards and Time Studies: Supporting industrial engineering time studies to establish granular task-duration benchmarks that account for travel distance, equipment type, and physical handling factors.
• Real-Time Productivity Monitoring and Task Tracking: Tracking floor activity as it happens rather than analyzing static end-of-shift reports.
• Predictive Scheduling and Dynamic Labor Forecasting: Anticipating staffing needs across shifts and zones based on incoming order waves and historical velocity.
• Automated Time, Attendance, and Incentive Management: Tying actual floor execution directly into attendance records and pay-for-performance or bonus programs.
• Customizable Dashboards and Ad-Hoc Reporting: Giving supervisors and operations analysts specialized views into cost-to-serve and task-level bottlenecks.

Notice the distinction here: Microsoft is not claiming that Dynamics 365 Supply Chain Management itself is becoming a full time-study and incentive-payroll engine. Rather, Microsoft is building a standard framework to connect warehouse execution data from Supply Chain Management into third-party LMS tools that specialize in those functions.

Section Summary: While Dynamics 365 Supply Chain Management includes native labor standards and basic worker productivity reports, the planned framework is designed to feed warehouse execution data into specialized third-party LMS platforms that handle engineered standards, predictive scheduling, attendance, and incentive programs.

Why "Warehouse-Only Mode" Support Is a Big Deal​

For enterprise IT teams, the explicit inclusion of Warehouse management only mode in roadmap item 576641 is arguably the most practical piece of news in the announcement.

As detailed in Microsoft Learn's documentation for Warehouse management only mode, this feature (which became mandatory and cannot be turned off as of Supply Chain Management version 10.0.47) allows a dedicated legal entity in Dynamics 365 to run advanced warehouse operations on behalf of other legal entities or completely external ERP and order management systems. Instead of relying on full purchase orders, sales orders, or transfer orders, it processes lightweight inbound and outbound shipment order messages, exchanges updates via business events and data entities, and can integrate using OData, APIs, or Dataverse virtual entities.

Consider a real-world scenario: a large manufacturer runs a legacy third-party ERP for financials and order entry, deploys Dynamics 365 Supply Chain Management in Warehouse management only mode to run its physical distribution centers, and uses an enterprise LMS to schedule and pay its warehouse workforce. Without a standard LMS integration framework that supports warehouse-only mode, the IT team is stuck in a three-way integration triangle—trying to correlate lightweight shipment order picks inside Dynamics 365 with worker rosters and clock-in data living outside the system. By supporting warehouse-only mode alongside standard warehouse deployments, Microsoft's planned framework aims to keep labor execution data flowing even when Dynamics 365 is acting purely as the warehouse execution nexus.

Section Summary: Supporting Warehouse management only mode ensures that organizations using Dynamics 365 strictly as a dedicated WMS alongside external ERPs will still be able to use the standard LMS integration framework.

What Remains Unanswered (And How IT Teams Should Prepare)​

As veteran systems integrators know all too well, the phrase "standard integration framework" on an early roadmap card can mean anything from a set of Dataverse business events and OData entities to a richly configured workspace with out-of-the-box message queues.

Right now,based on the verified roadmap record and current Microsoft Learn documentation, several critical technical details have not yet been published:

1. No Named LMS Vendors or Prebuilt Connectors: The roadmap entry describes integration with "external labor management systems" and "a third-party LMS," but it does not announce partnerships with specific LMS vendors or out-of-the-box connectors for named third-party products.
2. Unspecified Data Contracts and Directionality: While the roadmap states that you can connect warehouse execution data to a third-party LMS and mentions synchronized workforce schedules and warehouse task execution, it does not yet document the exact data entities, APIs, message schemas, polling intervals, or whether synchronization is strictly outbound from Dynamics 365 or bidirectional.
3. Configuration vs. "Automatic" Enablement: Although the roadmap metadata lists the feature as "Enabled for end users automatically," in Dynamics 365 Supply Chain Management that typically means the underlying framework code or feature management state becomes available without end-user client installation—not that an external LMS magically links itself without administrator setup, endpoint authentication, and mapping. (And administrators should not assume it uses the exact same Warehouse management > Setup > Warehouse management integration > Source systems screens currently documented for external ERP setups in warehouse-only mode until Microsoft publishes the specific setup guide for item 576641.)
4. Relationship to Native Labor Standards: Microsoft has not yet specified whether the new framework draws directly from the existing Allow labor standards calculations and All work tables, or introduces new staging tables and business events dedicated to labor telemetry.

Actionable Next Steps for Dynamics 365 Architects​

If your organization runs Dynamics 365 Supply Chain Management and is currently maintaining a custom LMS integration—or evaluating a new LMS purchase for 2027—here is how to play this smartly:

• Hold Off on Custom Plumbing: If you have a backlog project to build custom batch exports of All work transactions for an external LMS, pause non-urgent development until December 2026 when the preview lands and you can inspect Microsoft's standard framework.
• Audit Your Current Worker Setup: Review how your warehouses currently configure Human resources worker links, Warehouse Mobile Device Portal work users, and work transaction types. Clean master data is a prerequisite for any labor integration, regardless of the transport mechanism.
• Watch the 2026 Release Plan Updates: Keep an eye on the Microsoft Learn release plan documentation for Dynamics 365 Supply Chain Management as December 2026 approaches for the technical documentation covering exact data entities, business events, and version prerequisites.

Connecting warehouse floor reality with workforce planning is one of the fastest ways to trim fulfillment costs without burning out your staff. If Microsoft's upcoming framework delivers a clean, low-overhead pipeline between Dynamics 365 warehouse execution and third-party LMS engines, both warehouse managers and the IT admins who support them will have one less integration headache to babysit.