> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/connections/microsoft-outlook-calendar.md). # 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](/build-and-improve/automate/test-and-publish/publishing-workflows.md). ## 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.lleverage.ai/administer-and-govern/control/connections/microsoft-outlook-calendar.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.