From May 2027 your scanner app has a twelve-month support window

From May 2027 your scanner app has a twelve-month support window

Two support policies apply to the Warehouse Management mobile app, they work differently, and one already took effect. If your devices are still on version 3, the deadline you are planning for is not the one that passed.

Two policies, and the first one has already started

Support policy for the Warehouse Management mobile app (ms.date 2026-04-28, updated_at 2026-07-28) opens by splitting the world in two:

• Version 3 (V3) [DEPR] — "reaches end of support in May 2026. After that date, Microsoft no longer accepts support cases for V3. Migrate to V4 before May 2026 to keep support coverage."
• Version 4 (V4) and later [GA] — "follow a rolling 12-month support window starting May 1, 2027. After that date, a release is eligible for support cases only if its publication date is within the previous 12 months."

Read the first row's date. May 2026 is behind us: for any device on V3 this is not planning — Microsoft no longer accepts support cases for that client.

The second policy is explicit that V3 does not shelter under it: "Devices that stay on V3 after May 2026 follow this V3 policy. The 12-month rolling window doesn't apply to V3."

Version 3 ended because its framework did

The reason is not a licensing decision: "V3 runs on the Xamarin framework. Xamarin is no longer supported, so Microsoft can't ship new features or bug fixes for V3."

Microsoft cannot patch what it cannot build, so its investigable scope narrows with it. Three categories are out of scope for V3:

• Authentication and identity — "V3 uses legacy authentication libraries that Microsoft no longer maintains", so failures with modern MSAL flows, Device not compliant errors, and "new conditional access policies in Microsoft Entra ID" are unsupported.
• Client-side performance and connectivity — the V3 networking stack "and libraries are frozen at their current versions", so local latency, connection drops and timeouts caused by them are unsupported. One carve-out: "If a performance issue is verified as a server-side or service-wide problem, Microsoft still investigates it as part of standard cloud service support."
• Operating system compatibility — "Crashes, UI glitches, or launch failures on mobile OS versions released after the final V3 release" are unsupported.

It matters most if you are the person told the scanners are slow: the diagnostic boundary now runs between your device and the service, and only one side is investigable.

And a dependency: "Back-end APIs stay compatible with V3 during the migration period… The compatibility duration isn't guaranteed and may end as Supply Chain Management services change." A window with no stated end is not a plan.

What end of support does not mean

Take this to whoever hears "end of support" and pictures a dark warehouse:

"Older releases of the app continue to function. The policies define when Microsoft accepts support cases. They don't affect service availability or sign-in."

So nothing switches off on a date. What changes is what happens when something goes wrong, and that does not announce itself until you already have the incident.

Microsoft repeats it for the newer policy: "The app keeps running on any installed version. Microsoft doesn't block out-of-window clients, and back-end services don't reject their connections."

Then the caveat that makes complacency expensive: "However, Supply Chain Management services change over time. Older releases might eventually stop working with newer back-end behavior. Compatibility for out-of-window releases isn't guaranteed."

And the flat one: "Devices on older releases don't get those fixes."

From 1 May 2027, the window is evaluated when you open the case

One mechanic decides everything: the window is measured back from the day you ask for help, not a release calendar.

"Starting May 1, 2027, V4 and every later release follow a rolling 12-month support window. On or after that date, a release is eligible for support cases only if its publication date is within the previous 12 months. The window is evaluated on the date the support case is opened."

And it is universal: "This rule applies to every release from V4 onward. It applies to major, minor, and patch versions equally."

Microsoft's three worked examples state it best, and the first is the one that catches people:

• April 30, 2026 — April 30, 2027 — and "Because that date falls before May 1, 2027, the release becomes ineligible on May 1, 2027 (the date the policy takes effect)"
• June 15, 2026 — June 15, 2027
• August 1, 2027 — August 1, 2028

And there is no cushion: "There's no grace period after the 12-month boundary. Update the device to a supported release before you open a support case."

The publication date is App Center's, not your app store's

"The publication date of a release is the date the release first becomes available on Microsoft App Center. Releases on the Microsoft Store, Google Play, and the Apple App Store can appear later. iOS releases often arrive later because of store review times. Even so, the Microsoft App Center date is always the date that determines support eligibility."

