 Josh says, hi, all. I am struggling with an issue and hoping you can help. I have a domain, contoso.com, so original there. I think somebody owns that already. I think so. Where Microsoft Teams is being utilized and I am trying to invite external users to the team. I add them as a member and the user receives the email stating they have been added. However, the team does not show up in the external users team list. Am I missing a setting? Tried it with three separate users. I relate to this. I was trying to do this. I was trying to do this just yesterday, trying to fix my son's tenant. So yes, I'm sitting here with bated breath. It's one of my favorite because we just naturally think, oh, I can just put in an email address and invite someone. There are some administrative controls that have to be enabled, kind of switches and toggles that need to allow your external capabilities. We call that federation. So when I think of what you're trying to accomplish, there's a couple or a few different flavors that are inside of Microsoft 365 and Teams. One of them is just really simple. You wanna chat with someone. I always say allow this. You allow this in the Teams admin center. You enable federation or external chat. What that allows is simply the ability for you to communicate to anyone. You're opening a door up to everyone. I see that very similar to email. You allow everyone in your company to email out anyone they want to do the same thing with enabling the federation. So that's one. It could be blocked. The second way is if you wanna collaborate on files, then leverage what we call Azure B2B or guest access. That brings in not only just chat, but also now you can collaborate on files. The person has to change their tenant, come into your environment for you to do that collaboration. And then the third and final way, I think we talked a little bit about earlier, but that's shared channels. Another administrative control that's using cross-tenant access settings so you can enable the capability to either have a one-way communication or a two-way communication between two organizations. So those are the three ways. So I'm guessing here, Josh, that you might be getting tripped up a little bit by how to do the invitation, because you first have to allow it in order for you to be able to do any inviting of anyone into your environment. Yes, if somebody, that has not been set up from an administrative side of things. If that's the case, there's no error being thrown for Josh. He's not seeing that. Just he sends the invite, they see it, and then it's just, it's not showing up properly. Right. And I know you can add a person in there. It just won't do anything. So there's a few administrative settings, the Teams admin center, and as well as the Azure area. Those two areas control that capability and even allowing you to send an invite if you're leveraging B2B. But I would work with your admin or if you are the admin, go over there. Take a look at your federation settings. You might have it completely turned off, so therefore no one can come in and do any chatting with you. Yes, that'd be the first place. If you're not the admin, talk to your admin. Make sure that's enabled. Make sure there's a whole separate conversation of what that means. Organization has that turned off, thinking, hey, we're gonna make our system more secure. The downside is that what happens is people say, okay, well, I'll go use Google Docs or I'll send it to them in Facebook Messenger. So a much less secure way of collaborating happens when you just say no. But maybe hopefully for Josh, it's just an oversight and it was turned off and the admin corrects that. Yes.