For the complete documentation index, see llms.txt. This page is also available as Markdown.

Microsoft Outlook Calendar

Connect Microsoft Outlook Calendar so Agents and Workflows can work with calendars and events using an authorised Microsoft identity.

Microsoft Outlook Calendar is a separate Connection for calendar and event work in Microsoft 365.

Depending on the actions and triggers configured in the product, Lleverage can use the Connection to work with events and calendars or start a Workflow from calendar changes.

Connect Calendar

Open Control → Connections, choose Microsoft Outlook Calendar, select the actions the Connection may use and complete the Microsoft sign-in flow.

The Connection uses the authority of the Microsoft identity that was connected. If the tenant requires administrator consent, that remains a Microsoft-side prerequisite.

Outlook Calendar can also be configured through App Registration (S2S) when an IT team wants to use an Azure application identity rather than an individual user.

Delegated access

A delegated Calendar Connection can only do what the connected Microsoft identity is authorised to do in Microsoft 365. Calendar sharing and delegation remain Microsoft-side configuration.

The Enable shared mailbox access upgrade documented for the Outlook email Connection does not apply to Outlook Calendar. The providers have separate Connection and permission paths.

If a process needs broad service access to users' calendars, review whether an S2S App Registration with the appropriate Microsoft application permissions is the intended model instead of assuming the Outlook email shared-mailbox scopes apply.

Triggers and live execution

Calendar-triggered Workflows are background execution. Test runs and live trigger delivery are separate concerns: validate the Workflow, then publish the version intended for production and ensure its trigger is active.

For the current Draft/Published and active/default model, see Publishing workflows.

Troubleshooting

When an event or calendar cannot be reached, verify the connected identity, Microsoft-side calendar permissions, the Connection selected by the Workflow or Agent and whether the problem occurs in a test run or a published trigger.

Do not assume an Outlook email Connection or its shared-mailbox settings automatically grant Calendar access.

Last updated

Was this helpful?