Skip to main content

Import Microsoft Teams recordings

Quick start​

Connect Microsoft in NEXT, then enable the Teams recording subscription for the Teamspace where those meetings should land. NEXT will then pull new Microsoft Teams meeting recordings from the connected user's Microsoft Recordings folder into that Teamspace as Recordings.

Why integrate with Microsoft Teams?​

For many teams, Microsoft 365 is where customer conversations actually happen. Sales calls, onboarding sessions, steering committees, support escalations, and internal debriefs are often recorded in Teams, but that evidence stays trapped inside meeting storage unless it is moved into an analysis workflow.

Connecting Teams to NEXT solves that gap:

  • It turns customer-facing Teams meetings into searchable Recordings in NEXT.
  • It lets product, CX, and GTM teams analyze the same conversation stream without manually downloading files.
  • It keeps Microsoft-native workflows intact, while making the conversation usable for themes, clustering, and automations in NEXT.

What gets imported​

  • Object in NEXT: Recordings
  • Source objects: Recording files visible in the connected user's Microsoft Recordings folder
  • Included fields: Recording title derived from the file name, file reference, file type, and recording timestamp

How authentication works​

NEXT uses the Microsoft integration and authorizes access through OAuth 2.0. The connected Microsoft account must be able to access the recordings you want NEXT to import, because the current import reads that user's Microsoft Recordings folder.

How to set it up​

  1. In NEXT, open Settings -> Integrations -> Microsoft and connect the Microsoft account that has access to the relevant Teams recordings.
  2. In the Teamspace where you want the imported meetings to appear, enable the Microsoft Teams recording subscription.
  3. Let the scheduled import run, or trigger a manual run if your workspace supports it.

Configuration notes​

  • Imports are incremental. NEXT pulls newly available recording files after the previous successful sync.
  • The current Teams recordings import reads the Microsoft Graph path /me/drive/root:/Recordings.
  • In practice, this means the import is scoped to recordings stored in the connected user's OneDrive-backed Recordings folder.
  • The Teamspace subscription controls where the imported Recordings land in NEXT.

Limitations​

  • Only recordings visible to the authorized Microsoft account can be imported.
  • NEXT currently reads /me/drive/root:/Recordings, so it does not automatically discover recordings stored in Team SharePoint sites or in another user's OneDrive.
  • This import is based on the stored recording files, not on full meeting objects or transcript exports.
  • This integration is for recording artifacts, not for general Teams chat content.

Troubleshooting​

  • If expected meetings are missing, first verify where the recording is actually stored in Microsoft 365.
  • If the meeting was a channel meeting, the recording is often in SharePoint rather than in the organizer's personal Recordings folder. In Teams, open the Team, open the channel, click Files, then click Open in SharePoint. The recording is commonly under Documents/<Channel Name>/Recordings.
  • If the connected user attended the meeting but was not the organizer, the recording may live in someone else's OneDrive Recordings folder. In that case, /me/drive/root:/Recordings will not find it unless that user is the one who connects Microsoft in NEXT.
  • If the recording appears in Teams but not in NEXT, that usually means it is stored outside the connected user's own Recordings folder.
  • If the integration starts failing after a tenant or permission change, reconnect Microsoft so NEXT receives a fresh OAuth grant.
  • If only some meetings appear, confirm that those recordings actually exist in Microsoft storage and were created after the current subscription window.

FAQ​

What does NEXT create from a Teams meeting?​

Each imported Teams meeting becomes a Recording in NEXT so it can be searched, analyzed, summarized, and used in downstream workflows.

Does this import Teams chat messages too?​

No. This integration is focused on stored meeting recording files.

Why use this instead of manually uploading recordings?​

Because it removes manual export and upload work. Once connected, new Teams recordings can flow into NEXT automatically.

Where do the files come from?​

NEXT currently reads recording files from the connected user's Microsoft Graph path /me/drive/root:/Recordings.

Why do some Teams recordings show up in Teams but not in NEXT?​

The most common reason is storage location. Teams can store recordings in different places:

  • the organizer's or starter's OneDrive Recordings folder
  • a Team's SharePoint site for channel meetings

NEXT currently imports from the connected user's /me/drive/root:/Recordings, so recordings stored elsewhere will not appear.

Which Microsoft account should I connect?​

Connect the Microsoft account that can directly open the recordings you want to import. For many standard meetings, that is the organizer's account. For channel meetings, you also need access to the underlying SharePoint site where the recording was stored.

Where are Teams recordings usually stored?​

Microsoft Teams recording storage depends on how the meeting was created:

  • Private scheduled meetings are usually stored in the organizer's OneDrive Recordings folder.
  • Ad-hoc Meet now meetings are usually stored in the starter's OneDrive Recordings folder.
  • Channel meetings are usually stored in the Team's SharePoint site, often under Documents/<Channel Name>/Recordings.

This is why the Teams recordings import works best for recordings that live in the connected user's own Recordings folder.

What should I do if the recording is in SharePoint or another Microsoft folder?​

Use the more flexible Microsoft OneDrive import. That import is better when the source of truth is a SharePoint-backed folder, a Team document library, or another Microsoft file location outside the connected user's default Recordings folder.