Me talking about M365
A short edition while I fight off a Covid infection
Last week, I was invited to talk to Doug Austin and Tom O’Connor from the eDiscovery Channel about M365 and Teams.
You can watch the interview here:
It was a fun conversation, even amid a busy week in Ohio. I had planned to stay in Ohio and visit the office, friends, and family, but yesterday, the COVID test came back positive. So, instead, I will be staying by myself in Ohio, hoping to be well and ready to speak at the ILTA Conference in two weeks.
Say hello if you’ll be there, and I’ll understand if you want to skip the hug. I should be negative by then, but you never know.
After the conversation with Doug and Tom, I wanted to write about where to learn about Teams and M365 eDiscovery. I mentioned heading to Microsoft Learn, but I wanted to share a few specific links for eDiscovery:
Greg Buckles was also on with Doug and Tom the week prior and shared this resource he’s been working on.
First Steps to Leveraging Purview eDiscovery
If you want to know more about Teams - this is a good place to start:
Admin training resources for Teams
As I mentioned in the video, the best way to learn how Teams works and where the data is stored is to get your hands on a Teams environment and test. I briefly mentioned what “testing” looks like, but let me break it down even further for you. I’ve been asked to document how group and 1:1 chats are stored in this example. I would likely have a list like this with a code for each item I am investigating. (That would be included in the text of the item)
Chat message - 20240730A
Shared file in chat - 20240730B
Meeting chat message - 20240730C
File shared in chat - 20240730D
Transcript and recording - 20240730E
Whiteboard shared in the meeting - 20240730F
Meeting agenda in Loop - 20240730G
And so on.
This is my protocol. The idea is always to create an item using the tool, then follow the item using the eDiscovery tools to search for the code and collect the item.
It takes a lot of time, but nothing gives me a clearer picture of what happens when users are active in Teams chat, channels, apps, etc.
Likewise, nothing gives me a quicker view of what data the eDiscovery tools aren’t capable of locating and collecting!
I’ll discuss where the data lives in Nashville on Aug. 13 as part of a panel. No spoilers for now. ;-)
That’s it for this week. I hope to have more energy to dedicate to the M365 News issue for August next week. Until then, stay healthy and cool out there.