Terraform Cloud Notifies Slack When Infrastructure Changes. Teams Users Never See What's Deploying.

Terraform Cloud (now HCP Terraform) has built-in Slack notifications. In any workspace, go to Settings → Notifications → Create a Notification → Slack. Authenticate with your Slack workspace, select a channel, and choose notification triggers: run completed, run errored, run needs attention. When a Terraform plan finishes or an apply fails, the event appears in the Slack channel.

Terraform Cloud has no equivalent built-in Microsoft Teams notification.

There is no Terraform Cloud → Teams integration in the workspace notification settings. There is no native webhook that routes run events to Teams channels. For platform engineering and infrastructure organizations where engineers use Slack but engineering leadership, architects, or compliance teams use Teams, Terraform run results are invisible to the Teams-side audience.

What Teams Users Don't See

The visibility gap compounds across three event types:

Run completions and failures. When a Terraform apply succeeds in production — new resources provisioned, configuration changes deployed — the event reaches Slack. Engineering managers and architects in Teams see nothing until someone posts a status update manually.

When a production apply fails — resource provisioning error, state lock conflict, provider API failure — the on-call Slack channel receives the event. Teams-side engineering leads who need to make escalation decisions see nothing.

Drift detection. Terraform Cloud continuous validation (Plus and Enterprise plans) detects configuration drift — when real infrastructure has changed outside of Terraform (manual changes in the console, changes by other automation, resource deletions). A drift:detected event fires when the real state diverges from the managed state. This is one of the highest-urgency infrastructure signals for compliance-regulated environments. It reaches only Slack.

Sentinel policy failures. When a run fails a Sentinel policy check — the policy check:soft_failed event allows override; policy_check:hard_failed blocks the apply — the compliance owner needs to know immediately. In organizations where the compliance team uses Teams, Sentinel policy violations are Slack-only.

Webhook Notification Path

Terraform Cloud supports generic webhook notifications (Workspace Settings → Notifications → Webhook) alongside the native Slack integration. Configure a webhook notification pointing to a SyncRivo inbound endpoint. Both the native Slack notification and the SyncRivo webhook notification can be active simultaneously — they fire independently.

Configure routing rules in SyncRivo:

• run:errored (production workspace) → 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:errored (staging workspace) → Slack #infrastructure only (suppress Teams for non-production)

Organization-Level Notifications

Terraform Cloud Business plans support organization-level notification configurations — a single webhook that receives events from all workspaces in the organization. Point an organization-level webhook at SyncRivo. Use SyncRivo routing rules with workspace identifier filtering to route production workspace events to Teams leadership channels while suppressing staging and development workspace noise from stakeholder channels.

For the complete workspace webhook setup, organization-level configuration, and Sentinel policy routing patterns, see the Terraform Cloud Run Notifications in Slack & Teams integration guide.