Microsoft Team

IBN 4,371

Hello

Please i need your help on this issue.

We have teams set-up to Automatically admit people that are People in my organization and guests, But when a Guests Joins they have to wait in the Lobby to be allowed in.

Due to the Way we use Teams we have a number of meetings that do not have the person that booked them joining the Meeting.

Before today this worked but now all Guests are having to sit in the Lobby

1 answer

Dillon Silzer 54,931 Reputation points

2022-09-28T16:01:59.783+00:00

Hi @IBN

Please verify at https://admin.teams.microsoft.com/policies/meetings that your policies have the following set:

Participants & guests > People in my organization and guests

-----------------------------

If this is helpful please accept answer.
Please sign in to rate this answer.
IBN 4,371 Reputation points

2022-09-28T16:41:41.097+00:00

Thank you for your email.

I have checked the policy is correct.

So we do admits everyone including guest to bypass the lobby.

Dillon Silzer 54,931 Reputation points

2022-09-28T17:24:47.747+00:00

Do you have multiple meeting policies? Which policy is this one set in?

JimmyYang-MSFT 50,026 Reputation points Microsoft Vendor

2022-09-29T09:51:29.593+00:00

Hi @IBN

Could you try to change the automatically admit people from "People in my organization and guests" to "Everyone"?

IBN 4,371 Reputation points

2022-09-30T16:04:48.413+00:00

I have set-up a new Meeting Policies Called Assessment Meeting Setting as below.

we are not able to change the Default Policy. This is due to the Way our domain works.

when I add this to myself there is no problem but When I try to add this new Meeting Policy to our test accounts, I get the below Error.
This is a shared mailbox.

JimmyYang-MSFT 50,026 Reputation points Microsoft Vendor

2022-10-06T09:48:13.567+00:00

Hi @IBN

Do you mean all user in you organization cannot assign this custom policy?

Have you tried to assign this policy via Teams PowerShell Module?

IBN 4,371 Reputation points

2022-10-07T17:17:14.623+00:00

Thank you for your reply.

The Problem we are seeing could this be linked to Service Health ID: TM439228 which started the same time as the Problem we are seeing?
Sign in to comment

Share via

Microsoft Team

1 answer