How to Enable 2FA for Company Email in the Right Order
Learn how to audit email accounts, choose suitable authentication methods, pilot 2FA with administrators, expand by department, and prepare backup codes and phone-loss recovery procedures.
Two-factor authentication adds a second verification step alongside the password, which reduces risk when email login details are exposed in an incident. However, turning it on for everyone without preparing verification methods and recovery options can lock staff out of their accounts and interrupt work. Businesses should roll it out in a fixed order: review the accounts, choose suitable methods, test with the administrative group, and only then expand to other departments. Backup codes and a process for a lost phone must be prepared in advance, not discussed after an incident occurs.
Review accounts and how they currently sign in
The person responsible should build a list of email accounts, including administrative accounts, shared mailboxes, staff accounts, and accounts used by software. For each account, record the owner, the devices currently in use, and which applications connect to the mailbox using the email password. Automated sending applications may not support an additional verification step, so they must be checked separately before the policy is applied.
Next, identify the high-privilege group and the group that changes phones or computers often. Also choose a contact channel that is independent of company email, to support users who cannot sign in. The pilot round should have an administrator monitoring directly, recording errors as they arise, and guiding users through each step.
Choose a method that suits people who change devices often
Do not apply a single method to everyone when device conditions differ. Authenticator apps suit most staff because the codes are generated on the phone itself and do not depend on mobile signal or network coverage. Hardware security keys suit administrative accounts or people who need to sign in from several machines, but the rules for issuing, handing over, and revoking them must be explicit.
- People who rarely change devices: an authenticator app on the phone, with backup codes stored outside the device.
- People who change devices often: consider a security key or a method with a device-transfer mechanism controlled by the business. Before switching, register the new device, test signing in, and only then remove the old one.
- People without a personal phone: do not require personal accounts or codes sent to someone else’s number; provide a shared device with clearly assigned responsibility.
Codes sent by SMS should be treated as a fallback only, used when the system and the practical conditions do not allow any other option. Whichever method is chosen, test the device-transfer process on a test account, and do not assume authentication data will follow automatically to a new phone.
Enable it for the administrative group first, then the rest
The administrative group should register two-factor authentication first, because this group can change policies and support recovery. Each administrator must complete registration, sign out, sign in again, and test on both a browser and the email application in use. Then test revoking a sign-in session on one device to make sure the person responsible knows the steps during an incident.
Once the process runs smoothly, expand department by department. Send instructions in advance, stating the effective date, the supported methods, and the contact point when an account is locked. Do not set the mandatory date at the point when staff are busy handling important work. After each round, administrators should check accounts that have not registered and handle each exception individually instead of switching off the policy for everyone.
Prepare backup codes and a process for a lost phone
Backup codes should be generated at the moment two-factor authentication is registered. Users should store them in a business-managed password vault or in a securely kept paper copy; not in the mailbox being protected, not as a photo on the same phone, and not shared through group chat. For administrative accounts, add an emergency access option with separate permissions and monitoring, so that all recovery capability does not depend on one person.
The lost-phone process should be written as concrete steps:
- The user reports the loss through the designated channel; the administrator verifies identity using existing records or an independent channel, not a single message.
- Revoke sign-in sessions and disable the verification method tied to the lost device.
- Restore access using a backup code or an approved alternative method, and limit the use of temporary passwords sent through poorly controlled channels.
- Register the new device, regenerate backup codes if the old ones were used or may be exposed, and record the incident for review.
What to do now
- List administrative accounts, shared mailboxes, and applications that sign in with email.
- Choose a small group to test registration, device transfer, and recovery before wider rollout.
- Issue written guidance on storing backup codes and the process for reporting a lost phone, with a clear contact point.
Two-factor authentication only delivers value when everyday sign-in and account recovery have both been tested in advance. VASCOM can help businesses review their current setup and build a rollout sequence that fits actual working practices.