Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs
Based on my review of the current Microsoft Graph documentation, I have not found a supported way to configure webinar lobby settings through the Virtual Events APIs. I observed the same behavior you described, the Create virtualEventWebinar API appears to support only properties such as audience, coOrganizers, description, displayName, startDateTime, endDateTime, isRegistrationRequired, and settings. Neither lobbyBypassSettings nor allowedPresenters are exposed as writable properties during webinar creation.
Additionally, while
virtualEventSession inherits from onlineMeetingBase, the currently documented operations for webinar sessions appear to be limited to Get and List. I could not find any documented POST, PATCH, or other update operations for virtualEventSession. This would be consistent with the 404 Not Found responses you are seeing when attempting to update session properties.
Reference: virtualEventSession resource type - Microsoft Graph v1.0 | Microsoft Learn
It currently appears that webinar lobby configuration can only be managed through Teams meeting policies, such as those configured via Teams PowerShell or the Teams Admin Center, as you mentioned. I was unable to find a Microsoft Graph API equivalent that allows this behavior to be configured programmatically for webinars. Based on the current documentation, webinar-specific lobby settings do not appear to be exposed through the Virtual Events APIs.
Please note that this summary is based on my own findings and may not fully address your concerns. To help you reach your goal more effectively, I recommend engaging with [GitHub Community Forum] for a deeper technical dive or to connect with individuals who have relevant experience and expertise. Some approaches may behave differently or be restricted depending on your specific environment and configuration. These forums include many experienced developers and Microsoft specialists who can assist with troubleshooting and guidance.
As a community member, I do not have access to Microsoft internal tools, engineering resources, or undocumented product information, and I cannot definitively confirm whether this behavior is an API limitation on Microsoft's side. Therefore, my guidance is based solely on the publicly available Microsoft documentation and resources. That said, I'll do my best to provide any additional insight or clarification that may help.
If you have any additional concerns, feel free to comment below. I would be more than happy to assist.