 If I create a site on SharePoint, a SharePoint site, I've heard it, I've heard it both ways. Can I share it to the public so they can visit my site? Depending on what you consider public, yes. To find public. If your security is so poor, it is public. It's a public. There are very, there are very real use cases guys where there are SharePoint sites that are created with anonymous access that they're set up and that site is blocked off to serve a very specific need. Can it be done 100% are there better ways to do it? Absolutely. But is a lot of that just a holdover from older SharePoint when it was a supported functionality? I mean, Microsoft has been saying for many years, don't do that. I think that it versus should you do it? Yeah, I think it comes down to your security and your risk tolerance, right? So this is back to your governance question. Every single client, I have this governance question of what's your risk tolerance and what are your needs and what are your use cases? And I feel like if a business is setting up everything correctly and they have one site that is set up for anonymous access for a specific purpose and they have defined it that way and they have governance and they have security and they have control, then I don't think it's the wrong thing to do. But I think if they're just turning on everything for everybody that potentially could definitely bite them in the long run. I don't want my long run bitten it into. Where exactly is the long run? I don't know if it's probably pain to lift it. Very painful. But to Sharon's point, there are use cases, right? There's information you need to share and they started out as Dynamics 365 portals because companies had a specific need to communicate or share information with their clients, for example. So they had to client portals and now that's evolved into power pages. So it depends on what you're trying to share. But some of the things I'm currently upscaling on power pages that I'm impressed with, that they can't seem to do even in SharePoint, is in the data verse, you can secure a specific column. God bless you. Powerful, right? I'm asking for that, you know, I don't want to have to. In one year. Yes. Row and column level security, that's a big deal. And now we're, you know, we're, we're way out of the spectrum of like a webpage. If you're spending up a SharePoint site because you want to make a bunch of resources available to the public web, may not be the right tool. But if you have a business need where you need some of your business data to be consumed and interacted with the customers, then Sherry's right. A tool like power pages is going to service that need. You know, you use the tools that you have access to, right? And so if you've got any level license in SharePoint and Microsoft 365, excuse me, you're going to do whatever you can to get the job done. But if you're lucky enough to have more of the power platform licensing available to you, you should consider something like power pages. You're bringing some of your business data into the context of those pages where people can interact. You can get rid of all this silly stuff for your downloading PDF files for someone to fill out and then upload back into your anonymous SharePoint site that you've had to spin up. You can have it all happen in real time. You can give them a really good user experience. And honestly, if I can figure out how to do power pages in like one of these one hour tutorials that you do at Microsoft Learn, I think it's, you know, it's kind of reasonable that most people can figure this stuff out as well. Powered by Dataverse, which is a really great platform. If you have not heard of Dataverse before, it's what sits behind Dynamics. So, and it has all that security to manage service has all those built-in objects for you already that you might use for that common data model that they have inside of Dynamics and whatnot. And it's very scalable so you can start slow like you just, you know, crawling. You can go through that walk iteration and you can get up to the run state where we're, you know, where we were talking about column and row level security. It's quite a bit of stuff and then natural integrate integration into Power Automate, Power BI, Power Apps and all that other stuff. So I agree. Power pages might be a better tool. Perfect use case. I was just working on a migration between two different companies that one was acquired by the other. We had a SharePoint list listing all of the SharePoint sites, basically the checklist of over 6000 sites and what was happening with them. Were they being deprecated? Were they being absorbed into another site? You know, what was happening to them? And they wanted a copy of that on their site on both sides. So the old and the new. So I was using Microsoft Access because I have that skill to keep the three of those lists in sync because I can, I know how to do that. But not everybody knows how to do that. But how else would you do that? If you're like, we are only moving, you know, groups at a time, 150, 200th rate at a time. And then having to go update those lists with the new information. You know, so to have that one list and put it on a Power page and just say here, here's your, here's the gospel truth. And take out the middleman and, you know, me having to dust off those access skills with paste a pen and pay update queries. Yeah, that would have been beautiful. You're not in Christian, you know, I'm talking about, right? Access skills. So much fun. Christian's like, I don't know what words you just said. I used to build quite a bit. Sure. And I've had these conversations. I used to use access quite a bit. I was trying to help you likewise. It's one of those things where back trying to remember what I it was shortly after I was back in the Unix days and the Unix training courses that I actually went to access training. I made for that for me to do. I will nine hours of video on access in 2019. Nine hours of video clips. It's still very relevant. It's huge. What's that? It's still very relevant for people. It is. Yeah. And if you understand sequel, it's not a big jump data versus in a big jump if you have a skill set either so it's, it's didn't die. It hasn't died. Well, I guess access and Excel are like the original low code, no code in the office 365. True. Very true. I'd say, well, I put on Microsoft tech, I'd say access Excel and Lotus notes are the original low code, no code. I did Lotus. True. Yep. Just saying. I ran away from Lotus. Haters going to hate the state state was using it on a project. I'm like, I have no idea what this is. Original collaboration software. All right. Yeah, that's that's one of the reasons why Lotus notes was so, so difficult to, to back out of because there are so many little database based applications people would build tools little automations they go do on their own. And then they were just tied to it. They just couldn't get away and there was no migration path. In fact, when I was in MMS or the precursor to BPOS, we I was in months of meetings where we were looking at whether using access and access services would be a viable route to try and figure out a way to a path to migrate away from Lotus notes solutions. Access services was horrid. The answer was that it was not. Fair.