Tenant Health
Live + last 7 days vs trailing 30-day baseline · updated 12 min ago
📞 Calling
Healthy
0
📹 Camera video
Healthy
0
📅 Meetings
Degraded
0
🖥️ Screen share (VBSS)
Degraded
0
🗂️ App sharing
Healthy
0
🏢 Rooms
Healthy
0
Overall quality score
0/100
Awaiting Teams call data
Users monitored (7d)
0
Rooms monitored (7d)
0
Shared devices monitored (7d)
0
Rate-my-call
4.2★
▼ 0.3 · top token “Echo” ×41
Call quality distribution
Teams call quality streams · awaiting data
- ✅ Good0.0% · 0
- ❌ Poor0.0% · 0
- ❓ Unclassified0.0% · 0
Where is the problem?
Poor streams by attributed cause · 7 days
Awaiting data0
Top affected entities
Worst poor-rate first
| Entity | Type | Poor rate | Status | Top cause |
|---|---|---|---|---|
| Awaiting data | Tenant | 0% | Healthy | None |
Status thresholds: Critical ≥20% poor rate · Degraded 5-19% · Healthy <5%
Scoped monitoring diagnostics will appear here.
Recent quality events
Last 5 calls with issues · Most recent first
Awaiting data
Recent events show poor-quality streams from your Teams call data.
28-day quality heatmap
Quality rate by day
Network and Sites
Your Teams call data grouped by location and network, over the selected range. Network and site attributable poor streams only, using the published CQD thresholds; device issues are on the Dashboard.
Sites
Subnets
Wi-Fi access points
Connection type
Sites
Worst poor-rate first. Click a row to investigate and start resolution.
Loading…
Loading…
Users
People with Teams call activity, worst experience first. Not live; reflects the selected range. Quality is measured over classified streams using the published CQD thresholds.
What is driving poor user experience
Top cause across users with poor calls. Click a cause to filter the list.
Loading…
Users
Worst poor-rate first. Click a row to diagnose and resolve.
| User | Calls | Poor rate | Trend (14d) | Top cause | Persistence | Issues |
|---|
Users / User
ℹ️ Post-call diagnostics from Teams CallRecords, typically available 30 to 60 minutes after a call ends. Device firmware, USB-vs-Bluetooth and model are inferred from device names (not in CallRecords), so confirm in your device inventory. For federated or PSTN calls only your tenant's media leg is visible. Viewing a user's call detail is audited.
Tenant Settings
Network and sites · Graph permissions · Notifications
Network and Sites
Graph Permissions
Notifications
🌐 Network topology (subnet to site)
Map each network subnet to a physical site so Teams call quality can be analysed by location. Matches the subnet seen in your Teams call data.
CSV columns:
Subnet,SiteName,BuildingName,City,Country (Subnet is the network address, for example 10.20.0.0).Loading…
📶 Wi-Fi access points (BSSID to AP)
Map each Wi-Fi BSSID to a named access point and location. Matches the BSSID your Teams call data records for Wi-Fi calls, so you can pinpoint problem APs.
CSV columns:
BSSID,APName,SiteName,BuildingName,Floor (BSSID is the AP MAC, for example 86:0b:7c:c6:eb:b0).Loading…
📡 Known mobile hotspot and tethering ranges
CQL auto-detects common personal networks (iPhone hotspot, Android tethering, Windows Internet Connection Sharing) in your Teams call data, labels them in the unmapped list, and flags their calls as off the corporate network. Add your own ranges or suppress a system default.
Loading…
📡 Teams call data connection
The change-notification subscription that streams your Teams call data to CQL. It renews automatically; use these controls if it ever needs attention.
Loading…
Microsoft Graph application permissions
The application permissions CQL requests, checked live against what your organisation has granted. CQL follows least privilege and requests only what its features use.
Loading…
Notifications
Coming soon
Notification channels and routing rules will be available in a future update. CQL will support Teams channel webhooks, Teams chat messages and email via Microsoft Graph.
Privacy
Connected data sources · Governance and retention · Privacy and AI
Connected data sources
Data governance and retention
Privacy and AI
Connected data sources
Architecture reference data for the Microsoft sources used by CQL
| Source | Status | Last sync |
|---|---|---|
| Teams call data | Connected | Live, change notifications (< 1 min lag) |
| Presence | Connected | On demand per VIP detail page |
| Service health | Connected | Polled every 15 min |
| Directory and Groups | Connected | Delta sync every 5 min |
| Intune managed devices | Connected | On roster sync |
| Azure OpenAI | Connected | On demand narrative generation |
Stack is intentionally locked to Microsoft Graph, Microsoft Intune and Azure OpenAI. ServiceNow, Cisco DNA, Zscaler, NetBox and Aruba remain out of scope.
Data governance and retention
Reference policies for uploaded and derived data
- Storage regionUK South, tenant-isolated, encrypted at rest (CMK)
- Used forEnrichment of your tenant's Teams call data only, never shared cross-tenant
- RetentionActive until superseded, archived versions kept 90 days for rollback
- Audit logAll uploads logged with user, timestamp and file hash
- Right to deletionHard-delete on demand, purged from analytics within 24h
- ComplianceSOC 2 Type II, ISO 27001, UK GDPR DPA available on request
Azure OpenAI region and retention
AI model configuration for this tenant
Region pin
- Prompt logging · No PII leaves your tenant regionOff
- Retention · Configurable30 days
- Model · Standard 20K TPMgpt-4.1-mini
Privacy and visibility
Data visibility controls for this tenant
- Call content, transcripts, messagesNever read
Show meeting subjects in UI
When off, the UI shows the meeting ID only. Subjects are still fetched for AI prompts.
Enable audit log export
Representative front-end control until audit export settings are wired
Mask VIP names for non-admins
Names render as initials only for viewer-role accounts
- AI data sharingNone. Not used for training.
- Tenant data isolationPostgreSQL RLS + EF query filter
- Encryption in transitTLS 1.2+