Microsoft Bookings new booking alerts in a Teams channel

What people have asked#

• In a December 2025 Microsoft Q&A thread, an admin started from the template "When a Booking appointment is Created, post message in a Teams channel". The booking worked but no message ever arrived and the flow showed no runs. Turning on SMTP for the mailbox fixed it, after the admin role and connector consent had been checked.
• A May 2026 Q&A question asked how to push booking updates from an external booking website into Teams channels. The answer was a Workflows flow with a webhook trigger that posts an Adaptive Card. That works for systems that can call a URL. Bookings can't.
• A 2022 Q&A thread asked to add Bookings to a Teams channel. The answer then was that the Bookings app only goes in the left app bar, not in a channel.

Option 1: email the channel (no Power Automate)#

Get the channel's address. In Teams, go to the channel name and select More options (...) → Get email address. Microsoft says a Teams admin has to have the feature turned on, and it isn't available with Office 365 Government plans. If you use the advanced settings to limit who can send to the channel, keep your own organisation allowed, then test.

Turn on the business notification. In Bookings, open the page, go to Booking page → Scheduling policy, tick Notify when a booking is created or changed, and select Save and publish.

Get the email to the channel. Microsoft says this notification goes to "the mailbox specified on the Business information page". The only address field on that page is Send customer replies to, which also receives customers' replies to confirmations and reminders. You have two choices:

• Forward it (recommended). Keep that field pointing at a mailbox you control, such as a shared mailbox, and add an Outlook inbox rule there that forwards the Bookings notifications to the channel address. If the forward bounces with 5.7.520 Access denied, your tenant blocks automatic forwarding to outside addresses, and an admin has to allow it for that mailbox.
• Point the field at the channel. Microsoft doesn't document this, and customer replies would then post to the channel too. Only do it if that's acceptable, and make a test booking first.

Each email lands as a channel post with a View original email link, and people can reply to it as a thread. You get Microsoft's wording, not a card you design, and a post for every change as well as every new booking.

Why adding the channel as "staff" doesn't work#

Bookings lets you add staff by any email address, so it's tempting to add the channel's address. Staff emails only go to the staff member assigned to that booking, though. A channel added as staff would only hear about bookings assigned to it, and it would appear in your staff list. Microsoft doesn't document groups or channel addresses as staff. Use the business notification instead. The three notification switches are explained in notifying staff and the whole team.

Option 2: a Power Automate flow (standard connectors)#

This is still Power Automate, but both connectors are Standard on Microsoft Learn: Microsoft Bookings (Preview) and Microsoft Teams. The free Power Automate use that comes with a work account covers standard connectors, so you don't need Premium.

1. In Bookings, go to Staff and confirm you have the Administrator role on that calendar. Tenant admin rights don't count.
2. In Power Automate, create an Automated cloud flow with the trigger When a appointment is Created (Microsoft's spelling). Pick the booking page, or enter its SMTP address from Integrations → Power Automate in Bookings.
3. Add the Teams action Post message in a chat or channel. Set Post as to Flow bot, Post in to Channel, then choose the team and channel.
4. Write the message from dynamic content: CustomerName, ServiceName, StartTime and the staff member's DisplayName. For a richer layout, use Post card in a chat or channel with an Adaptive Card instead.
5. Save, then book on the public page to test.

Things that catch people out:

• Five flows per booking mailbox, shared by every admin. Put several actions in one flow rather than one flow per channel.
• Private channels. The Teams connector says posting to a private channel "currently isn't supported". Use a standard channel.
• Group services. Only the first attendee fires Created. Later attendees fire Updated.
• Silent flows. Work through why the Bookings trigger isn't firing, including the SMTP fix from the 2025 thread.

Workflows in Teams is Power Automate too#

The Workflows app in Teams looks separate, but Microsoft says Workflows "are powered by Microsoft Power Automate". A Bookings flow built from Workflows is the same flow with the same Bookings limits. Workflows are also tied to the person who created them, so they stop if that person leaves, unless you add co-owners.

Workflows also has webhook templates. In current Teams the channel one is called Send webhook alerts to a channel; older guides call it Post to a channel when a webhook request is received. It gives you a URL that posts any Adaptive Card it receives, and Microsoft says these templates don't need a premium licence. Bookings can't call that URL itself, so the template only helps when something else sends the booking. The old Office 365 Connector incoming webhooks are being retired, so use Workflows for anything new.

Doing this with BookingsXP#

If customers book through the BookingsXP widget on your site, the Pro plan can post each new booking to a Teams channel. It uses that Workflows webhook template: you create it in the channel, copy the URL, and add it in BookingsXP as a Microsoft Teams endpoint. Each booking arrives as an Adaptive Card with the service, time, staff member, traffic source and campaign, the customer's name and email, and a BXP reference. No Microsoft 365 permissions, Bookings admin role or flow quota are involved, and Microsoft says the template doesn't need a premium Power Automate licence. The limits: Store bookings must be on for the widget (the card includes customer details), alerts pause while Zero data retention is on, and only new bookings made through the widget are posted. Bookings on the page Microsoft hosts, bookings staff add themselves, cancellations and reschedules aren't. Failed posts are retried up to 8 times over about two hours. Pro allows 5 endpoints and Business 25. See the Teams integration page, the webhooks docs and pricing. BookingsXP is independent and not affiliated with or endorsed by Microsoft.