# Read eSIM activation status separately from carrier connectivity

> Does Active in Intune prove that an imported-code eSIM has working cellular service?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:22:08+00:00
- Modified: 2026-09-10T02:14:31+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Does Active in Intune prove that an imported-code eSIM has working cellular service?

## Potentially affected

Limit this interpretation to Windows eSIM devices using imported activation codes. Confirm that this is the deployed method before applying its status labels; review the recommended alternative when considering a new deployment.

## DSE recommendation

Give the support record two separate outcomes: activation-code delivery and usable carrier connectivity.

## Article

## Source facts

Intune’s imported activation-code eSIM workflow is in public preview; Microsoft recommends the download-server method for Windows 11 instead. In that workflow, Active means the activation code was installed successfully. The device then contacts the mobile operator to download the cellular profile and finish registration. The separate Cellular status value comes from the operator. [Microsoft Learn](https://learn.microsoft.com/en-us/intune/device-configuration/templates/enable-esim).

## Applicability

Limit this interpretation to Windows eSIM devices using imported activation codes. Confirm that this is the deployed method before applying its status labels; review the recommended alternative when considering a new deployment.

## DSE recommendation

Give the support record two separate outcomes: activation-code delivery and usable carrier connectivity. Direct a delivery failure to the Intune policy investigation and a carrier-reported problem to the mobile operator with the relevant device details. Avoid distributing activation codes through ordinary tickets. Ask the operator and endpoint teams to agree which evidence each needs for an effective handoff.

## Verification

Compare the subscription pool’s device status, last check-in, and operator status with the actual eSIM profile on the test device. Then test the intended cellular connection under an approved plan without assuming another network path proves cellular service. Record which stage succeeded and which remains unverified. An Active portal label should close only the code-installation check, not the end-to-end connectivity investigation.

## Official references

[Microsoft Learn: Enable eSIM data connections in Microsoft Intune](https://learn.microsoft.com/en-us/intune/device-configuration/templates/enable-esim).

## Primary reference

- Name: Enable eSIM data connections in Microsoft Intune - Microsoft Intune | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/intune/device-configuration/templates/enable-esim
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Read eSIM activation status separately from carrier connectivity,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.