u/badaz06

Retention and Purview are the bane of my existence.

Since MRM is going away, I'm working on retention via Purview. We have doc libs with various retention policies, say 1, 3 and 5 years for example. With Purview I push a label policy out to the site, the policy has the 3 retention policies in it, and I can then assign which of the 3 policies to whatever doc library I want, and apply it to all documents in the library.

Where I'm stuck is that if I move a file with a 1 year label on the document into a 5 year area, the 1 year sticks instead of adopting the 5 year policy. I can see this being a major headache down the road when users think they've moved something into a 5 year folder and it disappears.

Anyone already figured out a way around this? Doing a script is untenable for the # of files we have in SPO.

I'm in the process of (trying) making French Butter. My first go at it never broke, try #2.

I suspect I'll end up with a few sticks worth of butter, some of which I'll freeze, but I was thinking about adding some honey to one of them (we have some local beekeepers in the area).

How much honey should I add to 4 ounces of butter for the right mixture? Thoughts?

Any other mixes you would consider?

I know this is about One Drive, but it's more of a SharePoint and Azure Admin issue.

What is your current method for off boarding users regarding licenses?

The reason I ask is that we didn't realize that our process, which involved removing licenses manually from user accounts that were in the process of being deleted off the tenant, resulted in tons of One Drives being archived by Microsoft. In fact we had some accounts that we determined didn't need a license and removed them. I found all this out when I noticed one person's One Drive had archived, and started down the rabbit hole and found a ton of them had been. Evidently a one drive with no associated license is automatically archived.

When I reached out to MS, they essentially said we'd have to enable billing in order to unarchive and then delete them. At 60 cents a GB.

Evidently there's some process where the files "may" or "can" be deleted by Microsoft, but nothing in writing that says they "will" be deleted.

For those of you wondering if this is something you want to check out, go to your SPO admin page, Reports, OneDrive Accounts. That will show unlicensed One Drive accounts and their status.

TIA!

How are you handling the requirement for adding guest accounts to one drive in order to share files?

We have always allowed users to share files out of their One Drive without any assistance. Now that seems to have gone by the wayside, and for users to share a file with someone external, they now need a guest account created.

The downside to this is we've always been pretty stringent with guest accounts. Now we either have to hand over control to where anyone can invite a guest which in turn they can add to sensitive areas in Sharepoint, OR increase the over head to have admins add these guest accounts so users can share files. in which case they can still be added to sensitive areas of Sharepoint.

Pretty frustrated here at how this is being implemented. Any help would be appreciated.

Some updates:

One of my biggest concerns was SharePoint Access; as I indicated that you can share what you want from One Drive but I want to protect SPO files and folders. There is a setting in the SharePoint site if you go to the Sharepoint Admin Center, choose a site, under settings called "external file sharing" that you can restrict access to the site. I'm hoping that will save me at least in that regards. Researching more now as well as checking my sites to determine that setting for them.

How are you handling the requirement for adding guest accounts to one drive in order to share files?

We have always allowed users to share files out of their One Drive without any assistance. Now that seems to have gone by the wayside, and for users to share a file with someone external, they now need a guest account created.

The downside to this is we've always been pretty stringent with guest accounts. Now we either have to hand over control to where anyone can invite a guest which in turn they can add to sensitive areas in Sharepoint, OR increase the over head to have admins add these guest accounts so users can share files. in which case they can still be added to sensitive areas of Sharepoint.

Pretty frustrated here at how this is being implemented. Any help would be appreciated.

I use AzureAD groups for a majority of access, and use SPO rights sparingly.

When we were a 100% file based operation, the rights were so incredibly jacked up it took Sherlock Holmes to figure out who had what, and I wanted to have the ability to show users who had access to what.

So, Site and DL's are handled, but users share files, folders and lists out all the time.

How do you guys handle removing lists? (We dont give users admin access)

I pull some incredible boner moves, let me tell ya.

I made some chicken stock...and then get a colander out, put some cheesecloth in the colander and start dumping in the stock to strain it...and watch the broth flow into the sink, ya know..like maybe I forgot to put a bowl UNDER the colander?

Not much thankfully. But all I could think was, "Dude you are an idiot sometimes."

My mom has 2 old framed photos in convex glass frames. Unfortunately with the shape of the glass it's impossible to get a good picture of the images on a camera, and we're reluctant to mess with the frames for fear of damaging either the photos or the frames.

Has anyone dealt with these and know however to get a good shot, or what type of person would be best qualified to open them without doing damage?

One of them is a relative in a Confederate style uniform but it's impossible to see any decent detail.