Source: https://manu-tests-all-orgs.docs-staging.pageloop.ai/integrations/communication-collaboration/microsoft-outlook-calendar

# Microsoft Outlook Calendar

# Microsoft Outlook Calendar

## Microsoft Outlook Calendar: Setup and permissions

Manual calendar coordination slows incident response, creates scheduling conflicts, and adds administrative overhead to change management and onboarding processes. The Atomicwork-Outlook Calendar integration automates event creation and availability checks directly within service workflows, eliminating context-switching and accelerating resolution times.

#### Capabilities

Service teams can automate calendar management directly within workflows, including:
• Viewing calendars and calendar details
• Creating, updating, listing, and deleting events
• Managing event metadata such as time, timezone, attendees, descriptions, and conferencing
• Controlling notifications for event updates and deletions
​

This enables end-to-end automation for processes like onboarding and offboarding; admins can add actions to create and manage onboarding calendar invites, manager meet and greets and more.

#### Setup

1. In the Atomicwork admin portal, navigate to **Settings** > **App Store** > **Microsoft Outlook Calendar** from the list of available apps and click **Connect**.
2. You will be redirected to the Microsoft login page where you review the permissions Atomicwork requires to access your Microsoft Outlook calendar account.
3. Click **Accept** to grant the necessary permissions to Atom.
4. Once you accept, you will be redirected back to Atomicwork, confirming that the Microsoft Outlook Calendar application has been successfully connected.

#### Permissions

> \[!NOTE]
> The integration can access all the calendars accessible by the user setting up the integration.

Atomicwork requests the following Microsoft Graph API permissions:

| **Permission**      | **Purpose**                                                                          |
| ------------------- | ------------------------------------------------------------------------------------ |
| offline\_access     | Allows the app to maintain access to data even when the user isn't actively using it |
| User.Read.All       | Allows the app to read the full profile information of all users in the organization |
| Calendars.ReadWrite | Allows the app to read, create, update, and delete calendar events                   |

#### Supported actions

1. **Create Calendar** – Creates a new calendar under the authenticated user’s account.
2. **List Calendars** – Retrieves all calendars available in the user’s mailbox.
3. **Get Calendar by ID** – Fetches detailed information for a specific calendar using its Calendar ID.
4. **List Events – Default (Primary) Calendar** – Lists all events from the user’s primary calendar.
5. **List Events – By Calendar ID** – Lists all events from a specific calendar identified by its Calendar ID.
6. **Create Event – Default Calendar** – Creates an event in the primary calendar using date, time, and timezone placeholders.
7. **Create Event – By Calendar ID** – Creates an event inside a specific calendar using placeholders for date, time, and timezone.

Anything defined in the Outlook Calendar API can be accessed through Atomicwork

#### Example usecases

Integrating Outlook Calendar with Atomicwork enables powerful automation scenarios for IT service management:

- **Major incident response:** Automatically generate a Teams meeting and add core response members when a P1 incident is created, reducing coordination time from 15+ minutes to seconds.
- **Change request scheduling:** Automatically create calendar events for implementation windows, resource assignments, and stakeholder notifications when a change ticket is approved.
- **Technician availability:** Check technician availability before assignment to prevent delays and improve first-contact resolution rates.
- **Post-incident reviews:** Automatically schedule review meetings with relevant teams after a major incident is resolved.
- **On-call planning:** View shared or group calendar events to validate availability for on-call teams and avoid scheduling conflicts.

---