Last updated: August 2026
Choosing connectivity for an Internet of Things (IoT) product is rarely a one-time decision. Devices may remain in the field for many years, while networks, markets, providers, and regulatory requirements change around them.
An eSIM is a SIM solution based on an eUICC that supports secure remote provisioning and management of mobile operator profiles. This means a compatible connectivity profile can be downloaded or changed without replacing the physical SIM.
The terminology can be confusing because eSIM is also commonly used to describe a SIM that is physically embedded or soldered into a device. Physical form factor and remote profile management are separate concepts. A soldered SIM does not necessarily support remote profile management, and eSIM technology is not limited to one physical SIM form factor.
For IoT products, this means connectivity can be less dependent on decisions made at manufacturing and adapted later in the device lifecycle.
Learn more about the terminology and specifications from the GSMA, the global mobile industry association.
An eUICC is a UICC that securely supports the storage and management of mobile operator profiles, including remote profile provisioning.
The “embedded” in eUICC does not mean that it must be soldered into a device. eUICC describes a capability rather than a physical SIM form factor.
Put simply: eSIM is the broader technology and industry term, while the eUICC is the secure SIM component that enables remote profile management.
The Trusted Connectivity Alliance provides a useful industry explanation of the relationship between eSIM, eUICC, and physical SIM form factors.
An operator profile contains the subscription credentials, applications, and related configuration that allow a device to authenticate and connect to a mobile network.
An eUICC can securely store multiple operator profiles. How those profiles are downloaded, enabled, or changed depends on the remote SIM provisioning architecture and the specific deployment setup.
eSIM and eUICC are closely related, but they do not mean the same thing. It is also important to separate both terms from the physical form of the SIM.
| Feature | What It Describes | Example |
|---|---|---|
| Physical form factor | How the SIM is physically implemented | Removable SIM or soldered MFF2 |
| UICC / eUICC | The secure SIM component and its capabilities | UICC or eUICC |
| Operator profile | Subscription credentials and related configuration | Global or local operator profile |
| Remote SIM provisioning | Secure remote download and management of profiles | Downloading or managing a profile |
| GSMA architecture | How remote provisioning is implemented | SGP.02, SGP.22 or SGP.32 |
Machine-to-Machine Form Factor 2 (MFF2) is a specific physical SIM form factor designed for machine-to-machine applications. It describes how the SIM is physically implemented, not whether it supports remote profile management.
An eUICC, by contrast, describes a UICC with remote profile provisioning and management capabilities.
Not every IoT deployment needs remote profile flexibility. Its value increases when connectivity decisions made today may need to change during the lifetime of the device.
eSIM and eUICC are particularly relevant when:
The device, module, eUICC, and provisioning architecture must all support the intended setup. These decisions are therefore best considered before hardware design is finalized rather than after devices are already in the field.
This means SIM form factor, eUICC support, module compatibility, and remote SIM provisioning architecture should be considered as separate parts of the device design.
This flexibility is particularly valuable for long-lived devices, hard-to-access assets, and products deployed across changing markets.
Utility meters, vehicles, industrial equipment, infrastructure, and other remotely deployed devices may be difficult or costly to reach.
If the connectivity setup needs to change, remote profile management can reduce the need for physical SIM replacement and field intervention.
IoT products can remain in service for ten years or more. Over such a long lifecycle, the connectivity assumptions made at deployment may no longer remain valid.
eUICC reduces dependency on the initial operator profile by keeping open the option of introducing another compatible profile later.
Devices can be manufactured and tested with initial connectivity while another profile is provisioned later, once the final market or connectivity requirement is known.
This can support a single stock-keeping unit (SKU) strategy, reducing the need for different product variants purely because of SIM or subscription requirements.
It does not guarantee that one hardware variant can work globally. Frequency bands, module capabilities, certifications, regulatory requirements, and other hardware considerations may still require regional variants.
An eUICC can provide the technical option to introduce another compatible operator profile if connectivity requirements change.
This may be useful when entering new markets, changing connectivity providers, responding to new commercial conditions, or introducing local connectivity where required.
Not every IoT deployment needs remote profile flexibility. It becomes more relevant when the answer to one or more of these questions is yes:
The device, module, eUICC, and provisioning architecture must all support the intended setup. These decisions are therefore best considered before hardware design is finalized rather than after devices are already in the field.
eSIM does not replace IoT roaming. The two solve different problems.
Roaming allows a device to use its existing operator profile and subscription to access another mobile network.
Profile switching changes the operator profile or subscription itself.
For many global IoT deployments, roaming provides connectivity across multiple markets without requiring a separate local subscription everywhere. eSIM and eUICC add the option to introduce another profile later if requirements change.
For example, a deployment might use a global roaming profile across many markets and introduce a local profile where regulatory, commercial, or connectivity requirements make that appropriate.
Remote profile capability does not itself provide local operator agreements, regulatory compliance, or commercial access. Those requirements still need to be managed.
Learn more: How SGP.32 Works With Global Roaming and Local Profiles
GSMA remote SIM provisioning architectures have evolved to support different types of connected devices and use cases.
| Standard | Primary Role |
|---|---|
| SGP.02 | Earlier remote provisioning architecture developed for machine-to-machine deployments |
| SGP.22 | Consumer eSIM architecture used for smartphones and other consumer devices |
| SGP.32 | IoT-specific architecture designed for remote profile management in IoT devices |
SGP.32 is a current IoT technology rather than a future concept. Telenor IoT began commercial delivery of SGP.32 capabilities in April 2026. The architecture is designed to make remote profile management more practical for IoT devices, including devices with limited or no user interface.
Learn more: SGP.32 for IoT
For additional background on eUICC deployments, download Telenor IoT’s 2023 guide. The guide predates the current SGP.32 landscape, and some eSIM terminology has evolved since publication. For current definitions and guidance, refer to this page.
Choosing an eUICC is only one part of the deployment. The device, provisioning architecture, profiles, target networks, and operating model all need to work together.
Confirm that the hardware and firmware support the required eUICC capability and remote SIM provisioning architecture. If SGP.32 is part of the roadmap, compatibility should be considered before the hardware design is finalized.
Decide whether a removable or soldered SIM best fits the device design and operating environment. The physical form factor does not determine whether remote profile management is supported, so evaluate eUICC capability separately.
Review where the product will operate and how connectivity requirements vary between markets. Roaming availability, local connectivity requirements, telecom regulation, certification, and other conditions can affect the connectivity model.
Confirm which GSMA remote SIM provisioning architecture the deployment will use and whether the required operator profiles are available through that setup. Technical support for remote provisioning does not automatically mean that every operator profile is available in every market.
Define how the device will connect during manufacturing, testing, first deployment, and any later profile change. The device needs a reliable initial connectivity path because remote profile management depends on communication with the required provisioning infrastructure.
Define who will manage profiles after deployment and how connectivity changes will be handled over the expected device lifetime. Because eSIM and eUICC are intended to support lifecycle flexibility, the operational model also needs to support the expected product lifetime.
Test profile changes and device behavior before large-scale rollout.
Relevant scenarios can include module compatibility, network selection, fallback behavior, profile changes, and how the device recovers if connectivity or provisioning does not behave as expected.
The Telenor IoT Test Lab can be used to validate these scenarios as part of the complete device and connectivity setup before large-scale deployment.
Not exactly. eSIM is the broader industry term for a SIM solution based on an eUICC that supports remote profile provisioning and management. eUICC describes the secure SIM capability that enables those profiles to be stored and managed.
No. Physical form factor and eUICC capability are separate. MFF2, for example, is a solderable SIM form factor, while eUICC describes profile-management capability.
No. Roaming allows the existing operator profile to access other networks, while eSIM and eUICC make it possible to change the profile itself. The two can work together in a global IoT connectivity strategy.
The right eUICC, operator profile strategy, remote SIM provisioning architecture, and connectivity model depend on the device, target markets, and expected product lifecycle.
Telenor IoT can support the planning and validation of eSIM and eUICC deployments as part of managed global IoT connectivity, including profile strategy, roaming and local connectivity requirements, testing, and lifecycle planning.
Managed IoT connectivity for enterprises operating across markets and large-scale deployments, with operational oversight and lifecycle support built in.
Global vehicle connectivity with built-in compliance and support for software-defined vehicles, helping car manufacturers deliver connected services at scale.
Devices, SIMs, and data management in one service, supporting connected products from launch to scale without building your own IoT stack.