 So Christine says, I am trying to add a SharePoint communications feed on my site where employees can post questions and have one of the site owners respond to them like a community forum. The goal is a learning page where everyone can read questions and answers given. Yeah, this was this was my pet question for this set, I think. Definitely use the sharpest tool for the job. People tend to focus on whatever tool is new or special to them and SharePoint is not always the answer. Yeah, SharePoint communications sites are great. But that's not the tool that was meant to be a forum. That's what Yammer now known as Weave Engages for. So you can connect those two, they're completely integrable. So you can bring your feed from Weave Engage into a SharePoint site so you can centralize it. So that was the whole point of what Yammer was the differentiator between Yammer teams and SharePoint at that when they were originally released was Yammer was supposed to be building communities and giving people that opportunity and having that moderator that can field the questions and answer them and decide who can field the questions and who can answer them. But it doesn't mean it has to live just in Weave Engage or, you know, what again what used to be called Yammer, bring it into SharePoint. So if that's where they're working or bring it into teams, if that's where they're working, you want to, you know, store and use the right tool, but surface it where people are most productive. Yeah, it's a, and I know this is a topic that we've discussed with recordings through this series is that, you know, Microsoft is really trying to move at the SharePoint organizations, trying to move away from this idea of, you know, SharePoint as a Swiss Army knife and it can be anything that you want it to be like, can you go and build a solution that does those things using SharePoint? Yes. But why not go use the tools that were built that were designed for this. That is that it's integrated fully in me what the other side too is that there's a reason why that Viva Engage, formerly Yammer, we keep saying that it's like X or Twitter. I just like refer to it as Twitter because it's okay because nothing ever gets rebranded, right? Rename rebranded. But maybe people don't realize Yammer is now Viva Engage. I still have the Yammer t-shirt. Thank you very much. I wear it proudly. But before the rebranding, Yammer numbers were adoption numbers were going up and the cause of that I believe is entirely because of the deeper integrations with Outlook and primarily with Teams. So the fact that you can have a unified experience with all these pieces, Viva Engage is perfect for this scenario. This is a core thing. I've shared again Yammer stories from years ago that are this exact issue where I was with a company that was acquired and the first all hands, they were trying to answer questions of people sending emails. We had multiple offices that were doing a live stream and I just like, what are we doing? Do we not have a Yammer or Viva Engage account? Log in. Everybody shared the link and people started asking questions and then answering them in real time and we would flag to the live speaker, hey, there's a question that came through on Yammer that asked this and then we would capture their response and add it in. Six, eight months later, we acquired another company, had another all hands went through and we're answering questions for those employees. People like I came late to the all hands and realized people were already in Yammer and accessing the questions, the same questions, pointing redirecting people to that and adding to the knowledge base than that. I mean, it's perfect for that solution. One of the good things about Viva Engage is it is literally about creating a learning organization. I mean, you've got the social aspect, but it's about flattening the lines of the business and when it comes to Viva Engage and you think about the team is about your teams, it's about working as a team, it's a group, whereas Viva Engage is actually about the organization and it brings everyone together. So if you don't know who to ask and rather than doing a distribution list in mail, which is not what you want to do, it's in Viva Engage that you can put in information, ask questions to the organization where the other people can actually tag to answer and it's not just about one person to answer. So if you're thinking of your SharePoint site and you've got a community, is it you only want 10 people managing that SharePoint site that are going to answer those questions? Or do you want the organization answering questions? And that's where you come in to being a learning organization because you open it up as a community. That's what it's designed and built for, is that flattening of the business and providing opportunities of if you don't know who to ask, ask the business. So and that's kind of why we really get in and use it. I think the best analogy that people can relate to is that like chat is you and I sitting at our desk or texting each other. Teams is like that cube farm. Everybody kind of working there in that space. Yammer is kind of two things or what's Viva Engage. It's like the break room where there's the bulletin board and you can post things and people can consume and stop by. This is what my cat ate today, a hero shirt with everybody. I've got photos for me. It's kind of like Facebook. Yes, or it's the auditorium where you have the town hall and everybody can come by. So, you know, if you kind of think of it that way, you don't want to have, you know, in your teams, these all company teams drive me crazy because it's too much information from too many channels coming in one space and overwhelming everybody. That's what Engage slash Yammer was for and not having those all company teams. I just like sharing the fact that a few years back when they announced that all company channel in teams at the MVP summit. So you had a very packed room, about 200 Microsoft MVPs sitting in that room. And when they announced that feature, they got booed by the entire audience. And people were like, MVP, we were upset. We're like, like, that's not the way that you use teams. And so we like, we got it. And I think Microsoft went and developed that feature because there were very large clients that were demanding it. And I think it was the wrong thing to do. Or I mean, look, you know what, I don't care. Have it out there. I just never, I like, I don't look to that. I stay away from those conversations. I participate in the chats and the teams, the channel conversations that are relevant to the work that I need to do. I rarely go in because I never find any relevant information in those all company channels. And that's a problem. People tune it out just like they've tuned out email because they are just overwhelmed by it. And there's not those focused channels of things that they can visit when they need to know something. And they're missing the big announcements that are like, well, it went out in the all company channels. Like, I turned that out. I tuned that out months ago. And yeah, I know all of you that do architecture sitting here shaking your head at those all company channels, just like I do. Hey, Shari, just from a personal perspective, my team work on that. So I'm going to reach out to you and just have a conversation about that if that's OK. Oh, absolutely.