This setting allows users to complete device activation by entering a one-time passcode delivered via SMS. If a user has other identity verification methods registered, Salesforce automatically uses the strongest method available.
Step 1: Verify MFA Settings
Ensure Multi-Factor Authentication (MFA) settings in Salesforce allow SMS as an authentication method. This involves checking both the org-wide settings and any specific profiles or permission sets that might override default behaviors.
Step 2: Confirm User Phone Numbers
Make sure each user's profile has a correct and verified mobile phone number. A common oversight is missing or incorrect country codes.
Step 3: Explore Salesforce Authenticator App
If SMS remains non-functional due to Salesforce limitations or policy restrictions, pivot to recommending the Salesforce Authenticator app as a more reliable alternative for MFA. It provides a similar level of security without relying on SMS.
Step 4: Contact Salesforce Support
If initial troubleshooting does not resolve the issue, contact Salesforce Support for deeper insights. Provide them with specific examples of the issue, including any error messages users receive and steps already taken to resolve the problem.
Step 5: Communicate with Users
Keep users informed about the issue and the steps being taken to resolve it. Offer clear instructions for alternative authentication methods to ensure uninterrupted access.
By focusing on these steps, you can effectively manage situations where the SMS method for device activation is disabled, ensuring users have secure and reliable access methods available.
This setting allows users to complete device activation by entering a one-time passcode delivered via SMS. If a user has other identity verification methods registered, Salesforce automatically uses the strongest method available.
Step 1: Check MFA Configuration
Ensure Multi-Factor Authentication (MFA) is configured correctly in your org. This includes verifying that SMS-based authentication is enabled if Salesforce supports it for your use case.
Step 2: Review User Record Configuration
Ensure that user records are properly configured with correct mobile phone numbers. This is crucial for SMS-based MFA.
Example:
List<User> users = [SELECT MobilePhone FROM User WHERE IsActive = true];
for (User u : users) {
if (String.isBlank(u.MobilePhone)) {
System.debug('User with ID ' + u.Id + ' does not have a mobile phone number set.');
}
}
This Apex script could help identify users without mobile phone numbers in their records, which is a prerequisite for receiving SMS messages.
Step 3: Custom Notification Solution
If direct SMS method configuration is an issue due to Salesforce limitations or policy settings, consider implementing a custom solution for notifications using third-party SMS services like Twilio or AWS SNS.
Step 4: Implement a Custom Authentication Flow
If SMS is critical for your authentication process and Salesforce's standard functionality is limited, develop a custom authentication flow that incorporates SMS verification through an external service.
Step 5: Test and Deploy
Thoroughly test your custom solution in a sandbox environment to ensure it meets security and functional requirements before deploying it to production.
Step 6: Document and Train
Ensure that all relevant documentation is updated to reflect the new process or workaround. Provide training for end-users if the process for device activation or authentication has changed significantly.
By following these steps, you can address the disabled SMS method for device activation, either by ensuring correct configuration within Salesforce or by implementing a custom solution. Remember, any custom solution should prioritize user security and comply with Salesforce development best practices.
