 We'll start it off. So Minakshi says the user is unable to delete a classic team SharePoint site. He gets a message that there is a conservation hold on it, but the hold was removed. We are getting an error message. Sorry, something went wrong. This site collection can't be deleted because it contains sites that are included in an e-discovery hold or retention policy. On other sites where the hold was removed, we were able to delete the site without a problem. But for some sites, we cannot. Any idea how to overcome this issue? Yeah, so perseverance? I know, right? Just keep going at it. I actually have this problem for one of my clients where there had been a hold placed and they were trying to delete things. They couldn't get it. I've run into this several times. And the two things that he says here that are probably kind of the key words to this is that the site that are included in e-discovery hold or retention policy. So two things that will keep you from being able to delete things are e-discovery holds and retention policies. e-discovery holds have changed over the last few years. So anybody in the compliance world has noticed that all these holds have kind of changed and shifted. Well, there's several places that you can create a hold. So there is a regular area and there is an advanced area and you can actually have multiple holds set up in e-discovery. In fact, you can actually set up a hold and during the process of all of that, if you set a hold and you didn't remember where you put it, it might still be kind of hiding in one of those areas. So I would double check and make sure that all the holds have been removed and sometimes people go into one and they'll remove it in the core but not realize there was one in the advanced or vice versa. So make sure it's been removed in all of the different places. The other thing that it comments on here is a retention policy. So on the old SharePoint sites, you would go into Listen Libraries in a classic Listen Library and you could set up a retention policy. But a lot of times you didn't even know that a retention policy was set up because you had to go into the information services and the list setting. I can see it in my mind. It's in the bottom right. And you click on that and it would take you into retention policies and then you would have to go in there and you could actually set up retention policies. It was very, very common for people to go set it up on one place. So it's highly probable that they've got multiple things going on in multiple places that just haven't been cleared out that they just need to clean up. There's not a place to- It's got a problem with Klingons. Call the Star Trek clue. Who doesn't have problem with Klingons? No, but there's no way to go in without the box capability and look at an object and find out what all of those properties are, what holds are in place, what status of all those different things. So that's one of the strongest stories or reasons behind some of the third-party solutions that are out there that allow you to look at a list item, a library item, a document, and look and see who owned it, what things are, policies are in place, what sensitivity labels have been applied, all of those rules. Is there anything that's binding against this item? And then- I feel like you did a testifying theme. That's the third-party value, Ed. Apply the lens you want right on top of it and can- I think this is going to be a theme with some of the questions that we're going to get to today is kind of comes back to this core thing of really going and digging into and understanding what permissions, what all the different layers that can be applied. Yeah, so yes. Yeah, there's lots of hidey holes. Especially in the classic stuff, there's a ton of hidey holes where you can go into this and into this and into this and have set a setting that you don't realize ever got set. For those of you in the on-prem world, this is the Active Directory GPO application thing, where there must be a GPO in place. We don't have any GPOs in place and you go and look and eventually you find something that's buried under a bunch of books with dust and bugs and yeah, they've got a GPO in place. This is the stuff like back with the migrations where it's like, look, we should be able to go and migrate. Migration failed. And so when we develop the pre-migration analysis to start to identify this stuff and you do a run and it's the 80-20 rule. 80% of it's like, yeah, it'll migrate straight over. 20% know it'll have problems and you start digging in and you're like, hey, I found all of these e-discovery, all these holds, these things that are on there, go and fix that stuff, run it again. Hey, another 5% went through. Look at the next batch of problems. And so that's why this stuff is, again, out of the box. It's not clean because people have the ability to go and fudge with it at different levels and move things around. So yeah, good times. Lean. Keep digging.