What Microsoft built (short and friendly)

Windows 11 now has a built-in way for apps to figure out whether the person using them is a kid, a teen, or an adult — without peeking at anyone’s exact birthday. In plain terms: apps can ask Windows for a simple age signal instead of your full date of birth, and Windows answers with a category.

  • age ranges: under 10, 10–12, 13–15, 16–17, and 18+
  • APIs developers can call include GetUserAgeRangeAsync (gets the range) and GetAgeVerificationStatusAsync (says whether the age was verified or just self-reported)
  • Only the minimum info needed for the app experience is returned — no full DOBs or other sensitive details

Why this matters (and a few quirks)

Think of it as a “no-nonsense curtain” between apps and your birthday. Apps can automatically enable safer defaults or limit features for younger users without forcing parents to configure every single app. Microsoft specifically calls this useful for AI-powered features, where age-appropriate handling is becoming more important.

Microsoft also wants to make age checks less repetitive. A companion system called Microsoft Age Verification stores a verified age flag on your Microsoft account so apps can trust that status instead of asking you to prove your age again and again. The company frames it as: Verify once → use everywhere.

Availability notes: age verification is already supported in a few regions and parental control prompts are getting more visible during Windows setup in some countries. The Windows Age APIs are rolling out to Windows Insiders now and will reach the general user base soon.

One last, slightly grumpy security reminder: no magic API fixes all risks. Attackers who get legitimate credentials can still cause trouble, so treating identity and account protection seriously remains essential.