starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 16:26:09 +03:00

[GH-ISSUE #4960] [Feature Request]: Add "Who can bypass the lobby" in Global Meeting policy for Teams Standard. #2342

New issue

Closed

opened 2026-03-02 13:51:32 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 13:51:32 +03:00

Owner

Originally created by @cartier-info on GitHub (Nov 17, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4960

Originally assigned to: @kris6673 on GitHub.

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

Hi, Would it be possible to add "Who can bypass the Lobby" settings?
Currently the Standard set this setting to "People in my org", we like it to "People who were invited".
Having a choice between all possible options would be nice..

Thank you

Benefits for MSPs

It would reduce manual work.
Improve security by better managing teams security options
It would be more efficients, I had to search what was changing this teams meetings settings, it is not written on the Cipp Standard that it affect this settings.

Value or Importance

It's an optionnal feature but should at least be corrected as it change a settings that is not describe on the Standard.

PowerShell Commands (Optional)

No response

Originally created by @cartier-info on GitHub (Nov 17, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4960 Originally assigned to: @kris6673 on GitHub. ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement Hi, Would it be possible to add "Who can bypass the Lobby" settings? Currently the Standard set this setting to "People in my org", we like it to "People who were invited". Having a choice between all possible options would be nice.. Thank you <img width="1587" height="632" alt="Image" src="https://github.com/user-attachments/assets/077dd83f-4b51-41ec-b1fa-38f5a25b140d" /> ### Benefits for MSPs - It would reduce manual work. - Improve security by better managing teams security options - It would be more efficients, I had to search what was changing this teams meetings settings, it is not written on the Cipp Standard that it affect this settings. ### Value or Importance It's an optionnal feature but should at least be corrected as it change a settings that is not describe on the Standard. ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:51:32 +03:00

closed this issue
added the
enhancement

no-priority

not-assigned
labels

kerem commented

2026-03-02 13:51:33 +03:00

Author

Owner

@kris6673 commented on GitHub (Nov 17, 2025):

I would like to work on this please!

@kris6673 commented on GitHub (Nov 17, 2025): I would like to work on this please!

kerem commented

2026-03-02 13:51:33 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 17, 2025):

Great! I assigned you (@kris6673) to the issue. Have fun working on it!

@github-actions[bot] commented on GitHub (Nov 17, 2025): Great! I assigned you (@kris6673) to the issue. Have fun working on it!

kerem commented

2026-03-02 13:51:33 +03:00

Author

Owner

@KelvinTegelaar commented on GitHub (Nov 19, 2025):

Added to dev

@KelvinTegelaar commented on GitHub (Nov 19, 2025): Added to dev

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#2342

No description provided.

Rows
Columns