Using classic Outlook for Windows in business environments
Microsoft has not published a verified full-restoration time; the latest available status indicates an Outlook/Exchange Online disruption affecting desktop and mobile access, so monitor Microsoft 365 Service Health rather than reinstalling Outlook again.^1^
Check your organization’s incident status
If you or your IT administrator has Microsoft 365 admin access:
- Sign in to the Microsoft 365 admin center.
- Open Health → Service health.
- Under Active issues Microsoft is working on, select the Exchange Online/Outlook incident.
- Review Status, User impact, All updates, and any published restoration estimate.
- Optionally select Manage notifications for this issue to receive updates by email.
Service Health is tenant-specific and is Microsoft’s authoritative location for active incidents, restoration progress, and confirmation that service has been restored. Service Support admins and Helpdesk admins can also view it.^2^
If you are not an administrator, ask your company’s Microsoft 365 administrator or IT help desk to check Health → Service health. The recent reports reference Exchange Online incident EX1550543 and broader Microsoft 365 incident MO1550821, although the incident shown for your tenant may differ.^1^
What to do now
- Do not uninstall and reinstall Outlook again; that has already failed, and reinstalling cannot resolve a Microsoft-side service incident.
- If Outlook on the web also fails, wait for Service Health to report Service restored. Access should return as Microsoft completes recovery.
- If Service Health shows no relevant incident, have your administrator select Report an issue from the Service Health page. Microsoft uses those tenant reports to assess whether an unlisted problem is more widespread.^2^
- If the incident is marked Service restored but your account still fails on both the laptop and phone, your administrator should open a Microsoft 365 support request and include the exact error message, timestamp, affected email account, and confirmation that multiple connection methods fail.
References