Azure Logic Apps: Microsoft Bookings Created trigger no longer starts workflows across two tenants

Our previously working Microsoft Bookings → Azure Logic Apps integration stopped starting workflows for appointment events. New appointments are successfully created in Bookings, but no corresponding workflow runs appear. We reproduced the Created-trigger issue using minimal workflows across two separate Microsoft 365 tenants, three Bookings calendars, and two Azure regions.

Has anyone else encountered this?

• Has anyone observed similar Microsoft Bookings trigger failures around November 4–5, 2026?
• Is there a known incident or connector change we may have missed that could explain these symptoms?
• What additional diagnostics can determine where notifications stop between Bookings, the managed connector, and the Logic Apps webhook trigger?

Our troubleshooting details follow.

Timeline and symptoms

The last successful Created workflow run observed in production was November 4, 2026 at 19:26:22 UTC. Missing events were observed on November 5.

Expected events were also missing from the existing Updated and Cancelled workflows, but our isolated tests below focus on Created.

Expected: a new appointment in the selected Bookings calendar starts the Created workflow.

Actual: the appointment exists in Bookings, but no new trigger-history entry or workflow run appears. No error is shown for the missing event.

Minimal reproduction

1. Create a Consumption Logic App with the Microsoft Bookings trigger “When an appointment is Created”.
2. Connect using an account that is an administrator of the selected Bookings calendar.
3. Add only a Compose action with constant text.
4. Save and enable the workflow.
5. Create a new appointment in that calendar.
6. Check trigger history and run history.

Result: no new trigger-history entries or workflow runs following the test bookings, including checks more than five minutes after a booking.

These were new appointments, not additional attendees joining an existing group appointment. The diagnostic workflows had no Service Bus, custom code, or other downstream dependencies.

Environments tested

The tenants used different connection accounts. All tests showed the same missing-event symptom.

Verified configuration and troubleshooting

• Workflows are Enabled.
• API connections report Connected.
• Trigger definitions use ApiConnectionWebhook and reference the intended calendar and Created event.
• No trigger conditions are configured.
• Microsoft Graph confirms that the connection accounts have the administrator role in the respective calendars.
• Disabling/re-enabling the production workflow and reauthorizing its connection did not resolve the issue.
• Creating new connections and new diagnostic workflows also did not resolve it.

Webhook registration versus event delivery

In the production workflow, setup-related trigger outputs returned HTTP 200 with a webhookId.

Diagnostic workflows had setup/configuration-related history entries showing Succeeded / OK with Fired=false and no associated run. We do not interpret those entries as received appointment events or treat Fired=false itself as an error.

The issue is that subsequent new appointments produced no new trigger-history entries or workflow runs.

Control test and service health

A separate Recurrence → Compose workflow in Tenant B / Sweden Central ran automatically twice and succeeded. This confirms that scheduled workflow execution worked there; it does not verify managed connector webhook delivery.

The Azure Service Health events API returned no events for the production subscription when checked.