How do I turn off email verification on Bookings with me?

What bookers see#

Depending on the visitor, someone who opens your personal page may be asked to:

• Sign in or continue as guest. Visitors who aren't signed in to Microsoft 365 get a choice screen before the booking form.
• Verify their email. A one-time code is emailed, and the booking only completes once it has been entered.

Neither step needs a Microsoft account. The Personal Bookings FAQ says anyone can book on a Bookings with me page even without one. The extra steps still cost bookings, though: sales teams call the guest screen a barrier for prospects, educators report the same with students, and a 2026 thread describes mobile users leaving the page to fetch the code and timing out before they return.

What we saw when testing (September 2026)#

We captured the public booking pages and the calls they make, read how the page handles the code, and tried to book on a personal page and a shared page:

1. The first time the form is submitted, the booking is not created. Microsoft emails a 6-digit code to the address the customer typed, at that moment, and the page shows a code box.
2. The booking is created only when the same form is submitted again with the code.
3. "Resend code" is simply another submit, which triggers another email.
4. A wrong code is rejected and no booking is made.

Our personal test page asked for the code; our shared test page, on default settings, never did. So if a customer never receives the code, the booking doesn't exist: check their junk folder and the spelling of their address before assuming the page is broken.

Why there's no switch for personal pages#

The settings Microsoft documents for a personal meeting type are the name, color category, description, online or offline mode, duration, public or private tag, schedule, buffers and minimum and maximum lead time. Nothing covers authentication.

On the admin side, the only documented control for personal pages is on/off: PersonalBookingsDisabled in an OWA mailbox policy, for the whole organization or for specific users. Since August 5, 2026 (MC1418559), the older EWS-based settings no longer control Personal Bookings. The organization-level settings such as BookingsAuthEnabled and Block shared bookings from outside your organization apply to shared booking pages, and they add sign-in rather than remove it.

Shared pages do have a code setting. The shared Bookings documentation lists "enabling or disabling one-time passwords (OTP)" as a business setting that can take up to 10 minutes to apply, and a user in a Microsoft Q&A thread gives the checkbox name: on the shared page's Booking page settings, under access control, clear Require a one time password to create bookings. Microsoft doesn't document that label, so it may differ in your tenant. That box doesn't reach personal pages. In a 2023 thread, a Bookings with me user cleared it several times and the prompt stayed. A Feedback Portal idea asks for exactly this: "Allow personal bookings pages to disable one-time password email verification like shared bookings pages".

What people have tried#

• Asking Microsoft Support. In a 2026 Q&A thread, the asker says Microsoft Support confirmed OTP "can be disabled" in their environment. There's no public setting or procedure behind that for personal pages, so if you open a support case, treat it as a request with no guaranteed outcome.
• Filtering the stray "verify your email" messages. One thread involved verification emails addressed to placeholder contoso.com addresses. That was a bug, and Microsoft Support suggested an Exchange mail flow rule to delete the stray messages. It cleaned up the mailbox. It doesn't remove verification for real bookers.
• Looking for a menu from an old answer. Several people report that the menu path suggested in the most popular thread doesn't exist on personal pages. The box they were sent to is the shared-page setting above.

What to do instead#

1. Warn bookers. Put a line in the meeting type description, such as "You'll get a 6-digit code by email to confirm your booking". A step people expect loses fewer bookings than one that surprises them.
2. Send direct links to the people who matter most. A private meeting type or a single-use link won't remove verification, but it removes the extra step of picking a meeting type.
3. Move high-volume booking to a shared booking page. A shared page with yourself as the only staff member gives you the OTP checkbox, page-level access control and custom questions. Read shared booking pages vs Bookings with me before you switch: shared pages create an Exchange mailbox, and your admin may control who can create them. If you turn the code off, weigh the spam risk covered in stopping spam bookings.

If people can't book at all, rather than just being slowed down, see why your Bookings with me link isn't working. If a shared page sends them to a Microsoft sign-in screen, see why a booking page makes people sign in.

BookingsXP is independent and not affiliated with or endorsed by Microsoft.