Using WordPress? Every integration here is also available as a plugin. Browse the plugin store →
Articles Scheduling
Should appointments from your website go through Microsoft Bookings, or straight onto an Outlook calendar?
Use Microsoft Bookings when you are selling defined services with staff, durations and prices, and you want Microsoft to send the confirmations. Book against Outlook calendars directly when what you are scheduling is people's time, a meeting room or a piece of equipment — that needs no Bookings licence and no Bookings business to maintain.
A scheduling engine with a catalogue in it. A Bookings business holds services — each with a duration, a price, a description and buffers — and staff members assigned to them, and it derives availability from those staff members' real calendars. It also owns the customer-facing side: Microsoft sends the confirmation, the reminder, and the cancellation and reschedule links.
That last part is more valuable than it sounds. Confirmation email is a deliverability problem, a templating problem and a support problem, and Bookings has already solved all three. If your appointments have services and prices, starting from Bookings means you are not rebuilding that.
Access to the calendars that already exist, without introducing a second system anybody has to maintain. Availability is read from free/busy on the target calendar, the rules — slot length, working hours, notice period, buffers — are yours to set, and the confirmed appointment is written back as an ordinary calendar event.
It is also the only one of the two that answers rooms and equipment. A meeting room in Exchange is a resource mailbox with its own calendar, and reserving it means adding that mailbox to the meeting as a resource — which is what makes it show as booked to everybody else in the organisation, in the tool they already use.
From a calendar, in both cases — the difference is what sits between the calendar and the answer. Bookings applies the service definition, the staff assignment and the business hours it holds, and returns slots for a service. A direct Outlook booking applies the rules you configured to the free/busy it read, and returns slots for a person or a room.
One detail is worth knowing before you design around it: Microsoft Graph's Bookings staff availability operation is application-only. There is no delegated form of it, which means the call is made with the organisation's identity rather than a signed-in user's — exactly the shape a public website needs, and a reason Bookings suits public embedding better than it might first appear.
Whichever you choose, do the timezone work explicitly. Business hours are authored in one timezone and read by visitors in another, and a slot list that is silently shifted by an hour is the kind of defect that produces missed appointments rather than error messages.
| Microsoft Bookings | Direct Outlook booking | |
|---|---|---|
| Licence needed | Bookings in your Microsoft 365 plan | None beyond the mailboxes you already have |
| What you are scheduling | Defined services with staff and prices | A person's time, a room or a resource |
| Where availability comes from | The Bookings business | Free/busy plus rules you set |
| Who sends the confirmation | Microsoft | Outlook's meeting invitation, if the booker is added as an attendee |
| Meeting rooms | Not what it is for | Resource mailboxes, joined to the meeting |
| Where the appointment lands | Bookings, and staff calendars in Outlook | The target Outlook calendar |
| Setup you maintain | Services, staff and hours in Bookings | Rules in the component; no second system |
What should not decide it is where the booking form lives. Either engine can be presented on your own website, in your own brand, without sending the visitor to a Microsoft-hosted page — and sending someone off-site to book is where bookings are lost, regardless of which engine is behind the form.
Only if you use Microsoft Bookings as the engine. Booking directly against an Outlook calendar or a room mailbox needs no Bookings licence — it uses the calendars and mailboxes your organisation already has.
That is not what it is designed for. Rooms and equipment in Microsoft 365 are resource mailboxes, and reserving one means adding that mailbox to a meeting as a resource — which is a direct Outlook booking rather than a Bookings service.
With Bookings, in the Bookings business and on the assigned staff member's Outlook calendar, with Microsoft's own confirmation to the customer. With a direct Outlook booking, as an ordinary event on the target calendar, and the booker receives Outlook's meeting invitation if you add them as an attendee.
Yes, provided the timezone the business hours were authored in is configured separately from the visitor's. Converting between the two is the step that gets skipped, and skipping it produces slot lists that are quietly wrong for anyone in another region.
Embedding
Showing Microsoft 365 data to visitors who have no Microsoft account
Can a public website display SharePoint, Outlook or directory data to anonymous visitors?
Read the articleMicrosoft Graph
Managed or proxy: two ways to let a website read Microsoft 365
How does a public website read Microsoft 365 data without the vendor holding your Azure credentials?
Read the articleThese articles describe the general shape. Tenants differ, policies differ, and the interesting questions are the ones where the general shape does not fit.