Microsoft Bookings: what it is and how it works

Microsoft Bookings is the appointment scheduler that comes with most Microsoft 365 plans. You publish a web page, people pick a service and a free time on it, and Bookings puts the appointment on the Outlook calendar of the person booked, emails both sides a confirmation and adds a Teams link if the meeting is online. It comes in two forms: Bookings with me, a personal page for 1:1 meetings that runs off your own Outlook calendar (Microsoft now calls it Personal Bookings), and shared booking pages, which a team uses to offer several services across up to 100 staff.

To use it, go to book.ms or add the Bookings app in Outlook or Teams. Your personal page is already there. A shared page needs a few minutes of setup. The rest of this page explains how the pieces fit, then maps every chapter in these docs.

How Microsoft Bookings works#

A shared booking page goes through the same steps every time:

1. You publish a booking page. It lists your services. Each service has a duration, a location or Teams option, the staff who deliver it and its own scheduling rules.
2. A customer opens the link. No sign-in or Microsoft account is needed unless you restrict the page. Times are shown in the visitor's time zone unless you tell the page to use the business zone.
3. Bookings works out the free times. It starts from business hours, narrows them by each staff member's hours, then removes time that's busy on their Microsoft 365 calendar or already booked, plus any time off and closures. Lead time, the booking window and the time increment decide which start times are offered. The full rules are in how Bookings calculates availability.
4. The customer books. They enter their details and answer any custom questions. If the page requires it, they also enter a one-time code that Microsoft emails them.
5. Bookings records the appointment in the page's own mailbox, on the assigned staff member's Outlook calendar and in the Calendar tab of the page.
6. Emails go out. Confirmations, reminders and follow-ups are set per service. Customers can reschedule or cancel from the link in the email, inside the lead time you allow.

Bookings with me follows the same pattern with fewer parts. You are the only person who can be booked, your Outlook working hours or custom hours set the free time, and bookings go straight onto your own calendar.

Shared booking pages and Bookings with me#

Microsoft Learn now uses "Shared Bookings" and "Personal Bookings". The Personal Bookings FAQ says "Bookings with me" and "Personal Bookings" mean the same thing.

The rule we use is simple. If anyone other than you will ever be bookable, or you need a required question, an embed or an integration, start with a shared page. Shared Bookings vs Bookings with me has the full comparison and explains how to move from one to the other.

The mailbox behind a shared booking page#

Most surprises with shared pages make sense once you know that each page is an Exchange Online mailbox:

• It's a scheduling mailbox. The Bookings FAQ describes Bookings as using "shared mailboxes" to store customers, staff, services and appointments. In Exchange PowerShell, though, the pages are listed as SchedulingMailbox, not SharedMailbox, so filter on that type when you inventory them. Whether an ordinary shared mailbox can stand in for a booking page is covered in Bookings and shared mailboxes.
• The page address is the mailbox address. The public link and the Graph and Power Automate identifiers are all built from the mailbox SMTP address. Microsoft generates that address from the business name when you create the page. Renaming the business later changes only the display name. See changing the page URL.
• The domain is fixed at creation. New pages take the domain set in the OWA mailbox policy (BookingsMailboxDomain), or the tenant default, which is often onmicrosoft.com. Microsoft warns that the default domain can push notifications into junk folders. The setting applies only to pages created after the change.
• The URL format has changed before. In 2023 Microsoft moved booking links from /owa/calendar/<address>/bookings/ to /book/<address>/ (message center post MC528980). Old links redirect, but URL-based firewall rules needed the new pattern. Booking pages are also served from bookings.cloud.microsoft now; where to use Bookings lists the current hosts.
• Your data lives in that mailbox. Exchange retention and compliance policies for shared mailboxes also apply to booking mailboxes. See where Bookings data is stored.
• Deleting the page means deleting the mailbox. Only a Microsoft 365 admin can do it. Microsoft says the business details, staff, services and every booking are deleted permanently and can't be recovered.

How to set up the mailbox, and the decisions to make before you click Create, are in shared booking page setup.

Where bookings land in Outlook and Teams#

