Current Incident - NDUS Office 365 users experiencing Outlook connection issues and crashes

Resolved
Resolved

Microsoft resolved this issue at about 5:30 p.m. CDT.

Root cause: A recent change to the Outlook client inadvertently resulted in this issue.

Recovering

User Impact: Users may experience crashes or may be unable to access Exchange Online via Outlook.

More info: Microsoft's analysis indicates that Outlook on the web and mobile clients are unaffected. Users may be able to leverage those protocols as an alternative means to access email and service features while we remediate this problem.

Affected users will likely receive an error message that reads: "Outlook couldn't start last time. Safe mode could help you troubleshoot the problem, but some features might not be available in this mode. Do you want to start in Safe Mode?"

Further information on what admins will see in event viewer for this crash event can be found here: https://support.microsoft.com/en-us/office/active-investigation-into-outlook-crashing-on-launch-9c59ad4b-813c-432a-afdc-f14717a4528d?ui=en-us&rs=en-us&ad=us

Current status: Microsoft is continuing to monitor service telemetry as our fix propagates to all remaining affected users. Microsoft has received word from some previously affected customers that the issue is now resolved for them, and we'll continue our efforts to ensure that this process completes as expected.

Scope of impact: This issue may potentially affect any of your users attempting to use Outlook.

Estimated time to resolve: Microsoft expects this issue to be completely resolved for all affected users by July 15, 2020 at 9:30 PM UTC.

Next update by: Wednesday, July 15, 2020, 4:30 PM (9:30 PM UTC)

Identified

Microsoft's initial review of the available data indicates that recently deployed updates are the likely source of the problem. They are performing an analysis of all recent service updates to isolate the underlying cause of the problem and to determine the most expedient means to restore service.

Next update by: Wednesday, July 15, 2020, 1:30 PM (6:30 PM UTC)

Began at:

Affected components
  • Office 365
    • Outlook