 Teresa asked a great question and this is one I know we're going to have a heartfelt discussion around. What should organizations do to prepare for the new version of Outlook? Tell us how you really feel. I have thoughts on this. So in Outlook if you had a file and go down to the bottom there's a thing that says feedback. And if you click the feedback button then you can send a frowny face or you could suggest a feature. And in either of those locations you could type about how you feel about preparing about the new version of Outlook. That's my feedback. Yes. And it starts with the frowny face? Is that the default option? Is the frowny face default? Okay, so my opinion on this and having worked with the end users on it. If it is in the consumer space, the simplification of Outlook where it looks a little bit more of a ramped up mail, the mail app that you would actually have on a consumer side of things. So it's kind of ramped up a little from the mail app. And that app that's sort of very similar to the online version, we saw that sort of marrying up of trying to bring the two together so you had one app, one world. And look Microsoft did this with OneNote. They created the app for OneNote but then they didn't get rid of the old version. And the enterprise side of things absolutely lost their nana. And eventually of course now what's happening, the two are becoming one and they're maintaining the more advanced versions of OneNote. And that was back in 2018 and the MVPs back then had a real connection around it. Now they're going the same way on the Outlook side of things where it's simplifying down and inside enterprise, the features that I'm actually seeing utilized are just not there. And so many of them are just not there in the new mail, you know, Outlook app. So I'm seeing the likes of executive assistants who need some of those more advanced functionality and it's just not there for them. And I know I've tried and I'm working on stuff and I can't even teach some of the things that I used to be able to teach that are functionality that are needed for more advanced mail work. That is just not there. I have actually had to turn it off. And you know what's the first time ever that I have said that, that I've had to revert back to an old version. I have never done that on any of the technology, but it's become a nightmare for me to be able to help enterprise. So personally, I am not a lover, which is sad. So we're saying to prepare that people need to look at the new Outlook first and decide, but don't get rid of your Outlook. Don't jump ship. Make sure you trial it out first. Make sure it fits your needs. The nice thing about that is at least for the most time being you can run both clients at the same time. You throw the switch in the desktop version, get the new one to come down, go back into your desktop and bring the switch back off. Then both clients are there. You can AB them. You can play with whatever features are available and you will find many, many, many features that the desktop client has that the new Outlook pre does not. They're just not there yet. And many of them are just absolutely business, business critical. There's no common objects, no offline files, no PSD files, just no custom fonts, no. Oh, the list is in there. It goes on and on and on and on. And it makes a great thing for me being in the answers for him. Hey, it isn't doing this. And all I have to say is no, it doesn't do that yet. Okay. And the thing is, there are, I have, I have. In your in the magic column, Christian, I put a couple of links to, there are two pages that Microsoft maintains that pretty much they update with the new features and the new things that they've added on an ongoing basis. So people basically just need to look at those two pages to see whether or not the feature that they want that is missing has been addressed yet. Yeah, well, there I was by no means ready for prime time yet. There, there are some blog posts that are out there. There's I like I pulled one up. So Rudy men's who's the his his site, the lazy admin, he has a comparison, what you need to know kind of goes through each of the features and compares them. So there there is some guidance out there if you're wondering, like I made the comment before we started like how about a year and a half two years ago. I had problems I had a, I had a hacker incident, and it something got derailed and got screwed up in my account, and I the desktop version just stopped working. And in fact, Hal and I tried to figure out going through problems and I, I had just started using the browser version created a PWA just have a pin to the desktop. I was frustrated that there were several features that were missing from that experience. I don't remember what my complaints were. I've now it's, I've been using it for so long. I'm happy with it. It does just about everything that I need it to do. And so it was, it was tough for a couple months. Honestly, now here a year and a half, two years later, I don't remember what those things were that I felt were missing because I'm able to get everything done. So, you know, part of it is, and I jokingly say, you know, before we were recording, like, Oh, just lower your expectations, you know. Come on, there's so much that you can accomplish, accomplish in the world if you just lower your expectations. I can't do anything. I can run and win a race against five year olds, but I can win a race. Well, we would have, we would stick with the one night app if we'd lowered out expectations. So that's kind of what I'm hoping for personally is that they, they come to their senses and realize that I mean, you just well, they perhaps can replace all the functionality in the desktop client with a web client, but they certainly are not going to do it in the timeframe that they're suggesting a year or two. It's going to be considerably longer than that. Too many business critical features and functionality, something like that template templates to get used by an awful lot by, you know, executives, assistants and things like that. Taking away those sorts of functionality means you're not going to get them off the desktop client. They will hold on that to dear life until the new version and potentially has some of those core features. Can I ask, as I don't know if anybody knows, but what was the behind this complete rebuild and removing all the features? Like what's going on? Is it just a complete rearchitecture? Is that why? Are they just changing it fundamentally and so that they're having to recreate the entire product? I mean, if you think about modern technology in general, so when they started to reduce SharePoint for SharePoint online, this is one of the things I talked about for a while. Is that with the modern architecture and we think about cloud first and we think about any mobile device and, you know, any product, any platform, any solution, right? So like I want to be able to connect to anything in the cloud and I don't want to have to limit it to a specific device. You have to eliminate all downloadable, all executables if you want to achieve that goal. So from an architecture perspective, I'm not going to speak for Microsoft specifically, but from an architecture perspective for a cloud first world, for a modern first world, you have to eliminate anything that you would actually have as a downloadable, which means that you would have to have everything be app generated with all of the data living in the cloud. So that's the thing I'm thinking of when they do things like this is that it's on a path to get us to where basically you don't have to download anything anymore and everything is stored in the cloud. There needs to be a cloud then. Yeah. That's one of the big problems right now. You go ahead. No, sorry, how do you keep? Oh, that was just. Yeah, yeah. I'm just saying that connectivity with all the new with the AI, you know, with co-pilot and all that other stuff and how it all connects to potentially that bringing it into mail into teams and as an app and how it all, you know, that move over to, as you said, the latest tech, they're the sorts of things that you kind of go, I understand it, but when it comes to the business critical, they don't. They're not going to take on a lot of those sorts of things when they're quite secure gov environments not going to go that way anyway. So, yeah, beautiful. What does it look like? And then my point was data data maintenance. That's the problem. You've got a cloud. It's a fixed size. Just a personal thing here. I've got the offer the office 365 family subscription, which means I get I get a tool what I think it's the better part of a terabyte of data. But I only get a 50 gig mailbox. And those who get who are in the E3 and E5 worlds, they only get 100 gig mailbox. And that's I subscribe to a good many of the MVP distribution lists. I keep all of that. I keep all of that data. It goes back years. Why? Because people don't immediately upgrade to new stuff. They a lot of people got really old stuff that they got it. They broke. Why do I need to fix it or replace it? I have got data that will help them fix it. If it if there's a problem that data no longer exists in Microsoft's world. So I need some means of keeping that data offline. That's a PST file. You can also there's no such a thing in in the world that you're describing Sharon. That doesn't exist. Well, so so then we start thinking about different options. And this is where I do train some of my users that if they don't want to do PST files, you can actually send your emails directly to one note. And then you can save them in one note as an email architecture. And you can actually resend that email out as an email. So if you didn't know that, like that is a way to archive your emails in a functional way where you can still use them and respond to them and send them back out if you need to. But get them out of your inbox so that you can reduce clutter. So I think when you think about the modern architecture, there are new ways of doing things. So hopefully, even though maybe you're not, you don't have the features that you used to have, you can do it in a different way in the modern architecture. It's just a matter of knowing how to do some of those things. That being the case, then they need to publicize that a good deal more because. Yeah. There's a whole lot of friends if they don't. And I mean, that goes back to part of what Jonathan was saying too. I mean, if the stuff has got to be discoverable. You know, I mean, you don't know how long it's somebody may want to have a legal thing that they want. And it's got to be discoverable and available. So there you have it. You got to put it somewhere and you do have to keep it. Yes. Well, you know, and I don't disagree with you there. How I mean, I'm working with a client that's to know their office 2016. They still got even versions of office right back to 1997. They're some of their old tech. They're still on Skype. Not off. And they're they're slowly moving off and it's and starting with just minimal viable product on teams, which is just purely calling called me chat sort of thing. So, you know, the maintaining of information, they still got on premise SharePoint and multiple on premise SharePoints of old. So their migration path for their 22,000 employees is it's going to be painful. So, you know, when you look at all of that and keeping that information and the PSTs and that that go back forever are going to be a challenge in some of the new world. Well, this kind of goes back to the core question that Teresa posted, which is what what should organizations do to prepare for this change. And so one is how this is you identified being figure out your storage path for that historic data. Maybe have some better knowledge management processes in place than storing all of your past information in email inboxes to when we think about collaboration and we think about content. We think about, you know, tasks and knowledge and things like that. And, you know, are there better ways to take that information and get it into a group place where you can search that information where it's not maybe living in a mailbox. But I do. Yeah, I do think it's, you know, looking at the new tool and seeing if there's tool if there's features that are missing that maybe you use on a regular basis. Look and see if there's a way to get around that in a different way so that when you get to the other side you don't feel like you're missing it so much. And do an impact risk assessment on features that are just, you know, what are the things that are the difference between the two applications. And it depends on the organization. If it was one person, you know, who was just at home, you're probably not going to miss it. But if you're a large organization, then I would actually go, what is it feature parity and what does that look like? What is the loss and then go out to the business and then do some workshopping and look at, you know, what's that impact on the business and what's the risk around it. If you do lose that and what are alternatives around it, because there might be an alternative that you might be able to do use or plugins or don't know what that looks like moving forward. But that's going to be a really important part of that change process. In other words, you're going to have a lot of people really upset across potentially across your organization. If you haven't prepared them for what it looks like. And in all seriousness for all Microsoft applications, there's a feedback component in every Microsoft application. And often people don't realize it's there. And anyway, we kind of joke about this, but on all honesty, respond to that feedback, like click on the feedback and tell people what you're missing, what you want, because the product teams really do see that. And they use that to build their backlog so they know what to make next. And then also you can always go to feedbackportal.microsoft.com and go to the individual application and participate in the conversations. Like how I was mentioning, you can go to tech community or you can go to feedback portal and post that information. And it really does help because then they know what that business critical feature is so that they can prioritize it. Well put.