This article explains why the Identity Verification code is not sent to your email address when adding a new Multi-Factor Authentication (MFA) verification method in Salesforce and how to use the existing, connected method to complete the verification. This is the expected behavior when a stronger verification method, such as Salesforce Authenticator, is already connected.
Scenario: You're logged into Salesforce and want to add a security key as a backup verification method. You click to add the new method, but instead of receiving an email with a verification code, you see a prompt to approve via Salesforce Authenticator.
This is the expected behavior when a verification method, such as Salesforce Authenticator, is already connected. The identity verification code will not be sent to your email address; instead, the existing, stronger verification method will be used preferentially.
Resolution Steps
Reference:
Can users register Multiple Verification Methods for MFA?
000395169

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.