 Max says, is there a way to get email notifications when someone in a team has posted a message? I found only this notification in the team's client under Settings, you can activate this. Brings with me, but unfortunately, nothing. Can someone show a photo of how such a mail looks like? Could this be because we did not use Exchange or Outlook online? We still have an on-premise Exchange server, therefore no connection between emails between the cloud and local Exchange. We use only AAD for login. I'm going to defer to Sharon on that one. Yeah. So if you are only using AAD for login for online stuff and you have a separate AAD account and it sounds probably like they're just, they probably don't even have like maybe AAD Connect setup or anything like that. What you would have to do is you would have to leave it open in the web, enable notifications for your browser, and then if you enable notifications for your browser you will see the notifications. If you don't have Outlook online, that's going to get kind of messy. I do know like there's some Power Automate workflows. So like if you really want to be fancy, there are Power Automate workflows where you can go in the back and there's actually a prebuilt template where you can say, if there's a team's message, send me an email and if you do that, you can email it to yourself and it will notify you. I have a question. I have a question. I thought it was required that for teams to function, there has to be an exchange online, a cloud exchange. That there's the top secret double pinky behind the scenes, it creates even if you don't have it. But if what they're doing is maintaining their Active Directory on-prem, and they're only allowing them to log in for teams and they've got the exchange options shut down for them to access it online. What's happening is it's actually creating it, they just can't see it. I've seen organizations that have this that are in the process. A lot of them are usually in the process of migrating their exchange over, and so they don't want people in there while they're doing that and sometimes that can take six, eight, nine months to complete that project. So in the meantime, it's like you're flying blind, and so I have seen people, it's everything like I said, either stay in the browser with your notifications on where it ding, ding, ding, ding, ding all day, or set a workflow to any time I mentioned in Teams, email me like you can actually build some stuff on the background until they get it over there. But the other thing is push on your IT team and your exchange team to get that connected and enabled as soon as possible, because it definitely can drive a person crazy for sure. I've seen it. But with the earlier option, so with the browser notifications, but you have to have it open the entire time if you close it. You have to leave it open so you can leave the browser open. You can also leave your phone. So here's another handy trick hack is if you have the Teams app on your mobile device, your iPad, your phone, any mobile device that you want to put it on, you can actually leave it open on your mobile device and enable notifications, and then it'll actually at least notify you on your phone, and then you would know to go look on the browser. I've seen people do that as well. But yeah, you have to leave something open for it to happen that way. Well, and this goes back to a conversation we were having when we were in Minnesota this last week. People are like, oh, we want to move to OneDrive. We want to move to Teams. We want to do this. We'll do Exchange later. We'll do it to Exchange later. That's not how it works, right? Exchange makes it messy. Everybody talks about how, so well with Teams, it's SharePoint under the covers. No, it's SharePoint and Exchange under the covers. It's SharePoint for file management. It's Exchange for messaging and notifications. Then there's a lot of other little pieces here and there for different apps. But yeah, so Teams is just a browser interface basically. Yeah. Active Directory is the nerve center of everything. You can't do that later. You got to do that first. I used to say that people think that Exchange or Outlook is the primary consumer of Active Directory and that's not true. SharePoint was always the primary consumer of Active Directory. That was the first time people get AD health checks is their SharePoint stuff, it would pop up in their contact cards would be empty. They wouldn't be able to use the little people picker drop-downs and things like that would convince them to go do AD health checks. Well, Teams is even more, right? Like your people, that people stuff that's coming in from AD, if you want to see org charts, if you want to be able to have the little people picker card so that you can see who they are, who they're connected to, how to contact them. Yeah. Their presence. Presence becomes so crucially important with AD. Fix your AD people first. Yeah, Max. Integrate your apps. Get your own text. Put it all in exchange. Come on, guys. Just get on that. Yeah. Small project, people. Excellent, Max.