Edit

Share via

Migrate the Warehouse Management mobile app from V3 to V4

Note

Community interest groups have now moved from Yammer to Microsoft Viva Engage. To join a Viva Engage community and take part in the latest discussions, fill out the Request access to Finance and Operations Viva Engage Community form and choose the community you want to join.

Version 4 (V4) of the Warehouse Management mobile app brings significant improvements and new features that enhance the user experience and the app's performance.

For V4, Microsoft rewrote the code for the Warehouse Management mobile app to take advantage of the newest software technology. V4 offers the following benefits:

  • Enhanced performance – Improved application responsiveness and stability.
  • Better customer support capabilities – Faster issue resolution and customer assistance.
  • Future-ready architecture – Streamlined development of new features and integrations.

Tip

  • The Migration information section provides important advice that can help you avoid unexpected disruptions during the migration process.
  • The Rollout section provides the rollout schedule and download details.
  • If you're migrating iOS devices, read the Migrating from V3 to V4 for iOS section before you begin — connection settings are not preserved on iOS and Device Code authentication is no longer supported.

Rollout

Microsoft has been rolling out V4 globally for several months by progressively increasing coverage of countries and regions. Each expansion wave was carefully tested to ensure stability and readiness. The rollout phase is now nearing completion.

V4 general availability schedule and sources

The general availability release of V4 is available for the following platforms on the following schedule:

  • Google Android – Available globally starting at the end of January 2026 from Google Play and Microsoft App Center.
  • Microsoft Windows – Available globally starting in February 2026 from Microsoft App Center.
  • Apple iOS – The official release of WMA iOS v4 began on 23 February 2026. As of January 2026, it's available through Apple Test Flight.

Migration information

System requirements

The system requirements for V4 are the same as the system requirements for V3, except for Android devices. V3 supports Android 5 and later, but V4 requires Android 7 or later. Devices that run older Android versions can continue to use V3 until the May 2026 end-of-support date. However, no new releases or feature updates are available for V3, and all newly reported issues are resolved only in V4.

If you're running a newer version of Android, use V4 because it provides better compatibility than V3 on newer systems.

Compatibility between V3 and V4

V4 supports a smooth transition from V3. The following considerations summarize what stays compatible during the migration and what you should plan for when upgrading.

  • Customizations are preserved – All customizations and configurations from V3 are fully compatible with V4 and remain functional.

  • On Android and Windows devices, connection settings can be preserved on upgrade – When you upgrade the Warehouse Management mobile app from version 3.0.8 or higher to V4 on Android or Windows, your existing connection settings are automatically migrated. Connection settings are only preserved during an upgrade, not during a fresh installation. To preserve settings:

    • Don't uninstall V3. Instead, download the V4 installer and select the Upgrade option.
    • If you're running V3.0.7 or older, first upgrade to V3.0.8 or V3.0.9, then upgrade to V4.

  • On iOS devices, connection settings aren't preserved on upgrade – You must reconfigure connections manually after installing V4. To simplify this process, prepare QR codes in advance. Learn more in Use a QR code to connect the mobile app to Supply Chain Management.

  • MDM Deployment – If you use a mobile device management (MDM) solution to distribute the app, the connection settings are preserved when you migrate from V3.0.9 to V4, or from V4 to any later version of V4.

  • Concurrent operation – V3 and V4 can operate simultaneously in the same warehouse environment without conflicts provided they're installed on separate devices. You can use different authentication methods for each version without conflict. This capability allows for a phased rollout of V4 without disrupting ongoing operations. However, you can't run V3 and V4 on the same device at the same time.

  • V3 requests remain active – Microsoft doesn't block requests coming from V3. You can continue using V3 until you're ready to migrate.

Important

Microsoft doesn't force-update any device. When a new version of the Warehouse Management mobile app is released, Microsoft publishes it to the app stores (Microsoft Store, Google Play, and Apple App Store). The update is only downloaded to a device if auto-update is enabled in the device's store settings. If auto-update is disabled, the device continues to run its current version until an administrator or user manually triggers the update.

To ensure a consistent and predictable migration across your device fleet, use a Mobile Device Management (MDM) solution, such as Microsoft Intune. Unlike app stores, an MDM provides a dedicated management channel that gives administrators full control over when and how updates are applied to each device.

Migrating from V3 to V4 for iOS

Microsoft started the official release of WMA iOS V4 on 23 February 2026. The rollout is phased, starting with a limited percentage of users and gradually increasing over time.

Important

iOS migration has two key differences from Android and Windows:

  • Connection settings aren't preserved – When upgrading from V3 to V4 on iOS, you lose existing connection settings. You must manually reconfigure connections after the upgrade. To simplify this process, generate QR codes in advance. Learn more in Use a QR code to connect the mobile app to Supply Chain Management.
  • Device Code authentication isn't supported on iOS V4 – Before upgrading, ensure your environment is configured for username/password authentication.

Before you upgrade iOS devices

  1. Verify that username/password authentication is properly configured in your environment.
  2. Prepare QR codes or JSON configuration files for all connections that you need to reconfigure.
  3. If you want to validate V4 behavior before the full rollout, join Apple TestFlight to test the V4 version.
  4. If you want to prevent automatic updates, disable auto-update in your App Store or MDM configurations.

