Notifications
Clear all
Topic starter
14/07/2026 4:26 pm
TL;DR: eSIM-capable device shipments are forecast to exceed six billion between 2024 and 2028, while global IoT eSIM connections are expected to rise from 165 million in 2024 to nearly 1.3 billion in 2028, according to Counterpoint Research and Juniper Research. Scale is now a lifecycle and delegation problem, not just a connectivity one.
NHIMG editorial — based on content published by Workz Group: How telcos can implement eSIM IoT
By the numbers:
- 2024 and 2028., billion eSIM-capable devices will be shipped between 2024 and 2028.
- 10 cellular devices shipped in 2030 will have, d in 2030 will have eSIM.
- The number of global IoT eSIM connections will increase by almost 700%, from 165 million in 2024 to nearly 1.3 billion in 2028.
Questions worth separating out
Q: How should telcos govern eSIM IoT profiles at scale?
A: Telcos should treat eSIM profiles as governed lifecycle objects, not one-time provisioning records.
Q: Why do delegated eSIM channels create governance risk?
A: Delegated channels create risk when partners can provision widely without clear scope, logging, and revocation.
Q: How do organisations know if eSIM onboarding controls are actually working?
A: They know the controls are working when successful activations remain high but suspicious activations, repeated provisioning attempts and profile anomalies stay low.
Practitioner guidance
- Implement device-state-driven profile matching Automate profile assignment, replacement, and retirement based on device capability, location, and network requirements rather than manual selection.
- Bound delegated administration for distributors Create explicit delegation scopes for OEMs, aggregators, and regional partners, with revocation paths, logging, and periodic review of authority.
- Centralise multi-channel telemetry and inventory state Use one orchestration layer to track allocation, delivery, shortage signals, and lifecycle status across all channels and geographies.
What's in the full article
Workz Group's full article covers the operational detail this post intentionally leaves for the source:
- A practical implementation view of GSMA SGP.32-compliant eSIM IoT platform design for telco operations.
- How intelligent profile matching and delivery work across consumer, OEM, enterprise, and aggregator channels.
- The operational role of the eIM component in bulk push and pull profile management.
- Why real-time inventory tracking changes the economics of stockouts and delayed provisioning.
👉 Read Workz Group's analysis of how telcos can implement eSIM IoT →
eSIM IoT at scale: what profile lifecycle controls do telcos need?
Explore further
14/07/2026 4:33 pm
eSIM IoT should be treated as credential lifecycle governance, not device logistics. The article is really about managing a high-volume identity substrate for devices, partners, and channels. When profiles are distributed, updated, and retired without strong orchestration, the organisation inherits the same control problems seen in NHI environments. The practitioner conclusion is to govern eSIM profiles with lifecycle discipline, not ad hoc provisioning.
A question worth separating out:
Q: Who remains accountable when distributors manage eSIM provisioning?
A: The telco remains accountable for the control model, even when operational tasks are delegated. Distributors can execute provisioning, but the telco must define authority, review access, preserve logs, and enforce offboarding. Delegation without accountability creates the same governance gap seen in weak privileged access management.
👉 Read our full editorial: eSIM IoT scale exposes telco profile lifecycle and delegation gaps
