 Kaseem says, I've been encountering a peculiar problem with Microsoft Teams. I'm hoping someone here might have some insights or solutions. The issue is as follows. One of our users is unable to upload attachments or images to a specific group chat. Interestingly, this user can still send attachments and images without any issues in other group chats. Has anyone experienced a similar situation or have any suggestions on how to resolve this? Any help would be greatly appreciated. You got to think about who's in the group. If they allow external users, my guess is that this is a group chat that includes an external or a guest user, and that guest user's policy for their tenant probably prohibits uploading of attachments for external chats. I see this a lot where people will get into group chats with people outside the organization, and the other organization has blocked uploads or blocked whatever thing that you can't do. Then you get in a group chat and one person in the group is from not in your organization or their organization blocks it, and then that means the whole group is blocked. That's probably the most common scenario that would cause this to happen. If it's all internal people, there may be a policy behind the scenes. Maybe they have a person who's under e-discovery lock, or maybe there's a different policy that for whatever reason is blocking that particular group that's keeping people from being able to upload items. That'd be my guess. I've seen clients that they create these different policies, and they're group-based, but that you have someone who's in two policies. Right. Depending on which one is the higher priority in the policies list, is the one that takes effect. Yeah. It's almost interesting that it would be good to see what is that? There's an old dev tool to root through and you know what I'm talking about. Which one? Fiddler or Tracerow? Fiddler. That's what I was thinking of, like Fiddler. Through, you almost see like a Fiddler-type solution around perms to look at, to look at the hierarchy of the permissions and look at where their user is, to show the conflict between these. If you could almost visualize permissions that way. Product idea, somebody out there. But that would be, so when you run into these kinds of situations, if it could flag and say, well, I see this, here's all the permissions that are associated with this site, with this chat, here are the users. Oh, I see the user in two places. Why? What's the differences? Here's where the rules may be in conflict causing those issues. Absolutely. Unfortunately, there's just with policies between just regular policies confidential. I mean, maybe they're trying to upload something that was confidential too, and you can't do that, right? Or DLP policy. Exactly, right? So there's a number of reasons, right? But we don't have a good way to troubleshoot them. You literally, like you have to be the person that configured it, but in large organizations, the person who configures DLP is not the same person that does the labels and all that kind of stuff either. So it's like, there has to be some synergy, and right now there's no easy way to do that. So I'm with you, Chris. If someone wants to build something, I'd be all over it, all over it. No. It's not an easy one, unfortunately. Jeff, you going to build that? You like to build stuff? It's like a formula tracer in Excel. I'm made out of wood, Stacey. Hey, I didn't say it had to be perfect. I just said he could build something. It could be a wooden hammer because that would make me happy some days. If it was made out of wood, it would be perfect, then. Of course. If all else fails and you try turning it off and back on again.