Windows 11 is preparing to make age signals a built-in platform capability. Microsoft has documented APIs that can tell properly registered apps which age bracket a signed-in user falls into without exposing the user’s exact age or birth date.
The APIs are not active yet, but Microsoft plans to enable them in a Windows release later in 2026. They are designed to let apps apply age-based content and access controls without collecting birth dates or building their own age-verification systems.
The development comes as governments push age assurance closer to operating systems and app platforms. California’s Digital Age Assurance Act becomes operative Jan. 1, 2027 and requires operating-system providers to provide requested age-bracket signals to developers through a real-time API. Australia’s experience has already exposed implementation challenges, with tests of its teen social media restrictions finding that major platforms still relied heavily on self-declared ages.
How Windows 11 age signals will work
Microsoft’s age signals documentation identifies two APIs. GetUserAgeRangeAsync can return one of five groups: under 10, 10–12, 13–15, 16–17, or 18 and older. GetAgeVerificationStatusAsync separately reports whether the user’s age is verified, unverified, opted out, temporarily unavailable, or not applicable.
Verification status reflects whether an identity provider has independently verified the user’s age. The requesting app receives the age bracket and verification status rather than the user’s precise age or birth-date data.
Access is also restricted. Microsoft’s Digital Safety platform validates the calling application’s identity, and apps must be properly registered and identified before receiving meaningful signals. The APIs must run in a Windows 11 user session with a Microsoft account signed in.
The feature remains unavailable at runtime. Microsoft’s August 2026 Windows SDK release notes say calls currently return no usable age information, so developers must retain their existing behavior or age gate until Microsoft enables the APIs later in 2026.
Separate age-assurance measures are already appearing elsewhere in Microsoft’s ecosystem. The company announced storefront checks in Singapore on March 17 and similar measures in Australia on Aug. 10 for mature-rated Microsoft Store and Xbox content. Those checks are separate from the Windows Age APIs.
Developers get the signal, but deployment questions remain
Microsoft lists apps with user-generated content, communication features, in-app purchases, virtual currencies, and age-rated media among potential users of the signals. Developers could use the returned information to change content or functionality without collecting a user’s precise age themselves.
Managed environments still present unanswered questions. Microsoft requires a signed-in Microsoft account but has not detailed how the APIs will behave across shared PCs, kiosks, education deployments, or organizations primarily using work and school identities. Account type already affects some Microsoft management controls: some Edge privacy policies do not apply to profiles signed in with personal Microsoft accounts.
Microsoft also has not identified the Windows release that will activate the APIs. Deployment requirements can materially affect enterprise planning, as seen with Windows 11 hotpatching, whose eligibility depends on Windows version, licensing, management configuration, and device support. Existing age gates will remain necessary until Microsoft’s runtime support arrives.
Read more: Microsoft is also adding new identity and location signals to workplace software, with Teams Workplace Check-In raising privacy and administration questions for organizations deploying the feature.
Let us teach you How to Talk to AI for free! Try our six-minute course at The Neuron Academy and learn a few simple ways to write better prompts and get more useful results from AI, or browse our other AI course for free for seven days. Check out all the lessons here →