{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/", "item": { "id": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/", "slug": "dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity", "url": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity.md", "json": "https://update.dsesecurity.com/api/v1/posts/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/" }, "title": "Read eSIM activation status separately from carrier connectivity", "summary": "Does Active in Intune prove that an imported-code eSIM has working cellular service?", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-09-10T00:22:08+00:00", "modified_at": "2026-09-10T02:14:31+00:00", "reviewed_on": "2026-09-09", "reading_minutes": 2, "word_count": 222, "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.", "primary_source": { "name": "Enable eSIM data connections in Microsoft Intune - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-configuration/templates/enable-esim", "published_on": null, "authority": "Microsoft Learn" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Source facts

\n

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.

\n

Applicability

\n

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.

\n

DSE recommendation

\n

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.

\n

Verification

\n

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.

\n

Official references

\n

Microsoft Learn: Enable eSIM data connections in Microsoft Intune.

", "content_text": "Source facts\nIntune’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.\nApplicability\nLimit 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.\nDSE recommendation\nGive 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.\nVerification\nCompare 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.\nOfficial references\nMicrosoft Learn: Enable eSIM data connections in Microsoft Intune.", "content_markdown": "## Source facts\n\nIntune’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).\n\n## Applicability\n\nLimit 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.\n\n## DSE recommendation\n\nGive 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.\n\n## Verification\n\nCompare 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.\n\n## Official references\n\n[Microsoft Learn: Enable eSIM data connections in Microsoft Intune](https://learn.microsoft.com/en-us/intune/device-configuration/templates/enable-esim)." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/", "url": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-09-09" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Read eSIM activation status separately from carrier connectivity", "item": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/#article", "identifier": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/", "url": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/", "headline": "Read eSIM activation status separately from carrier connectivity", "description": "Does Active in Intune prove that an imported-code eSIM has working cellular service?", "abstract": "Does Active in Intune prove that an imported-code eSIM has working cellular service?", "articleBody": "Source facts\nIntune’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.\nApplicability\nLimit 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.\nDSE recommendation\nGive 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.\nVerification\nCompare 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.\nOfficial references\nMicrosoft Learn: Enable eSIM data connections in Microsoft Intune.", "datePublished": "2026-09-10T00:22:08+00:00", "dateModified": "2026-09-10T02:14:31+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/dse-20260909-588-read-esim-activation-status-separately-from-carrier-connectivity/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Read eSIM activation status separately from carrier connectivity" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 222, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Enable eSIM data connections in Microsoft Intune - Microsoft Intune | Microsoft Learn", "url": "https://learn.microsoft.com/en-us/intune/device-configuration/templates/enable-esim" } } ] } }