If you manage an iOS fleet, your clock started before your users could install the build. The gap is store review time, subtracted from your window rather than added to it.

Microsoft publishes the dates: every release "starting with version 4.1.1.0, lists its publication date in What's new or changed in the Warehouse Management mobile app."

To find what a device is running: "open the app. The version appears on the sign-in screen or in Settings."

The exceptions, and the one that is not an exception

Three carve-outs are published, and together they tell you how much room you have.

Severity 1 incidents — "Microsoft might still investigate severity-1 incidents that block widespread production operations. The team reviews these cases individually." Note might, and the sentence after it: "This exception isn't a substitute for staying current."

Preview builds are outside the window entirely — "Preview and beta builds from Microsoft App Center aren't part of the 12-month window. Use them only for evaluation."

And the one that is not an exception: autoupdate. Microsoft's remedy list is short and unglamorous — "Turn on autoupdate in your app store, or push updates through Microsoft Intune or another mobile device management (MDM) solution", track the publication dates, and "Update devices at least once a year. This practice keeps every device inside the 12-month support window."

Once a year is the whole requirement — so the fleets that fail it are not the ones that cannot update, but the ones where nobody owns it. Chapter 7's register has the same shape.

To validate releases before they reach the floor, Microsoft points to a release schedule with "upcoming release dates and options that help you pace updates while staying inside the support window."

The deprecation register records that the previous warehouse app — Supply Chain Management – Warehousing — was removed as of April 2022 and "has been removed from the Microsoft Store and Google Play store." Its Reason field reads "Effective April 2021, Supply Chain Management – Warehousing (the warehouse app) is deprecated and won't be supported after April 2022" — twelve months' notice of a fixed date.

So both were announced ahead of their end date. What is new above is the shape: a standing rule for every future release, instead of one date per app.

How we work alongside a device fleet, and where we would draw the line

Pick-Path & Slotting Optimizer decides which orders travel together and which item earns which slot, and writes the answer back into the wave, cluster and slotting objects Dynamics 365 already executes, behind an approval step. Dynamics is the system of record for the warehouse; the optimization above it is a modelling problem.

A working demo exists; it is not off the shelf. We build it against your systems and your constraints on request, and we have no delivered warehouse engagements — so this is a capability, not a report on somebody's building.

That design is why this policy does not reach us: we write into ERP objects rather than onto the scanner, so an app version is your Microsoft support question, not our compatibility matrix.

We would not build a mobile client. Microsoft ships one, maintains it against three platform vendors and publishes a support policy for it — the absorption test says advise, not duplicate.

We would also not model a fleet mid-migration: if half your devices run a version whose support ended, the data you would optimize against measures the migration, not the building.

What to do this week

1. Get the installed version off ten devices, not the MDM report. The number that matters is the one in someone's hand.
2. If anything is still on version 3, treat it as an incident, not a project. Microsoft no longer accepts support cases for that client, and the back-end compatibility window has no published end date.
3. Build your fleet's date list from App Center, not the store listing. That date determines eligibility, and for iOS it is earlier than the date your users saw.
4. Name an owner for the annual update. Updating once a year satisfies the policy, so the failure mode is ownership rather than capability.

About Cognilium Cognilium is the AI optimization layer for Dynamics 365 — complementary apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Built on Power Platform, Dataverse and Azure. https://cognilium.ai · https://www.linkedin.com/company/37180269/

If a device fleet is the thing standing between you and a warehouse project, book a fifteen-minute call and we will read the policy against your version list. No deck. https://cognilium.ai

Sources

• Support policy for the Warehouse Management mobile app
• What's new or changed in the Warehouse Management mobile app
• Warehouse Management mobile app release schedule
• Removed or deprecated features in Dynamics 365 Supply Chain Management

Sources

• learn.microsoft.com — warehouse app support info
• learn.microsoft.com — warehouse app whats new
• learn.microsoft.com — warehouse app control updates
• learn.microsoft.com — removed deprecated features scm updates