Legacy: use a Teams webhook

From rConfig V8.4.1 the .env-based Teams integration on this page is legacy. It keeps working for existing installs, but it gets no new features and is scheduled for removal in a future major release.

New setups should use a Teams webhook instead. You set it up in Settings → Notifications with no .env changes, and it posts to as many channels as you like, covers every event type, and keeps a delivery log. See Move to a Teams webhook below. The Power Platform DLP notes on this page apply to Teams webhooks too.

MS Teams Notifications: Real-Time Network Configuration Alerts for rConfig V8

MS Teams Notifications enable rConfig V8 to send real-time alerts and updates directly to your MS Teams channels. This integration keeps your team informed of important network events, configuration changes, and system activities without requiring constant monitoring of the rConfig interface.

When to Use This Page

Use this page if you already run the .env Teams integration, or you’re on a version older than V8.4.1. It covers configuration changes and SNMP traps that match a filter with a Send Alert action.

Move to a Teams webhook

1. In Teams, open the channel, then ⋯ → Workflows → Post to a channel when a webhook request is received. Finish the wizard and copy the URL it gives you. Your existing TEAMS_WEBHOOK_URL works too.
2. In rConfig, go to Settings → Notifications and click Add Teams webhook in the Slack and Microsoft Teams section.
3. Paste the URL, tick Configuration Changed and SNMP Trap Received (or any other events you want), and click Send test.
4. Once the test arrives, switch the legacy integration off: set TEAMS_ENABLED=false in .env and run php artisan rconfig:clear-all. Otherwise each event posts twice.

The Webhooks page covers event and severity filters, delivery logs and re-sends.

Supported Notification Types

rConfig V8 can send the following notifications to MS Teams:

Notification Type	Description	Availability
Configuration Changes	Alerts when device configurations are modified	rConfig V8+
SNMP Traps	Alerts when a received trap matches a filter with a Send Alert action (SNMP Trap UI Administration)	rConfig V8+
Health Checks	Alerts when system health checks start failing, and again when they recover	V8.4.1+

Note

Additional notification types will be added in future releases. Check release notes for updates.

Prerequisites

Before configuring MS Teams notifications, ensure you have:

• Active MS Teams workspace with administrative access
• Ability to create and install MS Teams apps
• Channel(s) designated for rConfig notifications
• Administrator access to rConfig V8

Create MS Teams App

In order to receive notifications in MS Teams, you need to create a webhook URL and workflow for the integration. Information on how to do this can be found in the Microsoft documentation: Create an Incoming Webhook. If you have any issues setting up the webhook, please reach out to your Azure/ O365 support Admin for assistance.

Hint: Most O365 Environments will have a Power Platform DLP that disables the use of custom connectors. Contact your O365 Admin to allow the use of custom connectors for the rConfig integration. Specifically, the When a Teams webhook request is received connector must be allowed for the integration to work.

Configure rConfig V8

Step 1: Edit Environment Configuration

Open the rConfig .env file:

vim /var/www/html/rconfig8/current/.env

Step 2: Add MS Teams Configuration

Add or update the following lines:

# MS Teams Integration
TEAMS_ENABLED=false
TEAMS_WEBHOOK_URL=

Configuration Parameters:

• TEAMS_ENABLED: Set to true to enable MS Teams notifications
• TEAMS_WEBHOOK_URL: Webhook URL from MS Teams app

Step 3: Clear Application Cache

Save the file and clear the rConfig cache:

php /var/www/html/rconfig8/current/artisan rconfig:clear-all

Verify the Integration

Check Status in rConfig

Go to Settings → Notifications and scroll to Slack and Microsoft Teams (server configured), marked Legacy. The Microsoft Teams Notifications panel shows whether Teams is enabled and has a Test Teams Notification button. A Teams webhook is bound to one channel when you create it in Teams, so every notification goes to that channel.

Choose which events post

The table above the panels has a Teams switch for Configuration Changed and SNMP Trap Received, both on by default, and from V8.4.1 for Health Check Failed and Health Check Recovered, both off by default. The switches apply to the whole organisation and are locked until Teams is enabled in .env. Changing them needs permission to update settings.

Note

From V8.4.1 users no longer opt in to Teams on their profile page. Before V8.4.1, events only posted when at least one user had ticked Microsoft Teams in Notification Preferences. The upgrade removes those per-user choices.

Send a Test Message

