Microsoft Graph Source Configuration

Microsoft Graph configuration

Create a Microsoft Graph source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Optional Client State values for provider signature. FastHook uses these settings to validate each Microsoft Graph delivery before it enters the routing workflow.

{
  "type": "MICROSOFT_GRAPH",
  "config": {
    "auth_type": "PROVIDER_SIGNATURE",
    "auth": {
      "provider": "MICROSOFT_GRAPH",
      "client_state": "optional-client-state"
    },
    "allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
  }
}

Validation token before change notifications

1. Microsoft Graph validates the notification URL with a validationToken value.
2. FastHook returns the validationToken as plaintext.
3. After validation succeeds, Graph sends change notifications and FastHook can check clientState when configured.

Microsoft Graph request contract

Microsoft Graph validation is challenge-based. FastHook echoes validationToken and optionally verifies notification clientState values.

Special response: Validation requests return the validationToken value as plaintext.

Microsoft Graph headers

Preserve validationToken, clientState when sending Microsoft Graph test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.

Microsoft Graph setup

1. Create a Graph change notification subscription with the FastHook Source URL.
2. If you use clientState, configure the same value in FastHook.
3. Use Requests to confirm validation requests and POST notifications are stored separately.

Continue with Microsoft Graph

• Microsoft Graph change notifications documentation
• Source operations and troubleshooting