Microsoft 365 Teams and Exchange Outage Status

Check Microsoft 365 Service Status

Start with Microsoft’s official public status information. Open {site} and look for the Microsoft 365 service status page in the support area. This resource can confirm a known, widespread incident when the Microsoft 365 admin center is unavailable or you cannot sign in.

Read the latest notice carefully. Check when it was posted, which services are named, the reported user impact, and whether Microsoft is investigating, applying a fix, or monitoring recovery. A notice about one Microsoft service does not automatically mean that Teams and Exchange Online are both affected.

Refresh the official notice periodically for updates. Avoid relying on social media posts or third-party outage reports as confirmation. They may help show that other people have trouble, but they do not establish the cause or provide an authoritative recovery status.

View Teams and Exchange Online Health

Organization administrators can find more detailed notices in the Microsoft 365 admin center. Sign in through {site}, open the service health area, and review active issues and recent history. The exact menu position can vary, but it is generally available under the health section.

Look separately for Microsoft Teams and Exchange Online. Select an incident or advisory to review:

• The incident identifier and current status.
• The features and users that may be affected.
• The time of the latest update.
• Microsoft’s stated next update time, if one is provided.
• Available technical details or administrator guidance.

Service health information may be tailored to the signed-in organization. An administrator may therefore see a relevant notice that is not shown on the broader public page. Users who do not have administrator access should ask their workplace or school support team to check these notices.

Identify Which Service Is Affected

A Microsoft 365 Teams and Exchange Online outage can affect several features, but similar symptoms may also come from one service, one organization, or one device. Note exactly what fails before drawing a conclusion.

• If meetings, calls, chats, or Teams channels fail while email still works, check for a Microsoft 365 Teams outage.
• If sending, receiving, or opening work email fails while Teams remains available, check for a Microsoft 365 Exchange outage.
• If the Outlook app has trouble but mail works in a browser, the issue may be limited to the app, device, or connection rather than Exchange Online.
• If both Teams and email fail for many coworkers, check the Microsoft 365 service status for Teams and Exchange and ask an administrator to review organization-specific notices.
• If only your account is affected, the cause may involve your sign-in, permissions, license assignment, mailbox, or organization settings.

Record the exact error text, affected device, app or browser, and the time the problem began. Also ask whether another user on a different connection sees the same problem. These details help distinguish a broad Microsoft Teams and Exchange outage from a local issue.

What to Do During an Outage

If Microsoft confirms a Microsoft 365 Teams Exchange Online outage, follow the official incident rather than repeatedly changing account settings. Password resets, app reinstalls, mailbox changes, and permission changes can create new problems without affecting a service incident.

1. Save the incident identifier and note which functions Microsoft says are affected.
2. Check official updates at reasonable intervals and share confirmed information with affected users.
3. Keep drafts or important work locally when possible until service access is stable.
4. Use another communication method already approved by your organization if Teams chat, meetings, or Exchange Online email is unavailable.
5. Follow instructions from your organization’s administrator or support team.

Do not repeatedly submit the same message, meeting request, or account change. Delayed actions may complete later and create duplicates. When service appears to return, test with one low-risk action before resuming normal use.

Troubleshoot When No Outage Is Reported

No public notice does not prove that every Microsoft 365 service is working for every organization. An incident may be limited, newly developing, or specific to your account. Try basic checks without treating them as guaranteed fixes.

• Confirm that the device has a working connection by opening another trusted online service.
• Check the date and time on the device, because incorrect settings can interfere with sign-in.
• Read the sign-in message and confirm that you selected the correct work or school account.
• Try the browser version if an app fails, or the app if the browser session fails.
• Close and reopen the affected app. Install approved updates if your organization permits them.
• Try a private browser window or clear Microsoft sign-in cookies if a stale session appears to be the problem.
• Disable a newly added browser extension temporarily if organization policy allows it.
• Ask a coworker whether the same Teams or Exchange Online feature fails for them.

Do not remove security controls, bypass organization policies, or repeatedly reset your password. If several people in the same organization are affected, send the evidence to an administrator so they can check service health, message center notices, identity services, and organization settings.

Contact Microsoft 365 Support

Administrators should use the support option inside the Microsoft 365 admin center. This connects the request with the organization and gives Microsoft the context needed to investigate. If an active incident matches the symptoms, include its identifier instead of opening several duplicate requests.

Most individual users should first contact their workplace or school help desk. Microsoft may require an administrator to review tenant-level health, account settings, or service configuration. Personal Microsoft account users can use the official support area and choose the affected Microsoft product.

Before requesting help, collect:

• Your organization name and account type, without sharing your password.
• The affected service and feature, such as Teams meetings or Exchange Online mail delivery.
• The exact error message and incident identifier, if available.
• When the problem began, including the time zone.
• Devices, operating systems, browsers, and apps affected.
• Whether other users and connections show the same result.
• Safe troubleshooting steps already attempted.

Never send a password, verification code, or recovery code in a support request. Continue checking the official Microsoft Teams Exchange Online status while the request is being reviewed.