-
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
DeadLetterManager
Quick summary / TLDR:
DeadLetterManager (DLM) is a new Azure FunctionApp with a function per ServiceBus queue / topic subscription, that is used to grab DeadLetter Messages as they move into the DeadLetter Queue. Each message will be gzipped & serialized, then stored in a particular blob storage container, then removed from the dead letter queue.
Video demo of how this would work: https://web.microsoftstream.com/video/66cda872-4d69-4a20-bf7c-8c8ee4f88d71?channelId=1817e822-4b66-46c3-81a4-3d7255bca7fe
The new FunctionApp’s functions will be bound with the DLQ of a specific ServiceBus queue / topic subscription, using the Microsoft.Azure.WebJobs ServiceBusTriggerAttribute like so:
Mappings of which ServiceBus triggered funtions are bound to which ServiceBus queues/topics can be found below.
Once a message is taken from a DeadLetterQueue by the DLM, it will be serialized and placed into a relevative blob storage container. Mappings of which ServiceBus queue/topic are bound to which container can be found below.
| DLM Function Name | ServiceBus Queue/Topic Name (and subscription if applicable) | Blob Storage Container Name |
| CallParsingDeadLetterManager | graph-responses (call-records) | dlm-call-parsing |
| CallSavingDeadLetterManager | parsed-calls | dlm-call-saving |
| EndpointsSavingDeadLetterManager | parsed-endpoints | dlm-call-saving |
| FailureInfoSavingDeadLetterManager | parsed-failure-info | dlm-call-saving |
| FeedbackSavingDeadLetterManager | parsed-feedback | dlm-call-saving |
| GraphApiCallingDeadLetterManager | graph-requests | dlm-graph-api-calling |
| M365GraphResponseParsingDeadLetterManager | graph-responses (m365-records) | dlm-m365-graph-response-parsing |
| M365MergingDeadLetterManager | database-add-or-updates | dlm-m365-merging |
| MediaDeviceSavingDeadLetterManager | parsed-media-devices | dlm-call-saving |
| MediaNetworkSavingDeadLetterManager | parsed-media-networks-with-building-data | dlm-call-saving |
| MediaNetworkSubnetMappingDeadLetterManager | parsed-media-networks | dlm-medianetwork-subnet-mapping |
| MediaStreamSavingDeadLetterManager | parsed-media-streams | dlm-call-saving |
| SegmentSavingDeadLetterManager | parsed-segments | dlm-call-saving |
| WebhooksProcessorDeadLetterManager | webhook-notifications | dlm-webhooks-processor |
These new DLM containers are being referenced by the storage accounts’ new lifecycle management rule “dlm-RetentionPolicy”. This will delete blobs out of the DLM containers that haven’t been modified in 7 days. This value is configurable.