I will admit, as interesting as SharePoint knowledge agents are, enabling them wasn’t very simple for a PowerShell novice like myself.
I’ve only had time to watch the keynote today, and I’m already overwhelmed by the number of announced changes coming to M365 – almost all of which involve AI of some sort.
If you want to see the firehose, you can check out the Book of News.
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.
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?
I do appreciate that the water between the two tools is less muddy. It’s still not clear. There is still confusion among the average users, but it’s a little less murky. That’s a good thing.
The surprising part is that someone put the word in a memo. They wrote it down. (Or maybe Copilot wrote it and they didn’t catch it?)
What’s not surprising is that this is the market strategy for an AI tool. Microsoft has a ton of money invested in AI. In many ways, they bet the company on the success of AI generally, and Copilot in particular, and the market just hasn’t developed the way they expected. So, what’s the next step?
Reposts