Home DistrictID PostureIQ Blog About Us Contact
DistrictID

MFA for Students Who Don't Have Phones

DistrictID is the second factor for K-12 students. Students keep signing in at Microsoft. When Entra asks for a second factor, DistrictID verifies the student with a passcode or a picture and signs the answer back. No phones, no migration, no new identity provider.

Talk to Us About a Pilot
Two-minute demo, recorded against a live Microsoft Entra test tenant with synthetic district data. Captions are on screen.
K-12
Every Grade Covered
0
Phones Required
Entra
Stays Your Identity Provider
Log-Only
Pilot Mode Before Blocking

Your Staff Have MFA. Your Students Probably Don't.

Entra's second factors expect an authenticator app, a text message, a phone call or a security key. A second grader has none of those, so most districts leave student MFA off.

StaffMFA on
StudentsMFA off

An unprotected student account is an easy first step for an attacker: phish teachers from a trusted internal address, then work toward staff and admin access.

New to student MFA? Read our practical guide for district IT.

How a Sign-In Works

DistrictID uses Microsoft's external MFA framework. Entra stays your identity provider and your front door.

  1. 1

    Student signs in at Microsoft

    Same Microsoft 365 sign-in as today, with their district account and password.

  2. 2

    Entra calls DistrictID

    Your Conditional Access policy requires a second factor and hands off to DistrictID.

  3. 3

    Student proves it's them

    A 6-digit passcode, or a picture and a short code for the youngest grades.

  4. 4

    DistrictID signs the answer

    Entra receives a signed result and finishes the sign-in. The student never leaves the Microsoft flow.

On Google Workspace? If your student accounts also sync to Entra, Entra can be the identity provider for Google, and DistrictID becomes the second factor for Google and Chromebook sign-ins too, shared carts included. You don't have to move off Google.

Built for How Schools Run

The controls a K-12 district actually needs, without handing students a phone.

Setup on One Page

Add DistrictID as an external MFA method in the Entra admin center, copy two values back, verify you own the tenant, and switch it on.

A Risk Score That Explains Itself

Every student sign-in is scored, and each score comes with a plain-English reason. Blocking stays off until you turn it on, so you can watch it in log-only mode first.

Sign-In Method by Grade

A picture or a shorter passcode for the youngest students, a 6-digit passcode for older grades, and per-student accommodations.

Rules by State, Not Just Country

Allow, block or add risk to sign-ins by U.S. state, plus school-hours and app-level rules.

Guardians as the Step-Up

For a risky sign-in, a guardian can approve it and trust the home network, for 90 days by default.

Teacher Passcode Resets

A teacher resets a code for her own students only, capped at 20 a day, and every reset is audited. The forgotten-code ticket never reaches IT.

Student Data, Kept to a Minimum

DistrictID stores what it needs to verify a sign-in and nothing about a student's schooling.

What we store

  • Sign-in events and outcomes
  • Hashed IP addresses
  • Passcode hashes, never passcodes
  • Session metadata

What we never store

  • Grades or attendance
  • IEP or 504 information
  • Discipline records
  • Demographics

Built For

IT Directors
Identity Administrators
Technology Coordinators
CISOs
Privacy Officers

Microsoft, Microsoft 365 and Entra are trademarks of the Microsoft group of companies.

Start with a pilot.

We connect DistrictID to a sandbox Entra tenant first, so your team sees the full sign-in round trip before a single student uses it.

Email Us About a Pilot info@cornerstone-innovations.com