The idea of circling back probably tempted a few of you to delete this email. I understand that, but I couldn't resist. ;-)
While we wait for some of the new features to start rolling out in February, I thought I would look at some features I’ve tested in this space to see if anything changed.
As we all know, in M365, things will change. We also know there may or may not be a lot of announcements about those changes.
But, before we get into some interesting things I found, I want to correct an inadvertent item that I left out of last week’s deep dive into the Updates app in Teams.
I forgot to mention that you can upload an attachment when submitting an update. This begs the question of where the attachment would be stored if uploaded from your computer.
Of course, the answer is your OneDrive. There’s a folder created just for attachments you submit in the Updates App called “Microsoft Teams Updates App Documents.”
Also, it doesn’t matter if you add the Updates app to a channel versus a chat. It behaves the same way. This makes sense when considering that what you see in a chat or channel conversation is being pulled from the Updates App database. On the other hand, uploading a document using a submission link in the channel conversation could seem to be uploading a document into a channel, so some might be surprised to know those documents do not live on the SharePoint site for the Team.
Another area I wanted to check again was the direct export from eDicovery Premium.
Keep reading with a 7-day free trial
Subscribe to Mike McBride on M365 to keep reading this post and get 7 days of free access to the full post archives.