If you need to return to V3

If critical problems arise while you're testing V4, you can return to V3.0.9. The following conditions apply:

  • Regional rollback – You can't downgrade a region after migrating it.

  • App downgrade – You can downgrade individual devices from V4 to V3.0.9 without problem to ensure operational continuity.

  • Download links – Use the following links to download V3.0.9 installers for Android and Windows devices:

  • To install the Microsoft Certificate from an MSIX bundle file – Follow these steps:

    1. Go to the folder that contains the MSIX bundle folder.
    2. Right-click the MSIX and select Properties.
    3. In the Properties window, open the Digital Signatures tab.
    4. From the list of signatures, select the Microsoft signature.
    5. Select Details, and then select View Certificate.
    6. Select Install Certificate.
    7. Choose the certificate store location.
    8. Select Local Machine and select Next.
    9. Select Trusted Root Certification Authorities.
    10. Select Next, and then Finish to complete the certificate installation.

Authentication

Authentication in cloud environments

The following authentication changes apply when you use a cloud environment of Supply Chain Management.

  • One-time reauthentication – App users must complete a single authentication process the first time they use the app on each device that is migrated to V4. After a device is successfully migrated, it stays authenticated. You won't need to reauthenticate the device again when updating to future versions of V4.
  • Windows platform configuration – For Windows applications, you must add a new redirect URI to your Azure application registration:
    1. Open the Azure portal.
    2. Go to App Registrations.
    3. Select your Microsoft Entra ID registration.
    4. Go to Manage > Authentication.
    5. Select Add a platform, and then select Mobile and desktop applications.
    6. In the Custom redirect URIs field, enter ms-appx-web://microsoft.aad.brokerplugin/{clientId} (where {clientId} is your Microsoft Entra client ID).

Authentication in on-premises environments

If you use an on-premises environment of Supply Chain Management, you don't need a new Entra ID account or infrastructure configuration to support V4. Continue to use your existing configuration as established for V3. However, to support Windows and Android devices, you must add a new redirect URI to your application registration for the Supply Chain Management tenant in AD FS. For V4 of the Warehouse Management mobile app, the redirect URIs are as follows:

  • Windows – ms-appx-web://microsoft.aad.brokerplugin/{clientId} (where {clientId} is your Microsoft Entra client ID).
  • Android – msauth://com.microsoft.warehousemanagement/hpavxC1xAIAr5u39m1waWrUbsO8=

For more information and detailed setup instructions, go to User-based authentication for the Warehouse Management mobile app in on-premises deployments.

Supported authentication methods

The following table summarizes the supported authentication methods for each platform and type of deployment environment (cloud or on-premises).

Platform Cloud environment On-premises environment
Windows Device code, Username/password, Broker Device code, Username/password
Android Device code, Username/password Username/password only
iOS Username/password only Username/password only

Transition period support

V3 support timeline

Use the following timeline to plan your transition from V3 and ensure devices are migrated to V4 before support ends.

  • End of support – May 2026 (estimated).
  • Final version – Version 3.0.9 is the final V3 release. Any reported issues will be addressed in V4.
  • Feature development – No new features will be developed for V3.

New features in V4

The following subsections summarize the key new features and improvements that are introduced in V4 of the Warehouse Management mobile app.

Camera improvements

V4 provides improved camera scanning capabilities. Here are some examples:

  • Faster scanning – Scan speed and accuracy are dramatically improved.
  • Expanded bar code support – The app now supports a wider range of bar code formats. Learn more in Scan bar codes using a camera in the Warehouse Management mobile app.
  • Multiple bar code support – Scan multiple bar codes in a single operation.
  • Hardware independence – There's less dependency on physical bar code scanners in environments where camera scanning is viable.

Customizable themes

V4 provides an enhanced user experience through comprehensive theming options. Here are some examples:

  • Eleven unique themes – A complete set of professionally designed themes is available.
  • Dual-mode support – Each theme is available in both dark mode and light mode.
  • Unified settings – Manage theme preferences through the Settings interface.

Enhanced audio experience

V4 offers expanded audio customization for improved user interaction.

  • Over 15 sound combinations – An extensive library of notification and interaction sounds is available.
  • Personalization – Workers can customize their device audio experience.
  • Centralized configuration – Sound settings are integrated with theme preferences.

Advanced diagnostics

V4 supports comprehensive diagnostic capabilities for improved troubleshooting and maintenance. Here are some examples:

  • Wi-Fi diagnostics

    • Self-diagnostic capabilities – Each device can independently assess its network connectivity.
    • Service ping tests – Verification of connectivity to critical services is automated.
    • Proactive monitoring – Detect network-related problems early.

  • Local logging system

    • Human-readable logs – The log format is improved for easier troubleshooting.
    • Filtering capabilities – Advanced log filtering allows for targeted analysis.
    • Export functionality – Easily export the log for support and analysis purposes.

  • Accessible scan testing

    • Simplified access – Scan test functionality doesn't require developer menu navigation.
    • User-friendly interface – The testing process is streamlined for users.
  • Last updated on