Why does my Microsoft Bookings page make people sign in?

• The page setting Require a Microsoft 365 account from my organization to book is ticked.
• An admin has forced sign-in for every page, with the tenant setting Block shared bookings from outside your organization or BookingsAuthEnabled.

Untick the page setting, and if the prompt stays, ask your admin to check the tenant settings. If your link is a Bookings with me link, the "Sign in / Continue as guest" screen and the email code are part of that product. See turning off Bookings with me verification.

First, check which kind of link you shared#

The rest of this page is about shared booking pages.

Let anyone book (shared page)#

1. Open Bookings, choose the page under Shared booking pages, and select Booking page.
2. Under booking page access control, clear Require a Microsoft 365 account from my organization to book. The FAQ words it as "Require a Microsoft 365 or Office 365 account from my organization to book".
3. Save, then test the link in a private browser window while signed out.

If the sign-in prompt is still there, a tenant setting is overriding the page. An admin should check:

• Admin center: go to Settings → Org settings → Bookings and clear Block shared bookings from outside your organization. Microsoft describes this setting as restricting "bookings to only authenticated users within your organization".
• PowerShell: run Get-OrganizationConfig and look at BookingsAuthEnabled. When it's $true, "all new and existing Bookings pages are forced to authenticate users before they can book".

Get-OrganizationConfig | Format-List Bookings*
Set-OrganizationConfig -BookingsAuthEnabled $false

Microsoft says tenant setting changes can take up to four hours to apply.

Why clients think they need an Outlook email#

When a page is organization-only, outside visitors see a Microsoft sign-in screen, and many assume they need an Outlook or Microsoft account. They don't. A public shared page takes any email address, with no account at all. Once the organization-only settings are off, clients can book with Gmail or any other address.

Block outside bookings on purpose#

For internal services such as IT help desks, HR sessions or room sign-ups, do the reverse:

• One page: tick Require a Microsoft 365 account from my organization to book. Visitors authenticate with Microsoft Entra ID, and only accounts in your tenant can view or book.
• Every page: turn on Block shared bookings from outside your organization, or set BookingsAuthEnabled $true. Page owners can't override it.
• Keep it out of search: also tick Disable direct search engine indexing of booking page.

Email verification on shared pages#

Separately from sign-in, the Microsoft Graph (beta) booking page settings include enforceOneTimePassword, which "determines if the one-time password is required to create an appointment". It's off by default. Microsoft's admin docs don't name the matching option in the web app. If external customers report being asked for an emailed code on a shared page, check the page's settings for an email verification option. The spam bookings answer covers when you might want it on.

Bookings with me can't be restricted the same way#

Admins can't limit Bookings with me to internal users. A Feedback Portal idea points out that shared pages can be restricted and personal pages can't. The only admin control for personal pages is turning them off with PersonalBookingsDisabled; see turning off Bookings for users. If external clients are stuck at the guest screen, a shared booking page with a single staff member avoids it. Shared Bookings vs Bookings with me compares the two.