> ## Documentation Index
> Fetch the complete documentation index at: https://docs.granola.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Automatic Heads Up for Microsoft Outlook

> Authorize scoped Microsoft 365 calendar access and add Heads Up links automatically.

Automatic [Heads Up](/help-center/consent-security-privacy/heads-up-for-enterprise) adds Heads Up links to eligible Microsoft Outlook meetings. Organizers can create meetings as usual, without using the Outlook add-in.

This feature requires activation for your Enterprise workspace. Before setup, arrange activation with your Granola contact.

## Authorize calendar access

A Granola workspace admin and a Microsoft 365 administrator must complete these steps:

1. In Granola, click your workspace name in the bottom-left corner, then select **Settings**. Open **Settings > Workspace > Heads Up Pages**.
2. Under **M365 service account**, select **Grant access**.
3. Sign in with a Microsoft 365 administrator account.
4. Review and accept the `Calendars.ReadWrite` application permission.
5. Return to Granola and check that **M365 service account** shows **Active**.

Start this flow from Granola rather than from a saved Microsoft link. Granola generates a short-lived consent link for the active workspace.

Your Granola workspace admin must also [enable the feature in Granola](/help-center/consent-security-privacy/heads-up-for-enterprise#enable-the-feature-in-granola).

## Create and check a meeting

1. As an approved Granola workspace member, create a future meeting on your default Outlook calendar.
2. Add Microsoft Teams, Zoom, or Google Meet conferencing and an internal attendee.
3. Save the event and allow time for Granola to process the calendar update.
4. Reopen the event and check that its meeting link opens a Heads Up page.
5. Select **Join meeting** and check that you reach the original call.

Automatic setup applies to future meetings organized by the connected Granola user. All-day events, past meetings, events organized by someone else, events on secondary calendars, and events containing multiple different conference links are not updated.

Attendees may receive an Outlook event-update email when Granola adds the Heads Up link. Your workspace's [automatic meeting setting](/help-center/consent-security-privacy/heads-up-for-enterprise#choose-which-meetings-are-updated) determines whether internal, external, or all eligible meetings receive Heads Up links.

If your check does not show a Heads Up link, confirm workspace activation, the user's connected Microsoft account, mailbox access, and the meeting requirements above.

The [Outlook add-in](/help-center/consent-security-privacy/heads-up-microsoft-outlook-add-in) remains a separate setup option.

## Restrict access to approved mailboxes (optional)

### Prepare mailbox access

Create a mail-enabled security group in Microsoft 365 containing the Granola users whose calendars can be updated.

Each included user must have an active Exchange Online mailbox and use the same Microsoft 365 account in Granola.

### Create and test the access policy

In Exchange Online PowerShell, replace the example group address and create a restrictive application access policy:

```powershell theme={null}
New-ApplicationAccessPolicy `
  -AppId "6e352def-250d-4e3e-bb67-d54351a9be2d" `
  -PolicyScopeGroupId "granola-heads-up@example.com" `
  -AccessRight RestrictAccess `
  -Description "Granola Heads Up approved mailboxes"
```

Check one mailbox inside the group and one outside it:

```powershell theme={null}
Test-ApplicationAccessPolicy `
  -AppId "6e352def-250d-4e3e-bb67-d54351a9be2d" `
  -Identity "allowed@example.com"

Test-ApplicationAccessPolicy `
  -AppId "6e352def-250d-4e3e-bb67-d54351a9be2d" `
  -Identity "denied@example.com"
```

The first check must grant access and the second must deny it. Microsoft notes that policy changes can take over an hour to affect Graph requests.

See Microsoft's [application access policy guide](https://learn.microsoft.com/en-us/exchange/permissions-exo/application-access-policies) for group and PowerShell requirements.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.