Buying a new phone should not turn into a conversation with your employer’s IT department. Yet that’s exactly the sort of nonsense you can run into with Okta Verify.

And Kohl’s associates have actually dealt with it.

Back in August 2025, someone in the Kohl’s employee community asked how to set up Okta on another device. Their previous phone had stopped working, so transferring things the usual way wasn’t an option.

The advice was remarkably short: submit a ticket through Evan.

The associate later confirmed that the request had gone through and approval was all they needed.

Not a particularly dramatic story. But it exposes one of those little problems with workplace authentication that nobody thinks about until they’re staring at a verification screen they can’t get past.

The Phone Number Isn’t the Important Part

This catches people off guard.

Okta Verify doesn’t simply recognize your phone number and decide everything is fine. Its authentication setup is associated with the registered device.

That means restoring your apps from an iCloud or Android backup doesn’t necessarily restore a working Okta Verify account.

You can have the same number, the same Apple ID, the same applications, and still be unable to approve a sign-in.

The old device was trusted. The replacement hasn’t been enrolled yet.

Okta’s own documentation confirms that replacing a phone can require re-enrollment. That’s not some peculiar Kohl’s-only restriction.

And reinstalling Okta Verify over and over isn’t going to magically recreate a device registration that’s no longer valid.

What Actually Makes a Difference?

There are three situations worth separating.

You still have the original phone.

Okta supports transferring an existing Verify account between devices using Bluetooth, provided the relevant setup and organizational configuration allow it. This is the situation you’d rather be in.

The old phone is gone, but another verification method works.

Okta can allow users to register a replacement device through their account settings. Depending on the organization’s configuration, the relevant area may be called Security Methods or Extra Verification.

That doesn’t mean every Kohl’s associate has those options available. Okta administrators decide which authentication methods and self-service features are enabled.

The old phone is dead and there’s no other usable method.

Now the problem belongs to the organization’s support process. Okta specifically directs locked-out users to their IT team for an authentication reset.

This is the situation closest to the August Kohl’s discussion, where the associate needed a ticket and approval.

There’s Also the Password Problem

A separate Kohl’s discussion from October 2025 involved someone who couldn’t get into UKG Pro.

Another associate suggested checking whether the password had expired and described using MyKohls → OKTA → IdentityNow to manage password changes.

That’s an important distinction.

IdentityNow password management and Okta Verify device enrollment are not the same operation. Resetting a password doesn’t automatically establish trust in a replacement phone.

I can see why people confuse them, though. Both problems ultimately look like the same thing from the outside: you can’t get into your work applications.

And the average retail associate shouldn’t need to know the difference between an expired password, a locked account, and an invalid authentication device just to understand who can fix the problem.

One Thing I’d Do Before Replacing a Phone

Check whether your current Okta setup has another usable verification method. If your organization supports device transfer, arrange it before wiping or trading in the old phone.

Not after.

Once the old device is gone, your available options may be much narrower.

The actual authentication technology makes sense. A random replacement phone shouldn’t automatically inherit access to workplace applications simply because somebody knows the username.

But there’s a practical difference between strong security and leaving people confused about how to recover their own accounts.

Kohls Okta is part of a much larger workplace application setup. When access fails, it can affect more than one tool, and the person dealing with it may not even know which system is responsible.

That’s why the small August support-ticket discussion says more to me than another glossy explanation of single sign-on.

The associate didn’t need a lecture about identity management.

They needed their new phone recognized so they could get back into their work tools.

And thankfully, in that particular case, approval resolved it.