Outlook and Microsoft 365 calendar sync, coming with Bookings.
For teams running on Microsoft 365 instead of Google Workspace, calendar sync will work the same way: staff busy time in, confirmed appointments out.
What works today
- A CalendarAdapter interface exists in the codebase today so this integration slots in without a rework of the booking engine once it ships.
What it needs from you
Nothing for calendar. One thing worth knowing: a Microsoft 365 mailbox connects today as email, because the mail presets already carry outlook.office365.com and smtp.office365.com, so a team on Outlook is not waiting on this row to use the shared inbox.
What it cannot do yet
Calendar sync, alongside Google Calendar and for the same reason.
What's next
Two-way sync ships as part of Bookings, Phase 7 of the roadmap, alongside Google Calendar.
Frequently asked questions
Can a team on Outlook use the shared inbox today?
Yes. A Microsoft 365 mailbox connects today as email, because the mail presets already carry outlook.office365.com and smtp.office365.com. You need the address and an app password, and new mail becomes an ordinary conversation in the shared inbox. It is only the calendar half of Microsoft 365 that is still coming.
What will the calendar sync do when it ships?
The same two things as Google Calendar sync, and it ships alongside it as part of Bookings: import busy time from an Outlook calendar so an outside commitment blocks a slot here, and push a confirmed appointment back the other way.
What does Bookings use for availability in the meantime?
The rotas, buffers and time off you set in Frontiva. The database refuses a double booking rather than apologising for one, so the diary is safe to use before any calendar is connected.
Connect Microsoft 365 when you're ready.
Start free - channel connections are configured per organization from Settings once you're signed up.