So, you're saying it's almost like a feedback loop. So, because there's a thing that you don't know what you don't know, right? So, it's like, worker is like, I didn't know that I needed to have that dropdown list of my attachments. So, in product group, do you have a, you have customer input and customer voice to kind of feed back in to think of a way the AI is used? Or do you just sit there as well and go, well, the customer doesn't know they need this at the minute, but this is a really good use of the technology.

Well, I think there's two things, right? First, we talked to customers about what they need. And so, this, one of the scenarios, like for Viva topics, that's pretty common that our customers told us about is onboarding. So, you come on either you're new to an organization or you're new to a team and they use a lot of terminology that, you know, is foreign to you, right? And it can be very confusing, right? And so, this is one scenario that we heard from customers early on that they said, you know what, this kind of thing could really help with that. And so, that's an example of listening to the customers to develop before we develop the product, right? When you say what, we could choose all the things we could do, all the different Microsoft research technology as you're causing cognitive services, power platform work, we could bring any of that in to Microsoft 365. But what do we focus on? And that's how we start, right? Yeah,

that's fascinating. And

look, and it's, when I got those emails, you know, the ones asking me to kind of provide feedback on a topic or a subject and an I apologize if I let anything out the bag, I didn't realize that that was in. No, no, it's not. I just wanted to let you know that it's on the use of that right now. For sure. So, I can see how that works in a test, you know, that's called an internal testing, you know, a dog food and kind scenario where I'm helping to, as an employee, to kind of teach the machine and give input to the models. You know, like, in a customer scenario, is how are they going to teach their own models and learnings? Does it have a similar mechanism externally or do we look at that kind of differently? Because that's, you know, requires a different nuanced mechanism when you're talking in different customer scenarios. Yeah, and that's the next feedback loop. I think that Dan, you were also, you know, kind of leaning towards is you can train the models to learn about your organization, right? So, so we've kind of got it built out in a couple different ways. And we have found internally that the email has been a great way to collect feedback. We just haven't built that out into a way that it's extensible, that works outside of Microsoft, because we have a different kind of contract with you than we have a test. Right. And so, in product, what you see is a couple different other feedback mechanisms. One of them is, if you hover over a topic that you see in SharePoint right now, and then later in other apps as well, or in search, there's sometimes there's questions on the bottom, like basically asking if we got it right. And what that'll do is that'll tune that model to your organization, right? So, what does this mean? You know, what is Minecraft and education is to have a specific meaning for us, or you, in your org? It might even tailor it more to you differently than it tailors it to me, because the people that you're talking to do about that and the documents you're collaborating on about Minecraft or education are good and be different ones than I am.