Skip to main content

Teams Emergency Call Notifications - System Architecture

Setup Information

For implementation details, see the Azure Integration Guide. This document explains how the system works technically.

What This System Does​

When someone makes an emergency call (like 911) through Microsoft Teams, this integration automatically captures that emergency notification and forwards it to Call Telemetry for immediate processing and alerting.

System Components​

The integration uses three main components:

  1. Azure App Registration - Provides secure authentication to Microsoft Graph API
  2. Microsoft Graph API Subscription - Monitors for emergency call notifications in Teams
  3. Azure Event Hub - Streams messages between Microsoft and Call Telemetry using Kafka protocol

How It Works​

The process:

  1. User dials 911 through Microsoft Teams
  2. Teams automatically creates a chat notification
  3. Microsoft Graph API subscription detects the notification
  4. Azure Event Hub forwards the event using Kafka protocol
  5. Call Telemetry receives and processes the emergency event
  6. Security teams get immediate notifications through configured channels

Authentication and transport boundaries​

The connector uses OAuth 2.0 Device Authorization Grant with delegated permissions for the dedicated Teams service user. Azure Event Hubs carries the Graph notifications to Call Telemetry over Kafka with TLS. The detailed permission list, authentication steps, Event Hub settings, and network requirements are maintained in the Azure Integration Guide, so the architecture reference and setup procedure do not drift apart.

Configuration reference​

Use the setup guide for the operational details that implement this architecture:

Data Privacy and Security​

Customer-Owned Infrastructure​

This Teams integration uses Azure resources in your organization's subscription and a Call Telemetry deployment that your organization operates or controls:

  • Azure Resources: Event Hub and App Registration are created in your Azure subscription
  • Microsoft Graph API: Uses delegated permissions scoped to your service user account only
  • Call Telemetry Instance: Runs on your infrastructure (on-premises or your cloud deployment)
  • Data Flow: Microsoft Graph and Azure Event Hubs handle notification delivery before events reach your Call Telemetry instance

Data Privacy Principles​

Managed-Service and Customer-Control Boundary:

  • Microsoft Graph and Azure Event Hubs are Microsoft-managed services involved in notification delivery
  • After delivery, your organization controls the Azure resources and can configure downstream access and retention for your deployment
  • Microsoft Graph API permissions are delegated to your service user account
  • Configure access, retention, and any vendor or data-processing controls according to your organization's policies

Data Handling and Sovereignty:

  • Emergency call notifications pass through Microsoft-managed services before reaching your customer-controlled Azure and Call Telemetry deployment
  • Call Telemetry processes data on the infrastructure selected for your deployment
  • You can configure data retention and access according to your organization's policies, subject to the capabilities and terms of the services you use
  • Configuration and credentials for customer-managed components are managed by your organization

Example References:

  • Any references to "Call Telemetry" in documentation are examples of your deployment
  • Screenshots and configuration examples represent your organizational setup
  • Confirm any third-party or vendor data-processing boundary against your deployment and organization's policies

Version Requirements​

  • Call Telemetry: 0.8.5 or later
  • License: Premium license required
  • Microsoft Graph API: Standard permissions (no admin consent required)
  • Azure Event Hub: Standard tier minimum
Last updated on by Jason Barbee