Docs / Vendor onboarding

Connect Microsoft Graph webhooks to Relin

Relin receives Microsoft Graph webhooks, verifies signatures, stores payloads, and delivers them to your endpoints with retries, alerts, and replay.

Open the Microsoft Graph dashboard

Before you start

  • Create a Relin workspace and sign in.
  • Have admin access to the Microsoft Graph account where you'll configure the webhook.
  • Decide which events you want to capture, or start with "all events" if you're exploring.

Setup steps

  1. In Relin, open your workspace and click New source. Pick the Microsoft Graph tile.
  2. Copy the ingest URL Relin shows. This URL is shown once, so store it.
  3. Create the Relin source first.
  4. Use the source URL when you create the Microsoft Graph subscription.
  5. Leave this blank unless your integration adds its own shared secret.
  6. Save and send a test event from Microsoft Graph. Confirm Relin received it in your workspace.

Signing secret: Optional for this source. Create the source, then use the Relin URL when you subscribe.

What Relin does next

  • Verifies the signature on every incoming event and records the status (verified, failed, unchecked).
  • Stores the payload so you can replay or inspect it later, bounded by your workspace retention window.
  • Delivers the event to every destination you've connected to this source, with retries and per-destination rate limits.
  • Surfaces lifecycle gaps (for vendors with known lifecycles) as anomalies you can triage from the dashboard.

Test it

The fastest check is the events view in your workspace. After you send a test event from Microsoft Graph, it appears within a second or two. Click into the event to see the raw payload, signature status, and the delivery attempts to your destinations.

You can also use the REST API or the MCP tools to inspect the stream programmatically.

Microsoft Graph-specific notes

  • Microsoft Graph webhook subscriptions expire. Renew them before expiration or Relin will stop receiving events; rotation is a Graph API concern, not a Relin one.
  • Graph uses a validation handshake on subscription create. Relin answers it automatically.

Troubleshooting

  • Signature status is failed: the signing secret doesn't match. Re-copy it from Microsoft Graph and update the Relin source.
  • Signature status is unchecked: no signing secret is configured on the source yet. Paste the secret on the source settings page.
  • No events arriving: check that the ingest URL in Microsoft Graph matches the URL Relin shows, including the token segment at the end.
  • Events arrive but destinations fail: open the delivery attempts tab on the event detail page. Each attempt shows the response body, status, and timing.

Next