 AJ asks a great question here that we've heard a lot. Doesn't creating a team in Teams create an Office 365 group? If so, why can't I find it in Outlook? Yeah. Microsoft and their infinite wisdom, when they first created Teams, they tied the two together. Then by default, it was added to Outlook. Then they decided halfway through, that we're going to not actually attach the two anymore because people are getting confused because all the groups were in their Outlook. Now, yes, it can. The problem is it has to be PowerShell scripted back in. I wish it was a checkbox. Would you like this when you create those, can we make this- Or add men control to go and do it, right? Yeah. But no, it has to be a PowerShell script. Thank you so much because not everybody has that ability. Then now you got to involve IT and they have to go run the script. I don't know. Go ahead. Why do you care? Why do I care? What about that? Why do you care if you have the group associated with the team? Because that's the foundation of everything, right? That's how you know the members, the permissions, all of that is involved with the group. You have the invisibility. Well, that's my point is that depending on what you're trying to do, I mean my question to AJ is like, well, what are you trying to accomplish by having that association? What are you doing with the group? Why wouldn't you just use teams the way with the out-of-the-box features and do everything there? I guess this is where it would be great if we could ask AJ a follow-up question is, what are you trying to accomplish that you're not able to do without having that show up in Outlook? My guess is that he's trying to use the inbox to be able to monitor the inbox locally in his Outlook. That would be my guess. Also the calendar, being able to see that more easily, instead of having to go out and browse to it, seeing the group calendar that's associated with it too. Though that would be my two guesses. But I like all my groups in my teams and I have to, and now what I do instead of creating a team, I create the Office 365 group in Outlook and then I teamify it. So I create the team from the group. That way, I get that in Outlook. So that's my little work around. That's a link we should provide to this as well, is that scenario. Okay. I can get those two links for you. Those script to fix it if you already have one, and my Sherry's hack. The teamify. Yeah. Maybe I'll do a video. That's something Mark Cashman talked about a lot back in the day when that was a new feature. Just to help you out, Sherry. If you have some folks that don't, want to touch PowerShell and they want to do that, hey, I'll do it for free. Just hit me up. I take cash, credit, whatever. I'm still a scaredy cat. I'm a scared PowerShell scared cat. I don't think there's anything wrong with that. I feel like it's one of the- Having that PowerShell fear, there's nothing wrong with that. No, having fear of PowerShell, I think that's normal because it's that barrier I think that people have to respect when it comes to Microsoft Teams and administration. Lots of barriers are brought down to make it simple, but the moment you want to start flipping the dials and the switches, you're not going to find a very fancy front-end. It's back to PowerShell that's usually reserved for a certain level of access in an organization, and hopefully a level of knowledge to go with that security. It's one of those things with Teams. It seems easier to use than really it is. It's a complicated thing, and it needs to be respected as such. There's no undo button if you mess it up. Again, I know I could bring this up, but that's another space where third-party tools, a lot of the admin and governance tools provide a lot of guidance is because it's, again, it's permissions-based. You have to have the right level and understanding of what you're doing so you don't go in and break things, but to put it to a UI and to automate a lot of those capabilities that you would otherwise have to go and do PowerShell. Sometimes you just can't get away from using PowerShell. Microsoft has not opened up the APIs to certain things or what have you. Sometimes it's just the quickest, easiest way to get what you want as an admin is PowerShell, but there are other tools out there to automate a lot of these capabilities as well.