Confirm a new browser or place

The sign-in moves to the Check your email screen. It says If this address can sign in, a message is on its way. Open the link in it, or enter the code from it below. The message is titled Confirm this sign-in to TDACorp Identity. It says that a sign-in looked different from your usual ones, and that if it was you, you should confirm it in the same browser, and if it was not, you should not confirm it. Its button reads Review this sign-in, and it carries an eight digit code as well as the link. This email is written in the language saved on your profile, otherwise in the language the application you were signing in to asked for, otherwise English. The English wording is quoted here; see Languages.

Opening the page changes nothing. Only one of the two buttons acts, so a mail scanner that opens the link on your behalf cannot confirm or refuse anything.

Instead of the link, you can stay on Check your email, type the eight digit code from the message in Code from the email and select Verify. Use the browser you started signing in from.

If you select No, this was not me, the sign-in that was waiting ends. If it is still open in the other browser, that page then shows This sign-in has ended with the reason You said it was not you, so it was stopped. If the person who started it was not you, consider changing your password, and look at your devices under Sessions and devices.

In some cases the platform does not offer a confirmation and stops the sign-in. The screen is titled Sign-in was refused and says This sign-in cannot continue., or a reason: This sign-in looks unusual, so we stopped it. Try again later, or recover your account if you cannot get in. when the check refused it, or Your account has no passkey or authenticator app, and the admin console, the application by name, or your organization needs one. (followed by Fastest way: recover your account. Nothing is set up yet, so there is no wait. Add a passkey or an authenticator app, finish, then sign in again.) when something demands a second factor the account does not have, and We have already sent the most emails allowed to this address for now, so we cannot send the confirmation message. Sign in with your password or a passkey, or try again later. (or, for the service-wide daily limit, We have reached the limit for sending email today, so we cannot send the confirmation message. Try again tomorrow, or recover your account.) when the confirmation message itself could not be sent. A correct password is not refused for being unusual: where the platform would otherwise ask for more than the password and nothing can answer, the sign-in goes ahead as a limited session with the sign-in alert email; see The second step. The refused screen's one button, Recover your account, starts account recovery. The other reasons are listed in Sign-in errors and what they mean.

A sign-in that follows the emailed code offered when a passkey is lost (see The second step) is not stopped for this confirmation, and it always sends the sign-in alert email afterwards. A sign-in that is judged too risky is still refused.

A device that you marked as trusted is not treated as new. A browser that only ever signed in with a password in a limited session stays untrusted until a sign-in that proved more than the password, such as a passkey, an authenticator code, or an emailed link or code, or a "Confirm it is you" with your second factor, makes it known. You manage trusted devices in your account. See Sessions and devices.

• The sign-in alert email, a different message about a sign-in that already happened
• Sign in with an emailed link or code