The first promise of eSIM in IoT was simple: stop shipping plastic, stop swapping SIM cards in the field, stop deciding an operator relationship before a device even leaves the factory.

For anyone managing distributed fleets, that sounded like relief. A payment terminal crossing borders. A utility meter in a basement. Instead of sending someone with a packet of SIMs, enterprises could change connectivity remotely.

Reality became crowded.

Every operator added a portal. Every connectivity provider added a dashboard. Every CMP promised control. Every eSIM platform added another layer for profile management, diagnostics, billing, alerts or support tickets. Suddenly, the “simpler” model looked like the old telecom mess, only with nicer UX and more logins.

This is why the recent Thales and Simetric discussion around converged eSIM orchestration is interesting. It points to a bigger enterprise problem: eSIM solved the plastic SIM issue, but it did not automatically solve operational fragmentation.

The pilot was easy. The fleet was not.

Can the profile be downloaded? Can the device activate? Can it switch networks? Can we avoid physical SIM replacement? Valid questions. But not the questions that matter once thousands of devices are live.

At scale, the questions become messier. Which devices failed after the profile update? Which ones are roaming unexpectedly? Which carrier has issues in a specific region? Which profile change was manual, which was automated, and who approved it?

That is where the portal problem begins.

READ MORE: Why Enterprises Need Orchestration, Not SIM Cards

One portal tells you SIM status. Another shows network usage. Another holds billing. Another handles tickets. Another belongs to the regional operator. Everyone has “visibility,” but nobody has the same view of reality.

For a small fleet, that is annoying. For a large IoT deployment, it becomes a risk.

SGP.32 is important, but not magic.

The GSMA’s SGP.32 specification is a serious step forward because it was designed for IoT devices constrained by power, network conditions or limited user interfaces. GSMA describes it as covering remote provisioning and management of the eUICC in IoT devices, plus the architecture, interfaces and security functions used in the eSIM IoT architecture.

That matters because older eSIM models were not always comfortable for massive IoT. Consumer eSIM assumes a person with a phone, a screen and some patience. Industrial IoT often has none of those. A sensor in the field does not politely scan a QR code.

But a standard gives the industry a shared technical foundation. It does not automatically give an enterprise a clean operating model. Too many eSIM discussions treat SGP.32 as if it removes complexity by itself. It does not. It changes where the complexity goes.

Juniper Research expects eSIM-connected devices to grow from 1.2 billion in 2025 to 1.5 billion in 2026. It also highlights logistics, oil and gas, and smart street lighting as fast-growing IoT eSIM sectors, and warns that enterprise IoT needs a server-driven model where profiles can be pushed centrally rather than pulled one by one.

That is the difference between eSIM as a feature and eSIM as infrastructure.

The new control plane

One quote from Simetric’s Allen Boone captures the shift neatly: “eSIM is no longer just a provisioning function.” He describes it as the operational and security control plane for the network edge.

He is directionally right.

Enterprise eSIM now sits at the intersection of connectivity, security, compliance, device lifecycle management, procurement and customer experience. A bad connectivity decision can delay a delivery, interrupt a payment, disconnect a medical device, or force a router into manual intervention.

READ MORE: Enterprise eSIM: The Buyer’s Guide to Global Workforce Connectivity

This is why the “single pane of glass” idea keeps appearing. Simetric positions its platform above carriers, MNOs, eSIM platforms, physical SIMs, eSIM profiles and satellite connectivity. Transatel, an NTT company, has also been recognized in Counterpoint’s 2026 IoT eSIM Orchestration CORE Report, where orchestration is described as a critical control layer for managing profiles, automating network policies and maintaining service continuity.

The language varies, but the direction is the same. Enterprise buyers are no longer impressed by a dashboard simply because it exists. They want fewer dashboards. More precisely, fewer blind spots between them.

When “more control” creates less control

Here is the uncomfortable part: many providers solve the same pain by adding another interface.

A better operator portal is useful. A cleaner CMP is useful. A sharper eSIM management tool is useful. But if each layer only gives control inside its own walls, the enterprise still has to stitch the truth together manually.

This is where IoT teams quietly lose time: “can someone check the other portal?” moments, exports, tickets, Slack threads and regional exceptions that nobody documented.

READ MORE: Vodafone Launches SGP.32 eSIM for Global IoT

That does not mean every company needs full orchestration on day one. A small deployment in one country may be fine with an operator portal or solid CMP. Buying too much orchestration too early can become its own complexity.

But once a fleet crosses regions, carriers, device types or regulatory requirements, the calculation changes. Then the question is not “do we support eSIM?” It is “can we govern what happens after eSIM is deployed?”

The market is splitting

Thales brings the secure eSIM and remote provisioning foundation. Simetric brings the operational layer. Kigen is pushing eIM capability aligned with SGP.32. IDEMIA has announced a fully GSMA-certified SGP.32 eSIM IoT solution. G+D is positioning around eSIM IoT Remote Manager capabilities. Tele2 IoT, IDEMIA and Cisco have moved from theory to commercial SGP.32 architecture, combining certified eSIM, connectivity management and global connectivity.

The market is not waiting for one perfect platform. It is building a stack.

Some players will own the secure element and provisioning layer. Some will own the carrier relationship. Some will own CMP workflows. Some will sit above everything as orchestration. The enterprise challenge will be choosing a stack that simplifies operations, not one that merely transfers the mess to a different vendor.

For buyers, the smartest question is not “how many networks do you cover?” It is: “What happens when something goes wrong at scale, and how many systems do we need to open before we understand why?”

Conclusion about eSIM IoT management

eSIM was supposed to simplify IoT, and in one important sense, it has. It removed the absurdity of treating every connected object like a tiny mobile phone that needs a physical SIM decision before deployment.

But removing plastic did not remove operational complexity. It exposed it.

The next phase of enterprise eSIM will be less about whether profiles can be provisioned and more about whether connectivity can be governed. That favors orchestration players, but it also pressures traditional CMPs, operators, eSIM vendors and IoT MVNOs to become more interoperable, more transparent and less possessive about their own portals.

The winners will not be the companies shouting “single pane of glass” the loudest. Enterprises have heard that phrase before. The winners will be the ones that make the pane trustworthy: connected to the right systems, clear about why decisions were made, useful during failure, and boring enough to run every day without drama.

Because in IoT, the best connectivity platform is not the one everyone admires in a demo. It is the one nobody has to panic-open at 2 a.m.