About This Article
This article was generated using an automated workflow leveraging generative AI. It is organized based on the official Microsoft Bookings Service Description and Microsoft 365 platform service descriptions verified as of September 17, 2026.Verification Status: 📘 Official Information Verified – Device Testing Not Performed
Microsoft Bookings is a Microsoft 365 service designed to eliminate the back-and-forth emails required to coordinate free time, allowing you toshare a booking page with others so they can schedule appointments from available time slots.Bookings is available in M365 E3/E5.
License Positioning
| Item | M365 E3 | M365 E5 |
|---|---|---|
| Bookings | Available | Available |
| Web Booking Page | Available | Available |
| Bookings API in Microsoft Graph | Available in Enterprise | Available in Enterprise |
| Teams Online Meetings | Appropriate license required on Teams side | Same as left |
| SMS Notifications | Regional restrictions + Teams Premium conditions apply | Same as left |
The official Service Description states that SMS notifications are limited to North America and the UK, and require an additional Teams Premium license.
First Step: Create a Single Test Booking Page
Instead of publishing a production portal right away, create just one service for testing, such as a "30-minute consultation".
Configuration Example:
サービス名 : テスト相談 時間 : 30分 担当者 : 自分またはテスト担当者 公開範囲 : まず組織内で確認 質問項目 : 必要最小限
Check This
Verify whether the available slots visible to the booker conflict with the staff member's Outlook calendar. Bookings synchronizes with Outlook to adjust availability.
Change One Setting
Modify only the booking lead time and observe how enabling or disabling last-minute bookings changes the available options on the booking screen.
Start with Read Operations When Using Graph
Bookings provides a Microsoft Graph API. Even when automating, it is safer to start by reading and auditing booking information rather than using booking creation or deletion for your initial tests.
In operational design, before looking at the API, it is essential to determine who owns the booking page and who will take over upon personnel changes or departures.
Best Practices for Business Use
Do not mix external-facing and internal-facing booking pages
Keep personal information collected during booking to the absolute minimum
Consider staff working hours/time off separately from bookable hours
Provide clear instructions on how to cancel or reschedule
Verify Teams licensing if attaching Teams meetings
Verify regional and Teams Premium conditions for SMS-driven operations
Bookings data is stored on the Microsoft 365 platform, using Exchange shared mailboxes to hold customer, staff, service, and appointment details. Therefore, design it not merely as a "reservation form," but as business data that encompasses retention, auditing, and access control.
Checkpoints for Administrators
Is Bookings enabled in the tenant?
External publication scope
Handling of Exchange/shared mailboxes
Teams meeting licensing
Personal data collection items
Permissions for applications using the Graph API
Change notifications in the Message Center
Official and Primary Sources
Microsoft Bookings Service Description: https://learn.microsoft.com/en-us/office365/servicedescriptions/microsoft-bookings-service-description
Microsoft 365 platform service description: https://learn.microsoft.com/ja-jp/office365/servicedescriptions/office-365-platform-service-description/office-365-platform-service-description
When implementing Bookings, the first thing to decide is not the screen colors, butwhose time is being booked, by whom, and under what conditions.
