 work out if it's possible to do something like this for Microsoft Forms, the initial form is completed, which then triggers two other forms located in OneDrive to be emailed to the email address is provided on the initial form. Looking on Power Automate, there isn't much innovation with forms. It's interesting. So I think what I heard was I fill out a form and then I'm sent other forms. I don't know if everyone agrees with me, but if that's the case, first thing that comes to mind is does branching work within the form? Thank you. I had that thought too, but it sounds like somebody's filling out the form and putting an email address in and then a different form is sent to that email address. Okay. I understand. That's how I interpret it. So if I fill out a form, and it could be multiples, but if I fill out the form and I add norm, enjoy your emails as part of the form and then it sends those out to you. Why not just add them as attachments to the form to begin with? That's what I'm like, why? Why doesn't need to trigger anything. You can simply add a link, make it anonymous to those items that you're storing in your OneDrive, and put the links in the Microsoft form from the beginning, and then when they fill out the form, you can have, to your point, branching if you want them to do that, or you could simply fill out the form and have those links be at the bottom of your form and say, please fill out this form and click on these links, and they could download those, or they could fill them out as well. I think the biggest thing then is, well, I want to send them back. Well, that is an option that you have in forms is that once they fill out those things, you can give them instructions, or when they submit the form, you can actually have them attach it back to that form. So there's a couple of different ways you can do that, depending on what you're trying to happen, but I wouldn't have it trigger anything. I would essentially present them with the things they need to do, have them do it all in one action, and then have them submit it and make it do what I want it to do after the fact. Unless you're sending it to someone that's not part of that initial form process, I'm filling this out, and then I need this to go to Bob. Right. Could have the link there and say, if there's anyone you know, please send it, but then there's no paper trail or audit trail back to what went to who, when. In which case Caraon may can do that. That's, yes. Right tool, right job. How many times do we say that? In my mind, I'm thinking it's like maybe as a scenario, a travel represented inside the organization. Christian's going on a conference. I submit Christian's name with his email. It's going to send him the right form, so to speak, to fill out from one drive. So, like we said, power automate is great because there is actually some decent integration with power automate into form. So, one of the triggers that you can use is when there's a new response. So, the initial form when we're submitting Christian's name for the travel, that in turn can get all of those response details, and then you can start filling out those subactions that will fulfill the rest of the business process. So, yeah, you can totally do it. One of your triggers in Power Automate is when a form is submitted, send an email, and you can have that standardized email with the links in it. So, I'm not sure why that's a, you know, unless there's an, if then, you know, if they've said, in this response in the form, send them this one, if they've sent a response, this one sends them something else, I'm not sure. I think it's funny, it says there's not much integration with forms. Well, no, there's not much integration with a form, there's an integration with an action. Yeah, when a form is submitted, yeah. Yeah, when a form is submitted, or if you really want to track the information, you can also have that form, put your information into a SharePoint list, and then have an action be, anytime there's a new item created in the list, then you have an action that goes on to that. If you're concerned that maybe when people fill out the form, it doesn't do what you want it to do there, you can actually put something in between. So, you're catching the data, you're doing, taking action on it kind of at a little bit more fancy, more advanced level, there's additional steps you can add in the middle. And there's a paper trail you were looking for, Joy. Yeah, and you could, even if they want to keep it in the Excel spreadsheet, right, have Power Automate, bust open that field wherever it is, if there's an email address, go send whatever to whoever, yeah. So, forms is great because it's approachable, anyone can just start building, but there's some kind of gotchas with it. Joy, Sharon, you were talking about audit trail. A lot of people don't realize that the responses to forms are being stored in your OneDrive by default, right? So, you create your own form, those responses are contained in your OneDrive as a container. That may not be such a bad thing, but if it becomes like a business critical or business important form, having it just in your OneDrive might be problematic. So, you might want to consider moving to SharePoint and having those responses moved over. And I believe it should be rolling out soon on the Microsoft 365 roadmap that forms to list integration is going to be a default offering. So, that's exciting for those people there. Yeah, for multi-select, yes please. So, I'm going to break it apart and put it back together. So, your point though, Norm, is that you should move it to SharePoint, but if you create the form from Teams or a SharePoint site, it automatically assigns it to the group. It doesn't create it in your personal. So, like if you're in Teams and you go from the new tab and add a form, it automatically assigns it to the group. A lot of people don't know that. That's right. So, it's the point of creation where the storage is. And that's with a lot of things that we're seeing now inside of the service. Like a Microsoft list could be in your OneDrive now if you're using the list experience. It's in the site. It's in the site. Teams, it's in the team. So, it's a bit of a departure. You kind of brought up a thought here. It's not about Melbourne, but a thought about... So, you know, one of the... Historically, one of the problems is like you create a solution that's stored in my OneDrive. It's like, well, that's not corporate. It's not scalable for that. If I'm hit by the bus and gone, are they going to go and look at that? I mean, is that really a limitation of using forms versus Power Automate? Because if it's being stored within my company OneDrive, the company still then has recourse there. There's a way of that. So, it's not really a scalability issue. But I think it's the... There's probably a scale. The organization's dependence on it or the criticality of whatever that solution is, whether it is in your OneDrive versus in a central available, supportable area, like SharePoint or Teams. The lunch planner form, who cares? It can live in my OneDrive. It can live and die in my OneDrive. I don't care. But the thing that does that travel request for the organization, I don't want that in my OneDrive. I want that in a site where there's continuity. Should I go on vacation or leave the company? This is a great example of... And I know we all talk a lot about governance of when you look at governance of solutions that are being created architected within your organization to have those conversations. To say, is this something that, again, needs to scale up, that needs to be enterprise scalable? Or is this a spot solution for this team, for this handful of users? Not a problem the way that it's built and developed. You're not going to know, to ask those questions, if you're not having those conversations. Governance is not just about automating, having policies and things that are happening in the background, which are all necessary to have that level of automation. That's why provisioning is so key to put the guardrails in place. But you also then have to be having the conversations about stuff like this. People are going to go create. People aren't going to stop building things and solving their own problems. They need to get work done. So they will move forward with or without IT's permission. Sorry, IT. But then there should be a conversation review of those things. And sometimes something that was built says, hey, you know, there is just a better way. Or that's fine, the way that it is in that scope. We've got it documented. And if somebody then comes and says, hey, we should have this across every team and organization. Nope, we need to go and re-architect that. Well said. Well, team, go.