ServiceNow + Microsoft Teams
Connect ServiceNow and Microsoft Teams to Speed Up IT Service Delivery
Get incident alerts, ticket updates, and approval workflows into the place where your teams actually spend their day.
Why integrate ServiceNow and Microsoft Teams?
ServiceNow is where your IT service management lives. Microsoft Teams is where your people work. When those two run separately, critical incident notifications get missed, approval cycles stall, and IT teams burn time jumping between systems just to check ticket status. Connect them, and the right people get notified at the right time, directly in the channels they're already watching.
Automate & integrate ServiceNow & Microsoft Teams
Use case
Real-Time Incident Notifications to Teams Channels
When a Priority 1 or Priority 2 incident is created or escalated in ServiceNow, tray.ai posts a structured alert card to the right Microsoft Teams channel, with incident number, description, affected service, and assigned group. On-call engineers and stakeholders are in the loop instantly — no manual status emails, no bridge call scramble.
Use case
Two-Way Ticket Updates Between ServiceNow and Teams
ServiceNow ticket changes — assignment, status, resolution — show up as threaded replies in the original Teams message. Technicians can also post work notes from a Teams bot that writes directly back into the ServiceNow incident record. Both sides stay current.
Use case
Change Request Approvals via Teams Adaptive Cards
ServiceNow change requests go to the right approvers as interactive Adaptive Cards in Microsoft Teams. They can approve, reject, or ask for more information without opening ServiceNow. Their responses write back to the ServiceNow change record automatically, keeping the audit trail clean and the approval moving.
Use case
Automated Major Incident War Room Creation
When a ServiceNow incident is classified as a Major Incident, tray.ai creates a dedicated Microsoft Teams channel or meeting, invites the relevant resolver groups and stakeholders, pins the incident details card, and posts the initial timeline entry. No more chaotic scrambles to pull the right people together mid-outage.
Use case
Service Request Fulfillment Status Notifications
End users get Teams messages at key fulfillment milestones — request approval, work in progress, pending their input, completion. They get updates in the chat interface they use daily instead of having to check the service portal.
Use case
Scheduled ServiceNow Report Digests in Teams
Daily or weekly ServiceNow operational reports — open incident counts by priority, SLA breach risk, backlog aging — post automatically as formatted Teams messages in leadership or team channels. Service desk managers get the visibility they need without running reports manually each morning.
Use case
On-Call Escalation and Acknowledgment Workflows
When a ServiceNow incident breaches its initial response SLA, tray.ai pings the on-call engineer directly in Microsoft Teams with a contextual alert card. Engineers can acknowledge or escalate further using Teams action buttons, and every response writes back to the ServiceNow ticket timeline.
Get started with ServiceNow & Microsoft Teams integration today
ServiceNow & Microsoft Teams Challenges
What challenges are there when working with ServiceNow & Microsoft Teams and how will using Tray.ai help?
Challenge
Handling ServiceNow's Complex Data Model in Real Time
ServiceNow records have deeply nested relationships — configuration items, assignment groups, SLA records, related tasks — that need to be resolved and presented clearly inside a Teams message. Raw webhook payloads often return reference fields as sys_ids instead of human-readable values.
How Tray.ai Can Help:
tray.ai's ServiceNow connector has built-in operations to resolve reference fields and look up related records, so you can enrich incident or change data before composing a Teams message. The visual workflow builder lets you map sys_ids to display names, pull in CI details, and format multi-field payloads into clean Adaptive Card structures without writing custom middleware.
Challenge
Building Interactive Two-Way Workflows Without Custom Bots
Creating a Teams bot that sends interactive Adaptive Cards and handles button responses normally means Azure Bot Framework registration, custom web hosting, and real development work. For IT and operations teams who need approval and acknowledgment workflows now, that's a six-week detour they can't afford.
How Tray.ai Can Help:
tray.ai handles the Teams bot and webhook infrastructure for you. Send Adaptive Cards with action buttons and capture user responses through a managed webhook endpoint. Teams interactions become structured data that tray.ai workflows act on immediately, writing results back to ServiceNow without custom bot development or Azure infrastructure to manage.
Challenge
Routing Notifications to the Right Teams Channel or Person
Large organizations have dozens or hundreds of Teams channels and thousands of users. Getting a ServiceNow incident notification to the correct channel based on assignment group, service classification, or affected business unit requires dynamic logic that a static webhook configuration just can't handle.
How Tray.ai Can Help:
tray.ai workflows support conditional branching and data lookups, so you can build routing logic that maps ServiceNow assignment groups or service classifications to specific Teams channel IDs or individual user email addresses. Store the mapping in a tray.ai data store or an external reference table and update it without touching the workflow.
Challenge
Maintaining a Clean ServiceNow Audit Trail from Teams Actions
When approvals, acknowledgments, or comments come from Microsoft Teams, those actions need to land accurately in ServiceNow — who did it, when, and what they said — to hold up for compliance, audit, and reporting.
How Tray.ai Can Help:
tray.ai captures the Teams user identity and timestamp from every interactive card response and maps them back to the corresponding ServiceNow record. Work notes include the originating Teams user's name and exact response content, so the ServiceNow audit log stays complete and accurate regardless of where the action happened.
Challenge
Managing Notification Fatigue from High-Volume ServiceNow Events
Active ITSM environments can generate hundreds of ticket updates a day. Push all of them into Microsoft Teams channels without filtering and you'll end up with noise, ignored alerts, and channels nobody reads anymore.
How Tray.ai Can Help:
tray.ai workflows support granular filtering, conditional logic, and deduplication so only meaningful events trigger Teams notifications. Set rules to post only on priority thresholds, specific state transitions, SLA risk conditions, or assignment changes — and use tray.ai's data store to suppress repeat notifications for the same incident within a defined time window.
Start using our pre-built ServiceNow & Microsoft Teams templates today
Start from scratch or use one of our pre-built ServiceNow & Microsoft Teams templates to quickly solve your most common use cases.
ServiceNow & Microsoft Teams Templates
Find pre-built ServiceNow & Microsoft Teams solutions for common use cases
Template
ServiceNow P1/P2 Incident Alert to Microsoft Teams Channel
Watches ServiceNow for new or escalated high-priority incidents and posts a formatted Adaptive Card to a designated Teams incident channel, with all key incident fields and a direct link to the record.
Steps:
- Trigger on new or updated ServiceNow incident where Priority equals 1 or 2
- Enrich the record by fetching assignment group and affected configuration item details from ServiceNow
- Post a formatted Adaptive Card to the designated Microsoft Teams incident channel with incident number, description, priority, and assignee
Connectors Used: ServiceNow, Microsoft Teams
Template
ServiceNow Change Request Approval via Teams Adaptive Card
When a change request enters the Awaiting Approval state in ServiceNow, this template sends an interactive Adaptive Card to the approver in Teams. Their approval or rejection writes back to the ServiceNow change record automatically.
Steps:
- Trigger when a ServiceNow change request state transitions to Awaiting Approval
- Send an Adaptive Card to the designated approver in Microsoft Teams with change details, risk level, implementation window, and Approve/Reject buttons
- Capture the approver's response and update the ServiceNow change record state, adding a work note with the decision and timestamp
Connectors Used: ServiceNow, Microsoft Teams
Template
Major Incident Auto War Room in Microsoft Teams
Provisions a dedicated Microsoft Teams channel, invites resolver groups, and posts a pinned incident summary card whenever a ServiceNow incident is promoted to Major Incident status.
Steps:
- Trigger on ServiceNow incident update where Major Incident field is set to true
- Create a new Microsoft Teams channel named with the incident number and short description, then invite members of the assigned and watch list groups
- Post and pin an Adaptive Card summarizing the incident details, and add a work note to the ServiceNow record with the Teams channel link
Connectors Used: ServiceNow, Microsoft Teams
Template
Two-Way ServiceNow Incident and Teams Thread Sync
Keeps ServiceNow incident records and their corresponding Microsoft Teams thread messages in sync — posting ServiceNow updates as threaded replies and writing Teams comments back as ServiceNow work notes.
Steps:
- Trigger on ServiceNow incident state change or new work note added to the record
- Post a threaded reply to the original Teams incident message with the updated status or work note content
- Separately, listen for replies to the Teams incident thread and write them back to the corresponding ServiceNow incident as work notes
Connectors Used: ServiceNow, Microsoft Teams
Template
ServiceNow SLA Breach Escalation to Teams On-Call Engineer
Detects when a ServiceNow incident is approaching or has breached its response SLA and sends a direct Teams message to the on-call engineer with acknowledgment action buttons that update the ServiceNow record.
Steps:
- Poll ServiceNow on a scheduled interval for incidents where SLA percentage elapsed exceeds the configured threshold and the incident is not yet acknowledged
- Send a direct Microsoft Teams message to the on-call engineer with an Adaptive Card containing incident details and an Acknowledge button
- On button press, update the ServiceNow incident with an acknowledgment work note and adjust the assignment if the engineer escalates to another team
Connectors Used: ServiceNow, Microsoft Teams
Template
Daily ServiceNow Incident Summary Digest to Teams
Compiles and posts a daily operational digest of open ServiceNow incidents, segmented by priority and assignment group, into a configured Microsoft Teams management channel.
Steps:
- Trigger on a daily schedule at a configured time each morning
- Query ServiceNow for all open incidents, group results by priority and assignment group, and calculate SLA breach risk counts
- Format the results into a structured Teams message card and post to the designated management or service desk channel
Connectors Used: ServiceNow, Microsoft Teams