Integration brief · Microsoft Teams ← Back to the page   Print or save as PDF
Integration brief Microsoft TeamsConferencing

Every Teams Recording Kept, Transcribed and Searchable

Microsoft Teams is where most meetings, calls and internal training now happen, and the recording lives in the meeting tool until it expires. With the Teams connector, Nexus ingests recordings automatically as they are made, transcribes and indexes them, and holds them under retention, access control and a custody trail. Teams stays the meeting tool, and nobody's meeting changes.

What you can do together

  • Have every Teams recording land in the library on its own, through Nexus, with a transcript aligned to its timeline so a phrase is found and played from that moment.
  • Keep recordings on a retention schedule you set, with lifecycle policies previewed before they run and a legal hold that overrides the schedule for anything tied to litigation.
  • Hold interview and hearing recordings with a SHA-384 integrity hash and a custody record of every action, which is what makes a Teams recording usable as evidence.
  • Ask AI Intelligence Hub, included in both Digital Evidence Management and Enterprise Video Platform, what a series of meetings decided and get a cited answer limited to the recordings you may open.
  • Turn recorded training sessions into courses with quizzes and LTI links to the LMS, using the portal's own learning features.

How it connects

Microsoft Teams is an ingestion connector, part of the platform's Microsoft 365 integration alongside SharePoint and OneDrive. Recordings and their available metadata transfer inbound, and after each one lands the source recording is left, moved or deleted, as configured. Transfer runs on the connector's schedule rather than at the moment a recording finishes, and what metadata arrives is bounded by what Teams exposes. Configuration is entered once by an administrator in the portal.

Nothing flows the other way. The connector reads recordings and writes nothing back beyond the configured move or delete. Teams membership does not become the portal's access model: who may open a recording in the library is decided by the portal's own roles, groups and sharing, applied inside every search and every answer.

VIDIZMO and Microsoft Teams · Integration briefPage 1 of 2
How it works Microsoft TeamsConferencing
Microsoft Teams recordings, files and folders where they already live connector, on a schedule or as content arrives Nexus library: transcribe, index, search; retention, audited access, chain of custody ask questions across it, run workflows AI Intelligence Hub ask, summarize, cite no-code workflows redact before anything is released Redactor faces, voices, PII in video, audio, images, documents Microsoft Teams VIDIZMO

A scenario

  1. SetupThe administrator configures the Teams connector in Nexus once: which recordings to pull, source left in place, run every hour.
  2. 10:00HR conducts a recorded interview. After the next run it is in the library with a transcript, a SHA-384 hash recorded at ingest and a custody entry for its arrival. Only the HR investigators' group can open it.
  3. 14:00The training team records a timesheet session. It lands the same way, and a week later a new hire searches "overtime approval" and plays from that phrase.
  4. End of monthA budget analyst asks AI Intelligence Hub, "What did the March budget meetings decide about vehicle replacement?" and gets an answer citing each recording and the moment. The HR interview was never a candidate; her role cannot open it.
  5. Eighteen months onA lifecycle policy soft-deletes routine meeting recordings past the county's schedule, previewed first. The interview is under legal hold, so disposition passes over it.

What stays where

Teams remains the meeting tool

Scheduling, participants, chat and settings stay in Teams and Microsoft 365. The connector reads the recordings and nothing else.

Nexus reads, and writes back only what you chose

A source recording is left, moved or deleted according to the post-ingestion action you set. Teams and its permissions are not changed.

Nothing is replaced

Meetings happen in Teams as before. The library holds a governed copy with its own access model, retention, custody trail and search.

Processing runs where the portal runs

Transcription, indexing, hashing and the assistant run on the portal's infrastructure, as SaaS, in your own Azure subscription, commercial or government, or on your own servers.

Products and solutions

Next step

See it on your own Microsoft Teams instance.

We will show the connection made, the data moving and the output, then size it for your deployment.

Contact VIDIZMO

sales@vidizmo.ai

+1 571-969-2180

vidizmo.ai

Product names and logos are the property of their respective owners.Page 2 of 2