The incident, as a card
An adaptive card carrying what fired, the service it belongs to and who is on call for it — enough for the channel to know the state without asking.
Microsoft
Microsoft Teams integration
Microsoft Teams is where the estate is discussed in most enterprises, and a card in a channel is read by whoever happens to be looking. ITOC360 posts the incident to the channel and pages the named on-call engineer in the same motion.
How ITOC360 connects to Microsoft Teams
Acknowledge from the card
Acknowledge, escalate or resolve without leaving Teams. The people who respond to an incident at 3 AM are the people already holding a phone.
Channels per service
Route by service or by escalation policy, so a platform channel and an application channel each see what belongs to them rather than everything.
Recorded, not just said
Every action taken from a card is written to the incident with actor and timestamp, which is what a postmortem needs and what a chat history is not.
Most enterprises run their day in Teams, which makes it the right place to say an incident is open and the wrong place to leave the question of who is handling it.
ITOC360 posts the incident as a card and pages the on-call engineer at the same time. The card carries the state and the actions; the escalation policy carries the responsibility. Anything done from the card is written to the incident's timeline rather than left in a channel history.
How it works
Monitoring sources
Alibaba CloudMonitor
Amazon CloudWatch
AppDynamics
Argo CD
AWS Budget
AWS GuardDuty
Azure Activity Logs
Azure Cost Budget
Azure DevOps
Azure Log Alerts
Azure Metric Alerts
Azure Service Health
Checkmk
Cortex
CrowdStrike
Datadog
Dynatrace
Elastic
GitHub
GitLab
Google Cloud Monitoring
Google Security Command Center
Grafana
Grafana Loki
Grafana Mimir
Graylog
InfluxDB
Instana
Jenkins
Jira
Kibana
Linear
ManageEngine OpManager
Microsoft Sentinel
Microsoft Teams
MongoDB Atlas
n8n
Netdata
New Relic
Pingdom
Postman
Prometheus
PRTG Network Monitor
Rollbar
Salesforce
Sentry
ServiceNow
SignalFx
SigNoz
Site24x7
Slack
SolarWinds Orion
StatusCake
Statuspage.io
Terraform Cloud
Twilio
VictoriaMetrics
Zabbix
Zapier
Growing integration library
ITOC360 core
Alert Ingestion & Deduplication
Noise Reduction / Grouping
Routing engine
On-call Schedule
Escalation Policy
Rotations
Notification layer
SMS
Voice Call
E-mail
Responder actions
Acknowledge
Assign
Resolve
Post-incident
Timeline Report
Common questions
How does ITOC360 connect to Teams?
Through an app your Microsoft 365 administrator installs, or an incoming webhook for a single channel. Credentials are stored encrypted and are never returned in plaintext.
Which channel does an incident go to?
Whichever you route it to, per service or per escalation policy. A channel can carry one team's services without carrying everybody else's.
Can we acknowledge from Teams?
Yes. The actions are on the card, and each one is recorded against the incident with who took it and when.
Does a card in a channel count as a page?
No. The card tells the channel; the escalation policy pages the person responsible through voice, SMS, push and email. Silence in the channel does not stop the escalation.
Does this work with Microsoft 365 single sign-on?
Yes. ITOC360 supports SAML 2.0 and OpenID Connect, so access follows your identity provider — removing somebody there removes them here.
Connect Microsoft Teams and stop missing alerts
Free to start, no card, and no agent to deploy on your monitoring host.