Known issues in UEM 12.25 and UEM Cloud

Installation and upgrade known issues

If your UEM on-premises environment includes the BlackBerry AtHoc UEM Notifications plug-in version 3.3.0.20 or earlier or the BlackBerry Workspaces UEM plug-in version 4.10.2.706 or earlier, when you upgrade to UEM version 12.25, the upgrade process fails, leaving UEM in a down state. (EMM-162831)

Workaround: Remove the plug-ins before you start the upgrade. Navigate to C:\Program Files\BlackBerry\UEM\ext and delete the folders for the AtHoc and Workspaces UEM plug-ins. You cannot install the same version of either plug-in after the upgrade is complete, as it will cause the down state again. You must install a later version of either plug-in when released.

If the "Delay software updates" and "Automatically update device OS" iOS IT policy rules are enabled, and you upgrade UEM version 12.22 to version 12.24 or later, the software update delay period on iOS 26 and iOS 18 devices might not be applied as expected. As a result, devices might download OS updates immediately instead of waiting until the delay period has expired. (EMM-160869)

Workaround: After you upgrade UEM, edit and save any impacted IT policies.

After upgrading to UEM version 12.24 or later, or after receiving a UEM Cloud update, any custom administrator roles that were granted all "View users and activated devices" permissions will not have the new permissions "View compliance violations" and "View device vulnerabilities". You must grant these permissions to any custom roles that you created before the upgrade. (EMM-160325)

In certain circumstances, in a UEM Cloud environment, when you open the BlackBerry Connectivity Node console for the first time after an upgrade, an HTTP Status 500 error displays and the console does not load as expected. (EMM-157113)

Workaround: Refresh the page after the error displays.

Management console known issues

When you view the details for a macOS app store app, you can make changes to the app category but you cannot save or cancel the changes. (EMM-162425)

If your UEM environment is configured to use BlackBerry Enterprise Identity with Entra ID and OIDC, when a UEM user without an administrator role tries to access the management console, a login failure page displays. If the user clicks "Click here to log in to BlackBerry UEM Self-Service" on this screen, the user is returned to the same login failure page instead of being redirected to UEM Self-Service. (EMM-162332)

Workaround: The user can access UEM Self-Service directly.

On the email notifications page (Settings > BlackBerry Dynamics > Email notifications), if you enter information and click "Test Connection", then click "Cancel" or navigate away from the page without saving, the page is blank the next time you navigate to it and it cannot be restored. (EMM-162196)

If you create or edit a BlackBerry Dynamics Notification Profile and enable both the "Use BlackBerry Connectivity Node route" and "Enable password expiry" settings, when you try to save the profile, the validation fails and the profile is not saved. (EMM-160923)

Workaround: Enable the "Use BlackBerry Connectivity Node route" setting, save the profile, then edit the profile again to add the password expiry settings.

When you remove an Apple VPP account from UEM and click "Delete" on the "Delete VPP account" dialog box, the dialog box remains and a delete confirmation message does not display. The VPP account is removed from UEM. (EMM-160109)

If you assign a new email profile to a user or group with an existing email profile, the prompt to replace the profile is titled "Assign Email profile" instead of "Replace email profile", and an "Assign" button is displayed instead of a "Replace" button. Clicking the "Assign" button replaces the existing email profile. (EMM-159112)

In unknown and intermittent circumstances, when a user activates a macOS device, the device details in the management console may list "Command failed" for the action of sending the IT policy and profiles to the device even though the policy and profiles were delivered successfully. (EMM-159166)

User, device, and app management known issues

If you connect UEM to Microsoft Active Directory and you enable onboarding, users with a Common Name (CN) that includes backslash-escape characters are not onboarded as expected. (EMM-162731)

If a macOS device user removes the UEM work apps menu item from the Dock, the work apps menu item is not restored on subsequent check-ins between the device and UEM. As a result, the user cannot access the work apps catalog to install optional apps that you assigned from UEM. (EMM-162374)

Workaround: Instruct the user to activate the device with UEM again to restore the work apps catalog on the Dock.

When UEM updates an iOS VPP app on a user's device, it sends an unnecessary license association request to Apple VPP. The update might be delayed until UEM receives a response that the request is no longer pending. (EMM-162226)

If you try to assign an iOS VPP app as an unmanaged app (disposition set to optional, target set to personal, and license assigned to user), the license is not assigned to the user as expected. (EMM-160481)

Workaround: Try to assign the VPP app with the same settings again. The assignment should work as expected on a subsequent attempt.

When you add an Apple ADE configuration to UEM, you can specify a support email address. On macOS devices, the support email address does not display as expected when a user clicks the info icon during the activation process. (EMM-160359)

As of macOS 26.2, Apple has made changes to how restriction payloads are handled. As a result, using a combination of device functionality rules and user functionality rules can result in unpredictable behavior (see developer.apple.com: Device Management Restrictions).

For devices with a version of macOS earlier than 26.2, it is a best practice to use either device functionality rules or user functionality rules. If you use a combination of both and create a rule conflict, the configuration of the device functionality rule takes precedence.

For devices with macOS version 26.2 or later, use device functionality rules only.

(EMM-159594)

