> 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/issues.md).

# Issues

This tab lists the service health issues Microsoft has posted for the selected tenant: the incidents and advisories about outages and degraded service, with their status, the affected service and feature, and when they started and were last updated. The other Service Health tabs are described on [Service Health](/user-documentation/tenant/administration/service-health.md).

With All Tenants selected, an issue Microsoft posted to several tenants is listed once, and the **Tenant** column shows how many tenants it reached.

## Summary Bar

Selecting a tile filters the table to the issues it counts.

| Tile              | Description                                                        |
| ----------------- | ------------------------------------------------------------------ |
| Open              | How many issues are unresolved.                                    |
| Open incidents    | How many unresolved issues Microsoft has classified as incidents.  |
| Open advisories   | How many unresolved issues Microsoft has classified as advisories. |
| Services affected | How many distinct services have at least one unresolved issue.     |

## Filters

| Filter          | Shows                                                     |
| --------------- | --------------------------------------------------------- |
| Open            | Issues Microsoft has not yet marked as resolved.          |
| Open incidents  | Unresolved issues Microsoft has classified as incidents.  |
| Open advisories | Unresolved issues Microsoft has classified as advisories. |
| Resolved        | Issues Microsoft has marked as resolved.                  |

## Table Details

The properties returned are for the Graph resource type `serviceHealthIssue`. For more information on the properties please see the [Graph documentation](https://learn.microsoft.com/en-us/graph/api/resources/servicehealthissue?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>

Below the issue details, the flyout lists every update Microsoft has posted for the issue, newest first, with the newest expanded. With All Tenants selected, it also lists every tenant the issue was posted to. Links inside an update open in a new browser tab.

***

## 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/issues.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.