 Benjamin asks, do you know of a way to delete a team and the associated SharePoint site while keeping the email group? The understanding is no because they're all very tight together. Because when you create a group, it funnels up all of the technology as part of it in the back end. So when you take one down, you're taking everything down, it's an all or nothing is my understanding. Is it possible to migrate that content, like create a separate email address and migrate the content there? I think the thing is you're going to end up with a different email. If you're needing to keep the email itself, that's where the challenge comes into play. Because I've got this scenario going on at the moment where that particular email is being used and there's content in there, including chat and all the above. That actual email is needed for another component now. But it leaves us now with this email group with content. If we're trying to delete that, but you've still got the chat, but it just becomes a little messy. Somebody created a team using an email that it should have been regulated or governed and now they can't reuse. If I were to create finance at abc.com, and I'm not in the finance department, now we've locked that down, somebody can't use it. People don't understand how interlinked all the pieces are with that. I mean, look, there's things that you can do, like you can remove permissions to the SharePoint site and even to the team site. You can, and just so that it essentially hides it from the view of normal people, and then still have the email open and have access to that. But it's like in the early days of teams where people would say, hey, I want to be able to keep everything and be able to start right up again. And it'd be like, well, then you're not archiving it, you're not shutting it, which will remove everybody. And again, they want to keep the chats, they want to keep the email, they want to keep all the different pieces. They're all part of the whole. Yeah, and even a planner board, that's where people get burned. Like they're like Christie's trip plans, and now there's an email of Christie's trip plans in the address book and all those things that you don't realize that are being spun up in the background, even from creating a planner, because it creates the group, it creates the site, it creates everything but the Microsoft team based on that. But you can always team a five later. Yeah, there's so much stuff, isn't it? Yeah, and there is, there's so much stuff, because I've found that. I'm going through and going, okay, what is there, trawling around the SharePoint, trying to clean things up, trying to work out if we start to use that for a wider group, how messy is it going to be? And there's quite a lot that actually gets created and funneled as part of that group. So it's like, well, what my question is, what are you trying to do with the group ultimately to keep it going? Are you trying to just keep it as like a distribution list? Which, you know, do something different instead? Yeah, Matt Wade has a great infographic that explains when you create it, when is a group created, and when you create certain things, what gets created, and I love that. It's a great visual if anybody has that. I'll put a link in the chat.