Microsoft Teams
Monitor Teams event notification delivery and logs.
This page covers Adaptive Card format, send history, and delivery logs for Microsoft Teams event notifications. Open MS Teams history and MS Teams delivery logs in the admin console. For endpoint setup and admin controls, see Microsoft Teams integrations. For how visitors subscribe on /subscribe, see Teams subscriptions.
When an event with Notifications enabled triggers a delivery, matching verified Teams subscribers receive an HTTPS POST with a Teams Adaptive Card describing the event at send time. For incidents and maintenance, the card includes an Impact Analysis section after the description when that field is set (before affected components).
Description, impact analysis, and timeline messages keep the formatting you author in the event editor: bold, italic, links, and bullet or numbered lists. Strikethrough and inline code are sent as plain text (Adaptive Cards do not style those).
For how Visibility and subscription toggles affect delivery across channels, see Notifications overview — FAQ. Turning the dashboard Subscriptions Teams toggle off hides public sign-up; existing verified endpoints still receive deliveries.
Monthly integration message limit
Outbound webhook, Teams, Google Chat, and Slack deliveries share an organization monthly integration message limit (UTC calendar month). Usage appears on Overview and integration or notification screens.
- When the limit is reached, further deliveries are skipped (logged as skipped for quota) and are not retried.
- Event saves always succeed — the limit applies only to asynchronous outbound delivery.
Send history
MS Teams history shows a UTC calendar-month bar graph of event notification MS Teams deliveries per day. Navigate 13 months of history with previous/next month controls. Counts match the event-notification portion of your combined integration delivery quota (history is tracked per channel). All bucketing uses UTC calendar days and months.
Delivery logs
MS Teams delivery logs list individual delivery attempts. Each row includes:
| Field | Meaning |
|---|---|
| Endpoint | Redacted endpoint display (urlDisplay) |
| Status | Aggregate outcome — Accepted, Failed, or Skipped (see below) |
| HTTP status | Numeric response status when a response was received |
| Event / dashboard | Related event and dashboard when applicable |
| Error | Short client-side reason on failures |
Open a row for request and response bodies (may be truncated). Logs are retained for 30 days.
Each log includes a delivery timeline with one step — integration delivery is a single HTTP round-trip. Status reflects the endpoint's HTTP response, not delivery inside Microsoft Teams or your handler.
Status values
| Status | Meaning |
|---|---|
| Queued | Delivery job accepted |
| Accepted | Destination returned HTTP 2xx |
| Failed | HTTP or network failure |
| Skipped (suppressed) | Endpoint is on the suppression list — no HTTP call. Clear on Teams suppression or see Suppression. |
| Skipped (quota) | Monthly integration message limit reached |
| Skipped (feature) | Integrations entitlement not available at send time |
Delivery timeline
| Timeline step | When it appears |
|---|---|
| Endpoint accepted | HTTP 2xx response received |
| Endpoint rejected | HTTP 4xx/5xx response received |
| Request failed | Network error before a response |
| Not attempted | Suppressed, quota, or feature skip — no HTTP call |