< Back to situation

[REVISION HISTORY]

Microsoft age verification implementation

Updated 1 time since CLSTR started tracking revisions of this situation.

What changed

2026-09-06 02:13 UTC → 2026-09-06 07:57 UTC · added removed

Microsoft has begun implementing age verification systems across its platforms to comply with digital safety and child protection regulations. In Australia, the company introduced requirements for the Microsoft and Xbox Stores to restrict R18+ rated content. Users may need to verify their age via credit cards, government IDs, or facial age estimation through a “secure selfie” to access mature-rated titles. While some users support these measures, others have criticized them as “extreme overreach” due to privacy and bureaucracy concerns. This initiative has expanded to into the Windows 11 ecosystem, where age verification allows ecosystem through the introduction of the Windows Age API. This system-level feature is designed to enhance privacy by allowing applications to adjust content or restrict features based on determine a user's user’s age group. group without accessing an exact date of birth. Users are categorized into five specific brackets: under 10, 10-12, 13-15, 16-17, and 18+. To prevent unauthorized data requests, Microsoft’s Digital Safety platform will pre-approve applications permitted to call this API. This mechanism helps developers enforce content filtering, social feature limitations, and in-app purchase controls to meet regulatory pressures in regions such as the US, UK, and EU. Microsoft Teams Free is among the first affected applications; applications expected to implement these changes. In jurisdictions where local laws mandate verification, users who do not verify their age may via Microsoft account methods—such as ID uploads or facial estimation—may lose access to generative AI tools like Copilot, the ability to record meetings, meeting recordings, and certain community features. Verification methods vary by region and may include government systems or identification documents.

Versions

  1. 2026-09-06 07:57 UTC Microsoft age verification implementation
  2. 2026-09-06 02:13 UTC Microsoft age verification implementation

Only revisions since CLSTR began indexing content versions appear here. Select a version to see what changed compared to the one before it.