Call Telemetry for Cisco

Appearance

Microsoft Teams Emergency Notifications - Quick Start Guide ​

Feature Overview ​

This quick start guide will get your Microsoft Teams emergency notification monitoring up and running in 30-45 minutes. It covers the essential steps for Azure setup, Call Telemetry configuration, and user authentication.

What You'll Achieve:

  • Real-time monitoring of Microsoft Teams emergency call notifications
  • Automatic detection and processing of emergency notifications
  • Complete audit trail of emergency communication events
  • Integration with Call Telemetry's emergency response workflows

Prerequisites Checklist ​

Before starting, ensure you have:

  • [ ] Azure Subscription with Event Hub creation permissions
  • [ ] Global Admin Access to create App Registrations
  • [ ] Dedicated Service User with Microsoft Teams license
  • [ ] Teams Emergency Policies Configured (emergency call notifications enabled)
  • [ ] Network Access (outbound HTTPS to Microsoft services)
  • [ ] Call Telemetry Access with Teams integration permissions

Step 1: Azure Setup (15 minutes) ​

Create App Registration ​

  1. Sign in to Azure Portal → Azure Active Directory → App registrations

  2. Click "+ New registration"

  3. Configure Registration:

    • Name: Call Telemetry Teams Integration
    • Account types: Single tenant
    • Redirect URI: Leave blank
    • Click "Register"

  4. Copy Key Information:

    • Application (client) ID: ________________
    • Directory (tenant) ID: ________________

  5. Create Client Secret:

    • Go to Certificates & secrets → + New client secret
    • Description: Call Telemetry Secret
    • Expires: 24 months
    • Copy secret value: ________________

  6. Enable Device Flow:

    • Go to Authentication → Advanced settings
    • Enable mobile and desktop flows: Yes
    • Click "Save"

Configure API Permissions ​

  1. Add Graph Permissions: Go to API permissions → + Add permission → Microsoft Graph → Delegated
  2. Add These Permissions:
    • [ ] User.Read
    • [ ] Chat.Read
    • [ ] Chat.ReadBasic
    • [ ] ChatMessage.Read
    • [ ] openid
    • [ ] offline_access
    • [ ] profile

Create Event Hub (10 minutes) ​

  1. Create Resource Group:

    • Resource groups → + Create
    • Name: RG-Call-Telemetry-Teams
    • Region: Choose closest to your location

  2. Create Event Hub Namespace:

    • Event Hubs → + Create
    • Namespace name: calltelemetry-teams-[random] (must be unique)
    • Resource group: Select created group
    • Pricing tier: Basic

  3. Create Event Hub:

    • Navigate to namespace → + Event Hub
    • Name: teams-events
    • Partition count: 2
    • Message retention: 1 day

Configure Event Hub Permissions ​

  1. Grant Microsoft Graph Permissions:

    bash
    # Replace with your values
SUBSCRIPTION_ID="your-subscription-id"
RESOURCE_GROUP="RG-Call-Telemetry-Teams"
NAMESPACE_NAME="calltelemetry-teams-[your-suffix]"

# Run this command
az role assignment create \
  --assignee $(az ad sp list --display-name "Microsoft Graph Change Tracking" --query "[0].id" -o tsv) \
  --role "Azure Event Hubs Data Sender" \
  --scope "/subscriptions/$SUBSCRIPTION_ID/resourceGroups/$RESOURCE_GROUP/providers/Microsoft.EventHub/namespaces/$NAMESPACE_NAME"

  2. Create Access Policy:

    • Event Hub → teams-events → Shared access policies → + Add
    • Name: CallTelemetry-ReadWrite
    • Permissions: Check Listen and Send
    • Copy Connection String: ________________

Step 2: Call Telemetry Configuration (10 minutes) ​

Configure Teams Integration ​

  1. Navigate to MS Teams:

    • Log in to Call Telemetry
    • Go to MS Teams (sidebar)

  2. OAuth Settings Tab:

    Client ID:                    [App Registration ID]
