This is a Segway from my last post on Reporting on Skype for Business Messaging Activity using the Conversation History Folder in Exchange .In this Post I'm going to be looking at the Private chat messages from Microsoft Teams that get stored in a hidden folder called TeamChat (see this post for how to get that folder in EWS) under the conversation History Folder as part of the compliance process for Teams. As Teams is still a work in process a lot of those compliance properties have changed since my first post about getting this folder and looking at the history of even the limited dataset in my mailboxes there is a lot of fluidity in the compliance information that is being added (so its a little bit of a dogs breakfast in terms of data when you go back a number of months). The compliance properties themselves get added when the substrate process in the cloud copies the Chat Message from the skypespaces backend to the Mailbox. To give you a visual representation on what these properties look like you can use a MAPI Editor
Unlike Skype where there was one message that would represent multiple messages in a Chat Thread, with Teams there is a one to one basis for each private Chat message in a Thread. All the interesting meta-information that is needed for reporting is held in the above Extended properties. Take for instance the ToSkypeInternalIds property which contains the list of the recipients for Private Chats stored in a Multivalued string property. (this information also gets stored in the Recipient Collection of the Message in a resolved format)
Instead of SIP addresses like Skype, (for chat anyway) Teams has its own format which contains the AzureAd guid of the user (or Guest). If you want to resolve this back into an EmailAddress or UPN the Graph API can be used to do this eg if I take a Teams address
using a simple Split to get just the guid portion of this string you can then do a simple Rest Get to get the user information as long as you have an underlying Token to use in the Graph API eg
$GUID = "8:orgid:fb25746f-fa0c-4f01-b815-a7f7b878786f".Split(':') "https://graph.microsoft.com/v1.0/users('" + $GUID + "')"
I've put together a script that first gets the TeamChat folder using EWS then enumerates the messages in that folder for a particular day time frame and using a number of the extended properties from the first screen shot to build some log entries that can then be summarised into some reports.
EWS Meet Graph
Because EWS doesn't have a way of resolving the Guids from the From and To Address properties in Teams. I've integrated a bit of Microsoft Graph Code to the do the resolution. Because by default this script uses oAuth we can take the Refresh Token from the first auth used to get into EWS and then get another token for the GraphEndpoint without needing to re-prompt for authentication so this all fits together nicely.
So by default when you run the script you will get flat log entries back like
Or you can Group the threads together (based on the ThreadId) using the -GroupThreads Switch
Like the Conversation History script I have 3 base reports that look something like this in HTML
To use these Reporting options
Get-TeamsIMLog -MailboxName email@example.com -Days 30 -reportbyDate -htmlReport | Out-file c:\temp\30dayreport.html
if you want the same report in csv use
Get-TeamsIMLog -MailboxName firstname.lastname@example.org -Days 30 -reportbyDate | ConvertTo-Csv -NoTypeInformation -path c:\temp\30dayreport.csv
To report the top senders that sent this Mailbox in Direct Chats
Get-TeamsIMLog -MailboxName email@example.com -Days 30 -reportFrom
To report the top recipients of IM's
Get-TeamsIMLog -MailboxName firstname.lastname@example.org -Days 30 -reportTo
I've put the code for this script up on Git Hub here
Hire me - If you would like to do something similar to this or anything else you see on my blog I'm currently available to help with any Office365,Microsoft Teams, Exchange or Active Directory related development work or scripting, please contact me at email@example.com(nothing too big or small).