Alex Morgan · Principal Engineer
Alex Morgan is a principal engineer at SyncRivo, focused on platform architecture, reliability engineering, and the infrastructure powering real-time messaging interoperability. LinkedIn
April 10, 2026 · 9 min read
Route Terraform Cloud run completions, apply failures, drift detection events, and Sentinel policy failures to Slack, Teams, Webex, Google Chat, and Zoom simultaneously.
Terraform Cloud has built-in Slack workspace notifications — but no native Teams notification. Infrastructure run results, drift detection, and policy failures are Slack-only. When infrastructure deploys or drifts, your Teams-side stakeholders are the last to know.
Every Terraform Cloud event — run completions, failures, drift detection, and Sentinel policy checks — delivered simultaneously to Slack, Teams, Webex, Google Chat, and Zoom.
Successful infrastructure apply events — new resources provisioned, configuration changes applied — routed to the infrastructure Slack channel and the engineering leads Teams channel simultaneously for deployment confirmation across both platforms.
Plan or apply failure events routed to the on-call infrastructure Slack channel and the engineering leads Teams channel immediately — so infrastructure failures are never siloed on one platform when response requires cross-team coordination.
Plan-complete events awaiting manual confirmation before apply — routed to the approving engineer on their native platform (Slack DM or Teams DM) and to the infrastructure review channel for visibility while the apply is pending.
Infrastructure drift detection events — real infrastructure diverged from Terraform state — routed to the infrastructure Slack channel and the compliance Teams channel simultaneously for coordinated investigation and remediation.
Sentinel policy check failures (soft-fail or hard-fail) routed to the infrastructure Slack channel and the security compliance Teams channel simultaneously — giving the infrastructure team and the compliance owner immediate cross-platform visibility.
Terraform Cloud workspace health assessment failures routed to the platform engineering Slack channel and the infrastructure leads Teams channel for coordinated response to persistent state drift or configuration issues.
In Terraform Cloud, go to any workspace → Settings → Notifications → Create a Notification. Select Webhook as the destination. Set the URL to your SyncRivo inbound endpoint. Select triggers: run:completed, run:errored, run:needs_attention, assessment:drifted, assessment:failed, policy_check:soft_failed. Optionally set an HMAC signing key — SyncRivo verifies the signature automatically.
Terraform Cloud Business plans support organization-level notification configurations that apply to all workspaces. Use an organization webhook pointing to a single SyncRivo endpoint. Configure workspace-based routing rules in SyncRivo — route production workspace events to Teams leadership channels; route staging events to Slack engineering only.
Set per-event routing in SyncRivo: run:errored → Slack #on-call + Teams Infrastructure Engineering simultaneously; assessment:drifted → Slack #infrastructure + Teams Compliance simultaneously; policy_check:soft_failed → Slack #infrastructure + Teams Compliance; run:completed (production workspace) → Slack #infrastructure + Teams Engineering Leads; run:completed (staging) → Slack #infrastructure only.
Terraform Cloud's built-in Slack notification includes rich formatting with run links, workspace context, and status icons. Keep the native Slack notification for Slack channels where the rich format is useful. Run the SyncRivo webhook notification in parallel for Teams delivery — both notifications fire from the same workspace configuration independently.
Route Terraform Cloud events to the right audience — infrastructure engineers in Slack, compliance and leadership in Teams — based on event type and workspace environment.
| Terraform Cloud Event | Slack Destination | Teams Destination | Rationale |
|---|---|---|---|
| Run errored (production) | #on-call (immediate response) | Infrastructure Engineering channel | On-call investigates; leadership tracks production incidents |
| Apply completed (production) | #infrastructure (deploy log) | Engineering Leads channel | Engineers track deploys; leads confirm production changes |
| Needs attention (plan awaiting approval) | #infrastructure (reviewer alert) | Engineering Leads channel | Engineers see pending applies; leads aware of blocked deploys |
| Drift detected | #infrastructure (remediation) | Compliance channel | Infra team remediates; compliance tracks state violations |
| Sentinel policy soft-failed | #infrastructure (review needed) | Compliance channel | Infra decides override; compliance monitors policy exceptions |
| Run errored (staging) | #infrastructure (Slack only) | — (staging not forwarded) | Staging failures are dev-team scope; no leadership escalation |
| Capability | Terraform Cloud Native | SyncRivo |
|---|---|---|
| Notify Slack | ✓ Built-in Slack notification (Workspace Settings → Notifications → Slack) | ✓ Via SyncRivo webhook relay |
| Notify Microsoft Teams | ✗ No native Teams notification | ✓ Full Teams channel delivery via SyncRivo routing |
| Notify Webex / Google Chat / Zoom | ✗ Not available natively | ✓ All 5 platforms |
| Single run event → Slack AND Teams simultaneously | ✗ Slack notification is Slack-only | ✓ One webhook URL, fan-out to all platforms |
| Drift detection → infra Slack + compliance Teams simultaneously | ✗ Slack-only drift notification | ✓ Per-event routing rules handle simultaneous delivery |
| Sentinel policy failures → compliance Teams channel | ✗ No Teams notification for policy checks | ✓ Policy check events routed to compliance Teams |
| M&A: notify both organizations on their native platforms | ✗ Slack-only | ✓ Add destination in SyncRivo in minutes |
| Per-workspace routing rules | ✗ One Slack channel per workspace notification config | ✓ Route by event type, workspace, or environment across any channel set |
Terraform Cloud (now HCP Terraform) does not have a native Microsoft Teams integration for run notifications. Terraform Cloud has a built-in Slack workspace notification integration (Workspace Settings → Notifications → Slack) that routes run plan results, apply completions, apply failures, and policy check events to a Slack channel. There is no equivalent built-in Teams notification in Terraform Cloud. For infrastructure and platform engineering organizations where engineers use Slack but engineering leadership, architects, or compliance teams use Teams, configure Terraform Cloud generic webhooks (Workspace Settings → Notifications → Webhook) pointing to SyncRivo. SyncRivo routes Terraform Cloud run events to Slack, Teams, Webex, Google Chat, and Zoom simultaneously.
In Terraform Cloud, go to the workspace where you want Teams notifications → Settings → Notifications → Create a Notification. Select "Webhook" as the destination type. Set the URL to your SyncRivo inbound endpoint. Select the notification triggers: run completed, run needs attention, run errored, drift detected. SyncRivo receives the Terraform Cloud webhook payload and routes to your configured Teams channel in real time.
SyncRivo routes any Terraform Cloud webhook notification trigger: run:planning (plan started), run:needs_attention (plan finished, awaiting confirmation), run:applying (apply started), run:completed (apply succeeded), run:errored (plan or apply failed), assessment:drifted (drift detection found infrastructure drift), assessment:failed (health assessment failed), policy_check:soft_failed (Sentinel policy soft-failed). Configure routing rules in SyncRivo — route apply failures to both the on-call Slack channel and the infrastructure Teams channel simultaneously; route drift detection to the infrastructure Slack channel and the platform engineering leads Teams channel.
Yes. Terraform Cloud continuous validation (available on Plus and Enterprise plans) runs health assessments on managed workspaces and detects configuration drift — when real infrastructure diverges from the Terraform state. When drift is detected, Terraform Cloud fires an assessment:drifted webhook notification. Point this notification at SyncRivo to route drift alerts to Slack, Teams, Webex, Google Chat, and Zoom simultaneously. Drift detection is particularly valuable for compliance-regulated infrastructure — route drift alerts to the infrastructure Slack channel and the compliance Teams channel at the same time.
Yes. Post-merger organizations often have infrastructure teams on different platforms — one organization's platform engineers on Slack, the other on Teams. Terraform Cloud run notifications (plan results, apply completions, drift detection) need to reach both teams when managing shared or transitioning infrastructure. SyncRivo receives the Terraform Cloud webhook payload and routes to Slack and Teams channels simultaneously — so infrastructure changes are visible to the full cross-platform team without requiring platform migration.
Yes. Terraform Cloud Sentinel policy checks fire webhook notifications when a run's policy evaluation completes. A policy_check:soft_failed notification indicates a policy failed but can be overridden; policy_check:hard_failed blocks the apply. Point Terraform Cloud policy check notifications at SyncRivo to route Sentinel policy failures to the security compliance Teams channel and the infrastructure Slack channel simultaneously — giving both the infrastructure team and the compliance owner immediate visibility into policy violations without waiting for manual escalation.
Terraform Cloud notifies Slack when infrastructure changes. SyncRivo routes those same events to Teams, Webex, Google Chat, and Zoom — simultaneously, from one webhook, with per-event and per-workspace routing rules.
Ready to connect? Slack ↔ Teams connection setup →