Quick start
From the Teamspace where you want meetings to land, open Settings → Integrations → Microsoft → Connect and authorize Microsoft 365. Then create a subscription to auto-import new Microsoft Teams recordings as Recordings in this Teamspace. NEXT AI detects new files and brings them in.
Why integrate with Microsoft Teams?
Each source adds a new dimension of customer truth. Microsoft Teams contributes the meeting/customer perspective (sales, onboarding, renewals, implementations, cross-functional working sessions) that complements other types of calls, support conversations, surveys, and app-store reviews you already capture in NEXT AI. Together, these streams create a richer customer-intelligence graph that improves decisions and workflows—with evidence attached.
What gets imported
Object in NEXT AI: Recording in the Teamspace where the integration is connected.
Connect Microsoft
In NEXT AI, open Settings → Integrations → Microsoft → Connect.
Sign in with your Microsoft 365 account and approve the Microsoft Graph consent.
The connection is scoped to the current Teamspace, so imported Recordings appear right where your team works.
Auto-import files/calls
Create a subscription that watches for new Teams recordings and imports each as a Recording:
Where Teams saves recordings:
Non-channel meetings → Organizer’s OneDrive → Recordings folder.
Backfill: Seed a recent window if offered, then let the subscription keep you up to date.
Supported OneDrive paths
We support path-based OneDrive folder addresses (Microsoft Graph “drive root” paths). The path must point to a folder and will be expanded to :/children by the importer, so do not include :/children yourself.
Supported pattern: /me/drive/root:/<folder path>
Notes:
The import reads only the immediate children of the folder (no recursive subfolders).
Only the connected user’s OneDrive is supported. SharePoint/Teams channel drives are not supported by the OneDrive import.
OneDrive for Business: In the Microsoft API,
/me/drive/rootalready represents the Documents library. Do not includeDocumentsin the path. For example, use/me/drive/root:/Recordings(not/Documents/Recordings).
Examples
/me/drive/root:/Documents/Meeting Notes/me/drive/root:/Recordings/me/drive/root:/Projects/Acme/Calls
Common mistakes
Including children yourself (invalid):
/me/drive/root:/Documents/Meeting Notes:/childrenUsing non-folder or item-based URLs:
/drives/{drive-id}/items/{item-id}
Troubleshooting
“I can’t find the file.” Non-channel recordings live in the organizer’s OneDrive → Recordings; channel recordings live in the Team’s SharePoint → Documents/Recordings library. Confirm which type of meeting it was.
Transcript didn’t show up. Teams transcripts must be enabled by an admin; when enabled, they’re stored with the recording in OneDrive and can be referenced by NEXT AI.
Consent blocked / insufficient access. Your admin may need to approve Files.Read.All and/or Sites.Read.All for the app before files are visible.
FAQ
Q: What exactly is created in NEXT AI from Microsoft?
One Recording per new Microsoft Teams meeting recording in the Teamspace where you connected Microsoft.
Q: Where does Microsoft Teams store recordings?
OneDrive for non-channel meetings (organizer’s Recordings folder).
Q: Do we need to enable transcripts?
If you want transcripts from Teams, an admin must enable transcription. When enabled, transcripts are stored with the recording in OneDrive.
Q: Can I import Teams channel recordings from Sharepoint?
NEXT currently supports recording imports only from OneDrive.
Q: Why does /me/drive/root:/Documents/Recordings return “Not Found” (OneDrive for Business)?
In OneDrive for Business, Microsoft Graph maps /me/drive/root directly to the Documents library. That means Documents is not a folder you can address in the path. If you include it, Graph looks for Documents/Documents/..., which does not exist and results in an API error (404):
✅ Correct example:
/me/drive/root:/Recordings❌ Incorrect example:
/me/drive/root:/Documents/Recordings
⚠️ This commonly happens because the SharePoint web URL shows /Documents/..., but Microsoft Graph addressing works differently.