Configure email and Microsoft Teams notifications

Notifications in NetLock RMM fan out from a single page — Settings → Notifications — to multiple channels. This guide walks through the two most common: email via SMTP and Microsoft Teams via a webhook created in the Workflows app. You will configure the global SMTP server, add one email recipient, create the Teams webhook and add it as a connector, and run the built-in test for each.

Before you start

• You have SMTP server credentials for your environment, and you can receive mail at a test address.
• For Teams, you are allowed to add a workflow to the target channel — that is where the webhook URL comes from since Microsoft retired the classic connectors. The first Teams step below creates it.
• Required permissions: settings_enabled, settings_notifications_enabled.

Email — Steps

1. Configure the global SMTP server

1. Open Settings → Notifications (route /manage_notifications).
2. On the tab labelled E mail, click SMTP settings to open the SMTP settings dialog.
3. Fill in:
   • Server — SMTP hostname.
   • Port — SMTP port.
   • SSL/TLS — tick if the server requires TLS.
   • Username — SMTP authentication username. If this is not a valid email address, the dialog reveals extra fields.
   • Password — SMTP password.
   • From address — if shown, the sender address the server will accept.
   • To address — if shown, a test-recipient address.
4. Click Test. The Console sends a message with subject NetLock - Test Alert and body Test successful.. A snackbar reports Test successful. on pass or Test failed: <error> on failure.
5. Save. The dialog's save action is gated behind a successful test — you cannot persist a configuration that has not been tested.

Note: Only one SMTP configuration exists per deployment. Editing it replaces the previous configuration for every email recipient.

2. Add an email recipient

1. Back on the E mail tab, click Add to open the Add Mail Notification dialog.
2. Fill in:
   • E mail — the recipient address.
   • Description — optional free text.
   • Severity — Any, Critical, High, Moderate, or Low. Events not matching the chosen severity are filtered out for this recipient.
   • Uptime Monitoring — on if this recipient should also receive disconnection alerts when uptime monitoring is enabled on a device.
   • Tenant scope — drag the tenants this recipient should receive events from out of the Tenants list and into Selected tenants.
3. Save. The row appears in the recipients table.

Microsoft Teams — Steps

1. Create the webhook in Teams

Microsoft retired the classic Office 365 connectors in May 2026. A channel's webhook URL comes from a Power Automate flow now, and the Workflows app inside Teams creates that flow for you.

1. In Teams, open the channel that should receive the alerts.
2. Open the channel's … menu and choose Workflows.
3. Pick the template built on the When a Teams webhook request is received trigger — Teams lists it as Post to a channel when a webhook request is received.
4. Confirm the connection Teams offers, click Next, check that the team and the channel are the ones you want, and add the workflow.
5. Copy the URL the dialog shows. That URL is what NetLock RMM needs; you can read it again later by opening the workflow and expanding its trigger.

2. Add a Teams connector

1. Back in the Console on the Notifications page, switch to the Microsoft Teams tab.
2. Click Add to open the Add Microsoft Teams Notification dialog.
3. Fill in:
   • Connector Name — a recognisable name for this channel.
   • Connector-Webhook-URL — the URL you copied in step 1. The value is masked once saved.
   • Payload format — Adaptive Card (Workflows webhook) for a workflow created as above. Pick Adaptive Card without envelope if you edited the flow so that it passes the request body straight into its Post card in a chat or channel action, and Plain text (legacy connector) only when the URL points at something other than Teams. See A.8.3.
   • Description — optional free text.
   • Severity — same five options as email.
   • Uptime Monitoring — same behaviour as email.
   • Tenant scope — drag tenants into Selected tenants.
4. Save.

3. Test the connector

1. On the new row in the Microsoft Teams table, click the row's Test action.
2. The Console POSTs a test message in the connector's payload format. A snackbar reports Successfully sent on pass or Failed sending: <error> on failure.
3. Open the Teams channel the workflow posts into and confirm the test message arrived. The webhook answers before the flow runs, so a successful send is not on its own proof that the message was posted.

Verify it worked

• An email arrived at your test address with the subject NetLock - Test Alert.
• The Teams channel shows a test message from Flow bot that names the connector you added.
• The recipient rows on both tabs show the severity, tenant scope, and uptime-monitoring values you set.

Troubleshooting

• SMTP test fails with authentication errors. Re-check username, password, and whether your SMTP provider requires an app password or OAuth. For providers that allow only specific sender addresses, fill in From address to match.
• Teams test succeeds but no message arrives. The webhook took the call and the flow failed afterwards. Open the workflow in Teams and read its run history: a failing Post card in a chat or channel step usually means Payload format does not match how the flow is built — switch between the two Adaptive Card options. A workflow that is turned off, or an archived channel, is quiet in the same way.
• Teams test fails outright. The URL is wrong, or the workflow behind it was deleted. Create it again as in step 1 and paste the new URL over Connector-Webhook-URL. A URL on webhook.office.com belongs to a classic connector and no longer works at all.
• Events do not trigger emails after setup. Severity filtering is on the recipient record. An event below the recipient's severity threshold is silently filtered; lower the threshold temporarily to verify.
• No messages for a specific tenant. Tenant scope on the recipient record acts as a filter. Add the missing tenant to Selected tenants or leave the scope empty to receive events from all tenants.

Related

• Appendix A.8 — Notifications deep dive — the other channels (Telegram, ntfy.sh, Webhook) and per-channel configuration details.
• Chapter 6.6.2 — Antivirus notifications sub-tab — per-policy event selection that feeds these channels.