Connectors · MSP & PSA

Microsoft 365 Service Health and Message Center MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Microsoft 365 Service Health and Message Center and the rest of your systems. It gives your agent 17 Microsoft 365 Service Health and Message Center actions (11 reads and 6 writes) and holds the Microsoft 365 Service Health and Message Center credential itself, so the agent never does. It paces Microsoft 365 Service Health and Message Center's limits and records every call. Connecting Microsoft 365 Service Health and Message Center needs your own Microsoft 365 Service Health and Message Center OAuth app and one admin sign-in.

Connect Microsoft 365 Service Health and Message Center free See pricing

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

claude mcp add --transport http actionlake https://connect.actionlake.com/mcp

the first call

do {  action: "m365_graph_service_health.issues.list",  intent: "check which Microsoft 365 Service Health and Message Center account is connected"}# List service health issues · read · 1 upstream call

17actionsin one signed file
11readlook, never change
6writecreate and update
0wait for a yesdestructive, confirmed first

Set up

Connect Microsoft 365 Service Health and Message Center in three steps.

01
Add actionlake to Claude.
Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
https://connect.actionlake.com/mcp
02
Connect Microsoft 365 Service Health and Message Center.
OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Microsoft 365 Service Health and Message Center, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on. actionlake stores what you paste write-only, sealed under your tenant's key.
Before the first sign-in, Microsoft 365 Service Health and Message Center needs an OAuth app of your own, registered in its developer portal. actionlake has no Microsoft 365 Service Health and Message Center app to lend you.
- access_tokenAccess token from one sign-in with your own OAuth app
- refresh_tokenRefresh token from the same sign-in; the access token is renewed from it
- client_idEntra application (client) id with delegated Graph permissions ServiceHealth.Read.All, ServiceMessage.Read.All and…
- client_secretEntra client secret
- tenant_idYour Microsoft 365 Service Health and Message Center tenant id
```
account { op: "connections.requirements", service: "m365_graph_service_health" }
# free: exactly what to paste, and what is found for you
```

Make the first call. Check before a write.

Ask in plain words; Claude picks the action. Before anything changes, check validates the call and prices it, for free.

do    { action: "m365_graph_service_health.issues.list" }# list service health issues · read · 1 upstream callcheck { action: "m365_graph_service_health.messages.archive", input: { … } }# free: inputs, permissions, cost and confirmations, nothing sent

Microsoft 365 Service Health and Message Center at a glance

Sign-in: OAuth 2.0, authorization code with PKCE. You register your own OAuth app with Microsoft 365 Service Health and Message Center, an admin signs in once, and you paste the app's client id and secret and the tokens from that sign-in; actionlake renews the access token from then on.
You provide: access_tokenrefresh_tokenclient_idclient_secret
Setup fields: tenant_id
Limits we pace to: 10,000 calls per 10 minutes, per connection
API covered: Microsoft Graph v1.0 (service communications API)graph.microsoft.com
Built from: Microsoft 365 Service Health and Message Center's documentation, read 23 October 2026OpenAPI spec (GitHub)learn.microsoft.com
Service file: Version 1.0.0, signed (Ed25519)
Cached reads: 11 of 11 reads, for up to 5 minutes; a write clears what it affects
Shared entities: 3, so ask can line Microsoft 365 Service Health and Message Center up with your other systems
Data: Processed and stored in Sydney, Australia. No US region yet

Capabilities

What an AI agent can do in Microsoft 365 Service Health and Message Center.

17 actions in 1 area. Every one carries its effect, so a key can allow the reads and hold the rest.

11readlook, never change
6writecreate and update
0destructivewait for a confirmation

Service health
17
11 read · 6 write · 0 destructive
Get the signed-in user · List service health issues · List service health overviews · Get a service health issue

Top actions

The Microsoft 365 Service Health and Message Center API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 5 of Microsoft 365 Service Health and Message Center's 5 action names are shared with at least one other connector, so an agent learns them once.

Action	What it does	Effect	Same name in
`m365_graph_service_health.me.get`Get the signed-in user	The signed-in admin behind this connection; a cheap check that the connection works.	read	`identity.current_user.get`307 connectors
`m365_graph_service_health.issues.list`List service health issues	Every service health issue (incident or advisory) for the tenant across all services, active and resolved.	read	`monitoring.incident.list`19 connectors
`m365_graph_service_health.health_overviews.list`List service health overviews	Current health status of every Microsoft 365 cloud service subscribed by the tenant (one row per service).	read	`monitoring.service.list`12 connectors
`m365_graph_service_health.issues.get`Get a service health issue	One service health issue with its impact description, status and posts (the timeline of updates).	read	`monitoring.incident.get`20 connectors
`m365_graph_service_health.health_overviews.get`Get one service's health overview	Health status of one Microsoft 365 service; add expand=issues to include its open and recent issues.	read	`monitoring.service.get`11 connectors
`m365_graph_service_health.messages.list`List message center posts	Message center posts (planned changes, new features, admin actions required) for the tenant.	read	this connector
`m365_graph_service_health.message_attachments.list`List a message center post's attachments	Attachments of one message center post, with base64 content inline.	read	this connector
`m365_graph_service_health.health_overview_issues.list`List the issues of one service	Service health issues (incidents and advisories) for one Microsoft 365 service.	read	this connector
`m365_graph_service_health.messages.archive`Archive message center posts	Archive a list of message center posts for the signed-in user.	write	this connector
`m365_graph_service_health.messages.favorite`Favorite message center posts	Mark a list of message center posts as favorite for the signed-in user.	write	this connector
`m365_graph_service_health.messages.mark_read`Mark message center posts as read	Mark a list of message center posts as read for the signed-in user.	write	this connector

