Microsoft 365 Service Health (BYOK)

Microsoft 365 Service Health (BYOK) — connector documentation

• MCP endpoint: https://byok-graph-service-health.connectorbay.com/mcp
• REST API: POST https://byok-graph-service-health.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-graph-service-health.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Microsoft 365 Service Health Microsoft Graph access token (an OAuth token valid for about an hour), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-graph-service-health.connectorbay.com/health · Tool schemas: https://byok-graph-service-health.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-graph-service-health · agent@connectorbay.com

What Microsoft 365 Service Health (BYOK) is for

Microsoft 365 Service Health (BYOK) lets an AI assistant read your own Microsoft 365 Service Health data through the Microsoft 365 Service Health API with a key you supply (Microsoft Graph access token (an OAuth token valid for about an hour)). Read-only: 6 tools (list_service_health, get_service_health, list_service_issues, get_service_issue, list_message_center, get_message_center_post). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to graph.microsoft.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Microsoft 365 Service Health. Microsoft 365 Service Health and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Are any Microsoft 365 services degraded right now?"
• "What is the health of Exchange Online and what issues does it have?"
• "Which Microsoft 365 incidents are open at the moment?"
• "What is the status of Microsoft 365 issue EX123456?"
• "Which Microsoft 365 changes need action in the next weeks?"
• "What does Message center post MC123456 say?"

What it does

• list_service_health: List the current health status of each Microsoft 365 service in the tenant (for example Exchange Online: serviceOperational or serviceDegradation). Needs ServiceHealth.Read.All.
• get_service_health: Get one service's health status together with its open and recent issues. Needs ServiceHealth.Read.All.
• list_service_issues: List service health issues (incidents and advisories) for the tenant with service, classification, status, times and impact summary. Needs ServiceHealth.Read.All.
• get_service_issue: Get one service health issue by id (for example EX123456) with status, impact description and timing. Needs ServiceHealth.Read.All.
• list_message_center: List Message center announcements (planned changes, retirements, prevent-or-fix notices) with category, severity, affected services, dates and action-required date. Needs ServiceMessage.Read.All.
• get_message_center_post: Get one Message center announcement by id (for example MC123456) with its dates, severity, affected services and body text. Needs ServiceMessage.Read.All.

BYOK key

You bring your own Microsoft 365 Service Health Microsoft Graph access token (an OAuth token valid for about an hour) (https://developer.microsoft.com/en-us/graph/graph-explorer). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to graph.microsoft.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://learn.microsoft.com/en-us/graph/api/resources/serviceannouncement?view=graph-rest-1.0 (the API this connector calls, with a BYOK key)

Live from the Microsoft 365 Service Health API (graph.microsoft.com) with a BYOK key; documentation: https://learn.microsoft.com/en-us/graph/api/resources/serviceannouncement?view=graph-rest-1.0. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Microsoft 365 Service Health. Microsoft 365 Service Health and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Microsoft 365 Service Health account.

Built for: Worldwide. Languages: English.

Microsoft 365 Service Health (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Microsoft 365 Service Health (BYOK) is. Microsoft 365 Service Health (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Microsoft 365 Service Health data: Read Microsoft 365 service health, incidents and Message center announcements for your tenant with a Microsoft Graph access token. You bring your own Microsoft 365 Service Health Microsoft Graph access token (an OAuth token valid for about an hour); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Microsoft 365 Service Health call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to graph.microsoft.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Microsoft 365 Service Health rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Microsoft 365 Service Health receives. The request we make on your behalf, including the key and the arguments, under Microsoft 365 Service Health's own terms and privacy policy. Microsoft 365 Service Health acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Microsoft 365 Service Health gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Microsoft 365 Service Health data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Microsoft 365 Service Health (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Microsoft 365 Service Health at any time to end all access.

Children. Microsoft 365 Service Health (BYOK) is a general-audience service operated by the adult using the assistant, under Microsoft 365 Service Health's own age rules.

Changes. We will post changes here with a new effective date.

Microsoft 365 Service Health (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Microsoft 365 Service Health (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Microsoft 365 Service Health (BYOK) provides: Read Microsoft 365 service health, incidents and Message center announcements for your tenant with a Microsoft Graph access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Microsoft 365 Service Health credentials and only access data you are allowed to access. Microsoft 365 Service Health's terms apply to your use of Microsoft 365 Service Health; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Microsoft 365 Service Health. Microsoft 365 Service Health and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Microsoft 365 Service Health returns, lightly trimmed; it may be incomplete, delayed or changed by Microsoft 365 Service Health. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Microsoft 365 Service Health account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Microsoft 365 Service Health's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Microsoft 365 Service Health may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Microsoft 365 Service Health key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Microsoft 365 Service Health takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-graph-service-health

Microsoft 365 Service Health (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-graph-service-health.connectorbay.com/mcp
• REST API: https://byok-graph-service-health.connectorbay.com/openapi.json
• Live status: https://byok-graph-service-health.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Microsoft 365 Service Health (BYOK) never asks for them.