If a device was part of a shared device group, after the device was checked in from the UEM management console by an administrator, the check-in status page in the BlackBerry UEM Client indicated that the device was still checked out. Apps and profiles were removed from the device as expected. (EMA-19691)

If you assigned a BlackBerry Protect Mobile profile to devices with the "Detect insecure Wi-Fi access point" setting enabled, and the user connected to an insecure Wi-Fi network that caused the device to be reported as out of compliance, the UEM Client might have continued to report the device as out of compliance even after the user connected to a secure Wi-Fi network. (EMA-19565)

If you tried to import Entrust certificates into the UEM Client, the import process failed. (GD-69791)

If a user activated a new device enrolled in Apple Device Enrollment Program (DEP), the device was unable to register with Entra ID and access Microsoft 365 apps. (EMA-19681)

The Enroll Conditional Access option displayed with a smaller font size than expected. (EMA-19261)

If you assigned a conditional access entitlment to a user after they activated their device with UEM, the conditional access enrollment process might have stopped and did not continue as expected until the user force closed and reopened the UEM Client. (EMA-19245)

If a user tried to activate the UEM Client on an iOS 26 device while on a home Wi-Fi network, the MDM profile might not have installed as expected on the device. (EMM-158986)

If a user tried to activate the UEM Client on an iOS 26 device over a mobile network, the activation process might not have completed as expected because some UEM profiles could not be applied to the device. (EMM-158716)

Microsoft plans to roll out Baseline Scope Enforcement for conditional access policies starting in May 2026. This release of the UEM Client includes a fix that allows for successful conditional access enrollment when Baseline Scope Enforcement is enabled. (EMA-19599)