'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Restrict Exchange Room Booking to a Specific Domain
Question details
The user needs to restrict an Exchange room-booking policy to accept meeting requests only from users within a specific email domain.
- Product
- Microsoft Exchange Online
- Device & OS
- not provided
- Scenario
- Configuring room booking limitations using the Set-CalendarProcessing cmdlet in Exchange PowerShell.
- Observed behavior
- Attempting to use a wildcard domain (such as *@domain.com) in the RequestInPolicy or BookInPolicy parameters fails to apply, as wildcards are not supported for this calendar processing configuration.
Ensure you are connected to Exchange Online via PowerShell with Exchange Administrator privileges, and that the target room mailbox is already created.
Use a Mail-Enabled Distribution Group Instead of Wildcards
Since the Set-CalendarProcessing cmdlet does not accept wildcard domains, the standard workaround is to place all users from the specific domain into a distribution group and apply the policy to that group.
Microsoft Exchange Online requires specific object identities (such as a User Mailbox, Mail User, or Mail-Enabled Group) for calendar processing parameters like BookInPolicy and RequestInPolicy. Wildcard domains are invalid syntax for these fields.
To achieve a domain-level restriction, administrators must funnel the target users into a supported group. Note that Dynamic Distribution Groups are not supported for this specific calendar processing restriction.
Log in to the Exchange Admin Center and create a standard Mail-Enabled Distribution Group or Security Group. Add all users from the specific domain as members of this group.
Open PowerShell as an administrator and run 'Connect-ExchangeOnline' to authenticate with your administrator credentials.
Run the command: Set-CalendarProcessing -Identity "RoomName" -AllBookInPolicy $false -AllRequestInPolicy $false -BookInPolicy "YourDistributionGroup@domain.com" to restrict automatic booking to that group.
Execute Get-CalendarProcessing -Identity "RoomName" | Format-List to ensure the BookInPolicy and RequestInPolicy fields reflect your distribution group.
Consult the Microsoft Q&A Community for Complex Scenarios
If you have a complex hybrid Exchange environment or need advanced custom routing rules, specialized Microsoft experts can provide exact syntax.
Manage Your Documentation Effectively with WPS Office
While Microsoft Exchange handles complex backend room booking policies and server scripts, you need a reliable tool for your daily desktop tasks. WPS Office is a highly compatible, free alternative to Microsoft Office that makes documenting PowerShell scripts, drafting IT policies, and analyzing data effortless.
- 1. Download the Installer: Visit the official WPS Office website and click the free download button.
- 2. Install WPS Office: Run the downloaded executable file and follow the standard installation prompts.
- 3. Start Creating: Open WPS Office to instantly view and edit your existing Microsoft Office documents without formatting loss.
Frequently Asked Questions
Why doesn't Exchange allow wildcards in Set-CalendarProcessing?
Exchange requires specific Active Directory object identities (like mailboxes or mail-enabled groups) to resolve permissions. A wildcard domain string does not correspond to an authenticable AD object, causing the validation to fail.
Can I use a Dynamic Distribution Group for BookInPolicy?
No. Exchange Online does not support Dynamic Distribution Groups for calendar processing policies like BookInPolicy or RequestInPolicy. You must use a static Mail-Enabled Distribution Group or a Mail-Enabled Security Group.
What is the difference between BookInPolicy and RequestInPolicy?
Users defined in BookInPolicy can automatically book the room if it is available. Users in RequestInPolicy can only submit a booking request; a configured resource delegate must manually approve or decline the meeting.
