"Some new users who signed up during the impact window were incorrectly treated as already onboarded, causing onboarding and privacy consent screens to be skipped, their profiles to appear as 'Unknown users' to others, and preventing them from being searchable or reliably reachable in chat," Microsoft said in a service health status update earlier today.
What Microsoft says went wrong
Microsoft attributes the disruption to a "recently deployed backend change" that causes new Teams Free accounts to bypass required onboarding and privacy-consent steps. According to the company, that bypass leaves profiles in an incomplete state so affected users "can not be discovered, connect with others, or successfully complete chat request flows." The vendor has publicly labeled the incident a "service degradation," a status typically used for problems that noticeably affect users without taking the service fully offline.
Who and when: the limited facts Microsoft has released
Teams Free is the subscription-free version of Microsoft Teams for individuals, families, and small community groups, offering video conferencing, instant messaging, and collaborative file‑sharing on mobile and desktop for users with a Microsoft account. Microsoft says the first reports of this particular problem surfaced on April 8; the company did not disclose which regions are affected or how many users are impacted. Microsoft says it is still working on a fix and has scheduled another update to share additional details later today.
How the problem appears to end users
When the onboarding and privacy consent screens are skipped, users who signed up during the "impact window" may be shown as 'Unknown users' to others. That state prevents them from being found through search and from reliably receiving chat requests or calls. In short, the affected accounts exist in name but appear incomplete and effectively unreachable from other accounts in Teams Free.
Related Teams service incidents this month
This incident follows two other recent service problems Microsoft acknowledged in April. Last week, the company identified an issue that was preventing Windows users from joining Teams meetings, which Microsoft tied to a bug introduced by a recent Microsoft Edge browser update. Earlier in the month, Microsoft reverted a service update after some customers were blocked from launching the Teams desktop client and were left on a loading screen displaying the error: "We're having trouble loading your message. Try refreshing."
What this means for end users, technologists, and affected enterprises
- End users: Individuals, families, and small community groups that rely on Teams Free may find new sign-ups effectively invisible to others until Microsoft completes a fix; users who signed up on or after April 8 are the ones Microsoft flagged as potentially impacted.
- Technologists and IT teams: Teams administrators and support staff should monitor Microsoft’s service health updates and prepare to validate account states for users who report being treated as 'Unknown users' or who cannot be reached by chat or calls.
- Affected enterprises and procurement leaders: Organizations that allow or depend on Teams Free for ad-hoc collaboration should note that Microsoft is treating this as a degradation and has not yet published scope or regional detail; contingency communication channels may be necessary while Microsoft works on a resolution.
Microsoft has acknowledged the defect, tied it to a recent backend deployment, and promised another status update later today. For users left unreachable and for groups that depend on Teams Free for lightweight collaboration, the question is whether Microsoft’s next update will restore discoverability quickly or reveal a wider rollback or remediation plan. The company’s record this month of reversing updates and identifying browser-related bugs underlines that the platform's recent changes have produced multiple, visible disruptions.
