Key keywords: Microsoft outage, Teams login failure, Outlook service disruption, Microsoft 365 outage, Azure Active Directory issue, Microsoft cloud service downtime, Microsoft service status, workplace SaaS outage On Thursday morning, thousands of users across North America, Europe, and the Asia-Pacific reported being unable to access core Microsoft services, sparking widespread frustration for remote workers, educational institutions, and businesses of all sizes. The outage first surfaced around 9:00 AM UTC, with users flooding social media platforms including X (formerly Twitter) and Reddit with screenshots of login error messages, frozen Teams interfaces, and undelivered Outlook emails. Many users reported seeing generic "authentication failed" prompts with no further troubleshooting guidance, leaving them unable to connect to work or school accounts for hours. According to Microsoft’s initial public update posted to its service health dashboard 45 minutes after the first reports emerged, the disruption stemmed from an unforeseen bug in a recent Azure Active Directory (AAD) configuration update. AAD, the identity management backbone that powers authentication for all Microsoft 365 services, failed to process valid login requests for approximately 60% of global users at the peak of the outage. In addition to Teams and Outlook, users reported disruptions to OneDrive cloud storage, SharePoint collaboration tools, and even limited functionality for Xbox Live players attempting to access cloud-saved game data. Small and medium-sized businesses were hit the hardest, as many lack backup communication or productivity tools to fall back on during outages. Multiple enterprise clients also reported that their entire remote work operations were halted for an average of 2.5 hours before partial restoration began. K-12 schools and universities that rely on Teams for virtual classes also faced major disruptions, with thousands of students unable to join scheduled lectures and exam review sessions. Microsoft’s engineering team rolled out a targeted rollback of the faulty AAD update roughly 2 hours after the outage was confirmed, with 90% of affected services restored by 1:30 PM UTC. The company noted that remaining edge cases for users in specific regions were fully resolved by 3:00 PM UTC. In a follow-up statement, Microsoft promised to publish a full root cause analysis report within 72 hours, and stated that it would be reviewing its update rollout protocols to prevent similar widespread disruptions in the future. For paid Microsoft 365 subscribers, the company noted that eligible users would receive service credit adjustments on their next billing cycle, though specific eligibility criteria have not yet been released.