How to turn off Microsoft Bookings or limit who creates pages

• The whole tenant. In the admin center, go to Settings → Org settings → Bookings and clear Allow your organization to use Bookings. The PowerShell equivalent is Set-OrganizationConfig -BookingsEnabled $false.
• Individual users. Untick Microsoft Bookings in each user's licence apps.
• Only new shared pages. An Outlook on the web (OWA) mailbox policy with BookingsMailboxCreationEnabled:$false stops page creation while people can still work as staff.

Bookings with me has its own switch, PersonalBookingsDisabled. Microsoft says tenant setting changes can take up to four hours to apply.

Option 1: turn off shared Bookings for everyone#

1. Sign in to the Microsoft 365 admin center. Microsoft's instructions say to sign in as a global admin.
2. Go to Settings → Org settings and open the Bookings entry. Microsoft's on/off article calls it "Shared Bookings".
3. Clear Allow your organization to use Bookings, then select Save changes.

Or in Exchange Online PowerShell:

Set-OrganizationConfig -BookingsEnabled $false

Microsoft's note: turning it off "will disable all access to the service including creation and management of Bookings pages". Plan for pages that are already published before you flip it.

Option 2: turn it off for particular people#

1. In the admin center, go to Users → Active users.
2. Select the user, then Licenses and apps.
3. Expand Apps and clear Microsoft Bookings.

This removes that person's own access to Bookings. They can still be booked as staff, because staff can be added by any email address.

Option 3: allow only some people to create shared pages#

This is the answer to the original forum question: shared pages named after individuals ("Ben's Booking Page") filling up the address list. Each shared page creates a mailbox and an unlicensed directory user. Private (personal) Bookings doesn't.

# 1. Policy for people who may create shared pages (creation is allowed by default)
New-OwaMailboxPolicy -Name "BookingsCreators"

# 2. Assign it to each allowed creator
Set-CASMailbox -Identity someCreator@contoso.com -OwaMailboxPolicy "BookingsCreators"

# 3. Block creation for everyone else on the default policy
Set-OwaMailboxPolicy "OwaMailboxPolicy-Default" -BookingsMailboxCreationEnabled:$false

Microsoft's steps assume you have no other OWA mailbox policies. If you do, set BookingsMailboxCreationEnabled on each of them. People outside the policy get an error when they try to create a page, but they can still be added as staff in any role, including Administrator.

Bookings with me (personal pages)#

Personal pages use a different control. Microsoft retired the old Exchange Web Services (EWS) settings on August 5, 2026 (Message Center MC1418559). Now only the OWA mailbox policy controls personal pages:

# Turn off Bookings with me for everyone on the default policy
Set-OwaMailboxPolicy -Identity "OwaMailboxPolicy-Default" -PersonalBookingsDisabled $true

To turn it off for some people only, create a separate policy with New-OwaMailboxPolicy, set the parameter on it, and assign it with Set-CASMailbox. For how the two page types differ, see Shared Bookings vs Bookings with me.

Clean up pages that already exist#

None of these switches removes existing booking mailboxes. To find and remove old ones:

1. List them with Get-EXOMailbox -RecipientTypeDetails SchedulingMailbox.
2. Get access to any you can't open. See how admins open every Bookings calendar.
3. Export and delete the ones you don't need.

Microsoft doesn't document hiding booking mailboxes from the global address list. Community reports say hiding them can make the pages harder for admins to find.

Middle ground: restrict instead of switch off#

If the concern is exposure rather than the app itself, the same Settings → Org settings → Bookings page has granular controls:

• Block shared bookings from outside your organization
• Block social sharing options
• Block sharing staff details with customers
• Require staff approvals before sharing free/busy information
• Disable direct search engine indexing
• Enforce a naming policy for page aliases
• Restrict collection of customer data

These controls aren't available in Microsoft 365 operated by 21Vianet. For the external-booking setting in particular, see why a booking page makes people sign in.