Microsoft Bookings Appointment Created trigger not firing in Power Automate although bookings are created successfully

Have a Microsoft 365 administrator check tenant service health and open a support request if no relevant advisory appears, because the absence of any run history across existing and newly created minimal flows indicates that the Bookings event is not reaching or registering with the Power Automate trigger.

Recent November 2026 reports describe the same pattern—appointments are created successfully, but the Bookings Created trigger produces no workflow run—although Microsoft has not published a confirmed general outage or public fix.^1^

1. Check tenant-specific service health

Ask an administrator with access to service health to:

1. Open Microsoft 365 admin center.
2. Go to Health → Service health.
3. Review:
   • Active issues Microsoft is working on
   • Issues for your organization to act on
   • Issue history for the last 7–30 days
4. Look for advisories involving Microsoft Bookings, Power Automate, Power Platform, or connector/event delivery.

Tenant advisories can contain information that does not appear on the public status page.^2^

2. Capture trigger-registration evidence

Since recreating the trigger, connection, and entire test flow did not help, do not repeat those steps. Instead, inspect the trigger state:

1. In Power Automate, open My flows → Test Flow.
2. On the flow’s Details page, check for:
   • There’s a problem with the flow’s trigger
   • A suspended or disabled state
   • A policy warning
3. Edit and save the test flow once.
   • If Flow Checker reports that the workflow is disabled by the organization, ask the Power Platform administrator to review the environment’s data loss prevention (DLP) policies.
4. Open the Bookings trigger’s Settings and ensure Trigger conditions is empty. This matters only if a condition was added previously.

Microsoft documents broken trigger registration, DLP suspension, and trigger conditions as reasons a trigger can fail before any run is created.^3^

3. Check Bookings-specific constraints

These are conditional checks rather than reasons established by the symptoms:

• Flow owner role: The flow creator must be an administrator of that specific Bookings page—not merely a Microsoft 365 tenant administrator.
• Mailbox limit: A Bookings mailbox supports no more than five flows. This limit is per Bookings mailbox, not per administrator.
• Business identity: The trigger must use the Bookings business SMTP address. If necessary, obtain it from Bookings → Integrations → Power Automate and compare it with the value stored in the trigger.
• Licensing: The account requires a license that includes Bookings.

The Microsoft Bookings connector remains a Preview connector and documents these administrator, mailbox-limit, SMTP-address, and licensing requirements.^4^ Microsoft also notes that some errors during flow creation are not fully visible in the flow portal.^5^

If the mailbox already has five flows, consolidate actions into an existing flow or remove an unneeded flow before creating another. If the current three flows are the only ones and they previously worked, this limit is unlikely to explain why all three stopped simultaneously.

4. Escalate with diagnostics

If service health shows no relevant advisory and the checks above reveal no registration, DLP, role, SMTP, or flow-limit issue, open a Microsoft 365 support request and describe it as:

Microsoft Bookings appointments are created successfully, but the Power Automate “When an appointment is created” trigger receives no event and creates no run history. The issue reproduces with a new minimal flow and affects internal and external services.

Include:

• UTC timestamps of several test appointments
• Booking page/business name and SMTP address
• Power Automate environment name and ID
• Flow names and flow IDs
• Tenant region
• Flow owner and confirmation that the owner is a Bookings administrator
• Screenshots of the Bookings appointments and empty run history
• Date/time when the last successful trigger occurred
• Confirmation that the issue affects multiple services
• Results of the trigger Details/DLP checks
• Any service-health advisory ID

These identifiers and investigation notes help support locate backend trigger-registration and event-delivery logs.^6^

References

1. Azure Logic Apps: Microsoft Bookings Created trigger no longer starts ...
2. How to check Microsoft 365 service health
3. Troubleshoot Power Automate trigger problems and errors
4. Microsoft Bookings - Connectors | Microsoft Learn
5. Use Power Automate connectors to build Bookings workflows
6. Create an effective Power Automate support request