Microsoft Outlook scheduling integration guide
Keep Microsoft calendars and scheduling in sync. The intended connection would check Microsoft 365 free/busy for the selected mailboxes and place confirmed meetings on the correct Outlook calendar.
PROVIDER SETUP GUIDE. Documented workflow, not a live Microsoft Outlook connection.
Microsoft Outlook at a glance
| Category | Calendars |
|---|---|
| Status | Provider setup guide |
| Job | Check microsoft 365 free/busy for the selected mailboxes and place confirmed meetings on the correct outlook calendar |
| Data exchanged | Free/busy status for the booking window; event start, end, zone, and location; reschedule and cancellation state |
| Related capability | Calendar scheduling integration |
What the Microsoft Outlook connection is designed to do
For calendars workflows, the important job is to check Microsoft 365 free/busy for the selected mailboxes and place confirmed meetings on the correct Outlook calendar. Keep Microsoft calendars and scheduling in sync. It sits beside the other calendars connections and supports the calendar scheduling integration requirements.
Microsoft Outlook-specific integration decisions
Map Microsoft 365 user mailboxes, shared calendars, rooms, and tenants before deciding which identity owns an event and which calendars block time.
Check these against current Microsoft Outlook documentation and your account edition; the verification standard explains how provider claims are reviewed.
Microsoft Outlook provider review points
- Map microsoft 365 user mailboxes
- Shared calendars
- Tenants before deciding which identity owns an event
- Which calendars block time
Scheduling data and actions in the workflow
For Microsoft Outlook, these are the data groups the connection exchanges. Record the source, destination, and owner of each before granting access:
- Free/busy status for the booking window
- Event start, end, zone, and location
- Reschedule and cancellation state
Common Microsoft Outlook scheduling use cases
- Separating a user mailbox from shared and delegated calendars
- Keeping room and resource bookings distinct from personal availability
- Maintaining accuracy when a meeting is changed from outlook rather than the booking page
Microsoft Outlook setup and verification checklist
- Confirm whether this is a Microsoft 365 tenant or a personal Outlook.com account.
- Obtain tenant admin consent if your organization requires it before user connection.
- Map user, shared, delegated, and resource calendars explicitly to conflict or destination roles.
- Change a meeting from within Outlook and confirm the booking page reflects it.
Availability, permissions, and limits
A calendar connection should expose availability, not private appointment content. Account permissions and administrator policy can also restrict what is available.
Retry and duplicate handling is covered in the API and webhook guide; ask about Microsoft Outlook to confirm production status before building on it.
Map the Microsoft Outlook workflow before connecting it.
Bring the trigger, required data, failure path, and desired guest outcome.
Discuss the connectionMicrosoft Outlook integration questions
Provider-specific answers for teams planning a Microsoft Outlook scheduling connection.
Does this work with a personal Outlook.com account or only Microsoft 365?
The two behave differently. Microsoft 365 involves tenant policy, admin consent, and possibly shared mailboxes; a personal Outlook.com account does not. Confirm which one you are connecting before testing anything else.
Can Meetin.gs use an Outlook room or resource calendar?
Room and resource mailboxes are a distinct permission model from user mailboxes. Verify which identity holds booking rights on the resource before designing a workflow around it.
Which Outlook calendar receives the confirmed meeting?
Choose one destination calendar explicitly. Writing to whichever calendar happens to be default is how meetings end up on a personal calendar that colleagues cannot see.
Microsoft Outlook data and lifecycle decisions
1. Choose the identity model
A Microsoft 365 user can see their own mailbox calendar, shared mailboxes, room resources, and calendars delegated by others. Only the user's own mailbox should receive Meetin.gs events; the others may block time if the host chooses them explicitly.
2. Protect business ownership
Delegation is the ownership question. An assistant who manages an executive's calendar should connect under the executive's identity with delegate permission, not their own, or confirmed meetings appear in the wrong mailbox and invitations go out from the wrong sender.
3. Map the full lifecycle
Outlook keeps tentative, busy, out-of-office, and working-elsewhere states. Decide which of those block a slot. Reschedules must update the existing item so the guest's accepted copy moves with it; cancellations should send the Outlook cancellation so attendees' calendars clear.
4. Keep traceable evidence
Keep the Outlook item ID and the mailbox it lives in with the booking record. Test a shared mailbox, a room booking, and a tenant with an external-sharing policy that blocks free/busy lookups, because that policy silently returns everything as available.
