 Renith asked, any idea on the resolution of the following error in Teams? It's happening in random users in the tenant. Research nothing found helpful till now, error messages. Sorry, your company policy prevents you from joining this call. Note, the affected users can join the meeting previously without any errors. Same error in all versions like web and mobile. So they're previously able to join a meeting. Now they're getting the, sorry, your company policy prevents you from joining this call. They got a new admin. He's been playing with the policies for Teams. It's clear there. Yeah, it's clear somebody has enacted a new policy of some sort that's keeping them from being able to join. So they need to reach out to their administrator and find out why. Those kinds of errors. This is just random. Well, right, because my first thought was exactly that was that. So where I had to like, what is this unexplained error? It's impacting across a number of things. I could do things locally. What's changed here? And it's because somebody in the admin went and said, oh, these users, they don't need this license type. We can put them under this license type. So they changed that and it cut off all the backend services, all the rest of the things that drive your work. So that would be the place I would start as well, is go and look at the licenses for the individuals and see if somebody has made a change. Well, and sometimes things that appear random to an end user are not random if you look at it from the admin perspective. So it might be a specific group. Maybe it's contractors and you don't realize who the contractors are. Maybe it's people in a certain department or, you know, especially in the larger the organization gets, the more kind of goofy those AD groups can get. Maybe they create a new policy to test it and they put it a test group in there. And there was people still in the test group that are random. And so it appears random, but when you look on the backend and the administration center against the policy, you find that it truly isn't random. Well, I'm wondering, this is kind of the on and off, you know, turn it on, turn it off again. Maybe kick them out of the meeting. Somebody who's in charge of that meeting remove those people and add them back in and the new policies would apply if those policies changed. So again, not having to go to the admin to try and fix it, can we try and fix it ourselves? We're, you know, taking them out, putting them back in might fix that, let them join as their new profile, whatever. And that might identify the error of, it'd be another error that would say why they can't join the meeting. You can't do this because XYZ. When you ask the admin and the admin says, I didn't change anything. Ask the follow-up question of what new features have we enacted? Or, you know, in addition to the licensing, you know, there was a change to the, what, telephony licensing or the telephony capabilities not too long ago, is that when it started having errors? That it's only changing the license itself around the feature set that may have impacted to Christian's point, specific license holders or even if they didn't change the license, it's perhaps that that feature changed for that license set and they just didn't realize it. In this case, it's pretty clear because it says that it's a policy, but it could be, it could be a feature set. Well, and remember these tools, these tools evolve all the time. Microsoft changes things in the background and they can affect the setting. So like external access, that's something, are these people external users or internal users? And maybe their external access policy as it evolved and Microsoft has changed it, has now changed something for how they actually joined that meeting.