Microsoft Bookings limits: every documented quota

Microsoft documents only a few hard limits for Bookings. As of October 2026 they are: 100 staff per shared booking page, around 50 services per page, five Power Automate flows per booking mailbox, four concurrent Microsoft Graph requests per app and mailbox, and 500 booking pages returned by the Graph call that lists them. Much of what people look for has no published limit at all: booking pages per user, attendees per group session, and the number of custom questions or reminders. The table below collects every documented limit with its source, and the sections after it cover where Microsoft pages disagree and what we measured ourselves.

Every documented limit (as of October 2026)#

Where Microsoft pages disagree#

As of October 2026, these Microsoft documents contradict each other. Plan for the stricter reading:

• Export window. The reporting article describes four months per file. The Bookings FAQ still says the TSV contains "all bookings made in the past 120 days". Check the first and last date in each file.
• SMS countries. The SMS article and the Teams admin article list the US, Canada and the UK. The service description says "North America and the United Kingdom". The Bookings FAQ still says SMS is "available in North America" and delivered through "a Skype or Twilio account", which dates from before Teams Premium. The define-service-offerings article says "only available in North America". Our SMS answer also covers a newer Teams Premium page.
• Who can open a page. The FAQ says staff in the Administrator or Viewer role can open a page. The staff roles article says Team members and Schedulers manage bookings in the mailbox, and only Guests can't open it.
• Licence for the API. The Graph Bookings overview still says the business needs Microsoft 365 Business Premium. The FAQ lists Business Basic, E1 and many other plans. See licence requirements.
• E1 in the Teams app. The Teams admin article lists Microsoft 365 plans without E1. The FAQ and the overview include it.
• The mobile app. The group attendees article still warns about editing "from the mobile app", which Microsoft retired on 15 July 2023. See where to use Bookings.
• The 90-day ceiling. Users have reported a booking window that stops at 90 days, explained on Microsoft Q&A as depending on the service plan. No Microsoft document mentions a plan-based cap, and the scheduling article says 365 days or more. Our lead time answer covers what to check.

Limits Microsoft doesn't document#

As of October 2026 Microsoft publishes no figure for any of these. Test at your own scale before you depend on them:

• Shared booking pages per user or per tenant
• Maximum attendees per group session. See group bookings before you promote a large class.
• Custom questions per page or per service, and the length of a question or answer. Questions live in one list shared by every service on the page, and deleting one removes it from all of them.
• Meeting types on a Bookings with me page
• Rows in a TSV export. A 2021 Q&A thread reports a cap at 10,000 rows. Microsoft doesn't confirm it.
• Bookings per day, per staff member or per customer. There's no setting to cap them. See limiting bookings per day.
• A rate limit on the public booking page

What we saw when testing (September 2026)#

We captured the public booking pages and the calls they make (13 live captures, 913 days and 7,924 slots), and made and cancelled a handful of test bookings. A few limits sit in the page code rather than in any document:

• Customer notes are capped at 3,000 characters by the shared booking page before it submits.
• Questions are text or single choice. The public page only offered free-text and radio-button questions. We saw no checkbox or multi-select type.
• Fallback scheduling values. If a policy value is missing, shared pages fall back to a 1-day lead time, 365 days in advance and 30-minute increments. Personal pages fall back to 1 hour, 90 days and 30 minutes.
• The earliest slot is later than the lead time. On shared pages it's about lead time + 3 minutes from now. On personal pages a slot must start more than lead time + 15 minutes from now.
• No throttling seen on the public page API. 150 requests in five waves of 30 concurrent calls all succeeded, with no HTTP 429. That's one run, not a promise of capacity.

Doing this with BookingsXP#

Bookings has no daily cap. If most of your bookings come through your website, the BookingsXP widget can stop offering a day once a set number of bookings have come through the widget for it. It can't count bookings made directly on the booking page Microsoft hosts, so treat it as a soft limit (widget extras). If you turn on booking storage, widget bookings can also be exported to CSV without a four-month window (stored bookings). BookingsXP is independent and not affiliated with or endorsed by Microsoft.