How to Set Up Two Factor Authentication for a Managed Account
To set up two-factor authentication for a managed account, choose a method approved by the organization, confirm that recovery is ready, register the factor and test a new sign-in. Keep the existing access method until the new one and the recovery route have been confirmed under the service’s rules.
The answer to how to set up two factor authentication depends on the service and its administrator’s policy. A work account may offer a security key, an authenticator application or another approved method. The following sequence provides a practical framework; follow the organization’s enrollment instructions when screens or requirements differ.
Choose a method and prepare recovery
Sign in through the organization’s normal portal on a trusted device. Open the account’s security or sign-in methods page and review the choices available for that account. Select the strongest method the organization supports for the service and the user’s working conditions. Where supported and approved, a FIDO security key offers phishing-resistant authentication. Authenticator codes and push approvals can provide additional protection but are not inherently phishing-resistant. CISA explains these distinctions in its phishing-resistant MFA guidance. Accessed November 19, 2026.
Before enabling a new two-factor authentication method, establish what happens if the device or key is lost. An organization may allow a second registered security key or another approved method; another may require a help-desk identity check. Confirm that the backup is enrolled and usable where policy permits, or that the recovery procedure and support contact are available. Password reset and sign-in recovery may be separate processes. If the service forces immediate enrollment before a backup can be added, confirm the help-desk route first and enroll the backup as soon as allowed.
Register and verify the factor
To configure two-step verification, in the security settings choose the approved method and follow the service’s enrollment prompts. For a security key, connect or tap the assigned key when prompted and complete the required local verification. For an authenticator app, install the organization-approved app, add the work account and use the service’s enrollment screen to pair it. Treat any enrollment QR code or setup key as a secret: do not share or save it in a ticket, message or screenshot.
A service may ask for a confirmation code or approval to complete registration. Enter a code only into the genuine service during the session the user initiated; approve a prompt only when it corresponds to that sign-in. If the process produces an unexpected request or certificate warning, stop and contact support. The service should show that the method is registered before the user leaves the two-factor authentication setup page.
To check how to set up two factor authentication successfully, initiate a fresh sign-in in a separate browser session or the approved test workflow. Use the newly registered factor when prompted and confirm that the intended account opens. A session that was already signed in may not request the new factor, so it is not conclusive evidence. If testing fails, retain existing access and ask the administrator for help rather than removing the old method.
Record the outcome and check recovery
After setting up two-factor authentication, test the approved backup method if the service and policy allow it. If recovery requires a help-desk identity check, verify the documented contact and procedure instead of deliberately locking the account. Store any recovery codes only in the approved secure location, separate from the primary factor. Report a lost factor promptly so it can be revoked and replaced.
For the administrator’s record, note the account identifier, service, method type, enrollment date, test result and whether recovery is ready. Do not record codes, passwords, QR images, setup keys or private keys. The completion check is straightforward: the new sign-in succeeds, the approved recovery route is available, and the previous method is removed only when policy permits and both checks are complete.