--- title: "Android eSIM Management" slug: "android-esim-management" updated: 2026-08-06T10:23:18Z published: 2026-08-06T10:23:18Z canonical: "help.scalefusion.com/android-esim-management" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.scalefusion.com/llms.txt > Use this file to discover all available pages before exploring further. # Android eSIM Management ## Introduction Effortlessly provision and manage carrier profiles across your Android fleet without handling physical SIM cards. Scalefusion’s Android eSIM Management allows IT admins to remotely push, activate, and wipe eSIM profiles over-the-air, streamlining cellular connectivity and device deployment. ## Supported On 1. eSIM Management is supported only on EMM-managed devices enrolled in Scalefusion- **Company-Owned device** (COD), **Personally enabled device/ Bring Your own device** (BYOD), or **Company-Owned Personally Enabled** devices (COPE/WPCO). 2. Android **OS** **15+** 3. **eSIM capable** device. 4. Scalefusion license plan- **Growth, Business and Enterprise 2025** ## Create a configuration 1. Navigate to **Device Profile & Policies** > **General Configurations** and go to **Android Utilities**. 2. Click on **eSIM Management**. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-0J9V93ST.png) 3. In the next page, click **Add New** button. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-P4Q2F0YL.png) 4. This will open a Configure eSIM window. 1. Provide a name to this configuration. 2. Download the Sample CSV and add the details like IMEI, Serial number, EID, ICCID number, device name. Make sure you enter the correct details in respective cells. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-LDLUATQM.png) ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-1CH38J5Y.png) 5. Once you have added the details, upload the CSV file and **Submit** it. 6. Next, click **Save Config**. This config will be published to all the enrolled devices automatically. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-WJC4ATKN.png) 7. You will see your newly created config on the eSIM Management page. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-FZ8Y8CDI.png) 8. Clicking on the config name will show more details like Activation Status and a quick summary. You can also download these details in a CSV. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-QVTG45TU.png) ## How it works? 1. **Configuration & Validation** 1. **Configuration Creation:** The admin creates an eSIM configuration. 2. **CSV Upload:** The admin uploads a CSV containing device identifiers and activation codes. 3. **Validation Check:** Is the CSV file valid or not? 1. **No:** The CSV must be fixed, requiring the creation of a new configuration. 2. **Yes:** The backend maps the CSV data to enrolled devices and pushes the configuration. 2. **Profile Delivery & Download** 1. **Client Synchronization:** The Scalefusion MDM client app receives the updated settings. 2. **SM-DP+ Download**: The client app downloads the profile from the **SM-DP+** server. 3. **Download Status Check:** Is download, successful? 1. **No (Failed):** The error is synchronized back to the dashboard, and the status moves to **Manage eSIM**. 2. **Yes:** Profile status transitions to **Downloaded**. 3. **Activation Process** 1. **Enrollment Mode Routing:** What is the enrollment mode? 1. **COD / COPE:** Auto-activates the first eSIM. 2. **BYO (Bring Your Own Device):** Make sure that the **Request Permission for EID** option is enabled in the BYO Profile on the dashboard. On the device eSIM config will only activate once the user manually gives permission to share EID. Refer to the section [**On the Device**](/v1/docs/android-esim-management#on-the-device). ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-R0HUMFCS.png) 2. **Completion:** Once processed through either pathway, the status is marked as **Activated**. 3. **Dashboard Sync:** The system syncs the carrier, phone number, and **ICCID** back to the dashboard. 4. **Unpublishing & Lifecycle Management** 1. **Admin Trigger:** Admin unpublishes the eSIM configuration. 1. **If previously was “Activated":** Status changes to Unpublished/ Deactivated. 2. **If previously was “Failed / Duplicated / Downloaded":** Status changes to **Unpublished Only**. ## Status Lifecycle | **Status** | **Meaning** | | --- | --- | | Published | Activation code pushed from dashboard | | Downloaded | Profile downloaded from carrier | | Activated | Active on device (COD/COPE: auto; BYO: manual) | | Failed | Error on dashboard + Manage eSIM (red text + RETRY) Click eye icon for more details. | | Duplicated | Duplicate config — fix CSV mapping | | Unpublished | Admin removed assignment | | Deactivated | On device — only after unpublishing an Activated eSIM | ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-RVDKC76R.png) ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-MJE63BHZ.png) ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-MNOQ1X8W.png) ## Enrollment Mode Reference | **Scenario** | **COD** | **BYOD** | **COPE** | | --- | --- | --- | --- | | Activation after download | Automatic | Manual — Manage eSIM | Automatic | | CSV identifiers (mapped) | All types | `device_name`**,** `eid` **only** | All types | | EID | Automatic | **Request Sharing EID** + **Share EID** post enrollment in Complete set up (Android OS **9+**) | Automatic | | First of multiple eSIMs | Auto by `esim_id` | User activates each | Auto by `esim_id` | | Manage eSIM menu | Multiple eSIMs | Multiple eSIMs / BYO activation | Multiple eSIMs | | Unpublish removes profile | Yes | **May not** (Android Enterprise) | Yes | | Block end-user mobile network config | EMM policies | - | **EMM policies** | ### Things To Keep in Mind 1. **BYO checklist:** **Use** `device_name` **or** `eid` **in CSV** → if `eid`, enable **Request Permission for EID** in the Profile and confirm **Share EID** post enrollment (device must be Android OS **9+**) → user opens **Manage eSIM** on the device to activate. 2. **COD / COPE:** EID is synced **automatically** when using `eid` in the CSV — no Share EID permission required. 3. To **disallow end users from changing mobile network configuration** on device, apply the relevant restriction via **EMM policies** in Scalefusion. This applies to **COD** and **COPE** enrollment modes. ## Safety Controls 1. **Deactivate eSIMs on Device Delete:** Android Utilities → Global Settings → Android Settings → Application & Policy Safety Controls. By default, its **Off**. When **on**, Scalefusion MDM client removes eSIMs before device deletes. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-VPIJT4LE.png) 2. **Clear eSIM Data:** Devices → Factory Reset. By default, its **Off**. When **on**, eSIMs cleared before device factory resets. Note that this will come under Maker Checker purview, if enabled. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-QDHIGZKA.png) 3. **Request Permission for EID:** BYOD Profile → Data Sharing. By default, its **Off**. Required for BYO provisioning by `eid`. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-R0HUMFCS.png) ## On the Device ### CO Devices On the CO device, users can see the eSIM details by clicking on 3-dots menu > eSIM Management. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-WNUMLKEZ.png) - **Active:** Means eSIM has been successfully activated. - **Activate:** Means eSIM config is downloaded on the device and is waiting for activation (COD and COPE auto activation. BYOD- user manually activates). - **Retry:** Means there was a failure while activating the eSIM. The user can retry manually (we display the response given by the carriers API). ### BYO Devices On a **BYO device**, users will have to manually enable **share EID** permission by clicking on 3 lines on the top left-hand side inside Scalefusion app on the work side and then clicking **Share**. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-IQE7WE6G.png) ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-SBBKIK4Q.png) ## Reports ### Device Inventory Report If admin needs eSIM related data, they can download a report from **Device Inventory Report**. Navigate to **Reports & Workflows** > **Reports** > **Device Inventory**. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-59BJOM05.png) ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-0A1XNFMH.png) ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-VVCBT55V.png) ### Account Activity Report In this report you will find the status of the eSIM config. Navigate to **Reports & Workflows** > **Reports** > **Account Activity**. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-9H6GLKWA.png) ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-ZWSKIMQC.png) ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-YML7JL3Z.png) ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-BIEHS6A8.png) If the eSIM config is unpublished from multiple devices, you get the option to download a CSV for the same. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-7IDXMOCC.png) ## Developer API support IT Admins can also request eSIM config data using the Device Management APIs: - /api/v2/devices.json - /api/v2/devices/{id}.json 1. Navigate to **Integrations** > **Developer API** and copy the API Key. 2. Click **Read API Docs** button. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-KI52K888.png) 3. Enter the key and click **Explore API Reponses**. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-DLRFVQZ3.png) 4. Scroll down to **Device Management** to view the API. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-8RDG7VCU.png) 1. The response body will show the following details. ![](https://cdn.document360.io/175c0eac-012f-4410-bdc5-ac60794f82d8/Images/Documentation/image-6TTRGGWJ.png)