One Phone Number Can Now Move Between Two iPhones. BYOD Policy Needs to Catch Up.

Before today's new device releases, Apple made iOS 27 available with iPhone Handoff, a carrier-supported feature that lets one phone number operate across two iPhones. Only one device is active for that number at a time, and unlocking the other iPhone can make the number active there. Calls, voicemail, messages, and Find My location follow the device currently in use.

For enterprise mobility teams, that creates a state most BYOD and COPE records were not written to describe. The phone number can remain unchanged while the device currently receiving its calls, messages, and SMS recovery traffic changes during ordinary use.

Signals & Moves You Shouldn't Ignore

The active device can change during normal use

Apple's support documentation describes one iPhone as the main device and another as the secondary device sharing the number. Unlocking the device a user wants to use makes the number active there, while the other iPhone becomes inactive for the number. Apple displays a confirmation after the switch and says the number is active on only one iPhone at a time.

That creates a straightforward inventory problem. A record associating a corporate number with one managed iPhone can describe yesterday's state while still containing a valid device and a valid number.

Dual SIM can move while other device relationships stay put

Apple says that when both eSIMs are configured for iPhone Handoff on supported carriers, both lines switch together when the other iPhone is unlocked. Apple separately notes that some transit passes, IDs, and corporate badges may work on only one device at a time. Third-party applications can also maintain their own authentication and synchronization behavior.

One user action can therefore change the cellular state while other enterprise relationships remain associated with another device.

For a BYOD or COPE program, the phone number, managed-device record, application session, corporate credential, and recovery path should no longer be assumed to describe one synchronized state.

Part of the lifecycle remains with the carrier

Carrier participation is required. Apple's documentation says some carrier services and account management remain associated with the main iPhone. Turning Handoff off requires contacting the carrier, and deleting the eSIM may not terminate the underlying service. Apple currently lists T-Mobile in the United States and Telekom in Germany as supported carriers.

That creates an ownership boundary worth documenting. MDM can govern a managed device. IAM can govern an account. The carrier still controls part of the cellular enrollment and termination lifecycle.

The Control Gap

The missing record is the authoritative relationship between the purpose of a cellular line and the devices permitted to receive it.

MDM can establish the state of an enrolled device. A carrier can establish the cellular subscription. An application may continue trusting a phone number for account recovery. None of those records, by itself, necessarily establishes which devices the enterprise has approved to receive that number.

Handoff makes that distinction visible because the active cellular device can now change as part of normal use.

The same distinction is useful for temporary connectivity. A cellular profile can exist only to provide data transport. It does not inherently need to become another communications number or account-recovery relationship.

BYOD and COPE policy should therefore record two things explicitly:

• what the line is for
• which devices are permitted to receive it

That record should also identify the person authorized to change the relationship.

My Take

For traveling executives, my fellow digital nomads, contractors, visitors, and other temporary connectivity use cases, I generally prefer data-only service where the use case permits it because it is more simple, doesn't require handing over your passport and other PII that some vendor scans, and can be activated remotely. You're not trading convenience for a surveillance graph.

These users usually arrive with an established communications identity, anyway. Providing network connectivity for a trip or assignment does not require creating another phone number or another recovery relationship that someone has to govern later.

Handoff reinforces why I prefer those responsibilities separated. The primary phone number can have its own carrier controls, approved-device relationship, communications history, and recovery dependencies. A temporary data profile can be much simpler with a much more narrow job: Provide Connectivity for the period in which it is required.

We are not submitting to weak controls around authentication and governance. The primary phone number and its PII remains. A corporate number using Handoff still needs an owner, an approved-device record, a change process, and a tested removal path.

For temporary connectivity, I would keep the phone number where it already belongs and let the data connection change with the use case.

— William

One Thing Worth Doing This Week

Pick one executive or privileged mobile user and create a Line Purpose + Device Binding Record.

Start with five fields:

The record is complete when another security or mobility owner can answer those questions without reconstructing the relationship from MDM, carrier portals, application settings, tickets, and email.

The complete version adds the policy and termination fields needed to use this as a BYOD/COPE update rather than a one-time inventory exercise.

Download the Line Purpose + Device Binding Record →

Field Notes

I resell data-only eSIM connectivity over networks I do not own. For executive travel, contractors, and visitors, I have been tightening one boundary in that work: temporary connectivity stays data-only wherever the use case allows it, while the person's existing phone number remains with the carrier already responsible for it.

Handoff made the reasoning easier to explain. A change in country, network, trip, or assignment can require different connectivity without requiring the temporary service to become another communications or recovery identity.

I turned that distinction into this week's Line Purpose + Device Binding Record because I want the enterprise to see the relationship before changing its policy or technology. The useful first step is proving what already exists: which devices may receive the primary number, which profiles exist only for data, and who owns each decision.

Cleared Today

A standing section on third-party access. Part 1: the enterprise.

Conditional Access has no field for whether the contract is still active

Microsoft documents Conditional Access conditions around signals such as user and sign-in risk, network, device information, client applications, and authentication flows. Contract or assignment status is not one of the documented native conditions.

A contractor's identity can therefore remain valid and the device can remain compliant after the business authority behind the relationship has expired somewhere else.

That state may live in procurement, legal, vendor management, or the sponsoring business unit rather than in the identity system making the access decision. Travel makes the ownership gap easier to see because the person may be using a personal device and connectivity selected outside the enterprise.

The access system can continue evaluating the signals it was designed to evaluate without knowing whether that person still has authority to perform the task today.

I am going to follow that authority gap across different operating environments in the coming issues.

For one executive or privileged user, can your team produce every device permitted to receive the primary number and the person authorized to change that relationship without reconstructing the answer from several systems?

EVERY FRIDAY. SIGNALS. ONE CONTROL GAP. ONE ACTION.

Sources

• Apple Support. Set up iPhone Handoff. Published September 9, 2026.
• Apple. Apple debuts iPhone 18 Pro and iPhone 18 Pro Max. September 9, 2026. Apple says iOS 27 became available September 14 and introduces iPhone Handoff for supported carriers.
• Microsoft Learn. Conditional Access: Conditions. Microsoft's documented policy conditions and signals.

#MobileSecurity #CISO #BYOD #COPE #iPhone