This site requires JavaScript to be enabled
An updated version of this article is available

Multi-Factor Authentication (MFA) : Getting Started

63.0 - Last modified on 2026-06-11 Revised by Aaron B Reiser

62.0 - Last modified on 2026-05-19 Revised by Aaron B Reiser

61.0 - Last modified on 2026-05-15 Revised by Aaron B Reiser

60.0 - Last modified on 2026-05-15 Revised by Aaron B Reiser

59.0 - Last modified on 2026-05-15 Revised by Aaron B Reiser

58.0 - Last modified on 2026-05-15 Revised by Aaron B Reiser

57.0 - Last modified on 2026-05-15 Revised by Aaron B Reiser

56.0 - Last modified on 2026-05-05 Revised by Scott R Richardson

55.0 - Last modified on 2025-12-18 Revised by Martha Avila

54.0 - Last modified on 2025-11-24 Revised by Aaron B Reiser

53.0 - Last modified on 2025-11-18 Revised by Aaron B Reiser

52.0 - Last modified on 2025-11-18 Revised by Aaron B Reiser

51.0 - Last modified on 2025-03-24 Revised by Scott R Richardson

50.0 - Last modified on 2025-06-06 Revised by Sophie Corless

49.0 - Last modified on 2024-07-05 Revised by Scott R Richardson

48.0 - Last modified on 2024-07-03 Revised by Sophie Corless

47.0 - Last modified on 2024-05-16 Revised by Sophie Corless

46.0 - Last modified on 2024-05-16 Revised by Sophie Corless

45.0 - Last modified on 2024-05-16 Revised by Sophie Corless

44.0 - Last modified on 2023-11-14 Revised by Gary Edward Ward

43.0 - Last modified on 2023-09-29 Revised by Gary Edward Ward

42.0 - Last modified on 2023-09-27 Revised by Gary Edward Ward

41.0 - Last modified on 2023-08-29 Revised by Scott R Richardson

40.0 - Last modified on 2023-08-16 Revised by Gary Edward Ward

39.0 - Last modified on 2023-08-16 Revised by Gary Edward Ward

38.0 - Last modified on 2023-08-14 Revised by Scott R Richardson

37.0 - Last modified on 2023-08-14 Revised by Gary Edward Ward

36.0 - Last modified on 2023-08-14 Revised by Gary Edward Ward

35.0 - Last modified on 2023-08-14 Revised by Gary Edward Ward

34.0 - Last modified on 2023-08-14 Revised by Gary Edward Ward

33.0 - Last modified on 2023-08-14 Revised by Gary Edward Ward

32.0 - Last modified on 2023-08-14 Revised by Gary Edward Ward

31.0 - Last modified on 2023-08-11 Revised by Gary Edward Ward

30.0 - Last modified on 2023-08-11 Revised by Gary Edward Ward

29.0 - Last modified on 2023-08-10 Revised by Gary Edward Ward

28.0 - Last modified on 2023-08-10 Revised by Gary Edward Ward

27.0 - Last modified on 2023-08-10 Revised by Gary Edward Ward

26.0 - Last modified on 2023-08-10 Revised by Gary Edward Ward

25.0 - Last modified on 2023-08-10 Revised by Gary Edward Ward

24.0 - Last modified on 2023-08-10 Revised by Gary Edward Ward

23.0 - Last modified on 2022-10-19 Revised by Gary Edward Ward

22.0 - Last modified on 2022-10-19 Revised by Gary Edward Ward

21.0 - Last modified on 2022-08-31 Revised by Gary Edward Ward

20.0 - Last modified on 2022-04-21 Revised by Aaron B Reiser

19.0 - Last modified on 2021-11-15 Revised by Aaron B Reiser

18.0 - Last modified on 2021-11-02 Revised by Aaron B Reiser

17.0 - Last modified on 2020-12-15 Revised by Aaron B Reiser

16.0 - Last modified on 2020-08-18 Revised by Aaron B Reiser

15.0 - Last modified on 2020-08-12 Revised by Aaron B Reiser

14.0 - Last modified on 2020-08-05 Revised by Aaron B Reiser

13.0 - Last modified on 2020-07-06 Revised by Gary Edward Ward

12.0 - Last modified on 2020-07-01 Revised by Aaron B Reiser

11.0 - Last modified on 2020-06-30 Revised by Gary Edward Ward

10.0 - Last modified on 2020-06-15 Revised by Aaron B Reiser

9.0 - Last modified on 2020-06-12 Revised by Scott R Richardson

8.0 - Last modified on 2020-06-12 Revised by Scott R Richardson

7.0 - Last modified on 2020-06-12 Revised by Gary Edward Ward

6.0 - Last modified on 2020-05-12 Revised by Aaron B Reiser

5.0 - Last modified on 2020-05-11 Revised by Aaron B Reiser

