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

337 views

Table of Contents

What's Changing with Duo Multi-Factor Authentication?

Duo Help Video from ITS

What is Multi-Factor Authentication (MFA)?

Why am I being asked to complete MFA?

Available Authentication Methods

Registering Backup Devices

Registration Steps for New Users

Registering Other Devices

 

Back to MFA Knowledge Base

 

 

What's Changing With Duo Multi-Factor Authentication?

On September 26th, 2023, the university is implementing a new security policy for all university affiliates to strengthen your Duo account against attacks. This change will automatically replace Duo Mobile push with Verified Duo Push, and your browser will only remember your device for one day. 

 

For more information on these upcoming changes, please visit: Duo Security Enhancement with Verified Push 

 

Back to Top

 

 

Duo Help Video from ITS

In the video below, UT’s Information Technology Services (ITS) introduces Duo, a multi-factor authentication service. Duo is used as an extra layer of security to make logins more secure.

To learn more about Duo and how to use it, you can view the videos below. Closed captioning is available via the [CC] button.

 

 

Back to Top

 

 

What is Multi-Factor Authentication (MFA)?

Authentication is the process by which a system determines that you are who you claim to be.

There are multiple factors of authentication, which can be broken down into categories:

  • Something you know, such as a password.
  • Something you have, such as your mobile phone.
  • Something you are (i.e., biometrics), such as your fingerprint.

When you use more factors of authentication, the system can be more confident that you are who you claim to be, leading to better security.

For example, your password might be comprised when a website gets hacked, but with multi-factor authentication, that password is useless without your mobile phone.

Back to Top

 

 

Why am I Being Asked to Complete MFA?

To better protect the security of your online information, the university has implemented MFA using the Duo product. This system will come up when you log into any university web application protected by MFA.

Before you can complete the authentication process, you will need to enroll a device. The recommended device is a smartphone or tablet, such as an iPhone or Android device.

If you have not enrolled a device, please follow the instructions below. You will need your chosen device handy to complete this process.

 

Back to Top

 

 

Available Authentication Methods

Authentication Methods Description
Phone Call Approval Receive a phone call and follow the instructions.
Duo Verified Push * Beginning September 26, 2023 - Pushes a request to your phone or tablet. Enter the code shown on your screen into the Duo Push request received on your Android or iOS device. Android users only: tap Verify to finish approving the login request.
Duo Push * No longer available September 26, 2023 -  Pushes a request to your phone or tablet (if you have the Duo Mobile application installed and activated on your iOS, Android, or Windows Phone device). Just review the request and tap Approve.
Security Key

Authenticate with a touch of a button (no passcode needed). The generic term is "security key" and one example is the YubiKey, a product made by YubiCo. Security keys configured for the university's MFA service can be purchased at the Campus Computer Store.


Product information is available at: https://www.yubico.com/.


Note:
Security keys sold by the Campus Computer Store are configured for the university's MFA service and are incompatible with the YubiCloud OTP validation infrastructure.

Duo Mobile Generated Passcodes Enter a passcode generated with the Duo Mobile application or generated by your hardware token. Click the Enter a Passcode to make use of this functionality.
Hardware Token Authenticate with a one-time passcode generated from a portable hardware token. The generic term is "hard token" or "token".
Hardware Tokens configured for the university's MFA service can be purchased at the Campus Computer Store under product ID#1867833
Touch ID

In order to use Apple Touch ID, make sure you have the following:
A MacBook Pro or MacBook Air with a Touch ID button.


A fingerprint is enrolled in Touch ID (see how to do this at the Apple Support site).


Chrome 70 or later. Safari and other browsers on macOS are not supported.


For UT Specific Registration Steps, please visit: Device Management

 

Back to Top

 

 

Registering Backup Devices

The university strongly recommends that you register more than one device.

  • In the event that your primary device is lost/stolen/broken, you can use your backup device to remove the lost/stolen/broken device and add a new one.
  • In the event that your smartphone or tablet is reset to factory settings, you can use your backup device to remove and re-add that smartphone or tablet.
  • If you do not configure a backup device, you will need to contact the UT Service Desk if your only device becomes lost, stolen, broken, or reset.
  • For directions to add a backup device, please visit: Device Management

 

Back to Top

 

 

Registration Steps for New Users

The first step in registration is to enroll your device using your UT EID. The device you enroll will be used when you are prompted to authenticate by university web applications protected by MFA.

Follow the instructions below to register your mobile phone or landline. 

 

Register Your Mobile Phone or Landline (Click to Expand/Collapse)

1. Click HERE to go to the Self-Registration Portal.

 

2. Sign on with your UT EID and EID password.

 

3. You will then be automatically redirected to the setup. Select "Next" to start setup. 

 

4. After a few data safety tips, you will be prompted to select a Duo option to use for authentication. "Duo Mobile," which utilizes the Duo app, is recommended. 

 

5. Select the correct Country Code and input your number. Once done, select "Add phone number". On the next page, verify that it is correct, and click "Yes, it's correct" 

 

6. If you chose the "Phone Number" method, you are all set up and ready to go. If you chose "Duo Mobile," navigate to your device's App Store and install the Duo Mobile app and select "next" 

 

7. Select "+Add" in your Duo app to scan the QR code that appears. Once scanned, a confirmation screen will appear, letting you know your device is set up. 

 

8. Once you continue, the setup is now complete. 

 

Back to Top

 

 

Registering Other Devices

For help registering other devices with Duo, please visit our Device Management article in the link below:

 

Note: Do not use the comments box below to request technical support. Please contact the UT Service Desk for assistance at 512-475-9400 or help@utexas.edu.

 

Back to Top