Two rules catch people out. The Bookings FAQ says appointments "can only be edited from the Bookings web portal", so a change made in Outlook doesn't reach Bookings or the customer. And the reverse sync, busy Outlook time blocking Bookings slots, only works for staff in your tenant who share free/busy. If an event is missing, start with why appointments aren't showing in Outlook. If slots ignore Outlook meetings, see stop Bookings booking over Outlook events.

Who can book#

By default, anyone with the link can book a shared page, anonymously. As of October 2026 you can tighten that in three places:

• On the page: Require a Microsoft 365 account from my organization to book limits it to signed-in colleagues, and also stops website embeds working for outsiders.
• For the whole tenant: an admin setting, Block shared bookings from outside your organization, does the same for every page. Tenant changes can take up to four hours.
• With a one-time code: a page can require an emailed verification code before a booking is created.

Search engine indexing can be switched off per page or tenant-wide. Bookings with me pages have no documented access setting, and the booker may be asked to sign in or continue as a guest and enter a code. If customers are being asked to sign in unexpectedly, see why a Bookings page makes people sign in and the Bookings with me verification code.

Licences#

The person who creates or owns a page needs a Microsoft 365 or Office 365 plan that includes Bookings. Bookable staff, customers and the booking mailbox don't. See which licence Bookings needs for the plan list and the A1 and Teams-meeting caveats.

Getting started#

1. Check that Bookings is turned on for you: the licence, the per-user app toggle and the org-wide switch.
2. Open book.ms. The home page has a Personal booking page section, already published with two meeting types, and a Shared booking pages section.
3. For a personal page, follow setting up Bookings with me.
4. For a team page, follow setting up a shared booking page. Decide the page name and the email domain first, because neither is easy to change afterwards.
5. Book a test appointment from a private browser window before you share the link.

If you look after Bookings for a whole organization, work through the Bookings admin checklist before you roll it out.

What Bookings doesn't do (as of October 2026)#

Know these before you commit. Each links to the answer with the workarounds:

• Payments ("there's no payment support in Bookings")
• Recurring appointments and approval before confirming
• Even round-robin assignment. "Anyone" picks at random.
• Daily or per-customer caps
• Rooms and shared resources
• Google Calendar availability and Zoom meetings
• A per-staff time zone, or one admin view of every page in the tenant

Bookings isn't being retired, either. Some features around it have been, including the phone apps and the Virtual Appointments app. Is Microsoft Bookings being retired? has the dates.

The Microsoft Bookings docs#

These chapters are the reference layer: each covers one area setting by setting and links to the answers that go deeper.

Overview#

• Where to use Bookings: web, Outlook, Teams and mobile: the sign-in addresses, the Bookings app in Outlook and Teams, what happened to the phone apps, and what to check when Bookings won't open.
• Microsoft Bookings limits: every documented limit in one table, with sources and the places where Microsoft pages disagree.

Bookings with me#

• Bookings with me in Outlook: what the personal page is, where it lives in Outlook and what it can't do.
• Bookings with me meeting types: every meeting type setting.
• Sharing your Bookings with me page: links, private types, single-use links and the email signature.

Shared Bookings#

• Shared booking page setup: creating a page and the mailbox behind it.
• Services: every service setting.
• Staff: roles, availability and notifications.
• Scheduling policy: lead time, booking window, increments and buffers.
• How availability is calculated: business hours, staff hours, Outlook free/busy, time off, closures and time zones.
• Group services and attendee limits
• Custom questions
• Customers, manual bookings and self-service changes
• Emails, reminders and SMS
• Customize and publish the booking page: branding, language, time zone, URL, custom domain and sign-in.
• Teams meetings and virtual appointments
• Reporting and exports

Admin#

• Turn Bookings on or off and control who uses it: tenant and per-user switches, granular controls, Personal Bookings, deleting and migrating pages, data location.
• PowerShell for Bookings admins: the documented cmdlets and parameters.

Integrations & API#

• Microsoft Graph Bookings API: what it can and can't do.
• The Bookings connector for Power Automate: triggers, actions and limits.
• What connects to Bookings: Zoom, CRMs, Google Calendar and Zapier.

Troubleshooting#

• Microsoft Bookings troubleshooting: a symptom index that points to the answer for each problem.

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