eSIM on Samsung devices running Android 15: Knox Service Plugin support

Android

When managing eSIM profiles on Samsung Knox-enabled devices running Android 15, Esper can provision and control eSIM functionality without requiring you to install an additional supervisor plugin.

Why this happens

Samsung Knox-enabled devices ship with a pre-installed OEM plugin called Knox Service Plugin (KSP). KSP acts as the supervisor plugin for Esper on Samsung hardware and automatically grants Esper the elevated permissions required for enterprise features — including eSIM provisioning. Additional supervisor plugins are only needed on non-Samsung devices that lack an equivalent OEM plugin.

Before you begin

Confirm the following before configuring eSIM:

The device is a Knox-capable Samsung model (such as a Galaxy Phone or Galaxy Tab with Knox support enabled).
The device is enrolled and managed in the Esper Console.
The Knox license is active on the device.
Knox Service Plugin is present and up to date. Check the installed KSP version against Samsung's Knox compatibility matrix for Android 15 before proceeding.

How to set up eSIM on a Samsung Knox device

Verify device enrollment. In the Esper Console, navigate to Devices & Groups → [Device Name] → Device Details and confirm the device status is Active. A device that is not fully enrolled will not accept eSIM commands.
Confirm Knox Service Plugin is active. On the device, go to Settings → Biometrics and security → Knox Service Plugin and verify the plugin is listed and running. If KSP is absent or disabled, eSIM management commands from Esper will not execute.
Issue the eSIM management command. In the Esper Console, navigate to Devices & Groups → [Device Name] and use the available Knox-supported eSIM command for your carrier activation flow. The exact command options displayed depend on your device model and KSP version.
Monitor command status. Navigate to Devices & Groups → [Device Name] → Activity Feed and confirm the eSIM command shows a Success status. Commands that remain in a Queued state indicate the device is offline or KSP is not responding.
Confirm eSIM carrier connectivity. On the device, open Settings → Connections → SIM manager and verify the eSIM profile is listed as active and connected to the carrier network.

Verify: The eSIM profile should appear as active in Settings → Connections → SIM manager on the device, and the corresponding command in Devices & Groups → [Device Name] → Activity Feed should show Success within 5 minutes of issuing the command.

If this doesn't resolve it

Try the following based on the specific symptom:

Commands fail or are unavailable: The KSP version on the device may be outdated. Update Knox Service Plugin through the device's app management and retry.
Device not recognized as Knox-capable: Verify the Knox license is active and confirm the device is not a carrier-locked variant with Knox disabled. Navigate to Devices & Groups → [Device Name] → Device Details and check the Knox license field.
Commands stay queued: Confirm the device is online and that KSP is running. Navigate to Devices & Groups → [Device Name] → Activity Feed to check for connectivity events that may indicate the device went offline.
Issue affects multiple devices: Verify that KSP is present and at a consistent version across all affected devices before attempting a fleet-wide rollout. Inconsistent KSP versions across a fleet are a common cause of partial eSIM failures.

If the issue persists, collect the following before contacting Esper Support:

Device serial number
Knox Service Plugin version
Android build number
Esper Agent logs from Devices & Groups → [Device Name] → Logs

Improved title: eSIM on Samsung Android 15 devices — managed via Knox Service Plugin

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.