ServiceNow Microsoft Teams Integration Guide

Architecture Overview

Implementation Steps

// Flow Designer condition script for filtering high priority incidents
(function execute(inputs, outputs) {
    var incident = new GlideRecord('incident');
    if (incident.get(inputs.sys_id)) {
        var currentPriority = incident.getValue('priority');
        var previousPriority = incident.getValue('priority').previous();
        // Send notification if priority changed to 1 (Critical) or 2 (High)
        outputs.sendNotification = (currentPriority == '1' || currentPriority == '2') && currentPriority != previousPriority;
    }
})(inputs, outputs);

// Scripted REST API to handle adaptive card responses
(function process(request, response) {
    var requestBody = JSON.parse(request.body.dataString);
    var changeId = requestBody.changeId;
    var action = requestBody.action;
    var approver = requestBody.approver;
    
    var change = new GlideRecord('change_request');
    if (change.get(changeId)) {
        if (action === 'approve') {
            change.setValue('approval', 'approved');
            change.setValue('approved_by', approver);
        } else {
            change.setValue('approval', 'rejected');
            change.setValue('rejected_by', approver);
        }
        change.update();
        response.setStatus(200);
        response.getStreamWriter().writeString(JSON.stringify({status: 'success', message: 'Change request updated'}));
    }
})(request, response);

// Script to resolve ServiceNow users to Teams mentions
(function execute(inputs, outputs) {
    var assignedTo = inputs.assigned_to;
    var user = new GlideRecord('sys_user');
    if (user.get(assignedTo)) {
        var userEmail = user.getValue('email');
        // Call Microsoft Graph API to get Teams user ID
        var rm = new sn_ws.RESTMessageV2('Microsoft Graph Get User', 'GET');
        rm.getEndpoint().setConnectionAndCredentialAlias('Microsoft Teams Production');
        rm.setStringParameterNoEscape('user_email', userEmail);
        var response = rm.execute();
        if (response.getStatusCode() == 200) {
            var userInfo = JSON.parse(response.getBody());
            outputs.teams_mention = '<at id="' + userInfo.id + '">' + userInfo.displayName + '</at>';
        }
    }
})(inputs, outputs);

// Test script to validate Teams integration
(function testTeamsIntegration() {
    // Create test incident
    var incident = new GlideRecord('incident');
    incident.initialize();
    incident.setValue('short_description', 'Teams Integration Test Incident');
    incident.setValue('priority', '1');
    incident.setValue('state', '1');
    incident.setValue('assignment_group', 'service_desk');
    var incidentId = incident.insert();
    
    gs.info('Created test incident: ' + incidentId);
    
    // Trigger the flow by updating priority
    incident.setValue('priority', '1');
    incident.update();
    
    return 'Test incident created and updated to trigger Teams notification';
})();

Common Use Cases

Troubleshooting

Pro Tips

• →Implement message throttling in your Flow Designer workflows using custom script steps that track message frequency per channel and introduce delays during high-volume periods. This prevents overwhelming Teams channels during major incidents and helps you stay within Microsoft Graph API rate limits while maintaining user experience. Consider using ServiceNow's sys_trigger table to queue and batch notifications during peak periods.
• →Create reusable subflows in Flow Designer for common Teams operations like user resolution, message formatting, and error handling to maintain consistency across all your Teams integrations. These subflows can include advanced features like message templating, conditional @mentions based on time of day, and automatic fallback to email notifications when Teams delivery fails. This modular approach significantly reduces development time for new use cases.
• →Leverage Teams' threaded conversation features by storing conversation IDs in ServiceNow records, enabling follow-up messages to appear as replies rather than separate notifications. This creates a more organized communication flow and helps users track related updates without channel flooding. Implement this by adding custom fields to your ServiceNow tables to store Teams message and conversation metadata.
• →Configure monitoring dashboards using ServiceNow Performance Analytics to track Teams integration health, including message delivery rates, API response times, and user engagement metrics with adaptive cards. Set up automated alerts when integration performance degrades or when approval response rates drop below acceptable thresholds. This proactive monitoring approach helps identify issues before they impact business operations.
• →Design your adaptive cards with progressive disclosure principles, showing essential information immediately while providing expansion options for detailed data that might overwhelm the initial view. Use Teams' card refresh capabilities to update approval cards with current information when the underlying ServiceNow records change, ensuring decision-makers always have the latest data. Include card versioning to handle scenarios where multiple approvers might see different card states.
• →Implement intelligent message routing based on ServiceNow data relationships, automatically determining the most appropriate Teams channel or user based on configuration item relationships, assignment group hierarchies, and business service mappings. This dynamic routing ensures notifications reach the right people without manual configuration, reducing maintenance overhead as your organization structure evolves.

Known Limitations

• —Microsoft Graph API enforces strict rate limiting with a baseline of 10,000 requests per 10 minutes per application, which can be restrictive for large ServiceNow instances with high incident volumes or frequent status updates. Organizations may need to implement message batching, caching strategies, or request queuing mechanisms to avoid hitting rate limits during peak usage periods. The actual rate limits can vary based on Microsoft 365 license types and tenant-specific throttling policies.
• —Adaptive cards in Teams have formatting and interactivity limitations compared to full web interfaces, restricting complex approval workflows or detailed data visualization within the Teams environment. Cards cannot embed rich media, support complex input validation, or maintain persistent state across interactions, requiring users to navigate to ServiceNow for advanced operations. Additionally, adaptive card schema updates may require redeployment of Integration Hub flows to maintain compatibility.
• —The integration requires users to maintain active sessions in both ServiceNow and Microsoft Teams for optimal functionality, and authentication tokens can expire unpredictably based on organizational security policies. Guest users and external collaborators may have limited access to ServiceNow-originated content in Teams, potentially excluding important stakeholders from critical communications. Cross-tenant scenarios in large organizations can introduce additional authentication complexity and feature limitations.

Frequently Asked Questions