What’s new?
Confirm’s LXP Microsoft Teams integration has, until now, been read-only — it could ingest attendance reports for a session, but never create the meeting itself. That changes in this release. The platform can now automatically create the Teams meeting when an online event session is created, and keep it in sync as the session is rescheduled or cancelled.
This ships in two organiser modes so it fits how different organisations want Teams meetings to work. In the simpler Application mode, a single nominated account inside your Microsoft 365 tenant organises every meeting — nothing to configure per person. In the new delegated mode, each session creator connects their own Microsoft account, so the meeting appears on their own Outlook calendar with the standard Teams Join button, exactly as if they'd created it themselves. Different organisations can pick different modes independently. Meetings created under the previous mode will keep working, but reschedules and cancellations of those sessions after the switch may need to be handled manually.
We've also extended automatic attendance tracking to work correctly under delegated mode, so attendance keeps populating automatically without the platform needing broad, tenant-wide permissions — something more security-conscious organisations have asked for.
For any enquiries, please contact Confirm Support.
Connecting to MS Teams
There are two ways to connect: Once in the service settings, If you choose ‘Single Learning Pool account’ then nothing changes from the previous version, you are in ‘Application’ mode.
If you choose "Each user is their own organiser," the platform integration now will be in ‘Delegated’ mode.
This means the platform can now integrate with Microsoft Teams in a way that respects strict IT security policies. Instead of being granted standing, tenant-wide access, the platform acts only on behalf of the individual who has personally signed in and consented — and only for that person's own meetings. Session creators will see a "Connect my Microsoft Account" button — once connected, the auto-create option becomes available on their sessions. Anyone who hasn't connected yet will see a clear prompt telling them what to do.
Which mode is right for you?
| Mode | How access is granted | Best suited for |
| Application | A single, organisation-wide permission granted once by an IT administrator. Curatr can then act across the tenant. | Organisations comfortable with a central service integration. |
| Delegated | Each meeting organiser signs in to Microsoft themselves and consents individually. The platform acts only as that person, only for their meetings. | Organisations whose security policy does not permit organisation-wide access. |
How the Delegated Mode works
The platform acts as the consenting organiser, never across your wider tenant access. The organiser consents once and from then on the platform acts as that person for their own meetings - creating the Teams meetings and later retrieving its attendance.
1. One-time sign-in. When a member of your team sets up a session, they click Connect and sign in to Microsoft. Microsoft shows them exactly what they are agreeing to, and they consent on their own behalf.
2. Meeting creation. The platform creates the Teams meeting as that person. It appears on their own Outlook calendar with the standard Teams Join button, exactly as if they had created it manually.
3. Attendance. After the session, the platform retrieves the attendance record for that organiser's meeting and updates the learner records — using the same permission already given, with no extra steps.
4. Staying connected. The connection renews automatically in the background, and the person can disconnect at any time, which immediately revokes Curatr's access.
What this means for your IT Security team
✓ No organisation-wide access. The platform is never granted tenant-wide permissions and cannot reach meetings, calendars or data beyond those of the individuals who have consented.
✓ Per-person consent. Access is granted by each organiser for themselves, through Microsoft's own standard sign-in and consent screen.
✓ Scoped to the task. The platform requests only the permissions needed to create meetings and read their attendance — nothing more.
✓ Revocable at any time. A user (or your administrators) can withdraw consent at any point, and access stops immediately.
✓ Credentials handled securely. The connection details the platform holds for each user are encrypted at rest.
Auto-create MS Teams meetings for Sessions
When creating an MS Team session, the Admin can now automatically create the link to a Teams meeting by clicking the ‘Auto-create Microsoft Teams meeting’ checkbox. No more creating a Teams meeting by hand and pasting the link into the session — the platform does it for you the moment the session is created. If the session is later rescheduled or cancelled, the Teams meeting is automatically updated or cancelled to match, so the meeting and the session never fall out of step.
That's it — the platform creates the meeting and keeps it updated automatically as the session changes. Manually pasted Teams links continue to work exactly as before, if you'd rather not use auto-create.
Automatic attendance tracking in delegated mode
Attendance for Teams sessions created under delegated mode is now retrieved automatically using the session organiser's own connected Microsoft account, rather than requiring the platform to hold broad, This means organisations that choose delegated mode for security reasons don't lose out on automatic attendance tracking — it keeps working the same way admins are used to. If the session organiser hasn’t connected their Microsoft account or their connection has expired, attendance refresh will fail. Reconnect the account, or import the attendance manually in the meantime. tenant-wide permissions.
What stays the same
From the Admin’s point of view, nothing else changes in how you use it — open the session's Manage Attendance section and select Refresh Attendance as normal. The platform automatically uses the right account behind the scenes depending on your organisation's chosen mode.
From the learner's and organiser's point of view, the Teams meeting will now appear in their calendars as from the Meeting Organiser, rather than from Curator. Otherwise the experience is unchanged: sessions are scheduled in the platform, Teams meetings are created automatically, and attendance flows back into learner records. The only difference is in how the platform is permitted to talk to Microsoft behind the scenes — in a way your security team can be comfortable with.