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

# Message Center

This tab lists the Microsoft 365 message center posts for the selected tenant: Microsoft's notices of new, changing, and retiring features, planned changes, and posts that need an administrator to act by a given date. The other Service Health tabs are described on [Service Health](/user-documentation/tenant/administration/service-health.md).

With All Tenants selected, a post Microsoft sent to several tenants is listed once, and the **Tenant** column shows how many tenants it reached.

## Summary Bar

| Tile             | Description                                                                                                  |
| ---------------- | ------------------------------------------------------------------------------------------------------------ |
| Action required  | How many posts carry a date by which action is required.                                                     |
| Major changes    | How many posts Microsoft has flagged as a major change. Selecting the tile filters the table to those posts. |
| High or critical | How many posts carry a severity above normal.                                                                |
| Plan for change  | How many posts are in the Plan for change category. Selecting the tile filters the table to those posts.     |

## Filters

| Filter               | Shows                                                            |
| -------------------- | ---------------------------------------------------------------- |
| Major changes        | Posts Microsoft has flagged as a major change.                   |
| High or critical     | Posts with a severity above normal.                              |
| Plan for change      | Posts announcing changes you may need to prepare for.            |
| Prevent or fix issue | Posts about known problems and the steps to prevent or fix them. |

## Table Details

The properties returned are for the Graph resource type `serviceUpdateMessage`. For more information on the properties please see the [Graph documentation](https://learn.microsoft.com/en-us/graph/api/resources/serviceupdatemessage?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 post details, the flyout shows the full text of the post. With All Tenants selected, it also lists every tenant the post was sent to. Links inside the post 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/message-center.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.