Microsoft Teams settings send Mini DBA alert notifications to Teams channels through webhook URLs.
Fields
- Major Alert Webhook URL: Teams webhook for major alerts.
- Minor Alert Webhook URL: Teams webhook for minor alerts.
Configure Teams Notifications
- Create Teams webhook endpoints for the target channels.
- Open Settings and select Teams.
- Paste the major alert webhook URL.
- Paste the minor alert webhook URL if minor alerts should route separately.
- Save.
- Trigger a controlled alert and confirm the Teams message is delivered.
Tips
Use separate channels or webhook URLs when major alerts need higher visibility than minor alerts. Keep Teams routing aligned with recipient groups and on-call processes.
Teams Alert Routing Guidance
Teams notifications work best when they are sent to channels that already match operational ownership. A DBA channel may need engine-level alerts, while an application support channel may need alerts for a specific server group or customer. Separating major and minor alerts helps prevent important notifications from being buried.
Treat Teams webhook URLs as secrets. Anyone with the URL may be able to post messages to the channel. Rotate a webhook if it is exposed, remove unused webhooks, and test delivery after changing channel ownership or tenant security settings.
If messages do not appear, check the webhook URL, channel permissions, web proxy settings, alert routing, and Service Log. A successful save does not always prove the external Teams endpoint accepted the message.
Microsoft Teams Settings FAQ
Should major and minor alerts go to different channels?
Often yes. Major alerts need higher visibility, while minor alerts may be better suited to a review or operations channel.
What if Teams notifications stop?
Check webhook validity, tenant settings, channel permissions, network/proxy access, and Mini DBA service logs.
Can Teams replace on-call paging?
Teams is useful for visibility, but urgent out-of-hours incidents usually need a paging tool such as PagerDuty.