After the upgrade to UEM 12.23 Quick Fix 2 or later or after the UEM Cloud January 2026 update, when you edit and save an IT policy with macOS user policy settings, macOS users who activated before the update may see a duplicate of the IT policy on their device. (EMM-159518)

If a VPP app is assigned as unmanaged (disposition set to optional, target set to personal, and license assigned to user), in unknown circumstances, when a user activates their device, the user might not be able to install the assigned VPP app. (EMM-159159)

Workaround: Instruct users to install another app from the Required tab in Work Apps, then try to install the unmanaged VPP app again.

If you configure a SCEP profile with an Entrust configuration, if the configuration does not include an igusername token, the certificate enrollment process does not complete as expected on devices. (EMM-159103)

If you create a group and assign multiple VPP apps with different VPP license configurations to the group as part of the initial group creation process, some of the apps might not be assigned VPP licenses as expected. (EMM-159063)

Workaround: Create the group first without assigning VPP apps, then assign the appropriate VPP apps to the group.

If you used UEM to assign the Vrbo Owner app to users or groups with the disposition set to optional and the target set to personal, but a user did not install the app yet, after the upgrade to UEM 12.23 or later or the November 2025 UEM Cloud update, when the user tries to install the app, an error message indicates that the app cannot be downloaded. UEM indicates that the app used a VPP license. (EMM-159034)

If you associate an enterprise connectivity profile configured for per-app VPN with an IMAP/POP3 profile, after the IMAP/POP3 profile is applied, iOS devices are not able to connect to the IMAP/POP3 server. (EMM-158971)

Workaround: Configure the enterprise connectivity profile for device-wide VPN.

If you create an email profile and you both specify a password and enable certificate authentication for iOS devices, the device does not authenticate as expected with the Microsoft Exchange Server. (EMM-158824)

Workaround: Configure the email profile to use either a password or certificate authentication, not both.

If a VPP app is installed on a device as unmanaged (disposition set to optional, target set to personal, and license assigned to user), then you change the Target setting for the app to Work, the app is still considered unmanaged by UEM and cannot be removed or otherwise managed from the management console. (EMM-158465)

If a VPP app is installed on a device as unmanaged (disposition set to optional, target set to personal, and license assigned to user), when you view the user's device details, the app status is displayed as Not installed. (EMM-158447)

If you enable automatic OS updates for iOS devices in the assigned IT policy, and set an update schedule of one day, the device OS is not updated on the one day schedule as expected. The update is automatically moved to the next day (and does occur as expected on that day). This issue occurs intermittently. (EMM-157987)

If you use a .csv file to import directory user accounts into UEM, and you use the Group membership column to specify the group that you want to add each user to, during the import process you receive a prompt asking you to select the groups that you want to add the users to, even though this information is already specified in the .csv file. If you make a selection in the prompt and click "Import", the selection from the prompt overrides whatever group memberships are specified in the .csv file. (EMM-157964)

Workaround: Don't select any groups in the prompt and click "Import". The imported users will be added to the groups that you specified in the .csv file.

If you configured the "Device is out of contact" compliance rule for iOS devices with an enforcement action to delete all data, delete only work data, or untrust, when UEM executes the enforcement action it might remove the device from UEM instead. The management console does not indicate that a different compliance action is carried out and work data might remain on the device. This issue can occur on iOS devices with the UEM Client. (EMM-157000)

If you configure compliance prompts for BlackBerry Dynamics apps for the "OS update not applied" (iOS and Android) or "Managed device attestation failure" (iOS) rules and you set the action for BlackBerry Dynamics apps to block or to delete BlackBerry Dynamics app data, then you remove and reassign the compliance profile, the UEM Client and other BlackBerry Dynamics apps may be blocked or deactivated and removed (depending on the selected action) without prompting the user first. (EMM-156895)

When you assign VPP apps with a user license to Apple ADE devices, if you assign the apps right after associating the VPP license to users, the apps might not install as expected because the app license cannot be retrieved. (EMM-156886)

Workaround: See Microsoft Intune - iOS and iPadOS app installation errors: Could not retrieve license for the app with iTunes Store ID.

If you assign a compliance profile with the iOS "OS update not applied" rule set to provide compliance prompts for BlackBerry Dynamics apps, then you change the compliance action for BlackBerry Dynamics apps from block to delete app data, or from delete data to block, prompts are not provided to the user before the enforcement action is applied. (EMM-156884)

Samsung devices that are activated with Android Enterprise Work space only and are assigned an enterprise connectivity profile cannot send or receive SMS or MMS messages. (EMM-154287)

Workaround: In the enterprise connectivity profile settings, on the Android tab, select Container-wide VPN and add the com.android.mms.service and com.google.android.apps.messaging apps to the list of apps restricted from using BlackBerry Secure Connect Plus.

Chrome OS devices do not synchronize with UEM if they are in an org unit that has no child org units. (EMM-150375)

If an authentication delegate app is configured in an assigned BlackBerry Dynamics profile, when a device user removes the authentication delegate app from their device and then restarts a different BlackBerry Dynamics app and uses the forgot password option, the forgot password option does not work and the user does not receive an error message. (GD-66829)

Workaround: Instruct the user to install the authentication delegate app again.