Skip to main content
Powers room booking for Juno events and calendar invites through Microsoft 365.

Why Juno integrates with Outlook

  • Room booking — admins can attach meeting rooms from your Microsoft 365 room directory to Juno events, and Juno checks room availability before booking.
  • Calendar invites — Juno keeps calendar events for sessions in sync so learners receive standard Outlook invites.

Permissions we request

All permissions are Microsoft Graph scopes on Juno’s Entra ID (Azure AD) app registration.

Entra ID: providing admin consent

Step-by-step walkthrough for granting admin consent to the Teams and Outlook integrations in Microsoft Entra ID.

Per-user calendar connection (delegated, each user consents)

Users who sync their own calendar with Juno grant these delegated scopes for their own mailbox only:

What we do with the data

  • Room directory entries are cached so admins can pick rooms inside Juno.
  • Room free/busy responses are used at booking time and are not retained.
  • Session invites created by Juno (attendee emails, times, responses) are stored to keep events and attendance in sync.
  • Juno does not read email, contacts, files, or the content of events it did not create.

Security and storage

OAuth tokens are encrypted at rest and used only server-side. Delegated tokens are scoped to the individual mailbox that granted them.

Revoking access

  • In the Microsoft Entra admin center, revoke the enterprise application’s permissions or delete it from your tenant.
  • Individual users can remove the app under their Microsoft account’s app permissions.
  • In Juno, disconnect the calendar integration from the admin integration settings.
Last modified on July 22, 2026