The new phone is set up, everything else came across, and now Microsoft is asking for a code that only exists on the old phone. This one catches everyone. The Authenticator app often does not survive a phone-to-phone transfer, and even when the app is there, the work account inside it frequently is not. Nothing is broken and nothing is lost.
If the old phone still turns on, even without a SIM card, this is the easy path. Put it on wi-fi, use it to approve one sign-in on your computer, and then go straight to aka.ms/mfasetup and add the new phone as a sign-in method while you are signed in. Then remove the old phone from the list. Five minutes and you are done.
This only works if you previously added a mobile number or a second method. If you did, you can sort this out yourself right now.
Then you need us, and that is fine - it is one of the most common tickets we get, particularly in the weeks after a new phone comes out. Log a ticket or ring 03 9028 4358.
Before we reset it, we will check that you are you. That is usually a call back on a number we already hold for you, or a quick confirmation from your manager or a director. We do this every time, for everyone, without exception.
It is worth knowing why, because it is the same check working in your favour. If someone can ring an IT company, say they have a new phone, and get the second factor reset, then the second factor protects nothing at all. Business email compromise very often starts with exactly that phone call. The two minutes we spend confirming it is really you is the thing standing between an attacker and your mailbox.
Once verified, we clear the old method and send you a link to register the new phone. Registering the new phone then takes you a couple of minutes.
Log a ticket at portal.yougrowit.com.au or email support@yougrowit.com.au. If it is stopping you working right now, call 03 9028 4358.
Support hours are Monday to Friday, 8:30am to 5:30pm Melbourne time, excluding Victorian public holidays.