Skip to main content
Integrations

5Mins.ai MS Teams Meeting App

What the app does

5Mins.ai includes an optional Microsoft Teams integration that lets your admins schedule Teams meetings directly from the 5Mins.ai admin console - e.g. when booking instructor-led sessions, group cohorts, or live events tied to a course.

The Teams meeting is created under the admin's own Microsoft account, on their behalf. 5Mins.ai does not read mailboxes, files, contacts, or directory data, and does not run any background service in your tenant.

Permissions requested

The app requests three delegated Microsoft Graph permissions. Delegated means the app only acts on behalf of a signed-in user - never as a service account, and never with broader access than that user already has.

Permission

Graph scope

Why we need it

Read and create user's online meetings

OnlineMeetings.ReadWrite

Create the Teams meeting (join link, start/end time, organiser) when an admin schedules a session in 5Mins.ai. We also read the meeting back to display join details.

Maintain access to data you have given it access to

offline_access

Refresh the access token so the admin doesn't have to re-authenticate every hour. Standard OAuth 2.0 refresh token scope - grants no additional data access.

View users' basic profile

User.Read

Identify the signed-in admin (name, email, object ID) to associate the meeting with the right 5Mins.ai user.

Not requested: Mail, Files, Calendars (other than the meeting we create), Directory.Read, application-level / app-only permissions, or anything that grants tenant-wide data access.

How admins connect Teams in 5Mins.ai

  1. In the 5Mins.ai admin portal, go to Events.

  2. Click Create Event and choose Online Event. If no conferencing tool is connected yet, the Choose your conferencing tool page opens.

  3. Click Connect with Microsoft Teams and sign in with your Microsoft work account. This is where the consent screen appears (see Option 3 below).

  4. Once connected, every online event you create gets a Teams meeting link automatically.

Note: the conferencing tool you choose becomes the default and can't be changed on your own afterwards - contact Customer Success if you need to switch.

How to grant admin consent

Option 1 - Admin consent URL (recommended)

Open this URL while signed in as a Global Admin or Privileged Role Administrator, review the permissions, and accept on behalf of your organisation:

Once consented, end users will no longer see the consent prompt at sign-in for the admin-consentable scopes.

Option 2 - Entra admin centre

  1. Sign in to https://entra.microsoft.com

  2. Navigate to Identity β†’ Applications β†’ Enterprise applications

  3. Search for 5MinsMeeting (App ID: fa91f0b5-ac8c-475e-93cf-e39d9ae875c3)

  4. Open Permissions in the left nav

  5. Click Grant admin consent for [your organisation]

  6. Important: there are two tabs - Admin consent and User consent. If your tenant has user consent disabled (common in security-conscious orgs), grant consent on the User consent tab as well to suppress the User.Read prompt.

Option 3 - Consent during first sign-in

When your first admin signs in to the 5Mins.ai Teams integration, they'll see the consent screen. If they're a Global Admin, they can tick "Consent on behalf of your organization" before accepting.

Revoking access

You can revoke consent at any time:

  • Entra admin centre β†’ Enterprise applications β†’ 5MinsMeeting β†’ Permissions β†’ review and remove individual permissions, or

  • Enterprise applications β†’ 5MinsMeeting β†’ Properties β†’ Delete to remove the app entirely

  • Individual users can revoke at myapps.microsoft.com

Revoking will disable the Teams meeting feature in 5Mins.ai but won't affect the rest of the platform.

Security & Compliance notes

  • Delegated permissions only. No background service principal acts on your tenant.

  • Scoped to meetings. We can only create/read meetings created by the admin; we cannot read existing calendar events, mailboxes, or other users' data.

  • Tokens. Access tokens are short-lived (1 hour); refresh tokens are stored encrypted at rest in our infrastructure.