I realize I’ve been spending a lot of time discussing Copilot in these monthly news posts. It’s hard not to when Microsoft spends so much time talking about Copilot.
There’s still much to discuss with Copilot, but I thought we’d change things up this month and start with SharePoint.
From an eDiscovery perspective, this may seem insignificant, but understanding how SharePoint Admins have set this up could be important in understanding the available versions. They’ve been given much more control than limiting the number of versions.
Speaking of SharePoint storage space, keep this handy - Understanding SharePoint Online Storage. It’s not so straightforward.
There is also a new feature for coauthoring in SharePoint - Microsoft SharePoint: Collaborate on SharePoint Pages and News with coauthoring.
Tony Redmond recently also made me aware of the ability to expire internal sharing links: Sharing Links Expiration Supported for all Link Types.
I spent some time with expiration dates yesterday and found them a bit confusing. Essentially, if your SharePoint Admin has set a default for expiring external guest and/or anyone links, that will take precedence over what the user does on an individual shared link. However, internal users will be subject to the individual shared link’s expiration.
For example - in my test environment I expire all external guest links after 60 days. If I create new share links for specific internal and external users and expire them both on July 30, internal users will lose access on July 30, but the external users access to the shared folder will expire in 60 days. At least that’s the way it appears to be working right now. As always, that is subject to change and you should test this yourself.
This also applies to OneDrive for Business.
Speaking of ODB, this bug probably didn’t seem like a big deal unless you were using the sync tool and planning to work offline with some OneDrive data - Microsoft confirms OneDrive shared folders are indeed turning into internet shortcuts.
This new Teams feature doesn’t change the shared file storage in chat, but it makes it easier for users to see all the files. I like the idea. Microsoft Teams Chats to Get New Shared Tab.
While we’re on the topic, Joanne Klein shared a couple of good resources in the last month related to files shared in Teams:
I also found a couple of videos related to Loop from Jonathan Edwards, which might inspire you to take another look at it -
Also, if you have been using the board view in Loop - Microsoft Loop has added more functions for its boards such as expanding them into margins.
Before we dig into all things Copilot since we don’t have a retention tool for the Planner app itself (You can set a policy for Exchange that would capture notifications, but not the whole plan), this PowerShell tidbit might be worth saving - The Set-PlannerUserPolicy Cmdlet Stops the Deletion of Plans
All Things Copilot This Month
In no particular order:
New Copilot for Microsoft 365 features will be rolled out in July
What your security team needs to know about Copilot for M365
This newsletter includes information about the ability to use Copilot for Security to assist with writing your Purview eDiscovery queries, among some other useful information about Copilot for Security.
How Company-Wide Links Work with Copilot for Microsoft 365 - interesting and not what I would have expected.
The Importance and Relevance of Sensitivity Labels with Copilot for Microsoft 365
A short, informative podcast - AI for legal departments: Managing eDiscovery and data retention risks with Microsoft Copilot
Microsoft adds a number of new features to its Copilot Dashboard for businesses
One final note before we wrap this up. Microsoft recently announced this change - Teams Blocking Federated Communications with Trial Tenants. While it makes sense to block this feature with trial tenants, it might also impact some of the testing I do in the future. I use a Dev trial tenant for much of the testing related to this newsletter. Microsoft has been changing who can have and keep a development tenant, but that hasn’t impacted me yet. This latest change will probably mean that I can’t test some of the guest and sharing features using this tenant any longer, even if I get to keep the tenant for a long time. I’d love to purchase a couple of e5 licenses to eliminate the chance of losing access to features, but this newsletter doesn’t bring in enough subscription revenue to allow for that. (Y’all know that ain’t cheap!)
So, if you’ve ever considered becoming a paid subscriber or know anyone who might benefit from the information I share in each issue, now would be a good time to let them know about it. I can’t promise I will earn enough to get a subscription, but it will let me consider it.
That’s all the news for this month. I’m sure it won’t stop, and we’ll have plenty more by the time August rolls around!