Bookings Staff Availability Sync from Outlook

Overview

This flow keeps Microsoft Bookings availability accurate by syncing each staff member's Outlook calendar. On an hourly schedule it reads Busy and Out-of-Office (OOF) time across a configurable window and creates matching availability blocks in Bookings so customers can't book over PTO, meetings, or leave. It flags conflicts with existing Bookings appointments in Teams rather than overwriting them, notifies staff of synced blocks, and writes an idempotency ledger to Dataverse so the same event is never blocked twice.

Why it matters: A customer booking onto a staffer's PTO or meeting is a guaranteed bad experience. Syncing real availability from Outlook prevents it - automatically.

Status: Built. Ships Off (demo). Going live requires only connection authorization and environment-variable configuration. Solution: FlowLibsBookingsStaffAvailabilitySync.

Idempotency / conflict design: every busy event is keyed by its Outlook event id in the Dataverse ledger (flowlibs_BookingAvailabilityBlock). On each run, already-synced events are skipped. New events are only blocked when no existing Bookings appointment overlaps; otherwise the overlap is logged as a Conflict and flagged in Teams so it is never silently overwritten.

Dataverse table flowlibs_BookingAvailabilityBlock (Bookings Availability Block) columns: flowlibs_name (Block Key, primary), flowlibs_staffemail, flowlibs_staffname, flowlibs_sourceeventid, flowlibs_sourcesubject, flowlibs_showas, flowlibs_blockstart, flowlibs_blockend, flowlibs_bookingsblockid, flowlibs_syncstatus, flowlibs_syncedon.

Use Case

A services team wants Bookings availability to reflect each staffer's true Outlook calendar automatically, with no manual blocking. Operations gets a run summary; conflicts that need a human are routed to a Teams channel.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
Office 365 Outlook	shared_office365	GetEventsCalendarView SendEmailV2
Microsoft Teams	shared_teams	PostMessageToConversation
Microsoft Bookings	shared_microsoftbookings	ListBookingsBusinessUserAsAdmin
Microsoft Dataverse	shared_commondataserviceforapps

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Buffer

Add a travel buffer around external meetings by widening the block start/end before Create Bookings Block.

Selective

The Filter already keeps only Busy/OOF; add tentative to also block tentative holds.

Two-way

Extend with a reverse leg that writes Bookings appointments back onto the staffer's Outlook calendar.

Cadence / horizon

Change the Recurrence interval and flowlibs_SyncWindowDays for a longer or shorter look-ahead.

Routing

Point conflict alerts at a dedicated scheduling-ops Teams channel via the Teams env vars.

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@addDays(utcNow(), variables('varSyncWindowDays'))

@or(equals(toLower(coalesce(item()?['ShowAs'],'')),'busy'), equals(toLower(coalesce(item()?['ShowAs'],'')),'oof'))

@{concat(items('For_Each_Staff')?['email'],'|',items('For_Each_Busy_Event')?['Id'])}

@empty(body('Check_Existing_Block')?['value'])

@greater(length(coalesce(body('Check_Bookings_Conflict')?['value'],createArray())),0)

https://graph.microsoft.com/v1.0/solutions/bookingBusinesses/@{encodeURIComponent(parameters('EnvVar_BookingsBusinessId'))}/appointments

Customize & download