Microsoft has published developer documentation for Windows 11 age signals, a set of system APIs that hand an app the age bracket of the signed-in user. The app never sees a date of birth. It asks Windows, and Windows answers with a range. The documentation page was last updated on 27 August 2026, and the APIs are not switched on yet.
What Windows 11 age signals actually share
There are two calls. GetUserAgeRangeAsync returns one of five buckets: Under 10, 10-12, 13-15, 16-17, or 18+. If Windows does not know, it returns null, and Microsoft tells developers to fall back to their own age gate.
The second call, GetAgeVerificationStatusAsync, says whether that age has been independently checked by the identity provider. It can come back as Verified, Unverified, OptedOut, TemporarilyUnavailable or NotApplicable.
Microsoft’s framing is explicit in the overview page:
The Windows Age APIs provide a privacy-preserving mechanism for apps to determine the age group and age verified status of the signed-in user.
That claim is fair as far as it goes. The documentation says the API does not return your age, your date of birth, or family relationship details. Not every installed program can ask, either. Microsoft’s Digital Safety platform checks the calling app’s identity first, so an app has to be registered before it gets a real answer back.
Why Microsoft is building this now
The regulatory pressure is already visible. On 10 August, Microsoft said it was introducing age assurance across the Microsoft Store and Xbox storefronts in Australia, to meet that country’s Age Restricted Material Online Safety Codes. Account holders were emailed about it on 30 July.
That Australian rollout is worth reading next to the privacy language. The age range an app receives is small and generic. Getting to a Verified status is not. Microsoft listed the options there as email-based verification, facial age estimation, an official document scan, or a credit card check, with Yoti and Verifymy named as partners. A face scan or an ID upload is the part that costs you something, and it happens upstream of the tidy little bracket the app finally sees.
The Microsoft account requirement
One line in the platform requirements matters more than it looks. Age signals must run in a user session with a Microsoft account signed in. If you use a local account on Windows 11, there is no signal for an app to read.
Today that means nothing, because the APIs are dormant. But it adds one more thing that stops working without an MSA, on top of the sync and backup nudges Windows 11 already makes, including the OneDrive prompts baked into the Start menu. If age-gated apps or games start treating an unknown bracket as an under-18 assumption, local-account users could find themselves defaulted into a restricted experience. Nothing in the documentation says that will happen. It is simply the direction the plumbing points.
When does this reach your PC?
Microsoft says the APIs are documented ahead of availability and are planned to be turned on in a future release later this year. Until then every call returns an unknown range and an unavailable status. The minimum listed OS version is Windows 11.
The documentation also lists OptedOut as one possible verification status, but neither the overview nor the implementation guide explains how a user reaches that state. There is no user-facing setting described in either page. That is the gap worth watching when the switch is flipped, because a privacy feature you cannot find in Settings is only as good as the default Microsoft picks for you.
Sources: Microsoft Learn, Microsoft News, via Windows Latest
