Microsoft Authenticator: Information & FAQs

Summary

Provides details about Microsoft Authenticator, Multi-Factor Authentication as a concept, and answers several Frequently Asked Questions (FAQs).

Body

This article contains general information pertaining to Microsoft Authenticator and Multi-Factor Authentication (MFA) as a concept. Frequently Asked Questions (FAQs) regarding Microsoft Authenticator / MFA are also present within this article. Multi-Factor Authentication with Microsoft Authenticator will be required for faculty, staff, and students starting November 9th, 2026. 

Table of Contents

Overview

Overview

Multi-Factor Authentication

Diagram showing three authentication factors: something you know, have, and are.

Multi-Factor Authentication (MFA) adds an additional layer of security to your university account. Instead of relying solely on a password (which can be guessed, stolen, or compromised in a data breach), MFA requires you to verify your identity using two or more distinct factors:

  1. Something you know: Your Oakland University NetID password.
  2. Something you have: A registered trusted device, such as a smartphone with an authenticator app, a physical security key, or an external email address.
  3. Something you are: Biometric verification, such as a fingerprint or face scan on a compliant device.

Why is this needed?

Higher education institutions like Oakland University are prime targets for cyberattacks, including phishing, credential harvesting, and ransomware. We want to help keep you safe from these threats. MFA protects both individual users and the University as a whole:

  • Prevent Account Takeovers: Over 99% of automated account attacks are blocked by enabling Multi-Factor Authentication.
  • Protect Sensitive Data: Ensures that academic records, personal information, payroll details, and research data remain confidential.
  • Maintain Compliance: Meets cybersecurity industry standards, federal privacy regulations (such as FERPA), and university insurance policies.

Conditional Access diagram showing signals used to allow, require MFA, or block access.


What Multi-Factor Authentication methods are supported?

Oakland University supports the following MFA methods that you can use to access your account: 

Method Type Description
Microsoft Authenticator (Push / Number Matching) App-based Sends a push notification to your smartphone with a 2-digit number match.
YubiKey Security Token Physical Security Token Uses a USB hardware key (YubiKey) as an alternative to enrolling in Microsoft Authenticator. This is only for users who have received an exception from enrolling their device in Microsoft Authenticator due to disability, or other qualifying factors. 

Oakland University does not currently support device-based passkeys, Windows Hello on university-owned Windows-based workstations, or Touch ID on university-owned macOS-based workstations.

FAQs

Is Microsoft Authenticator enforced on all Oakland University accounts?

Microsoft Authenticator is enforced on most Oakland University user accounts. The only exceptions are shared & guest accounts, which will still use Duo Multi-Factor Authentication (MFA).

You will be sent communications through the proper channels if this ever changes in the future. 


Can I install the Microsoft Authenticator application on a tablet instead of a phone?

Yes, you can install Microsoft Authenticator & register your Oakland University account on any device running iOS / Android. This includes Apple iPads & Android tablets. 


Do I need to use Microsoft Authenticator when I log-in to my computer? 

No, you will only be prompted for Microsoft Authenticator Multi-Factor Authentication when you are attempting to access a web service that uses Oakland University's authentication page. Laptops & Desktops managed by the university (typically used by staff & faculty members) do not require Microsoft Authenticator to log-in. 


Are there minimum requirements for Microsoft Authenticator to run on my device? 

Microsoft Authenticator requires a minimum version of iOS / Android in order for the application to run on your mobile device. You can check the minimum iOS/Android requirements by reviewing the application from your device's respective application store. If your device is incompatible with Microsoft Authenticator, you will receive an incompatibility error upon installing the application: 

As of 10/30/2026 Apple iOS 17.0 and Android 8.0 or later is supported.


How do I register my methods?

You will be prompted to register for Microsoft Authenticator and an alternate email address starting in late October 2026. The following Knowledge Base articles detail the registration further: 


Are third-party Authenticator applications supported? What if I cannot use Microsoft Authenticator? 

No, only the Microsoft Authenticator application is supported for enrolling in Multi-Factor Authentication (MFA) on your mobile device. If you are unable to enroll in Microsoft Authenticator, lack a mobile device, or require certain accommodations, please see the following article for instructions:


Why do I need to enter a number every time I approve an MFA request? 

With our previous Multi-Factor Authentication system, DUO, users may have found it easier to simply approve a push notification. Microsoft Authenticator uses number matching in the application because a simple “Approve” push is vulnerable to MFA fatigue attacks. An attacker who has your password can repeatedly send login prompts until you accidentally approve one. Entering the number confirms that you initiated the specific sign-in.

It’s a small inconvenience, but it helps prevent:

  • Accidental approval of someone else’s login
  • Repeated push-spam attacks
  • Attackers tricking you over the phone into approving a request

What methods do I need to register?

We require users enroll in the Microsoft Authenticator application on a mobile device running iOS or Android. If you are unable to enroll your mobile device in Microsoft Authenticator, you will need to submit a request for a YubiKey provided you have a valid exception (disability, device incompatibility, or other qualifying factor): 


Do I need to use MFA when logging into my Oakland University workstation or lab computer?

No. Multi-Factor Authentication will only be applied if you are logging into a University service or portal - not for logging into your workstation.


Will I have to approve an MFA prompt every single time I log in?

No, as long as you are using a trusted device. When logging in through the Oakland University sign-in page, select Yes when prompted with "Stay signed in?" (and check "Don't show this again"). This saves a persistent cookie in your browser so you won't be asked for your password or Authenticator app every time you open Microsoft 365, Google Workspace, Sail, or campus web applications.

Important: Only click "Yes" on your own computer or mobile device. If you are using a public computer (like a library PC or lab computer), always click "No" and log out when finished.

Does Microsoft Authenticator work on Apple Watch/Android wearable devices?

No, Apple Watch and Android wearable devices (such as Samsung Galaxy Watch) are currently incompatible with Authenticator's security features, but you can mirror Authenticator notifications from your phone to your wearable device.


Does MFA work when I am traveling, offline, or without cell service?

Yes - using Microsoft Authentication. Open the Microsoft Authenticator app on your mobile device, tap your university account, and use the rotating 6-digit One-Time Password Code (OATH) displayed in the app. This code works without Wi-Fi or cellular service.

Please reference the following article to see an overview of all other articles pertaining to Microsoft Authenticator and the new Self-Service Password Reset (SSPR) solution: 

Additional Resources

Microsoft provides an official FAQ document for Microsoft Authenticator, which can be reviewed in conjunction with this article:

The OU Technology Center can provide support for any issues you may encounter with SSPR & Authenticator. Their contact information is below: 

  • 44 Oakland Center
  • Rochester, MI 48309-4479
  • (248) 370-4357
  • Office Hours: M-F 8:00am - 5:00pm

Details

Details

Article ID: 1093
Created
Tue 9/1/26 1:55 PM
Modified
Thu 11/5/26 11:52 AM

Related Articles

Related Articles (2)

This article contains links to all Knowledge Base articles pertaining to Microsoft Authenticator, and Self-Service Password Reset.
This article provides instructions for enrolling your Oakland University account into Microsoft Authenticator's secure Multi-Factor Authentication (MFA) solution.

Related Services / Offerings

Related Services / Offerings (3)

Get help with Microsoft Authenticator, request a physical hardware security key, or get assistance registering or removing a key.
Report problems with receiving authentication prompts, enrolling in Microsoft Authenticator, etc.
Request a physical hardware security key as an alternative to Microsoft Authenticator.