--- schema_version: "1" id: 6ef6241aeb5e0c43cbfeb371c87ba38db44cec6677e624c1f3cf8161bd16019a title: Test Your MFA Implementation for Salesforce Orgs collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/mfa_test.md canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.mfa_test.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: eff4951820d849c3416deec7b80928463f4ae9e2ae47c005cc98d60778236923 description: If you test MFA ahead of time, you gain experience with the MFA registration process and can assist users with login issues. Even if Salesforce automatically enabled MFA for your existing org, it’s beneficial to evaluate how things work in a test environment. products: - Security release: "264" --- # Test Your MFA Implementation for Salesforce Orgs If you test MFA ahead of time, you gain experience with the MFA registration process and can assist users with login issues. Even if Salesforce automatically enabled MFA for your existing org, it’s beneficial to evaluate how things work in a test environment. ### Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: all editions
![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-security-264-0-0-production-enus/8cecd769-ab2d-4e07-addf-c4f2927925e1/images/icon_important.png) Important Salesforce enforces MFA requirements in the summer of 2026. See these articles for more information and detailed rollout timelines. - [Prepare for MFA Enforcement for All Employee Users](https://help.salesforce.com/s/articleView?id=005321561&type=1&language=en_US). - [Prepare for Phishing-Resistant MFA Enforcement for Privileged Users including Admins](https://help.salesforce.com/s/articleView?id=005321563&type=1&language=en_US). ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-security-264-0-0-production-enus/8cecd769-ab2d-4e07-addf-c4f2927925e1/images/icon_note.png) Note To make sure that you keep access to your test environment, don't use your admin account for MFA testing. When MFA is enabled for your test environment, log in as a test user and complete the registration process for each of the verification methods that you support. See [MFA Verification Methods for Direct Salesforce Login](https://help.salesforce.com/s/articleView?id=xcloud.mfa_supported_verification_methods.htm&release=264.0.0&type=5 "The multi-factor authentication (MFA) login process requires users to provide an identity verification method in addition to their username and password. Salesforce MFA functionality supports several types of verification methods, including passkeys (built-in authenticators and security keys) and authenticator apps. You can control which methods are available to your users."). Then log out and log in again to confirm that the methods are working as expected. It’s also a good idea to test access recovery options so that you’re prepared to help if a user loses or forgets their verification method. See [Resolve MFA Access Issues for Your Users (Salesforce Orgs)](https://help.salesforce.com/s/articleView?id=xcloud.mfa_access_recovery.htm&release=264.0.0&type=5 "As a Salesforce admin, part of your role is managing and maintaining user access. With multi-factor authentication (MFA) in effect for your org, it’s important to know how to resolve MFA-related access issues that users can encounter. There are three likely scenarios. A user doesn’t have access to their MFA verification method and can’t log in. A user loses or replaces a verification method and must register a new one. And the connection between a user’s registered verification method and their Salesforce account stops working. Use temporary verification codes to allow users to regain access immediately. When dealing with a broken connection or a missing verification method, revoke the connection and help the user set up a new method."). #### See Also - [Support Your Multi-Factor Authentication Implementation for Salesforce Orgs](https://help.salesforce.com/s/articleView?id=xcloud.mfa_support_users.htm&release=264.0.0&type=5 "After multi-factor authentication (MFA) is enabled, it introduces some new admin responsibilities to support users and maintain operations. Common tasks involve helping users solve verification method or authentication issues, including account lockouts. It’s also valuable to monitor MFA usage patterns over time for insights such as the most and least used verification methods, or recurring login problems. And consider MFA optimizations that can improve the user experience. Need help? You can assign MFA management permissions to trusted users.") - [Disconnect Identity Verification Methods that are Lost, Replaced, or Not Working (Salesforce Orgs)](https://help.salesforce.com/s/articleView?id=xcloud.security_disconnect_verification_methods.htm&release=264.0.0&type=5 "When addressing multi-factor authentication (MFA) access issues, there are situations where a Salesforce admin must disconnect a user’s current verification method from their Salesforce account. This step is necessary if a user has lost their method, or has acquired a replacement method that they want to use instead of their current one. If a user’s method stops working, disconnecting it allows the user to re-register the method and restore its connection to their account. It’s also a good practice to disconnect all of a user’s verification methods if they leave your company.") - [Multi-Factor Authentication Considerations for Sandbox Environments](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_mfa.htm&type=5&language=en_US)