> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/tenant/administration/service-health/status.md).

# Status

This tab lists the current health of each Microsoft 365 service for the selected tenant, as Microsoft reports it, so you can tell at a glance whether a problem a user is reporting is a known service issue. The other Service Health tabs are described on [Service Health](/user-documentation/tenant/administration/service-health.md).

With All Tenants selected, services that share the same status are combined into a single row, and the **Tenant** column shows how many tenants report it.

## Summary Bar

| Tile                 | Description                                                                                                     |
| -------------------- | --------------------------------------------------------------------------------------------------------------- |
| Services             | How many distinct services are listed.                                                                          |
| Services with issues | How many services are reporting any status other than operational.                                              |
| Degraded             | How many services are reporting degraded service. Selecting the tile filters the table to those services.       |
| Interrupted          | How many services are reporting a service interruption. Selecting the tile filters the table to those services. |

## Filters

| Filter          | Shows                                                      |
| --------------- | ---------------------------------------------------------- |
| Not operational | Services reporting any status other than operational.      |
| Degraded        | Services Microsoft reports as running in a degraded state. |
| Interrupted     | Services Microsoft reports as interrupted.                 |

## Table Details

The properties returned are for the Graph resource type `serviceHealth`. For more information on the properties please see the [Graph documentation](https://learn.microsoft.com/en-us/graph/api/resources/servicehealth?view=graph-rest-1.0).

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

With All Tenants selected, the flyout lists every tenant reporting that service and status.

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cipp.app/user-documentation/tenant/administration/service-health/status.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.