-
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 Articles (10) 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 Articles (3) 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 Articles (3) 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 Articles (3) 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 Articles (2) Collapse Articles
-
-
Teams Audit
-
Teams Chat Assist
-
OneConsultation
How to make Logic App Webhooks for TWA Automation Actions
1. Create a new Logic App in Azure
a) Nagivgate to theĀ Azure Portal, and once signed in choose Create a resource, and then Logic App (you may need to search for this);
b) Click the create button and fill in the required fields as in the example below
After a short wait, your logic app will have been created. Navigate to the resource group and move on to section 2.
2. Build the workflow in your Logic App
a) Click the edit button on the Logic App home screen, and in the designer, choose “When a HTTP request is received” as your default trigger;
b) When the designer opens, make sure you leave “Request Body JSON Schema” blank, as the message from the Adaptive Card is unlikely to be strongly typed and it will cause the webhook to reject any input. Do not change this unless you are 100% sure about the schema of the Json response from your card.
c) Hit the save button straight away and a URL will be generated forĀ configuration in the Automation API by Modality. Once you have passed it on. Test out your webhook, and view the result in “Runs history” on the overview page;
d) Click on one of the runs to see what the data looks like. You should see the webhook input by looking at the “Body” property of the “When a HTTP request is received” operation. Copy the value in this box for step e.
e) Go back to the designer and add a new “Parse Json” operation after “When a HTTP request is received”. Set the values as follows;
f) From this point, you should have all the available information from your webhook, and are free to build out the logic app as required.