Integration guide

Microsoft Teams

Creates each live class as a Teams online meeting, moves or cancels it when the class changes, and reads the meeting attendance report so attendance is recorded against each learner. It connects in one of two ways: a signed in account, where a person (and optionally each teacher) signs in with their own Microsoft account, or an organisation connection, where an app registered in the Azure portal acts for your organisation’s users.

What you need

A Microsoft 365 subscription that includes Teams.
Permission to register an app in the Azure portal.
For the organisation connection: a Global Administrator or Privileged Role Administrator to grant admin consent, and a Teams administrator to create an application access policy.

Permissions requested and why

Signed in account (delegated permissions)

Permission or scope	What it allows	Why it is needed
`OnlineMeetings.ReadWrite`	Create and read your online meetings	Creating the class on the signed in account and reading it back.
`OnlineMeetingArtifact.Read.All`	Read your meetings’ attendance reports	Recording who attended. Without it meetings are still created but attendance cannot be read.
`User.Read`	Read the signed in account	Showing who signed in and checking the connection.
`offline_access`	Stay signed in	Renewing access without asking the person to sign in again.

Organisation connection (application permissions)

Permission	What it allows	Why it is needed
`OnlineMeetings.ReadWrite.All`	Create and read online meetings	Creating the class for the host or teacher and reading it back.
`OnlineMeetingArtifact.Read.All`	Read meeting attendance reports	Recording who attended.
`User.Read.All`	Read users in the directory	Finding the host account and each teacher in your directory.

Bodhaka Lumen asks for nothing beyond this list. Credentials you enter are encrypted with your workspace’s own key and are never shown again after saving.

How to connect

In the Azure portal, open App registrations and select New registration.
For the signed in account, add a Web redirect address. Bodhaka Lumen shows the exact address on the Sign in step of the guided setup, with a copy button. It has the form https://your-workspace.bodhakalumen.com/uia/signin/callback.
Under API permissions, add the Microsoft Graph permissions listed above for the way you are connecting.
Under Certificates and secrets, create a client secret and copy its value.
In Bodhaka Lumen, open Integrations, choose Microsoft Teams in the guided setup, and enter the directory (tenant) ID, client ID and client secret.
For the signed in account, select Sign in with Microsoft and agree to the permissions. For the organisation connection, complete the admin consent steps below.
Select Try the connection. A test meeting is created, read back and deleted. Then switch the integration on.
Each teacher can connect their own Microsoft account from Live Sessions, Your meeting account, so their classes are created on their own account.

Admin consent steps (Microsoft)

Sign in to the Azure portal as a Global Administrator or Privileged Role Administrator.
Open App registrations, select the app, then API permissions.
Select Grant admin consent for your organisation and confirm. Each permission should show Granted.
Application permissions for online meetings also need an application access policy. A Teams administrator runs New-CsApplicationAccessPolicy with the app’s client ID, then Grant-CsApplicationAccessPolicy for the host account and each teacher, in Teams PowerShell. The policy can take up to 30 minutes to apply.
If your organisation requires admin consent for delegated permissions too, grant it in the same place before people sign in.

How to disconnect and delete data

In Bodhaka Lumen, open Integrations, then My integrations, choose the Teams integration and select Remove. The stored client secret and any stored sign in tokens are deleted from your workspace.
A teacher can disconnect their own account at any time from Live Sessions, Your meeting account. Their stored sign in token is deleted.
In the Azure portal, delete the client secret or the whole app registration, and under Enterprise applications remove the app’s granted permissions. People can also remove the app from their Microsoft account at myapps.microsoft.com.
Meetings already created stay in Microsoft 365 until you delete them there. Attendance already recorded stays in Bodhaka Lumen as part of the class record until your administrator deletes it or asks us to.

To have any data that came through this integration deleted from Bodhaka Lumen, your workspace administrator can delete it, or write to support@bodhakalumen.com. See the Privacy Policy.

Want early access?

Tell us about your school or organisation and we will be in touch.

Write to us