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. Teams recordings are saved in OneDrive (for non-channel meetings) or SharePoint (for channel meetings); NEXT AI detects new files and brings them in with a source link for traceability.
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.
Included fields: title, media file, meeting timestamps/duration, participants (when available), and a source link (OneDrive or SharePoint).
Transcripts: if your tenant enables Teams transcripts, they’re stored alongside recordings in OneDrive/SharePoint and can be referenced during import.
Connect Microsoft Teams
In NEXT AI, open Settings → Integrations → Microsoft Teams → Connect.
Sign in with your Microsoft 365 account and approve the Microsoft Graph consent.
Recommended Graph scopes for read-only import include Files.Read.All (OneDrive) and Sites.Read.All (SharePoint) depending on your admin policy.
The connection is scoped to the current Teamspace, so imported Recordings appear right where your team works.
Auto-import 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.
Channel meetings → Team’s SharePoint → Documents/Recordings library.
Detection method: NEXT AI uses Microsoft Graph change notifications (webhooks) and/or periodic checks to discover new files reliably.
Backfill: Seed a recent window if offered, then let the subscription keep you up to date.
Tips
Keep permissions minimal: work with IT to approve read-only Graph scopes that match your policy (e.g., Files.Read.All/Sites.Read.All).
Channel vs. non-channel: if a file isn’t where you expect, check whether the meeting was a channel meeting (SharePoint) or not (OneDrive).
High volume? Microsoft Graph applies throttling—stagger large backfills and add retry/backoff to avoid 429s.
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/SharePoint 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.
429 (throttled). Respect Graph throttling guidance—use exponential backoff and reduce concurrency during backfills.
FAQ
Q: What exactly is created in NEXT AI from Microsoft Teams?
One Recording per new Microsoft Teams meeting recording in the Teamspace where you connected Microsoft—media, meeting details, and a source link to OneDrive/SharePoint.
Q: Where does Microsoft Teams store recordings?
OneDrive for non-channel meetings (organizer’s Recordings folder) and SharePoint for channel meetings (Documents/Recordings).
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/SharePoint.
Q: How does NEXT AI know when to import?
By subscribing to Microsoft Graph change notifications (and/or periodic checks) for new files in the relevant OneDrive/SharePoint locations.