Connector library

Implemented source APIs, Messaging & Protocols

Microsoft Graph API connector.

Retrieve Microsoft 365 tenant service health and incident details with paged health-overview and issue queries through Microsoft Graph v1.0.

Connector download

Download Microsoft Graph API

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.1 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Bearer token
Connection settings
API Base URL
Package size
7 KB
SHA-256
4b880a9e5ab5c0914bcb0dc821f7b1aff587cd455c391a4e78cabda75833e68a

Version history

What's new

  1. v0.2.0.1Latest · 2026-10-03 · Implemented source

    Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.

  2. v0.2.0.0Earlier · 2026-10-03 · Implemented source

    Retrieve Microsoft 365 tenant service health and incident details with paged health-overview and issue queries through Microsoft Graph v1.0.

  3. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Retained immutable historical scaffold archive.

Included in this version

Included actions

Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.

List service health

Retrieve one vendor-sized page of up to 100 service health summaries.

Get service health

Retrieve a service health summary by the ID returned by List service health.

List service issues

Retrieve one page of service issues; these are vendor reports, not local tickets.

Get service issue

Retrieve a Microsoft 365 service issue and updates.

Vendor API

API and access

Implementation considerations
  • Protocol connectors are intentionally broad; start with simple get/create/update/delete or send/receive operations and add schema-specific behavior per customer.
  • Confirm authentication, TLS, VPN/private networking, payload schema, idempotency keys, rate limits, and retry expectations.
  • Keep secrets out of payloads, prompts, and logs; store credentials centrally and redact sensitive fields.
  • Microsoft Graph calendar APIs support calendar, calendarGroup, event, attendee, and meeting-time workflows.
  • CXFabric Microsoft workflows should confirm delegated versus application permissions, tenant consent, mailbox scope, and throttling behavior.

Support

Need help with Microsoft Graph API?

Tell us what you need to connect or change.