4.0 - Last modified on 2020-05-08 Revised by Aaron B Reiser

3.0 - Last modified on 2020-05-07 Revised by Aaron B Reiser

2.0 - Last modified on 2020-05-01 Revised by Aaron B Reiser

1.0 - Created on 2020-05-01 Authored by Aaron B Reiser

699 views

Table of Contents

What is Multi-Factor Authentication (MFA)?

Why Does UT Require MFA?

Enroll Your First Device

Add a Backup Device

Available Authentication Methods

Duo Help Videos

Back to MFA Knowledge Base

 

What is Multi-Factor Authentication (MFA)?

Authentication is the process a system uses to verify that you are who you claim to be. It can rely on one or more of the following factors:

Multi-factor authentication (MFA) requires two or more of these factors. Even if your password is stolen or guessed, an attacker still cannot access your account without your second factor — such as your phone.

Back to Top

 

Why Does UT Require MFA?

The University of Texas at Austin uses Duo, a multi-factor authentication service, to protect university accounts and systems. When you sign in to any UT web application protected by MFA, Duo will prompt you to verify your identity after you enter your UT EID and password.

This extra step helps protect your personal information, university data, and the broader campus community from unauthorized access.

Back to Top

 

Enroll Your First Device

Before you can use MFA, you must enroll at least one device. The recommended option is a smartphone or tablet with the Duo Mobile app installed. Don't have a smartphone? You can also enroll a landline, a hardware token, or another supported device. See Available Authentication Methods for all options.

Have your device on hand before you begin.

To enroll your device:

  1. Go to the Self-Registration Portal at mfa.login.utexas.edu.
  2. Sign in with your UT EID and password.
  3. Select Next to begin setup. After a brief data safety overview, you will be prompted to choose an authentication method.
  4. Follow the on-screen prompts for your chosen method:
    • Duo Mobile: Download the Duo Mobile app from your device's app store when prompted. Open the app, tap + Add, and scan the QR code displayed on your screen.
    • Phone Number: Select your country code, enter your phone number, and confirm it is correct. Select Add phone number to complete setup.
  5. A confirmation screen will appear when your device is successfully enrolled.

For detailed, illustrated enrollment instructions, see the Duo Universal Prompt Enrollment Guide.

Back to Top

 

Add a Backup Device

The university strongly recommends enrolling at least two devices. A backup device protects your access if your primary device is ever lost, stolen, broken, or reset to factory settings. With a backup device enrolled, you can remove the unavailable device and add a new one on your own — without contacting support.

Important: If you have only one enrolled device and it becomes unavailable, you will need to contact the Enterprise Technology (ET) Support Center at 512-475-9400 or help@utexas.edu to regain access.

To add a backup device or manage your enrolled devices, visit the Device Management Knowledge Article.

Back to Top

 

Available Authentication Methods

Duo supports several authentication methods. Not all options require a smartphone — see below to find what works best for you.

Method Description
Verified Duo Push

Sends a push notification to the Duo Mobile app on your phone or tablet. Enter the code shown on your computer screen into the Duo Mobile app to approve the login. This is the recommended method for smartphone users.

For device requirements and step-by-step instructions, see the Duo User Guide for Android or iOS.

Duo Mobile Passcode

Generates a one-time passcode in the Duo Mobile app — works even without an internet connection. At the Duo prompt, select Enter a Passcode, then enter the code shown in the app. Hardware token users may also use this option.

Security Key

A physical USB security key that authenticates with the touch of a button — no passcode required. One example is the YubiKey, made by Yubico. See yubico.com for product details.

Security keys configured for UT's MFA service are available at the Campus Computer Store.

Note: Security keys purchased from the Campus Computer Store are configured for UT's MFA service and are not compatible with the YubiCloud OTP validation infrastructure.

Hardware Token

A small portable device that generates one-time passcodes. A good option if you prefer not to use a smartphone. Hardware tokens configured for UT's MFA service are available at the Campus Computer Store (product ID #1867833).

Touch ID

Authenticate using the fingerprint sensor on a Touch ID-equipped MacBook Pro or MacBook Air. Requires a fingerprint enrolled in macOS Touch ID settings and a supported web browser.

For current browser requirements and registration steps, see the Duo User Guide: Touch ID and the UT Device Management Knowledge Article.

Phone Call or Text

Duo calls or texts your registered phone number. Approve the login by following the phone prompt or entering the texted passcode. Works with any phone capable of receiving calls or texts — no smartphone required.

 

Back to Top

 

Duo Help Videos

Enterprise Technology has produced the following videos to help you get started with Duo. Closed captioning is available via the [CC] button on each player.

 

 

 

Back to Top

 

Note: Do not use the comments box below to request technical support. Contact the ET Support Center for assistance at 512-475-9400 or help@utexas.edu.