If you don’t realize that your employer’s IT folks already have a dozen different ways to tell whether you’re logged in to the office wifi or not, you’re kidding yourselves. We didn’t need Teams to start ratting out employees.
If you’re meeting involves a screenshare or some kind of visual presentation, then video recordings make sense. That’s not every meeting, though. I can’t imagine many things being as boring as watching people talk in a meeting after the fact.
I will admit, as interesting as SharePoint knowledge agents are, enabling them wasn’t very simple for a PowerShell novice like myself.
OneDrive retention presents several challenges due to the variety of items that reside there by default. Share a file in a Teams chat and collaborate on it? It’s in OneDrive. Upload a file for Copilot to summarize, which will be copied to OneDrive. Meeting recordings and notes? OneDrive. Items from your local desktop and documents folders? Likely synced to OneDrive.
Use OneNote to store notes that you want to keep as a historical record? Yeah, OneDrive.
How do you establish a single policy to cover the retention of all these different scenarios?
As I’ve said many times, Microsoft has invested too much money in AI to let users opt out of using it, even if it does ruin everything Microsoft has been known for.
I know many of you who work in regulated industries or deal with security risks may not want to hear this, but it makes sense to allow users to share files back and forth in Teams chat with external parties.
Apparently, instead of purchasing M365 licenses and then additional Teams licenses, your M365 licenses will come in with or without Teams flavors.
Forgive me for picturing your MS partner with a headset asking, “Do you want Teams with that?”
That seems to be how we’ll be ordering our licensing in the future, though.
If you’re rolling out Copilot at work and looking for ways to teach people about using it, this might also be a good place to start.
Everything about Teams—security, retention, eDiscovery, privacy, and so on— starts with understanding the data involved. To understand the data involved, you need to be familiar with all the details of this chain reaction. You’re not protecting and investigating data in a Teams channel; you’re dealing with data in Exchange, SharePoint, and potentially in various other locations, depending on the apps used in the channel.
I want to be charitable and say that this doesn’t reek slightly of desperation, but is instead a strategic decision, possibly to be followed by a price increase next year. Or even that they are trying to lessen the confusion around the different versions of Copilot.
Then I counted the number of “Try Copilot Chat Now!” buttons on that page and immediately realized how desperate they are to get people to use Copilot.
