A new SharePoint Look and Feel: What’s Changing and Why It Matters | Microsoft Community Hub
Has anyone else had this switched on in their tenant, it's not been rolled out completely, we have a mix of users who are still on the old view.
Favourites have disappeared for users on the new experience, adding again does nothing.
The option to turn it off is missing from the admin centre as well.
Is there anyway of listing ALL active sites on your tenant in the admin console rather than root site collections?
We use it as a quick way to determine what our largest sites are, however the Storage Usage on a site with private channel(s) only shows the storage for the root site collection.
You have to drill into the private channel link on each site to see the storage usage for the channel storage usage
I know I can get this from powershell but I'm trying to find a way of getting this done in the GUI where you can simply export to excel.
I'm trying to implement Retention Labels with deletion at the end of the period and allow deletion during the period.
I'm running into issues however as users who can edit the file can also remove the label.
I can't find any way of prevent this, in sensitivity labels you have the option to prevent users from removing the label, they can however change it.
There appears to be no similar option with Retention Labels. I've read you can mark the item as a record but this then prevents deletion as well according to the documentation.
Has anyone come up with an out of the box solution to implementing Retention Labels without the users removing them?
I've been trying without success to get an accurate picture of current Storage being used by Sharepoint Embedded Containers.
The Admin Console only shows x.xx GB
get-spocontainer also only shows x.xx GB
I could really do with getting the size in KB
Any idea how I might approach this?
This is a follow up to my previous post as I've learnt a few things since posting.
The main thing is that "true" duplicate files do not actually take up space in your site collection, when a file is uploaded it has a unique hash assigned to it, if that file is copied or uploaded again then the same file hash is assigned and only one of the files actually counts towards storage allocation.
You can get the unique file hash from the Graph Interface, simply query the list item(s) and then retrieve the hash from the properties.
I used this Graph URL to retrieve all drive items
$graphUrl = "v1.0/sites/$($SiteId)/lists/$($ListId)/items?`$expand=fields(`$select=FSObjType,UniqueId,FileRef,Created,Modified,Author),driveItem(`$select=id,name,size,file,createdDateTime,lastModifiedDateTime)&`$select=id"
It's then a simple case of getting the hash from this part of the returned response
file.hashes.quickXorHash
Hopefully this will help some of you with the same issue and not fret over duplicate files within site collections.
** edit **
I need to put a caveat on this that this won't work on office files as they're given a unique quickXorHash regardless of how they are duplicated in sharepoint.
I'm primarily using this to identify duplicated data from a Network Drive Migration that wasn't sanitized before moving.