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

MS Teams Notifications enable rConfig V8.2 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 when you want configuration changes or SNMP traps posted directly to an MS Teams channel instead of relying on team members to check rConfig for them.

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	Notifications when SNMP traps are received	rConfig V8+

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 worflow 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

Configure Notification Preferences

Step 1: Access Notification Settings

Navigate to Settings > Integrations > MS Teams Notifications in the rConfig interface.

Step 2: Enable Notification Types

Select which events should trigger MS Teams notifications:

• ✓ Configuration changes detected
• ✓ SNMP traps received

Step 3: Configure Channel Routing (Optional)

Specify different channels for different notification types:

• Configuration changes → #network-changes
• SNMP traps → #snmp-alerts

Step 4: Test Notification

Click Send Test Message to verify the integration is working correctly.

Expected test message in MS Teams:

🔔 rConfig Test Notification
This is a test message from rConfig V8.
Integration is working correctly!

Notification Examples

Configuration Change Notification

📝 Configuration Change Detected

Device: core-router-01.example.com
Type: Cisco IOS
Changed: 2025-10-14 10:23:15 UTC
User: admin@example.com

View Details: https://rconfig.example.com/devices/123/configs/456

SNMP Trap Notification

🚨 SNMP Trap Received
Device: edge-switch-02.example.com
Type: Link Down
Received: 2025-10-14 11:45:30 UTC
View Details: https://rconfig.example.com/devices/456/snmp-traps/789

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.

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.log | grep -i teams

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

Organize channels: Create dedicated channels for different notification types (e.g., Network Changes, SNMP Alerts).

Use threading: Configure notifications to use threads for related events to reduce channel clutter.

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

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

Document channel purposes: Clearly communicate to team members which channels receive which notification types.

Related Documentation

• Slack Notifications - Configure Slack alerts
• Scheduled Tasks - Configure automated operations
• Compliance Overview - Understanding compliance notifications