Try it

Prompts to paste into Claude.

Each one names the Microsoft 365 Service Health and Message Center actions it will call, so you know what it reads and what it changes before you send it.

Readread
Which Microsoft 365 Service Health and Message Center incidents are open, and how long has each been open?
callsm365_graph_service_health.issues.list
Writewrite
Archive message center posts in Microsoft 365 Service Health and Message Center. Show me exactly what you will send before you save it.
callsm365_graph_service_health.messages.archive

Governance for Microsoft 365 Service Health and Message Center

Every write can wait for a yes.

None of Microsoft 365 Service Health and Message Center's actions is destructive. A key can still be held to reads, capped, and set so a person confirms every write.

A destructive action runs only with confirm: true. Under the human policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

a key for this connector

account {  op: "keys.create", name: "m365-graph-service-health-agent",  allowed_actions: ["m365_graph_service_health.*"], cap_calls: 2000,  confirm_policy: "human_for_writes"}

Illustrative. Scoped to Microsoft 365 Service Health and Message Center only, capped at 2,000 upstream calls, every write confirmed.

Cost

What Microsoft 365 Service Health and Message Center costs on actionlake.

Every Microsoft 365 Service Health and Message Center action is one upstream call, the only thing actionlake bills. Searching, check, cost, account and any call Microsoft 365 Service Health and Message Center refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

1upstream call per actionall 17 Microsoft 365 Service Health and Message Center actions
5actions pageeach page of a long list is one call
11reads can be cacheda cache hit costs nothing
100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Microsoft 365 Service Health and Message Center action.

17 actions by area: the id your agent calls, what it does, and its effect.

Service health17

m365_graph_service_health.health_overview_issues.getGet one issue of one serviceread
m365_graph_service_health.health_overview_issues.listList the issues of one serviceread
m365_graph_service_health.health_overviews.getGet one service's health overviewread
m365_graph_service_health.health_overviews.listList service health overviewsread
m365_graph_service_health.issues.getGet a service health issueread
m365_graph_service_health.issues.listList service health issuesread
m365_graph_service_health.me.getGet the signed-in userread
m365_graph_service_health.message_attachments.getGet a message center attachmentread
m365_graph_service_health.message_attachments.listList a message center post's attachmentsread
m365_graph_service_health.messages.archiveArchive message center postswrite
m365_graph_service_health.messages.favoriteFavorite message center postswrite
m365_graph_service_health.messages.getGet a message center postread
m365_graph_service_health.messages.listList message center postsread
m365_graph_service_health.messages.mark_readMark message center posts as readwrite
m365_graph_service_health.messages.mark_unreadMark message center posts as unreadwrite
m365_graph_service_health.messages.unarchiveUnarchive message center postswrite
m365_graph_service_health.messages.unfavoriteUnfavorite message center postswrite

Questions

The Microsoft 365 Service Health and Message Center MCP server, answered.

Is there a Microsoft 365 Service Health and Message Center MCP server for Claude?

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 17 Microsoft 365 Service Health and Message Center actions, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Microsoft 365 Service Health and Message Center.

What do I need to connect Microsoft 365 Service Health and Message Center?

Your own Microsoft 365 Service Health and Message Center OAuth app, registered with Microsoft 365 Service Health and Message Center (its client id and client secret), and the access and refresh tokens from one admin sign-in. actionlake has no Microsoft 365 Service Health and Message Center app of its own, so this is not a one-step consent. actionlake renews the access token as it expires. Plus your tenant id. The free call account { op: "connections.requirements", service: "m365_graph_service_health" } lists exactly what to paste.

Can an AI agent change things in Microsoft 365 Service Health and Message Center?

Only if its key allows it. 6 Microsoft 365 Service Health and Message Center actions write, and none is destructive. A key can be limited to reads, capped, and set so a person confirms every write.

Will an AI agent use up my Microsoft 365 Service Health and Message Center API limit?

actionlake paces every call to the limits in the Microsoft 365 Service Health and Message Center service file: 10,000 calls per 10 minutes per connection. Repeated reads are answered from cache (11 Microsoft 365 Service Health and Message Center actions can be), which never reaches Microsoft 365 Service Health and Message Center.

What does a Microsoft 365 Service Health and Message Center action cost?

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (5 Microsoft 365 Service Health and Message Center actions page). Cache hits, searches, dry runs and calls Microsoft 365 Service Health and Message Center refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

Which Microsoft 365 Service Health and Message Center API does it cover?

The Microsoft Graph v1.0 (service communications API) at graph.microsoft.com. It is built from Microsoft 365 Service Health and Message Center's documentation as read on 23 October 2026. 17 actions in 1 area, each one in the signed service file (version 1.0.0).

Does actionlake keep my Microsoft 365 Service Health and Message Center data, and where?

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Microsoft 365 Service Health and Message Center credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

Which AI clients can use it?

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

Give your agent Microsoft 365 Service Health and Message Center today.