The complete guide to Microsoft Webhooks โ connect services, automate workflows, and build event-driven integrations across Teams, SharePoint, Azure & beyond.
A webhook is a user-defined HTTP callback. When an event occurs, the source makes an HTTP POST to the registered URL โ delivering real-time data with zero polling.
A change happens in the source system (new message, file update, build completes).
The source sends a JSON payload to your registered webhook endpoint URL.
Your endpoint verifies the request via HMAC signature, header key, or query string.
Your service processes the payload โ logging, alerting, transforming, or forwarding data.
Microsoft supports webhooks across its entire cloud ecosystem. Each service has its own webhook capabilities and patterns.
Incoming Webhooks post messages with Adaptive Cards to channels. Outgoing Webhooks let users @mention a service and get real-time responses within 10 seconds.
Subscribe to list and library changes with SharePoint webhooks. Notifications include the subscription ID, resource URL, and tenant ID โ use GetChanges API for details.
Service hooks send JSON event payloads for work items, builds, releases, code pushes, and pull requests. Supports HTTPS endpoints with filtering and basic auth.
Register webhooks as service endpoints to receive server event data. Supports HttpHeader, WebhookKey, and HttpQueryString authentication with 60-second timeouts.
Trigger runbooks via webhook URLs for maintenance events, VM management, and scheduled tasks. Integrates with Event Grid for pre/post maintenance workflows.
Subscribe to change notifications for users, messages, calendar events, drive items, and more. Uses delta queries for efficient state synchronization across tenants.
Simulate sending webhook payloads and see the response in real-time. Edit the JSON, choose a scenario, and fire away.
Get started with webhooks in your language of choice. Copy, paste, and deploy.
Essential patterns and best practices when working with Microsoft webhooks.
Implement exponential backoff. Microsoft services retry failed deliveries โ return 2xx quickly to confirm receipt.
Always validate the signature header using a shared secret to ensure the payload is from a trusted source.
Most Microsoft services enforce a 60-second timeout. Process webhooks async โ acknowledge first, process later.
Teams limits messages to 28KB. Dataverse strips properties when payloads exceed 256KB. Design compact payloads.
Teams throttles at 4 requests/second per connector. Azure DevOps may batch notifications. Monitor HTTP 429 responses.
Webhooks may be delivered more than once. Use unique event IDs to deduplicate and ensure safe reprocessing.
SharePoint and Graph subscriptions expire. Implement renewal logic before expiration to maintain continuity.
All Microsoft webhook endpoints must use HTTPS. HTTP endpoints will be rejected to prevent data leakage.
Real-time log of webhook activity from the tester above.