Authenticator App for Outlook Setup and Sign-In

Which Authenticator App Outlook Uses

The official authenticator app for Outlook accounts is Microsoft Authenticator. Outlook uses the security settings of the Microsoft account behind the email address, so setup does not normally happen inside the Outlook mailbox.

First identify the account type. An address you created for personal email uses a personal Microsoft account. An address supplied by an employer or school uses a work or school account, and its available sign-in methods are controlled by that organization.

Some organizations permit another standards-based authenticator app, but Microsoft Authenticator is the normal option for approval notifications and passwordless Microsoft sign-in. Follow the method displayed in your account’s security settings.

Set Up the Authenticator App for Outlook

Install Microsoft Authenticator from your phone’s official app store. Have your phone and another screen ready because the QR code must remain visible while you scan it.

For a personal account:

1. Sign in to your Microsoft account and open the Security section.
2. Choose the option for managing how you sign in, then add a new way to sign in or verify.
3. Select the option to use an app. Continue until a QR code appears.
4. Open Authenticator, select the plus sign, choose Personal account, and select Scan a QR Code.
5. Scan the code displayed by Microsoft and complete the test or approval request shown on the screens.

For a work or school account, open its Security info page after signing in. Select Add sign-in method, choose Microsoft Authenticator, and continue until the QR code appears. In the app, select the plus sign, choose Work or school account, and scan the code.

Allow camera access for scanning and notifications for approval requests. If scanning fails, use the “can’t scan” choice shown during setup and follow Microsoft’s on-screen manual-entry instructions. Do not scan a QR code sent unexpectedly in email or chat.

Approve an Outlook Sign-In

Enter your Outlook email address on the genuine Microsoft sign-in screen and continue. If necessary, select Other ways to sign in and choose the option to approve a request in Microsoft Authenticator.

Open the notification or open Authenticator directly. Confirm that the account and sign-in details match the attempt you just started. Microsoft may display a number on the sign-in screen and ask you to enter or select it in the app. Complete any requested phone unlock, PIN, or biometric check, then approve.

Never approve a request you did not start. Reject it instead, then review the account’s recent sign-in activity and change the password if the attempt looks suspicious. Never give an Authenticator code to someone who contacts you.

Sign In Without an App Notification

An approval notification requires an internet connection, but it can arrive over Wi-Fi; the phone does not need mobile data. Turn off Airplane mode, connect to working Wi-Fi, and open Authenticator manually because the request may be waiting without an alert.

If the sign-in page offers Other ways to sign in, select it. Depending on methods already registered and the organization’s policy, choices may include a code generated in Authenticator, a code sent by text or email, a security key, or another approved method.

A changing verification code displayed in Authenticator can generally be read without mobile data. Enter the code for the correct account before it changes. Alternative methods appear only if they were previously added or permitted; their absence is not an error and should not be bypassed.

Move Outlook Authentication to a New Phone

Keep the old phone until the new one successfully approves a test sign-in. Adding Outlook to the new phone or restoring the phone itself does not guarantee that authentication registration will transfer.

1. While you can still sign in, add another recovery method in the account’s security settings.
2. Use Authenticator’s backup feature if appropriate. A restore works only between the same device platform, and restored entries may still require verification.
3. On the new phone, restore the Authenticator backup or add the account again from its Security or Security info page.
4. For a restored work or school account, sign in again or scan a new QR code when the app says action is required.
5. Test a sign-in on the new phone. After it works, remove the old phone’s Authenticator registration from the account’s security information.

If you are moving between different phone platforms, plan to register accounts again. A backup does not copy Outlook email or files, and organizational policy may require an administrator-approved registration.

Recover Access When the Authenticator App Is Unavailable

On the sign-in screen, select Other ways to sign in and use a recovery method you previously registered. This might be another email address, text verification, a security key, a recovery code, or another signed-in device.

For a personal Microsoft account, use Microsoft’s official account recovery process if no registered method is available. Find it through Microsoft Support or the recovery option on the Microsoft sign-in screen. Supply accurate account information; do not pay anyone or share passwords or verification codes for “recovery.”

For a work or school account, contact your organization’s help desk or account administrator. The administrator may need to clear the old authentication registration, issue an approved temporary sign-in method, or require you to register again. Microsoft cannot substitute personal recovery answers for an organization’s security policy.

Fix Common Authenticator Problems

• Missing prompts: Open Authenticator manually. Check Wi-Fi or mobile data, Airplane mode, Do Not Disturb, notification permission, and battery restrictions. Update the app and phone, then retry.

• Rejected or expired approvals: Start a fresh sign-in and respond only to that request. Unlock the app and complete number matching exactly as displayed.

• Wrong account: Check the email address on both screens. Personal and organizational accounts with similar names are separate entries.

• Codes fail: Set the phone’s date and time to update automatically. Use the current code from the correct account before it changes.

• Prompts reach an old phone: Register the new phone, test it, and remove the old registration from Security info. Ask an administrator if organizational controls prevent changes.

• Repeated sign-ins: Finish all prompts, allow required cookies in the browser, and check whether your organization requires frequent verification. If the loop continues, remove and re-add the Authenticator method only after confirming another recovery method works.