Client Secret:               [Secret Value]
Tenant ID:                   [Directory Tenant ID]
Refresh Token Expiration:    2196 (leave default)

  3. Subscription Settings Tab:

    Delivery Mode:               Event Hub
Subscription Timeout:        4320 minutes

  4. Event Hub Tab:

    Enable Event Hub:            ✅ True
Event Hub Name:              teams-events
Consumer Group:              $Default
Connection String:           [Your connection string]
Partition Count:             2

  5. Permissions Tab:

    • Verify all permissions are checked ✅
    • Click Save to apply configuration

Step 3: User Authentication (10 minutes) ​

Add Monitoring User ​

  1. Start Authentication:

    • Click Add Monitoring User → Start Authentication
    • Note the User Code (e.g., BFCC-GQVT)
    • Note the Verification URL

  2. Complete Authentication (on separate device):

    • Open browser on phone/tablet/computer
    • Go to https://microsoft.com/devicelogin
    • Enter the User Code
    • Sign in with service integration user
    • Grant consent to all requested permissions

  3. Verify Success:

    • Return to Call Telemetry
    • Status should show ✅ Success
    • User profile populated with service user details

Create Chat Subscription ​

  1. Setup Monitoring:

    • Click Setup Chat Monitoring
    • Select Event Hub delivery
    • Click Continue

  2. Review and Save:

    • Review OAuth settings → Save and Continue
    • Review Event Hub settings → Save and Continue

  3. Create Subscription:

    • Click Create Subscription
    • Wait for subscription creation (30-60 seconds)
    • Verify subscription shows Active status

Step 4: Verification and Testing (5 minutes) ​

Verify Integration Health ​

  1. Check Teams Integration Dashboard:

    • Navigate to MS Teams → Dashboard
    • Verify connection status shows Healthy
    • Confirm subscription is Active and Tokens are Valid

  2. Test Event Processing:

    • Send a test chat message by dialing 933 (test emergency number)
    • Check Event Hub metrics in Azure Portal
    • Monitor Call Telemetry logs for message processing

Troubleshooting Quick Fixes ​

Authentication Issues ​

Problem: "Device code expired"
Solution: Restart authentication process, complete within 15 minutes

Problem: "Permission denied"
Solution: Verify service user has Teams license and proper permissions

Problem: "Invalid tenant"
Solution: Confirm tenant ID matches Azure AD tenant

Subscription Issues ​

Problem: "Send claim required"
Solution: Run the Microsoft Graph permissions command from Step 1

Problem: "Subscription creation failed"
Solution: Verify Event Hub connection string and permissions

Problem: "No events received"
Solution: Check Teams emergency policies and notification settings

Network Issues ​

Problem: "Connection timeout"
Solution: Verify firewall allows outbound HTTPS to Microsoft services

Problem: "DNS resolution failed"
Solution: Ensure DNS can resolve *.microsoft.com and *.servicebus.windows.net

Success Criteria ​

Your integration is successfully configured when:

  • [ ] Authentication Status: ✅ User authenticated with valid tokens
  • [ ] Subscription Status: ✅ Active subscription with future expiration
  • [ ] Connection Health: ✅ Excellent or Good connection to Event Hub
  • [ ] Event Processing: ✅ Messages flowing from Teams → Event Hub → Call Telemetry
  • [ ] Dashboard Active: ✅ Real-time metrics and monitoring available

Next Steps ​

After successful quick start:

  1. Configure Monitoring: Set up alerts for authentication and processing failures
  2. Test Emergency Scenarios: Validate end-to-end emergency notification flow
  3. Review Documentation: Read full installation and operations guides
  4. Plan Maintenance: Schedule regular token and subscription monitoring
  5. Scale Considerations: Plan for additional integration users if needed

Estimated Time

Estimated Total Time: 30-45 minutes for basic setup Production Ready: Add monitoring, alerting, and operational procedures

Your Microsoft Teams emergency notification monitoring is now active and ready to detect emergency call notifications in real-time!