Click Test Teams Notification to verify the integration is working correctly. The test posts directly to the webhook, whether or not any events are switched on.

Expected test message in MS Teams:

rConfig Teams Test Notification
Microsoft Teams test notification from rConfig

Source: https://rconfig.example.com
Timestamp: Tue, Oct 14, 2025 10:23 AM
Channel: Microsoft Teams

Notification Examples

Configuration Change Notification

rConfig Change Notification - core-router-01
Configuration change detected

Device: core-router-01
Device ID: 123
Command: show running-config
Config Version: 42
Timestamp: Tue, Oct 14, 2025 10:23 AM

Changes
<summary of the diff, up to 1,200 characters>

[View Complete Configuration]

SNMP Trap Notification

rConfig SNMP Trap Alert
SNMP trap matched a configured action

Source IP: 10.1.1.20
Filter: Link Down Alerts
Trap OID: 1.3.6.1.6.3.1.1.5.3
Action: <matched filter action>
Timestamp: Tue, Oct 14, 2025 11:45 AM

SNMP trap alert: Source IP: 10.1.1.20 - Filter: Link Down Alerts - Oid: 1.3.6.1.6.3.1.1.5.3

Trap Payload
{ ...full trap data as JSON... }

[Open SNMP Trap Logs]

Common Gotchas

Caution

• Power Platform DLP blocks the connector by default in most O365 tenants. The When a Teams webhook request is received connector must be explicitly allowed, or the workflow never fires even with a correctly configured webhook URL.
• This uses the newer workflow-based webhook, not the classic Incoming Webhook connector, which Microsoft has deprecated for Teams. Follow the linked Microsoft workflow guide, not older Incoming Webhook instructions.
• The webhook URL itself is the only credential. Anyone with it can post into the channel, treat it like a secret rather than a plain config value.
• The cache must be cleared after every .env change. Run php artisan rconfig:clear-all after adding or updating the Teams variables, or the old (or missing) values keep being used.
• A working test button does not mean events will post. Events only go out when their Teams switch is on in Settings → Notifications.

Troubleshooting

Test message not appearing in MS Teams

Check MS Teams app installation:

• Contact your MS Teams administrator to confirm the app is installed and configured correctly in the workspace.
• Follow the steps in this Microsoft documentation to verify DLP for incoming MS Teams webhooks: Admin data policy ‘Connectors’ restricts use of these apis: TeamsWebhookRequestReceived.

Hint: In our lab, we had to add the MS Teams, and MS Teams Webhook connectors to the allowed Business connectors list in the Power Platform DLP settings for the integration to work.

Verify rConfig configuration:

# Check if MS Teams is enabled
grep TEAMS_ENABLED /var/www/html/rconfig8/current/.env

# Verify webhook URL format
grep TEAMS_WEBHOOK_URL /var/www/html/rconfig8/current/.env

Check rConfig logs:

tail -50 /var/www/html/rconfig8/current/storage/logs/laravel-$(date +%F).log | grep -i teams

Test works but event notifications never arrive

• Confirm the event’s Teams switch is on in Settings → Notifications. When it’s off, the log shows Microsoft Teams disabled for <event> by admin
• For SNMP traps, confirm the trap matches a filter with a Send Alert action

Security Considerations

Protect the webhook URL: Anyone who has TEAMS_WEBHOOK_URL can post messages into the target channel. Never commit it to version control or share it publicly, store it only in the .env file.

Recreate the webhook if compromised: Unlike an OAuth token, a webhook URL has no separate secret to rotate, if it leaks, delete and recreate the workflow in Teams to get a new URL and update .env.

Restrict connector approval carefully: Only allow the When a Teams webhook request is received connector for the users or environments that actually need it in your Power Platform DLP policy.

Channel access control: Use private or restricted channels for sensitive notifications and carefully manage channel membership.

Best Practices

Pick the webhook’s channel deliberately: Since the webhook is bound to one Teams channel at creation and rConfig has no in-app channel routing, choose (or create) a channel appropriate for both configuration-change and SNMP-trap volume before generating the webhook.

Set notification schedules: Consider limiting non-critical notifications to business hours.

Test regularly: Periodically send test messages to ensure the integration remains functional.

Document the channel’s purpose: Tell team members which channel receives rConfig notifications and which event types are posted there.

Related Documentation

• Webhooks - The recommended way to post to Teams from V8.4.1
• Slack Notifications - Configure Slack alerts
• Scheduled Tasks - Configure automated operations