-
Teamwork Analytics
-
-
- Target Specific Team Owners by Country with Information
- Reminder about Team Guests
- New Public Teams without Guests
- Single Owner Reminder with Channel ID
- Public Teams Reminder with Channel ID
- Target Specific Team Members by AD attributes
- Teams Activity Reminder with Channel ID
- New Public Teams without Guests
-
-
- Summary
- Activity by Country and Modality
- Active User Counts
- Active User Percentages
- Active User Percentages All Bands
- Month on Month
- Device Usage
- Device Usage Details
- Avg Use Per User Per Day by Country
- Relative User Activity
- Users and Attributes
- Custom AD Attributes
- Data Freshness Detail
- Daily Active Users
- Weekly Active Users
- Monthly Active Users Percentage
- Relative Daily Active Users
- Relative Weekly Active Users
- Relative Monthly Active Users
- Activity Counts Daily
- Activity Counts Weekly
- Activity Counts Monthly
- Per User Activity Daily
- Per User Activity Weekly
- Per User Activity Monthly
- Show Remaining Articles10 Collapse Articles
-
- Team Stats
- Teams Distribution
- User Collab Activity
- Collab Activity (Averages)
- Collab Activity (Totals)
- User Mention Activity
- Team Files
- Per Team Profile
- Guest Distribution
- Guest Details
- Users and Attributes
- Threads Country Interaction
- Replying Country Interaction
- Threads Department Interaction
- Replying Department Interaction
- Active Teams Files and Chat
- Teams Channel Chat Activity
- Data Freshness Detail
- Show Remaining Articles3 Collapse Articles
-
- Meeting Trends
- Meeting Detail
- Meetings Per User Trends
- Meeting Join Stats
- Meeting Join Dashboard
- Meeting Joins by Country
- Meeting Join Country Detail
- Meeting Joins by User
- Calls Per User Trends
- Call Stats
- Calls Dashboard
- Calls by Country
- Calls Country Detail
- Calls by Users (All)
- Calls by Users (Last 14 days)
- Interaction Overview (Last 14 days)
- Call Interactions (Last 14 days)
- Meeting Interactions (Last 14 days)
- Show Remaining Articles3 Collapse Articles
-
-
-
- Querying the RAW JSON Call Records Files
- Data Issues with Microsoft Teams user activity Get user detail Endpoint
- Check Data Freshness from Microsoft Reporting API
- Get Call Record from Graph
- Calls and Meetings Database Schema
- Deploy a Calls & Meetings Automation scenario (CAT)
- CAT Installs – Customer Monitoring
- Configure Task Scheduler for Automation
- SQL Backups
- CAT Configuration Notes
- Data Nuances
- DeadLetterManager
- Calls and Meetings Aggregate Table Calculations
- Anonymisation of Selected Users PII Data
- Excluding teams from file scan
- Configure Custom User Attributes – Usage and Governance
- Configure Data Retention – Usage and Governance CAT
- Data Collection Configuration (Scan)
- Show Remaining Articles3 Collapse Articles
-
- Call Queue and Auto Attendant data
- Collecting Logs – Usage and Governance
- Comparing Teamwork Analytics to other solutions
- Data Collection Explained Usage and Governance
- Data Dictionary and Reporting Capabilities Usage and Governance
- Decommission
- Determining current data collection state
- FAQ Usage and Governance
- Files / Drive Items
- Messages
- Monitoring and Maintenance Tasks Usage and Governance CAT
- Relative User Activity Thresholds
- Security Details
- Usage and Governance Data Collected and Capabilities
- Usage and Governance Dependencies
- Calls & Meetings Definitions
- Database Version
- Show Remaining Articles2 Collapse Articles
-
-
Teams Audit
-
Teams Chat Assist
-
OneConsultation
Network Key Performance Indicators
When you make a Teams call your audio, video and screen sharing is sent over the network as streams of network “packets” – hundreds every minute. When networks are healthy, those packets should all arrive at their destination without getting lost or delayed during the journey. Teams calls are “real time” communication and can be affected by poor network performance.
The Teams software codecs are good at dealing with minor network quality issues by using techniques such as forward error correction (sending extra packets in case some get lost or delayed), and concealing lost or late packets by smoothing over any gaps.
We look at network quality for Teams calls using three Key Performance Indicators (KPIs); Microsoft has defined thresholds above which a stream or call is considered “poor”. Teams software clients monitor these KPIs during the call, and record the average and maximum values at the end of the call.
Jitter
On a good network, our packets should arrive regularly and in order – if they don’t (high jitter) it can cause audio to be “robotic” and hard to understand.
Jitter is expressed as a time (ms) value – the change in delay between successive packets.
Packet Loss
On a good network, packet loss is zero – everything sent makes it to the destination. When packets are being dropped, this can create the effect of missing parts of words, or cause choppy or frozen video.
Packet loss is expressed as the percentage (%) of packets lost compared to the total packets sent.
Round Trip Time (RTT)
Delays on the network cause packets to take a long time to reach their destination, so audio and video are also delayed. If round trip time is bad, normal conversational flow may be difficult and people talk over each other.
Round trip time is the time (in ms) it takes for a packet to travel to the destination and back.
Some delay is inevitable, particularly on long distance calls. For example, a good RTT between London and Paris is under 10ms, while between London and Sydney a good RTT is around 250ms.
Microsoft Thresholds
Microsoft publishes thresholds, above which a call is classified as poor.
KPI | Threshold |
---|---|
Jitter | Average 30ms |
Packet Loss | Average 10% loss |
Round Trip Time | Average 500ms |