NEW Free · Microsoft Teams Workflows · Unlimited domains
Microsoft Teams SSL Certificate Alerts
Send SSL certificate expiry reminders to any Microsoft Teams channel using a free Workflows incoming webhook. Five-minute setup, unlimited domains, configurable 30 / 7 / 1-day windows — no extra license, no per-seat fee.
Why route SSL expiry alerts into Microsoft Teams
If your SRE, platform, or web team already lives in Microsoft Teams, that is where outage-prevention signals belong. Email alerts get caught by spam filters and shared-inbox triage delay. A Teams card lands in the same channel as your deploy and on-call notifications, with @mentions, threaded follow-up, and mobile push out of the box.
Certimon delivers to Microsoft Teams through the official Workflows (Power Automate) incoming webhook — the supported replacement for the retired Office 365 Connectors. No tenant-wide app install, no admin approval per-channel: any user with permission to manage a channel can wire up the webhook in under five minutes.
Pair the Teams destination with Telegram delivery in the same alerting rule so the same expiry crossing reaches both the channel and the on-call engineer's phone — without configuring two separate monitors.
Setup: Microsoft Teams SSL alerts in five steps
All of the Teams-side work happens inside the official Workflows wizard. No legacy connectors, no admin consent dialog.
-
1
Open Workflows in the target Teams channel
In Microsoft Teams, navigate to the channel that should receive the SSL alerts (e.g.
#sre-alerts). Click the three-dot menu next to the channel name and choose Workflows.Search for the template “Post to a channel when a webhook request is received”. This is the supported replacement for the retired Office 365 Connector.
-
2
Configure and create the workflow
Sign in with your Microsoft 365 account when prompted. Give the workflow a recognisable name — for example Certimon SSL alerts — and confirm the Team and channel.
Click Add workflow. Teams creates the flow in Power Automate and returns a unique HTTPS webhook URL.
-
3
Copy the webhook URL (and treat it as a secret)
The wizard shows a long URL that starts like this:
https://prod-XX.logic.azure.com/.../invoke?sig=...Anyone with this URL can post messages to the channel, so store it like an API key. You can rotate it later from the Workflows editor.
-
4
Add the destination in Certimon
Open the Certimon dashboard at app.certimon.com and go to Alerting → Destinations → New destination.
Channel type: Microsoft Teams
Name: something searchable, e.g. #sre-alerts Teams channel
Webhook URL: paste the value from step 3
Save. Use the Send test message button to confirm the card appears in the channel.
-
5
Bind the destination to an alerting rule and attach domains
Create or edit an alerting rule under Alerting → Rules. Bind the Teams destination with one or more reminder windows — common choices are
30, 7, 1days. The same rule can also include a Telegram or PagerDuty destination.Attach the rule to the domains you want monitored from the Domains list. From that point, every threshold crossing posts a deduplicated card to Teams.
Best practices for Microsoft Teams SSL alerts
A few conventions that keep the channel useful instead of noisy.
Pick the right channel
Route alerts to a low-volume operational channel (e.g. #sre-alerts, #platform-oncall) — not a general team chat. Adaptive Cards in noisy channels get skimmed past.
Layer reminder windows, don't stack one big one
Use 30, 7, 1 day windows rather than a single 30-day reminder. A single card gets muted and forgotten; three escalating cards do not.
Use one destination per channel, not per domain
Create one Microsoft Teams destination per Workflows webhook (= per channel). Reuse it across rules — the per-destination dedup ledger guarantees one card per threshold crossing per channel.
Mirror critical alerts to a personal channel
Bind the same rule to a Telegram destination too. Production checkout endpoints want both a channel card and a push notification on the on-call phone.
Test before you trust it
Always use Send test message after creating the destination, and again after rotating the webhook URL. Microsoft Teams webhook errors are silent on the sender side until the next real alert fires.
Plan webhook rotation
If the channel owner leaves, the workflow they created keeps working until deleted. Document the destination's owner in the Certimon destination name and rotate the URL when ownership transfers.
Workflows webhook vs the retired Office 365 Connector
Microsoft is retiring the legacy Office 365 Connector (the “Incoming Webhook” app most older guides reference). New connectors can no longer be created, and existing ones will stop working. Certimon only supports the supported Workflows / Power Automate webhook path.
| Workflows webhook (used by Certimon) |
Office 365 Connector (retired) |
|
|---|---|---|
| Supported by Microsoft | ✅ Yes | ❌ Retiring 2025 |
| Can be created today | ✅ Yes | ❌ Creation disabled |
| Card format | Adaptive Cards 1.5 | MessageCard (legacy) |
| Setup location | Channel → Workflows | Channel → Connectors |
| Tenant admin approval | Not required for default templates | Not required (when enabled) |
FAQ — Microsoft Teams SSL alerts
How do I send SSL certificate expiry alerts to a Microsoft Teams channel?
Create a Workflows incoming webhook in the target Teams channel using the “Post to a channel when a webhook request is received” template, copy the generated webhook URL, then add it as a Microsoft Teams destination in the Certimon dashboard at app.certimon.com. Bind it to an alerting rule and attach the rule to the domains you want monitored.
Does Certimon use the legacy Office 365 Connector webhooks?
No. Microsoft is retiring Office 365 Connectors in 2025. Certimon uses the supported Microsoft Teams Workflows (Power Automate) incoming webhook, which is the official replacement.
Is sending SSL alerts to Microsoft Teams free?
Yes. Certimon is free with unlimited domains and unlimited reminder windows. Microsoft Teams Workflows webhooks are included in standard Microsoft 365 plans at no extra cost.
Can I route different domains to different Teams channels?
Yes. Create one Microsoft Teams destination per Workflows webhook (one per channel) and separate alerting rules per group of domains. The same rule can also fan out to Telegram or PagerDuty so the same expiry event reaches multiple teams.
What does a Certimon SSL alert look like in Microsoft Teams?
Certimon posts an Adaptive Card containing the domain, days until expiry, certificate issuer, the reminder window that triggered the alert, and a deep link to the Certimon dashboard for that domain. Alerts are deduplicated per destination so the channel only sees one card per crossing of each threshold.
How do I rotate or revoke the Microsoft Teams webhook URL?
Open Workflows in Microsoft Teams (or Power Automate directly), edit the workflow, and use Update trigger to generate a new URL. Paste the new URL into the matching destination in the Certimon dashboard. To revoke entirely, delete the workflow — Certimon will mark the destination as failing on the next send.
Do I need to be a Microsoft 365 admin to set this up?
In most tenants, no. Any user with rights to add a workflow to the channel can create the webhook from the channel's Workflows menu. If your tenant has restricted Workflows/Power Automate, a Teams admin needs to allow the “Post to a channel when a webhook request is received” template.
Related guides
Telegram SSL certificate alerts
The original Certimon delivery channel — bind it alongside Teams for on-call phone push.
Free SSL certificate monitoring
Unlimited domains, free forever — the full pricing & limits overview.
SSL monitoring for small teams
Pairing channel alerts (Teams) with personal alerts (Telegram) for the whole on-call rotation.
Datadog SSL monitoring alternative
When a focused, free SSL-expiry-to-Teams alert is enough — and when it isn't.
Get SSL alerts into your Teams channel in ten minutes
Create the Workflows webhook, paste it into Certimon, attach it to your domains — and stop chasing expiry emails through shared inboxes.
Open the Certimon dashboard