eSIM setup during device enrolment

[davidguill]

Hi All, 

Is anyone aware of a way to configure an eSIM on a device during enrolment rather than later in settings?

We have a large customer that wants to use eSIM's but currently has to connect to a WiFi network to complete enrolment and then configure the eSIM later. 

This adds many extra steps to the device setup greatly increasing the onus on the end user and the chance of something going wrong.  

Many thanks

David

[Moombas]

Hi David,

i don't know an automated way yet. The only thing i know is (if i remember correctly) the MDM we use is working on something to configure eSIM but this will also only take place after device is enrolled already.

And to be honest, i don't know how it should work (in both cases) as you would need to have some kind of unique QR for each device then or somekind of mechanism working in the background in order to make this happen. Just because of the different providers you could choose from and everything behind it.

And i guess that's why you need to do that in settings (if your OS provided to your devices doesn't ask for eSIM during enrollment itself).

My best guess is that eSIM is still too new and not really considered to be managed and if your devices doesn'T request that during enrollment, you may need to contact the manufacturer of your devices to add this as a step during enrollment, so the employee can scan the QR from the provider to add the eSIM details. 

Be aware that those QR-codes very often one-time use, so if something fails it could happen you need to order a new QR-code for that "account".

[jasonbayton]

Indeed it's an immature technology. I've been struggling with the same requirement for a few weeks and have gotten to the point of engaging with the OEM to help in tandem with carrier. 

It may be something Knox Configure or a similar solution, aimed at preconfiguring devices before EMM, could handle, but because we don't have a "deploy subID" in the QR payload to use, it's tricky.

[Moombas]

And to be honest you would need 2 things in my opinion (in order to automate it):

- the provider knowing which eSIM should get which contract, so they need a list of all eSIM's to be used.

- the enrollment system/mechanism needs to get to know which provider to contact and how (which URL,...)

So, it sounds like an easy task but it's more tricky than it seem to be to automate it.

[davidguill]

The problem with using any cloud solution to configure it is that it needs an internet connection to deploy the profile first. 

Ideally you would be able to setup an eSIM during the Out of Box experience before enrolling into any services, this should be a simple a scanning the QR code. 

I have also read that  it is possible to Install a pre-assigned plan using the device EID, but this again seem to need some manual intervention after device setup.  

If not already possible in Android 15 (I haven't got access to the latest version for testing) it looks like something that Google or a Third party OEM's would need to integrate.  

I have reached out to Samsung to see if this is on the roadmap.  

[Timmy]

As already mentioned in this thread, this is something that the OEM needs to implement by the looks of things. If I take an example for Zebra devices where they have StageNow which is configuration that are scannable. I have not tried it myself with eSIM but they seem to have a partial solution for it https://supportcommunity.zebra.com/s/article/000021043?language=en_US 

I know you are looking for something in regards to Samsung but maybe this can help you in the discussion with them.

[davidguill]

Thanks Timmy, that is really useful.  I am speaking to Samsung about doing something similar with KME Direct but also think Google should integrate it into the OoBE

[Moombas]

But just FYI, see here: https://www.androidenterprise.community/t5/reports-assets/android-15-screenshots-and-slide-deck-asse...

There's eSIM management stated for Android 15 but i guess still only after enrollment and not sure about the details.

[jasonbayton]

Yep it's policy driven. What we'd need is a DPC.extras payload akin to system apps, locale, etc to allow the sending of a subscription ID

[Moombas]

I mean best would be DPC and then having a tool in background which knows of the relevant information (which the eSIM QR would provide) and with that generating dynamic QR codes or something similar.

And in addition (for ex. fully managed devices using ZTE) you would need to add something into the Zero-Touch portal, to add the relevant information per device (csv file import), so Zero-Touch provisioning possible as well. But i guess i start dreaming 😄