Microsoft 365 Service Health: Check Your Tenant and Fix Lingering App Issues | 14 November 2026

Last verified: 14 November 2026, 13:14 UTC.

Microsoft’s public service health page showed a Microsoft 365 service degradation report during verification, warning that users may be unable to connect to multiple services. Search results also surfaced an operational status snapshot, so the public signals were not consistent. Microsoft’s page did not provide a confirmed root cause in the available results. For businesses, the practical next step is to check the organisation’s tenant-specific Service health view before assuming an app problem is local—or telling staff the service is fully restored.

A service-level recovery does not automatically clear every app problem. A user may still have a stale sign-in, a stuck sync, an add-in conflict or a device-specific network issue. Checking scope first helps avoid unnecessary reinstalls and gives IT a clearer picture of work still affected.

Destaques

• Microsoft’s public status results included a degradation notice affecting access to multiple Microsoft 365 services, alongside an operational snapshot.
• Tenant-specific Service health in the Microsoft 365 admin centre is the more useful check for business impact.
• If the tenant shows healthy service, compare affected users, devices and web versus desktop access before repairing software.
• Microsoft recommends restarting affected apps and offers Office repair options for persistent Windows desktop problems.

How do you check Microsoft 365 service health?

Go to Microsoft’s public service status page for a broad indication, especially if the admin centre is unavailable. It does not replace the view for your own organisation. A Microsoft 365 administrator can sign in to the admin centre, then open Health > Service health. Microsoft says Service Support and Helpdesk admins can also view service health.

In the tenant dashboard, check both the active issues Microsoft is investigating and any issues that require action in your organisation. Open the incident or advisory and read its affected services, user impact, status and update history. A “restoring service” or “extended recovery” status means recovery work may still be underway for some users. Even a “service restored” notice confirms the service health state, not that every device or session has recovered.

Microsoft says the dashboard retains issue history for 7 or 30 days. If the issue is missing, administrators can use Report an issue to send details for investigation. They can also enable email notifications for service health changes. Planned maintenance is tracked separately in the Message centre, under messages categorised as “Plan for change.” See Microsoft’s guide to checking Microsoft 365 service health.

Why can an app remain broken after Microsoft reports recovery?

A service incident and an individual app failure are related possibilities, but one does not prove the other. The issue could affect only a subset of users or a particular service feature. A user’s session may also need to reconnect after a disruption. If only one person or device is affected while colleagues can use the same service, that pattern points towards a narrower account, app, device or network fault. This is a troubleshooting inference, not a confirmed diagnosis.

Start with a quick scope check. Ask whether the same user can open the service in a browser, whether another affected colleague sees the same symptom, and whether the problem follows the user to another device. Note the app name, exact error, approximate start time and whether work is blocked or merely delayed. Avoid repeatedly retrying actions such as sending a message or submitting a form if success is uncertain; first check whether the item already went through.

What should you try when one Microsoft app is still failing?

1. Check the tenant notice and affected service. If Microsoft lists an active incident that matches the symptom, follow its workaround and updates. Record the incident details for your support team.
2. Compare web and desktop access. If the browser version works but the installed app does not, focus on the local app or device. If both fail for several users, report the shared pattern to your administrator.
3. Close and reopen the app, then restart the device. Microsoft recommends restarting an app as an initial step; some startup issues may require a device restart before trying again. Save work first where possible.
4. Check the connection and sign-in. Confirm the device is online and the user is signed into the expected work or school account. Follow your organisation’s identity or network support process if authentication fails.
5. Repair the desktop installation if the issue persists. On Windows, open Settings > Apps > Installed apps, find Microsoft 365 or Office, choose Modify, then select a repair option. Microsoft describes Quick Repair as faster and Online Repair as more thorough; Online Repair may take longer and can require a restart. The repair applies to the suite, even when one app is affected. Follow Microsoft’s Office repair instructions.

For Outlook, Teams or OneDrive symptoms that persist across devices, check the service-specific status and the tenant’s incident notes before resetting local data or reinstalling. Those steps can disrupt local settings or unsent work, and should follow your organisation’s support guidance.

What should administrators do next?

Keep the incident ID, affected users, timestamps and error text together. Ask users whether the web version works and record whether the issue is isolated to a single device, network or location. If the tenant health page is clear but multiple users still cannot work, submit a report from Service health and open a Microsoft support request if the business impact warrants it. Provide reproducible steps and the scope observed rather than guessing at a cause.

What happens next: Microsoft’s service page and tenant notices may change as investigations progress. Check the latest update before making a recovery announcement. A status notice can guide triage, but it cannot predict when an individual device will recover or establish that every remaining problem shares the same cause.

FAQ

Can I check Microsoft 365 status without an admin account?

Yes. Microsoft’s public status page provides broad service information. Tenant-specific details in the admin centre require an account with an appropriate admin role.

Why does my app still fail when Microsoft says the service is restored?

The notice describes the service’s health, while a particular app may still have a session, account, device or network issue. Compare access in a browser and on another device, then follow your organisation’s troubleshooting process.

Should I reinstall Office immediately?

No. Restart the app and device first, check tenant health and compare browser access. If a Windows desktop app remains broken, Microsoft’s repair option is a reasonable next step before reinstalling.

Sources

• Microsoft Service Health Status
• How to check Microsoft 365 service health
• Repair an Office application