Back to top

Error code 23000 when applying managed configurations to Separated Apps

Last updated October 17th, 2024

Categories:

Environment

  • Knox Service Plugin
  • EMMs
  • Devices running Android 14 or higher
  • Separated Apps application with managed configurations

Overview

If Separated Apps is managed with Knox Service Plugin, you may encounter an issue where applying managed configurations in Separated Apps fails with the following error:

[List of Apps to Separate in App Separation mode failed.][23000]

Cause

Managed configurations for Separated Apps with an EMM are prioritized over Knox Service Plugin.

Once Separated Apps is enabled with managed configurations, configuration attempts to override the existing Separated Apps policy results in the aforementioned error.

Resolution

Separated Apps must be managed with either a managed configuration or through the Enabled Separated Apps policy from Knox Service Plugin. To resolve the issue, you can disable Separated Apps from either Knox Service Plugin or managed configurations.

To disable Separated Apps from Knox Service Plugin:

  1. On your EMM console, go to the Knox Service Plugin configuration.

  2. Modify the following policies:

    Policy Value
    Separate Apps policies > Enable Separated Apps False
    Separate Apps policies > List of Apps to Separate Remove all apps from the list
  3. Push the profile to your device fleet.

To remove Separated Apps from your managed configuration, unassign the app from the Group or Organization. Afterwards, enable Separated Apps with managed configuration to create a new Separated Apps folder.

The exact process for this procedure depends on the EMM you are using. Please consult your EMM’s documentation.

Additional Information

For more information regarding managing Separated Apps, visit Separated Apps for Android 14.

Is this page helpful?