LaunchDarkly's native Slack integration routes flag change events to Slack channels. The Slack app subscribes to flag toggles, targeting rule changes, and audit log events for a project. When a flag is toggled in production, the event appears in the subscribed Slack channel — with the flag name, environment, who made the change, and the new state.
LaunchDarkly has no equivalent native Microsoft Teams integration.
There is no LaunchDarkly Teams app in the Microsoft Teams app store for flag change notifications. There is no built-in LaunchDarkly integration that routes flag events to Teams channels. For organizations where developers and release engineers use Slack but engineering leadership, product managers, or operations use Teams — flag changes are invisible to the Teams-side audience unless someone posts manually.
The Kill Switch Gap
Kill switch activation is the highest-urgency flag event. When a feature is causing degraded performance, elevated error rates, or customer impact, the kill switch flag is toggled off to disable the feature in production immediately.
This is exactly when cross-platform visibility matters most. The on-call engineer toggling the kill switch is likely in Slack. The engineering director who needs to inform the executive team is likely in Teams. The product manager tracking the feature rollback is likely in Teams.
With LaunchDarkly's native Slack integration, the kill switch event reaches Slack. Teams users see nothing.
Two Webhook Paths
LaunchDarkly offers two webhook integration points, both usable with SyncRivo:
Audit log webhooks (Account Settings → Integrations → Webhooks) fire for every flag and environment change across the entire project — flag toggles, targeting rule edits, new flags, archived flags, segment changes. Point the audit log webhook at a SyncRivo inbound endpoint. Configure routing rules in SyncRivo to filter events: kill switch events to Slack on-call + Teams Engineering Leads simultaneously; targeting changes to Slack releases only; new flag creation to Slack only.
Flag triggers (Flag Settings → Triggers → Webhook, Enterprise plan) allow individual flags to fire a webhook on toggle. Use flag triggers for high-visibility flags where you want Teams coverage: kill switches, billing feature flags, experiment variants in a major launch. Point the flag trigger at SyncRivo. When the specific flag toggles, SyncRivo fans the event to Slack, Teams, Webex, Google Chat, and Zoom.
Native Slack App Coexistence
LaunchDarkly's native Slack app supports interactive features — toggling flags directly from a Slack message, subscribing to specific flag changes from Slack with the /launchdarkly subscribe command. These features require the native Slack app and are Slack-specific.
The SyncRivo webhook path runs in parallel. Keep the native Slack app for interactive Slack features; use SyncRivo for Teams delivery. The same flag change event triggers both paths independently — native Slack app delivers the Slack notification with interactive controls; SyncRivo delivers the Teams notification.
Environment-Based Routing
LaunchDarkly's webhook payloads include the environment where the flag change occurred. Use SyncRivo routing rules to route by environment:
- Production flag toggle → Slack #releases + Teams Engineering Leads simultaneously
- Staging flag toggle → Slack #qa only
- Development environment changes → suppressed (too noisy for stakeholder channels)
This prevents staging and development flag changes from flooding production-monitoring channels on Teams while ensuring production flag events reach the full cross-platform team.
For the complete LaunchDarkly webhook setup, flag trigger configuration, and environment-based routing rules, see the LaunchDarkly Flag Changes in Slack & Teams integration guide.
Ready to connect your messaging platforms?
