Is Microsoft Exchange Server Down? Status Help

Microsoft Exchange Server may be down if multiple users cannot reach mailboxes, but a connection error alone does not prove an outage. Check the correct official health source, then compare affected users, devices, networks, and error messages to determine whether the problem is widespread or local.

How to Check Microsoft Exchange Server Status

The correct Microsoft Exchange Server status check depends on which product your organization uses. Exchange Server is hosted and managed on an organization’s own systems, while Exchange Online is Microsoft’s cloud-hosted email service.

1. Confirm whether the account uses on-premises Exchange Server or Exchange Online. Ask your organization’s administrator if you are unsure.
2. For Exchange Online, ask a Microsoft 365 administrator to review Service health in the Microsoft 365 admin center. An incident or advisory there can confirm that Microsoft is investigating a cloud-service problem.
3. If administrators cannot enter the admin center, check Microsoft’s official public service-status information for a broader access problem.
4. For on-premises Exchange Server, check the organization’s monitoring system, server logs, network alerts, and maintenance notices. Microsoft’s cloud-service status does not report the health of an organization’s own Exchange servers.
5. Match any official incident to the affected service, region, time, and symptom. An unrelated Microsoft incident does not explain every Exchange connection failure.

If no relevant incident appears, continue troubleshooting. The lack of a public report does not prove that every server and account is working.

Signs That Exchange Server May Be Down

Possible outage symptoms include failed sign-ins, unavailable mailboxes, delayed incoming or outgoing mail, repeated password prompts, and connection errors in an email client. Webmail may also fail to load, or several users may lose access at approximately the same time.

These signs are clues, not proof. One user may have an expired password, locked account, damaged local profile, incorrect server setting, or device problem. A single office may have a network or DNS issue; DNS is the system that helps a device locate a server by name.

• A problem affecting one device usually points to that device, application, or saved account configuration.
• A problem affecting one user on every device may point to the user’s account or mailbox.
• A problem affecting many users on different devices and networks may indicate a server or service incident.
• Mail delays without sign-in failures may involve mail flow rather than complete server unavailability.

How to Check Your Exchange Server Connection

Test the Exchange Server connection without deleting the account or changing settings repeatedly. Record the exact error text and the time before starting.

1. Open another reliable online service to confirm that the device has internet access. If nothing loads, address the network connection first.
2. Try the Exchange account through another approved access method, such as your organization’s webmail, if available. If webmail works but the email application does not, the application or its local profile may be the cause.
3. Try another device or network when your organization’s security rules permit it. This helps separate a device problem from a broader service problem.
4. Ask whether another user is affected. Do not ask anyone to share a password or verification code.
5. If you are an administrator, check whether the Exchange services, required servers, certificates, name resolution, storage, and network paths are available. Review monitoring alerts and logs before restarting anything.

Do not guess server names or security settings. Use only configuration details supplied by the organization’s administrator.

What to Do During an Exchange Server Outage

During a confirmed or suspected Exchange Server outage, preserve useful evidence and avoid changes that could create a second problem.

1. Check the appropriate official health information and your organization’s internal notices for updates.
2. Notify the Exchange administrator or help desk once, including the exact error, affected account, device, connection method, and time the problem began.
3. Save screenshots or copy error text without exposing passwords, verification codes, or confidential message content.
4. Keep unsent work in a safe draft location. Do not assume that a message marked as sent has reached the recipient until mail flow is confirmed.
5. Avoid deleting the account, recreating profiles, changing server settings, or repeatedly resetting the password unless an administrator directs you to do so.

Repeated sign-in attempts can also trigger account protections, making recovery harder after the original incident ends.

When to Contact Your Administrator or Microsoft Support

An end user should contact the organization’s Exchange administrator when access fails on multiple devices, several coworkers report the same symptom, a mailbox is unavailable, or an error says that administrative action is required. Contact the administrator promptly if access is needed for urgent work or if account security may be involved.

Provide the account identifier, time zone, approximate failure time, application or webmail method, device type, network used, and exact error. Never send a password or verification code.

An administrator may need Microsoft Support when an Exchange Online problem is not explained by official service health, documented troubleshooting does not restore access, or Microsoft must inspect the tenant-level service. For on-premises Exchange Server, the administrator should first collect relevant logs, version and update details, configuration history, and the scope of affected users before requesting official Microsoft assistance.

How to Recover Access After Exchange Service Is Restored

After Exchange service is restored, reconnect carefully and verify both mailbox access and mail flow. A health notice marked resolved does not automatically confirm that every device has refreshed its connection.

1. Close and reopen the email application, then sign in again only if prompted through the organization’s normal process.
2. Confirm that folders open and recent messages appear. Allow time for the application to synchronize before changing settings.
3. Send a test message to an approved internal recipient and ask for a reply. This checks outgoing and incoming delivery.
4. Review the Outbox and Drafts for queued or duplicated messages. Confirm delivery before resending anything important.
5. Check that messages created during the interruption were delivered and that calendar or mailbox changes synchronized.
6. If errors continue after the official restoration, report the new time and error details to the administrator. The remaining issue may affect only one account, device, or local profile.