Creating an Online Meeting with a guest user account

Question

Creating an Online Meeting with a guest user account

Maria Pequeno Camarero 20

We created an Online Meeting using application authentication and configured a guest user as a presenter.

The guest user exists in the customer’s tenant and has an M365 license assigned.

The meeting is created successfully; however when the guest user joins the meeting, they are not recognized as a presenter and are required to wait in the lobby.

Could you please clarify why this behavior occurs? Are guest users supported as presenters when creating an Online Meeting using application authentication, or are there any additional requirements for the guest identity to be correctly resolved and assigned the presenter role?

0 comments

1 answer

Your answer

Answer 1

Alina Le 5,505 Independent Advisor

Hello Maria Pequeno Camarero

Guest users are supported in Teams meetings and can be assigned presenter permissions. However, the guest must be represented as a valid guest identity in the tenant and join using the same account that was configured for the meeting. If Teams cannot match the joining user to the specified guest identity, the participant may be treated as a regular external attendee instead.

In this scenario, I recommend validating the following:

1/ Confirm the user has been added to the tenant as a "Guest" user

In Microsoft Entra Admin Center, go to Users and verify that the user exists in the directory as a Guest account.
If the user is not present, add the user as a guest (B2B collaboration) and ensure the invitation is accepted.
Ask the user to sign in and join the meeting using the same guest account that was added to the tenant.

For your reference:

Quickstart: Add a guest user and send an invitation - Microsoft Entra External ID | Microsoft Learn

User's image

2/ Review the meeting lobby policy to confirm whether guest or external users are allowed to bypass the lobby.

Check the Meeting Policy

Open the Microsoft Teams Admin Center.
Click on "Show all" and navigate to: "Meetings" -> "Meeting policies"
Open the policy assigned to the meeting organizer (often Global (Org-wide default)).
Under Meeting join & lobby, verify the following settings: "Who can bypass the lobby" -> Set to: "Everyone"

User's image

These settings allow anonymous and external users to join and start meetings without requiring the organizer to join first

For your reference:

IT Admins - Manage lobby options in Microsoft Teams - Microsoft Teams | Microsoft Learn

3/ If the participant successfully joins the meeting but is not assigned the Presenter role, the organizer can manually change the participant's role to Presenter during the meeting.

This can be done from the participant list after the user has been admitted.

User's image

For your reference: Roles in Microsoft Teams meetings | Microsoft Support

Hope my information is helpful to you!

Maria Pequeno Camarero 20 Reputation points

2026-10-07T08:44:45.26+00:00

Hi @Alina Le ,

The user does exist in the tenant as a Guest account. The UPN contains the expected #EXT# format, and the email attribute contains the correct external email address.

Does the Who can bypass the lobby setting still need to be configured as Everyone for a guest user that already exists in the tenant?

My expectation was that, since the user is a valid guest identity in the tenant and has been explicitly assigned as a presenter when the meeting is created, they should be recognized accordingly without requiring the lobby policy to allow all external users to bypass it.

Could you please confirm whether this is expected behavior?
Thanks in advance.
Alina Le 5,505 Reputation points Independent Advisor

2026-10-07T09:09:36.05+00:00
Hi Maria,

Thank you for the clarification.

I agree with your expectation. Since the user already exists in the tenant as a valid Guest account and was explicitly assigned as a Presenter, I would also expect Microsoft Teams to recognize the participant accordingly.

However, the Guest identity, Presenter role, and lobby admission settings are separate meeting controls. - - --

Being added as a Guest determines who the user is

Being assigned as a Presenter determines what the user can do in the meeting.

The lobby policy is a separate control that determines whether participants can enter the meeting directly or must be admitted first.

In this case, you could test "Who can bypass the lobby" = "People in my org and guests" rather than Everyone, as this aligns more closely with your scenario.
Maria Pequeno Camarero 20 Reputation points

2026-10-08T08:45:00.76+00:00

Hi @Alina Le ,

Thank you for the clarification.

We have also tested with the lobby bypass setting configured as Everyone. With that setting, the guest can enter the meeting directly, but they are still not recognized as a Presenter.

I reviewed our request in more detail and noticed that we are currently sending allowedPresenters = 1, which in the SDK corresponds to organization.

We also explicitly include the guest user in the request as both organizer and attendee, but the role is currently set to OnlineMeetingRole.Producer (Role: 3).

This configuration works for internal users, but not for the guest user.

Could this be because allowedPresenters = organization only grants presenter permissions to users who are members of the organizer’s organization, while a B2B guest is not considered part of the organization for this setting?

If we want a specific guest user to be recognized as a Presenter, should we instead use allowedPresenters = roleIsPresenter and explicitly assign that guest OnlineMeetingRole.Presenter?

The guest exists in the organizer’s Entra tenant, and we reference it using the guest user object ID.
Alina Le 5,505 Reputation points Independent Advisor

2026-10-08T09:22:52.7+00:00

Good day Maria,

I’m so happy to hear that you were able to resolve the lobby issue.

Regarding the presenter role for the guest user, I noticed that you're currently using allowedPresenters = organization, which is documented as "Everyone in the organizer's organization is a presenter." Since the affected user is a B2B guest rather than a regular member account, this may explain why the presenter role is not being applied as expected.

As a next step, I suggest testing allowedPresenters = roleIsPresenter and explicitly assigning the guest user the OnlineMeetingRole.Presenter role. Based on the documentation, this option is designed to grant presenter permissions according to the participant's assigned role rather than their organizational membership.

onlineMeetingbase resource type - Microsoft Graph v1.0 | Microsoft Learn

_

If you find the information above helpful, please click "Yes" so the answer is highlighted in green, helping others with similar issues benefit from your case.