Shared Bookings pages should be creatable only by selected users
This check looks at who in your organization is allowed to create shared Bookings pages in Microsoft Bookings. The safe setting is that only a chosen group of users can create them, rather than every licensed user.
Why it matters
A shared Bookings page publishes a calendar that outsiders can use to book time with your staff. Each page can expose staff names, services and availability to anyone with the link. If every licensed user can create these pages, nobody in IT knows what is published or who is listed on it.
Microsoft Learn describes a policy approach that limits creation to the users you name. Users who are not in the policy get an error when they try to create a page. See the source below.
How to check it yourself
In the Microsoft 365 admin center go to Settings → Org settings → Shared Bookings to see whether Bookings is on for the organization. The creation limit itself lives in Exchange Online, so connect to Exchange Online PowerShell with a read-only account and run these read-only commands:
Get-OrganizationConfig | Select-Object BookingsEnabled
Get-OwaMailboxPolicy | Select-Object Name, BookingsMailboxCreationEnabledIf the default policy (OwaMailboxPolicy-Default) shows BookingsMailboxCreationEnabled as True, everyone with that policy can create shared pages.
How to fix it
Microsoft's steps use Exchange Online PowerShell. Create a policy for the approved creators, assign it to each of them, then switch creation off in the default policy. Replace the address with a real user:
New-OwaMailboxPolicy -Name "BookingsCreators"
Set-CASMailbox -Identity creator@yourdomain.example -OwaMailboxPolicy "BookingsCreators"
Set-OwaMailboxPolicy "OwaMailboxPolicy-Default" -BookingsMailboxCreationEnabled:$falseMicrosoft notes that these steps assume no other Outlook on the web mailbox policies exist in the organization, so list your policies first. You run these commands yourself. ConfigCobra never changes your tenant; it reports the finding and suggests the fix.
What changes when you fix it
Users who are not in the approved group can no longer create new shared Bookings pages and see an error message if they try. Pages that already exist keep working, and approved creators can still add anyone as staff on a page.
Before you switch the default policy, ask which teams already publish booking pages, such as support desks, sales or HR, and add them to the approved group. Agree how someone requests permission, so a legitimate need does not turn into a stream of help-desk tickets.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft 365 Foundations v7.0.0 | 1.3.9 | E3 Level 1 |
More checks in Microsoft 365 admin center
- The password expiration policy should be set to never expireCIS 1.3.1
- Idle session timeout for unmanaged devices should be three hours or lessCIS 1.3.2
- External calendar sharing should be turned offCIS 1.3.3
- User-owned apps and services should be restrictedCIS 1.3.4
- Internal phishing protection for Microsoft Forms should be enabledCIS 1.3.5
Go further
- Microsoft 365 admin center15 controls in this section
- CIS Microsoft 365 Foundations v7.0.0160 controls
- CIS Microsoft 365 Foundations checklistEvery control in one list, as CSV
- RemediationSee what a fix changes in your tenant before you apply it, then use the generated script
- Monitoring & DriftScheduled scans, drift detection and email alerts when a control regresses
Check this on your Microsoft 365
ConfigCobra runs this check with every other control of the CIS Microsoft 365 Foundations Benchmark, read-only.