Microsoft Bookings connector for Power Automate

The Microsoft Bookings connector is the only event source Microsoft offers for Bookings. It has three triggers (appointment created, updated, cancelled) and a single action that lists the booking pages you administer, so it can react to appointments but can't create, change or cancel them. As of October 2026 it's still labelled Preview, it's a Standard connector, only an Administrator on the booking page can build flows with it, and each booking mailbox allows five flows in total.

At a glance#

Triggers#

Each trigger takes two required parameters: Booking page (SMTPAddress), which you pick from a list or type, and change_type, an array described only as "Changes to listen on". Microsoft doesn't document its values; the designer fills it in. The booking page list only shows pages you administer and have opened recently. If yours is missing, open it once in the Bookings web app or choose Enter custom value and paste the address shown under the page's Integrations area for Power Automate. One user on Microsoft Q&A saw that address with %40 in place of @; it's still the booking mailbox address, not your own.

The action#

List Booking Businesses where user is an admin (ListBookingsBusinessUserAsAdmin) returns a mailboxes array, each with displayName and email (the booking mailbox SMTP address). It's useful for picking a page dynamically, and nothing else. The connector page's introduction says it exposes "all appointment booking actions - like Create/Update/Delete of Bookings". The action list on the same page shows that isn't true.

What the triggers return#

All three triggers return the same AppointmentData object. Which fields are filled depends on whether it's a one-to-one or a group service.

The field-by-field use of this payload in a real flow (normalising one-to-one and group bookings, picking one custom answer) is worked through in the Power Automate CRM guide.

Known issues and where the Microsoft pages disagree#

Microsoft documents the connector in two places: the connector reference and a Bookings article on Power Automate integration. They overlap but don't match.

Both pages say fixes are coming "soon" or "in the next release". As of October 2026 neither page records that any shipped.

The documented error codes when saving a flow:

Problems users report that Microsoft doesn't document: the Updated trigger showing no runs while Created and Cancelled work (two Microsoft Q&A threads, 2024 and 2025, with a March 2026 comment still asking for a fix), flows that only started triggering after SMTP was enabled on the booking mailbox, and invalid_grant errors in tenants with Conditional Access. Each is worked through in why a Bookings trigger isn't firing.

Licensing#

Because the Bookings connector is Standard, the Power Automate rights that come with Microsoft 365 are enough to use it; Microsoft describes even the free tier as covering "standard connectors only". The licence question comes from what else the flow connects to. On Microsoft Learn, as of October 2026:

The HTTP action, which you need to forward a booking to Zapier, your own API or the Graph API, depends on your plan; check Settings > View my licenses before you design around it.

Common flows#

Working within the flow cap#

The cap is per booking mailbox, not per person, and old test flows count. A layout that leaves room: one flow per trigger (three), one spare for alerts and one for testing. When you need a second outcome from the same event, add actions to the existing flow instead of creating another. Because the connection can't be shared, the flow stops if its owner leaves or loses the Administrator role, so build it under an account your organization will keep.

When the connector can't do the job (government clouds, writing appointments, or reconciling missed updates), the Microsoft Graph Bookings API is the fallback, and Bookings webhooks and alternatives compares the options.

Doing this with BookingsXP#

For bookings made through the BookingsXP widget on your site, BookingsXP can send each one as a signed booking.created webhook, including the UTM source and click ID the connector can't see. That path needs no Bookings Administrator role and doesn't use any of the five flows, but it only covers widget bookings, not ones staff add in the calendar or ones made on the booking page Microsoft hosts. See webhooks. BookingsXP is independent and not affiliated with or endorsed by Microsoft.