Microsoft 365 crash overthrows teams, Exchange Online



[ad_1]

Office 365

Azure Active Directory outage prevents users from signing in to Microsoft 365, Microsoft Teams, Exchange Online, Forms, Xbox Live, and Yammer.

As of around 3:34 p.m. EST, users began reporting that they couldn’t sign in to their Microsoft 365 accounts, Microsoft Teams, or access other Microsoft apps.

The outage also affects Microsoft sites, such as the Tech Community website, because users cannot sign in to the site.

“Due to the issues that Azure AAD is currently facing, we are currently experiencing login and authentication issues within the Microsoft tech community. This will prevent users from signing in and users who are already logged in will receive unexpected errors when sessions expire. ” a manager of the Microsoft Tech community.

Microsoft acknowledged the outage in Microsoft 365 incident report MO244568, which states that the outage initially affected Microsoft Teams but now affects other services.

“Initial reports indicate that the primary impact is on Microsoft Teams; however, other services, including Exchange Online and Yammer, are also affected.”

“We investigate a potential problem and verify its impact on your organization. We will provide you with an update within 30 minutes, ”the outage report said.

The widespread outages affecting Microsoft’s online services are actually the result of an Azure Active Directory issue that prevents users from authenticating to Microsoft 365, Exchange, Online, and Teams.

“As of approximately 7:15 p.m. UTC on March 15, 2021, a subset of customers may experience authentication issues in Microsoft services, including Microsoft Teams, Office and / or Dynamics, Xbox Live, and the Azure portal.” , we read on the Azure status page.

Microsoft shares updates on their Microsoft 365 Status Twitter account, with the latest update indicating that the outage is caused by a change in their authentication system.

Based on user reports, it appears to be a global outage.

Update 03/15/21 4:48 PM: The outage is confirmed to be caused by an Azure Active Directory issue. Article updated with this information.

This is a developing story.



[ad_2]

Source link