A production Outlook calendar connector needs the right Microsoft access mode, explicit calendar ownership, time-zone-safe event writes, calendar-view delta, schedule queries, and renewable subscriptions.
Delegated permissions act within the signed-in user's calendar rights. App-only permissions act as the application and usually require administrator consent, so tenant-wide scheduling must be a separately governed enterprise feature.
Store event and calendar IDs, organizer and attendee states, start and end with time zones, recurrence and series identity, transaction ID for idempotent creation, change key, location, and online-meeting details.
Microsoft Graph getSchedule returns free/busy information for users and resources over a bounded interval. Apply your own booking policy afterward and respect the target user's sharing controls rather than fetching event details unnecessarily.
Track the chosen date range through opaque delta links, renew Graph subscriptions before expiration, and use lifecycle notifications and periodic delta reads to recover. Treat removed events and recurring instance changes as explicit records.
For new applications, Outlook calendar capabilities are accessed through Microsoft Graph rather than the retired standalone Outlook REST endpoint.
Its main purpose is free/busy availability. Returned detail depends on permissions and the target user's sharing controls, which is useful for data minimization.
Not as released connectors. Google Calendar has one feature-flagged development method, calendar.event.create, plus list/get for DewEngine-confirmed creates and the resulting canonical creation event. Provider calendar reads and sync, update/delete, availability, recurrence, watches, and Microsoft Graph Calendar remain planned. The implemented slice has only local fake-provider evidence, not real-account or production conformance.
DewEngine is in development. Real use cases decide what ships first.