Connect Microsoft Calendar and review synchronization conflicts

Microsoft Calendar connects selected busy calendars to WeddingBoard availability and synchronizes appointments created in WeddingBoard. The connector is implemented and tested with deterministic provider responses and isolated PostgreSQL. Real Microsoft consent, tenant policies, Teams licensing, and provider concurrency behavior remain part of the coordinated activation rehearsal.

Choose two different responsibilities

The workspace owner opens Calendar → Microsoft Calendar, connects an account, and chooses the calendars that block booking slots. A personal calendar can block time without becoming the destination for client appointments. If a selected calendar cannot be read, booking availability stays unavailable until the connection is repaired.

Choose a writable destination to mirror WeddingBoard appointments. Changing that destination affects new copies; existing copies retain their original calendar. Selecting Do not mirror appointments pauses synchronization. Unrelated Outlook events remain read-only availability inputs and agenda entries; they do not become WeddingBoard clients or appointments.

Know which fields travel

Mirrored appointments share their title, start, end, location, and cancellation. Private notes remain in WeddingBoard. A 9 a.m. Los Angeles appointment is sent as its actual UTC instant rather than an assumed browser timezone. An ambiguous daylight-saving time must be corrected before synchronization.

Optional Teams links are created only for new mirrored events when the selected calendar advertises Teams support. They appear beside the appointment's synchronization status. Existing online-meeting body content is preserved. The connector does not add attendees or send invitations automatically. If someone adds attendees in Outlook, subsequent outgoing edits pause so the owner can control invitation updates in Outlook.

Client bookings and mini sessions have capacity, reservation, and notification obligations. Change those times in Scheduling, then resolve the mirror to keep WeddingBoard's version. Outlook timing edits to those records are held for review instead of bypassing the booking workflow.

Resolve a disagreement

If an appointment changes in both places, the connection page shows a conflict and a saved Microsoft snapshot. Review it before selecting the version to keep. A later edit invalidates that review; refreshing is required. Remote writes include the provider's revision marker, and incoming writes verify that the local appointment has not changed while the request was running.

For example, if WeddingBoard changes “Venue visit” to “Venue visit with florist” while Outlook moves the time, neither side silently wins. Decide where to reconcile those changes, review the resulting version, and sync again.

Recover a lost response

Before a create request, WeddingBoard saves its transaction identity. If the response disappears, recovery looks for the exact tagged event in the mailbox. It does not create another appointment merely because no result has arrived. An unresolved attempt stays uncertain with an explanation; use Sync / reconcile now to check again. A provider-side investigation may be required when the original result remains unknown.

The connection page shows the latest 100 mirror records. Background synchronization processes bounded batches and rotates through connected workspaces. This is periodic synchronization, not an immediate Microsoft push-notification guarantee.

Disconnect or change accounts

Only the workspace owner can change the connection. Disconnecting deletes saved access and refresh credentials and stops new synchronization. Appointment history and existing Outlook copies remain. Reconnecting the same Microsoft account retains mirror identities; connecting a different account starts a separate generation and asks you to choose calendars again. Revoke Microsoft's own app grant in Microsoft account settings when needed.

See Microsoft's event API, calendar-view pagination, and online-meeting guidance for provider behavior. Calendar permission does not authorize mailbox synchronization; Outlook mail is a separate integration scope.