Microsoft Teams Alerts for Your Cron Jobs
Get instant Microsoft Teams notifications when a scheduled job fails, recovers, or is disabled by the circuit breaker. Connect CronJobPro to any Teams channel in minutes using an Incoming Webhook URL.
Start freeHow Microsoft Teams alerts work
When a job fails (non-2xx response, timeout, or connection/DNS error after your configured retries), recovers, or is auto-disabled after repeated failures, CronJobPro posts an alert to every notification channel attached to that job. You can set an alert threshold so notifications are suppressed until N consecutive failures occur, reducing noise from transient errors. Heartbeat and dead-man's-switch monitors follow the same alerting path, notifying your Teams channel when a ping is missed.
Set up Microsoft Teams notifications
You'll need your Incoming Webhook URL.
- 1
Create an Incoming Webhook in Teams
Open the Teams channel you want to receive alerts in. Go to Manage channel → Connectors (classic) or use the Workflows app to add an Incoming Webhook flow. Copy the webhook URL that Teams provides. Note: Microsoft is migrating classic connectors to Power Automate Workflows — either path produces a webhook URL that works the same way.
- 2
Add a Teams channel in CronJobPro
In CronJobPro, navigate to Settings → Notifications and click Add channel. Select Microsoft Teams as the channel type, give it a recognizable name (for example, "Ops alerts"), and paste the Incoming Webhook URL.
- 3
Send a test message
Click the Test button next to the newly saved channel. A test message will be posted to your Teams channel immediately so you can confirm the webhook URL is correct and delivery is working before attaching it to any jobs.
- 4
Attach the channel to your jobs
Open any scheduled job or monitor and select the Teams channel under its Notifications setting. You can attach the same channel to multiple jobs, or create separate channels per team or environment.
- 5
Set an alert threshold (optional)
On each job you can configure an alert threshold — for example, "notify after 2 consecutive failures" — to avoid being paged on a single transient error. CronJobPro will still record every failure; the threshold only controls when the Teams message is sent.
Frequently asked questions
Which events trigger a Teams notification?
CronJobPro sends a Teams alert when a job fails (non-2xx HTTP response, timeout, or connection/DNS error after retries), when a failed job recovers on a subsequent run, and when a job is auto-disabled by the circuit breaker after repeated failures. Heartbeat monitors alert when an expected ping is missed.
Microsoft is deprecating classic Teams connectors — will my webhook stop working?
Microsoft is moving Teams Incoming Webhooks from the classic Connectors experience to Power Automate Workflows. Both approaches produce a webhook URL that CronJobPro posts to in exactly the same way. If you set up your webhook via Workflows, it will continue working after the classic connectors are retired. We recommend using the Workflows path for new setups.
Can I send alerts from different jobs to different Teams channels?
Yes. You can create as many Teams channels in Settings → Notifications as you need — one per project, environment, or on-call team — and attach each job to whichever channel is appropriate.
Does CronJobPro support heartbeat / dead-man's-switch monitoring with Teams alerts?
Yes. Heartbeat monitors in CronJobPro watch for an expected ping from your job or script. If the ping does not arrive within the configured window, CronJobPro fires an alert to all notification channels attached to that monitor, including Teams.
Other integrations
Monitor your cron jobs in Microsoft Teams
Schedule HTTP jobs and heartbeat monitors, then get failure and recovery alerts where your team already works.