You can view the health of your Microsoft services, including Office on the web, Microsoft Teams, Exchange Online, and Microsoft Dynamics 365 on the Service health page in the Microsoft 365 admin center. If you're experiencing problems with a cloud service, you can check the service health to determine whether this is a known issue with a resolution in progress before you call support or spend time troubleshooting.
If you're unable to sign in to the admin center, you can use the service status page to check for known issues preventing you from logging into your tenant. Also, sign up to follow us at @MSFT365status on X (Twitter) to see information on certain events.
The Overview tab (the default view) shows all services, their current health state, and any active incidents or advisories. An icon and status in the Health column indicate the state of each service.
The Issues for your organization to act on section lists any issues detected in your environment that require your action. If there are no issues in your environment that need action, this section won't be visible.
If you're experiencing an issue with a Microsoft 365 service and you don't see it listed on the Service health page, tell us about it by selecting Report an issue, and completing the short form. We'll look at related data and reports from other organizations to see how widespread the issue is, and if it originated with our service. If it did, we'll add it as a new incident or advisory on the Service health page, where you can track its resolution. The Reported issues tab will show all issues your tenant has reported from this form and the status.
To customize your view of which services show up on the dashboard, select Customize > Custom view, and clear the checkboxes for the services you want to filter out of your Service health dashboard view. Make sure that the checkbox is selected for each service that you want to monitor.
To sign up for email notifications of new incidents that affect your tenant and status changes for an active incident, select Customize > Email, select Send me email notifications about service health, and then specify:
You can also subscribe to email notifications for individual events instead of every event for a service. To do so, select the active issue you want to receive email notification updates for, select Manage notifications for this issue, and then specify:
In the Active issues Microsoft is working on section, select the issue title to see the issue detail page. This page shows more information about the issue, including a feed of all the messages posted while we work on a solution.
Most of the time, services will appear as healthy with no further information. When a service is having a problem, the issue is identified as either an advisory or an incident and shows a current status.
Planned maintenance events aren't shown in service health. You can track planned maintenance events by staying up to date with the Message center. Filter to messages categorized as Plan for change to find out when the change is going to happen, its effect, and how to prepare for it. See Message center in Microsoft 365 for more details.
Service health lets you look at your current health status and view the history of any service advisories and incidents that have affected your tenant in the past 30 days. To view the past health of all services, select History view.
Service health posts are written in English due to the timeliness of the information we're posting but can be automatically displayed in the language specified by your personal language settings for Microsoft 365. If you set your preferred language to anything other than English, you'll see an option in the Service health page to automatically translate posts. The messages are machine translated to your preferred language, meaning that a computer did the translation.Before you can choose your language settings, you have to set your preferred language. No translation options are shown when your language is set to English. You can't specify a preferred language for others; each person has to change this setting for themselves.
Before you can choose your language settings, you have to set your preferred language. No translation options are shown when your language is set to English. You can't specify a preferred language for others; each person has to change this setting for themselves.
Under Language and time zone, select View all to show the available options. Select your desired language from the drop-down menu, and then select Save. Microsoft 365 will try to refresh and display the new language. If that doesn't happen immediately or if it seems that it's taking too long, you can either refresh your browser or sign out and then sign back in.
To set Service health posts to automatically machine-translate and display in your preferred language, go to Health > Service health dashboard. You'll see a button to toggle automatic translation on or off. When this setting is off, posts are shown in English. When this setting is on, messages display in your preferred language. The setting you choose will persist for each visit.
Microsoft has released the PC Health Check app to help customers check the compatibility of their Windows 10 computer. The PC Health Check app can be run on your current Windows 10 computer to test if it meets the minimum requirements to run Windows 11.
Windows 11 is the latest version of Microsoft Windows. Minimum software and hardware requirements must be met before upgrading to Windows 11. Dell has verified computers that are tested to upgrade to Windows 11. For more information, reference Dell computers tested for update to Windows 11.
The PC Health Check app may be downloaded by going to -11#pchealthcheck and then clicking DOWNLOAD PC HEALTH CHECK APP. The following steps address how to run the PC Health Check app.
This information relates to a pre-release product that may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Health checks are typically used with an external monitoring service or container orchestrator to check the status of an app. Before adding health checks to an app, decide on which monitoring system to use. The monitoring system dictates what types of health checks to create and how to configure their endpoints.
The basic configuration registers health check services and calls the Health Checks Middleware to respond at a URL endpoint with a health response. By default, no specific health checks are registered to test any particular dependency or subsystem. The app is considered healthy if it can respond at the health endpoint URL. The default response writer writes HealthStatus as a plaintext response to the client. The HealthStatus is HealthStatus.Healthy, HealthStatus.Degraded, or HealthStatus.Unhealthy.
The preceding example uses curl to make an HTTP request to the health check endpoint at /healthz. curl isn't included in the .NET Linux container images, but it can be added by installing the required package in the Dockerfile. Containers that use images based on Alpine Linux can use the included wget in place of curl.
Health checks are created by implementing the IHealthCheck interface. The CheckHealthAsync method returns a HealthCheckResult that indicates the health as Healthy, Degraded, or Unhealthy. The result is written as a plaintext response with a configurable status code. Configuration is described in the Health check options section. HealthCheckResult can also return optional key-value pairs.
The health check's logic is placed in the CheckHealthAsync method. The preceding example sets a dummy variable, isHealthy, to true. If the value of isHealthy is set to false, the HealthCheckRegistration.FailureStatus status is returned.
If CheckHealthAsync throws an exception during the check, a new HealthReportEntry is returned with its HealthReportEntry.Status set to the FailureStatus. This status is defined by AddCheck (see the Register health check services section) and includes the inner exception that caused the check failure. The Description is set to the exception's message.
The AddCheck overload shown in the following example sets the failure status (HealthStatus) to report when the health check reports a failure. If the failure status is set to null (default), HealthStatus.Unhealthy is reported. This overload is a useful scenario for library authors, where the failure status indicated by the library is enforced by the app when a health check failure occurs if the health check implementation honors the setting.
Call RequireHost to specify one or more permitted hosts for the health check endpoint. Hosts should be Unicode rather than punycode and may include a port. If a collection isn't supplied, any host is accepted:
To restrict the health check endpoint to respond only on a specific port, specify a port in the call to RequireHost. This approach is typically used in a container environment to expose a port for monitoring services:
Call RequireAuthorization to run Authorization Middleware on the health check request endpoint. A RequireAuthorization overload accepts one or more authorization policies. If a policy isn't provided, the default authorization policy is used:
Although running health checks manually from a browser isn't a common scenario, CORS Middleware can be enabled by calling RequireCors on the health checks endpoints. The RequireCors overload accepts a CORS policy builder delegate (CorsPolicyBuilder) or a policy name. For more information, see Enable Cross-Origin Requests (CORS) in ASP.NET Core.
Use ResultStatusCodes to customize the mapping of health status to HTTP status codes. The following StatusCodes assignments are the default values used by the middleware. Change the status code values to meet your requirements:
d3342ee215