Transcription management Q&A

Transcription management Q&A

Full whitepaper · Supporting references

Edited from a working Q&A log captured on 29–30 September 2026, with key claims spot-checked against Microsoft Learn on 2 November 2026. This page is editorial guidance for a customer conversation. It is not Microsoft guidance or legal advice.

What this page is

This page gives practical answers to one customer requirement: remove Teams meeting recordings and transcripts after 7 days, with deletion users can’t override, and restrict who can access them.

It has two kinds of source:

The answers combine the two and add editorial recommendations. Where the whitepaper and current Learn pages disagree, both are recorded rather than silently reconciled. Product behaviour, licensing and preview status can change.

Questions

Controls at a glance

From preventing a recording to purging it

Scroll sideways to read the full diagram →

Accuracy notes

Checked on 2 November 2026 against Microsoft Learn using the Learn documentation tools. Pages checked are marked in Supporting references; other details are carried over from the 29 September 2026 log without re-check.

Confirmed: Teams expiry range (1–99,999 days, default 120, new items only); owners can change expiry and restored files aren’t deleted again; the 93-day recycle-bin process and up to seven days for the timer job; Preservation Hold library timing of up to 37 days; the 14-day SharePoint backup window; second-stage purge is immediate. Also confirmed: Priority Cleanup permanent deletion (public preview from 24 August 2026), its approvals, two-person rule, audit events and review-set exclusion; -PriorityCleanup on the retention cmdlets; Graph permanentDelete and its permissions; the admin, label, template and organizer control matrix; two “who can record” options in current documentation; E2EE disabling recording, transcription and Copilot; Graph transcript access off by default.

Corrections and qualifications made to the original log:

Additions from Learn: expiry deletion usually happens within a day (rarely up to five days); moving a recording removes it from expiry; -1 means never expire; A1 users are capped at 30 days; Work IQ transcript access is off by default and takes effect on 14 November 2026; Priority Cleanup can take up to seven days to enable and to delete after approval.

Not verified: the “Restore your OneDrive” rollback period; the support article on artefact access; whether a PowerShell-created Priority Cleanup policy can select permanent deletion; how Graph permanentDelete behaves on retained items.

What was left out

The source log’s first two sections, a workspace review and the whitepaper conversion and registration work, are project notes and aren’t reproduced. Three items were also removed or narrowed: an unsourced reference to “field reports” of inconsistent Graph deletes at scale (replaced by a reconciliation step); a “minimum period 1 day” claim for Purview delete-only policies, which wasn’t rechecked; and repeated recommendations, now consolidated. The original log remains in the repository as transcription-management-retention-and-access-qa.md.

1. Retention and deletion

Q&A index · Full whitepaper · Supporting references

Edited from a working Q&A log (29–30 September 2026). Whitepaper statements link to the converted page; other statements cite Microsoft Learn, spot-checked on 2 November 2026. The customer requirement throughout: remove Teams meeting recordings and transcripts after 7 days, with deletion users cannot override.

Q1. What does the whitepaper say about retention?

Short answer. Teams auto-expiration is the built-in control, but the whitepaper says it is for storage management and "not intended for compliance purposes". Microsoft Purview retention is the recommended compliance control, and legal holds override both (page 14).

If a user deletes a recording before a retention period ends, it disappears from their view but persists in the Preservation Hold library until the period ends (page 14). The whitepaper’s governance “dial” suggests a shorter expiry for organisations that want to minimise storage and exposure, and Purview for content-specific retention (page 16).

Q2. How can a customer remove recordings and transcripts after 7 days?

Short answer. Set the Teams expiry to 7 days as a baseline, then add a Purview delete-only retention policy or auto-apply label at 7 days if users must not be able to keep the files. Neither gives irreversible deletion at day 7 (see Q3).

How Teams expiry behaves, per Manage Teams recording expiration policy and Recording compliance:

• At expiry the file moves to the recycle bin of its storage location and the expiration date field is cleared. Deletion usually happens within a day of the expiry date, occasionally up to five days.
• The owner is emailed and pointed to the recycle bin. If they restore the file, the expiry setting does not delete it again.
• Owners can change the expiry date of recordings they control, and a recording moved from its original location is no longer affected by the setting.

How Teams expiry and Purview interact (corrected from the original log, which said simply that Purview wins):

Source: Recording compliance; holds per page 14 and How retention works for SharePoint and OneDrive.

Q3. Does retention deletion still go through the 93-day recycle bins?

Short answer. Yes. A Purview delete-only (or retain-then-delete) policy removes the file from users’ view at the end of the period, but it moves to the recycle bins and is only permanently deleted at the end of 93 days. A 7-day expiry that users cannot override is achievable; automatic irreversible deletion at day 7 is not a standard retention behaviour.

Where a deleted recording goes

Scroll sideways to read the full diagram →

What happens at the end of a retention period, per How retention works for SharePoint and OneDrive:

Residual copies and recovery paths:

• Second stage: site collection admins can view and restore content during the 93 days.
• Backups: SharePoint keeps backups of all content for 14 days beyond actual deletion. They support only a site-collection-level restore through Microsoft Support, not single files (SharePoint data deletion).
• Configurability: Learn documents the 93-day period and states that recycle-bin quota values are not configurable. It does not document a tenant setting to shorten the 93 days. One Teams page quotes support text saying work or school recycle-bin items are deleted after 93 days "unless the administrator has changed the setting" (Manage Teams recording expiration policy); no such setting was found. Treat the 93 days as fixed unless Microsoft confirms otherwise.

Routes that bypass the 93 days:

Even after hard deletion, the 14-day SharePoint backup window above still applies. The Priority Cleanup documentation does not address backups, so this is an editorial inference from the SharePoint data-deletion page.

Recommended design

1. Set the Teams meeting expiry to 7 days (new items only) as a hygiene baseline. Don’t present it as enforceable.
2. Add a Purview delete-only retention policy at 7 days, scoped to organizers’ OneDrive and to channel SharePoint sites. Users lose access at day 7 and can’t extend it. Be explicit that the files persist in recycle bins for up to 93 days.
3. If the requirement is “no recoverable copy”, use Priority Cleanup permanent deletion with its approval workflow (preview), or manual purge as a stopgap.
4. Prevent artefacts for sensitive meetings: restrict who can record, or use “Copilot only during the meeting”.
5. Include adjacent stores: Copilot summaries and prompts in Exchange (the Microsoft Copilot experiences retention location), meeting chat, and any eDiscovery review sets. Otherwise a transcript purge is not a full purge of the meeting’s AI-derived content.

Q4. Can users’ access to the first- and second-stage recycle bins be removed?

Short answer. No. There is no supported setting to disable or hide the recycle bins. In OneDrive, the owner is the site collection admin of their own OneDrive, so they can always reach both stages.

Recordings of non-channel meetings are stored in the organizer’s OneDrive (page 8). The practical exposure is therefore the organizer and SharePoint admins; participants with a share link can’t restore someone else’s bin. For channel meetings, anyone with edit rights on the site who could see the item can see it in the first-stage bin.

What can be done:

• Narrow access in the first place. Restrict edit permission on team sites and use view-only or blocked download for participants. The bin only exposes what a user could already see.
• Control site collection admins on team sites. This isn’t possible on a user’s own OneDrive.
• Purge proactively. A site collection admin can empty both stages; items deleted from the second stage are purged immediately. There is no scheduled bin purge.
• Use Purview retention. While a retain policy applies, users can’t permanently delete; deletions land in the Preservation Hold library.
• Use Priority Cleanup permanent deletion (preview). This is the supported, audited route that bypasses the bins.
• Prevent creation. Use the admin policy to turn recording off, end-to-end encryption, labels or templates, or “Copilot only during the meeting”. No file means no bin.

Disclose the residual risk to the customer: unless content is permanently purged, the OneDrive owner can recover their own deleted recordings from both bins for up to 93 days.

2. Teams Premium, labels and templates

Q&A index · Full whitepaper · Supporting references

Edited from a working Q&A log (29–30 September 2026). Whitepaper statements link to the converted page; other statements cite Microsoft Learn, spot-checked on 2 November 2026. Where the whitepaper and current Learn pages differ, both are recorded.

Q5. What does the whitepaper say about sensitive meetings and Teams Premium controls?

Short answer. The whitepaper focuses on restricting who can capture, who can access the artefacts, and whether a transcript is kept at all. Sensitivity labels on the meeting invitation can control who can record and override templates if they conflict (page 8).

Sensitive-meeting controls in the whitepaper:

There is no external or anonymous access to artefacts. Channel meetings are the exception to the access controls: every channel member can view, edit and download (page 9, page 10).

Current Learn guidance adds a highly sensitive tier that uses end-to-end encryption and watermarks, which makes recording unavailable (three tiers of protection). See Q6.

Discrepancy recorded. The whitepaper lists three “who can record and transcribe” options, including “No one”. Current Learn lists two (organizers and co-organizers; or organizers, co-organizers and presenters). To prevent recording entirely, use the admin recording policy, which can’t be applied through a template or label (Manage recording options for sensitive meetings).

Q6. Does Teams Premium add anything for expiry or templates?

Short answer. Not for expiry. Expiry is an admin meeting policy and the deletion lifecycle belongs to Purview; Premium changes neither. Premium helps with prevention and enforcement: templates, labels and end-to-end encryption can stop recordings and transcripts being created, or lock down who can create them.

What Premium does not do:

• It adds no Premium-only expiry, shorter deletion or hard delete. Microsoft’s control matrix lists Recordings and transcripts expiration as admin policy only, not available through a sensitivity label, template or organizer (Manage recording options for sensitive meetings).
• Recap and intelligence features create more derived content to govern, not less.

What Premium does help with:

Matching the lever to the customer’s goal:

Q7. Can a template set an expiry that users can’t override?

Short answer. No. Templates have no expiry option. Expiry is set only by admin policy, and even that is a default the recording owner can change. The only expiry users can’t override is a Purview retention policy or label.

Where each setting can be configured, from Microsoft’s matrix (Manage recording options for sensitive meetings):

Note: there is no admin policy for automatic recording, but the PowerShell -AutoRecording policy controls whether organizers see the option.

The template option list in Create a custom meeting template has security, audio and video, recording and transcription (Record meetings automatically, Who can record, Allow Copilot), roles and engagement options. There is no expiry field.

So:

• Templates and labels can only restrict who records and whether recording is automatic. That is prevention, not lifecycle.
• Admin policy sets the expiry per user or group (-NewMeetingRecordingExpirationDays), not per meeting or template. It is not tamper-proof: "End users can modify the expiration date of any recordings they control, so you shouldn’t rely on meeting expiration settings for legal protection" (Recording compliance).
• Purview delete-only retention is service-enforced, and users can’t extend or remove it. Permanent deletion still goes through the 93-day recycle bins (Q3).

The closest thing to a per-meeting-type expiry without Purview is to assign a separate meeting policy, with a 7-day expiry, to the group of organizers who run sensitive meetings. That varies expiry by audience, not by template.

3. Admin controls, Priority Cleanup and automation

Q&A index · Full whitepaper · Supporting references

Edited from a working Q&A log (29–30 September 2026). Statements cite Microsoft Learn, spot-checked on 2 November 2026, or the converted whitepaper. Priority Cleanup permanent deletion is in public preview; confirm availability in the tenant before relying on it.

Q8. What can a Teams admin policy do?

Short answer. The meeting policy (Teams admin centre → Meetings → Meeting policies, or Set-CsTeamsMeetingPolicy, assigned per user or group) is the only control that can turn recording or transcription off entirely. It also sets the default expiry and can require consent. It is the prevention and default layer; Purview is the enforcement and deletion layer.

Recording and transcription settings (Teams settings and policies reference; Manage recording options for sensitive meetings):

Tenant-level and calling settings:

• Transcript API access (Meetings → Meeting settings): Microsoft Graph access is off by default; when off, apps and agents can’t read transcripts through Graph regardless of app permissions. A separate Work IQ access setting for real-time transcripts is also off by default and takes effect on 14 November 2026 (Manage transcript API access). PowerShell: Set-CsTeamsMeetingConfiguration -EnableGraphTranscriptAccess.
• Calling policy (Voice → Calling policies): call recording, call transcription, Copilot for calling (page 7), consent, and -CallRecordingExpirationDays for call recording expiry.
• Blocking downloads from OneDrive and SharePoint: Set-SPOTenant -BlockDownloadFileTypePolicy $true -BlockDownloadFileTypeIds TeamsMeetingRecording. This is an org-wide policy for new recordings and transcripts, with security-group exemptions. Learn lists SharePoint Advanced Management as the prerequisite (Block the download of Teams meeting recording files); the whitepaper says SharePoint Advanced Management and Copilot licences (page 10).
• Adjacent levers for sensitive meetings: lobby and anonymous join, who can present, meeting chat including in-meeting-only values (page 12), watermarks, screen sharing, attendance reports, and live events recording.

For the customer: a group-scoped meeting policy for sensitive-meeting organizers (7-day expiry, consent on, recording restricted), plus a Purview delete-only policy if the 7 days must hold.

Q9. Can Priority Cleanup be managed through Graph or PowerShell?

Short answer. PowerShell: partly. Security & Compliance PowerShell exposes a -PriorityCleanup switch on the retention cmdlets. Graph: no Priority Cleanup API was found. The documented approval and disposal workflow is portal-based.

Cmdlets with a documented -PriorityCleanup switch (Security & Compliance PowerShell, Connect-IPPSSession):

The cmdlet reference pages list these switches but give little description. The following is an illustrative sketch, not a tested script:

Connect-IPPSSession -UserPrincipalName admin@contoso.com

New-RetentionCompliancePolicy -Name "Meeting recordings purge" `
  -SharePointLocation All -OneDriveLocation All `
  -PriorityCleanup -Comment "Reviewed cleanup of Teams recordings and transcripts"

New-RetentionComplianceRule -Name "Meeting recordings purge rule" `
  -Policy "Meeting recordings purge" `
  -ContentMatchQuery "ProgID:Media AND ProgID:Meeting" `
  -PriorityCleanup

Priority Cleanup: who does what

Scroll sideways to read the full diagram →

Caveats, from Override holds to clean up files and Permanently delete files with Priority Cleanup:

• Portal workflow. For SharePoint and OneDrive, simulation must run at least once and after any change other than the description. A second Priority Cleanup admin turns the policy on, because the last editor can’t. Approvers then select Approve disposal under Pending cleanups. The cmdlet reference doesn’t document the turn-on or approval steps, so plan for human approval.
• Two deletion modes. Standard Priority Cleanup moves items to the second-stage Recycle Bin, where the normal 93-day process applies. Delete data permanently bypasses the bins and is documented only as a portal choice. No cmdlet parameter for it was found, so test what a PowerShell-created policy does before relying on it.
• Roles and approvals. Priority Cleanup Admin is needed to create policies, and every item needs approval from someone other than the creator. eDiscovery admin approval is also needed for items under eDiscovery hold. Auditing must be on at least one day before the first policy.
• Exclusions. Records and regulatory records can’t be cleaned up. Items already in an eDiscovery review set aren’t deleted.
• Timing. A policy can take up to seven days to reach Enabled (Success). Allow up to seven days after approval for deletion.

What can be automated around it:

• Monitoring: search the audit log with the policy’s Cleanup ID for PriorityCleanupTagApplied, PriorityCleanupFileRecycled (standard mode) and PriorityCleanupFileDeleted (permanent mode).
• Discovery: identify content with eDiscovery or Graph search before targeting a policy.
• Not a substitute: SharePoint CSOM/REST delete (as opposed to recycle) purges immediately without using the recycle bins (SharePoint data deletion). It is not documented as overriding retention or holds, which is the gap Priority Cleanup fills.

Q10. Can the 7-day removal be automated with a script, agent or CLI?

Short answer. Yes, by three routes that trade automation against governance. A Purview policy needs no script. A scheduled Graph permanentDelete job is fully automatic and irreversible but ungoverned. Priority Cleanup is governed but keeps a human approval step.

Route 2: Graph permanentDelete. POST /drives/{drive-id}/items/{item-id}/permanentDelete permanently removes an item without sending it to the recycle bin. The least-privileged application permission is Files.ReadWrite.All; Sites.ReadWrite.All is the higher option (driveItem: permanentDelete). A workable design:

• Scheduler: Azure Functions, Logic Apps or an Azure Automation runbook with a managed identity. Daily runs are enough for a 7-day target.
• Discovery: enumerate organizers’ OneDrives and channel sites, or search with ProgID:Media AND ProgID:Meeting (the query Learn gives for Priority Cleanup), then filter on createdDateTime older than 7 days.
• Safety rails: a dry-run mode, an allow-list of drives, a strict date filter, and logging of every item ID and call.

Caveats:

• Retention and holds. The permanentDelete page doesn’t say how the call interacts with retention. Learn’s retention model says a deleted item under retention or hold is copied to the Preservation Hold library, and deletion of records is blocked. Expect retained copies to survive; Priority Cleanup exists to override holds. This is an editorial inference; test it in the tenant.
• Blast radius. A bug hard-deletes the wrong files irreversibly, apart from the 14-day site-level backup (SharePoint data deletion).
• Reconciliation. Re-query after each run to confirm that deletions took effect.

Route 3: Priority Cleanup. PowerShell can create the policy and rule (Q9). Learn recommends leaving a policy for Teams recordings running continually. Disposal still needs approval in Pending cleanups, and no Graph or CLI route for that step was found. The gate is deliberate.

CLI options:

Recommendation for the customer:

4. Access to recordings and transcripts

Q&A index · Full whitepaper · Supporting references

Edited from a working Q&A log (29–30 September 2026). Whitepaper statements link to the converted page; other statements cite Microsoft Learn, spot-checked on 2 November 2026. One template capability couldn’t be confirmed and is flagged below.

Q11. Can access to recordings and transcripts be limited to organizers or specific people?

Short answer. Yes. The meeting option Who has access to the recording and transcript offers Everyone (default), Organizers and co-organizers, or Specific people. It requires a Teams Premium or Copilot licence and is separate from who can record.

What the control covers (page 9, page 11):

The setting governs the transcript, the recording, the AI-generated recap and Copilot. Copilot respects permissions, so users need transcript access for its contents to appear in a Copilot response (page 11). Organizers can change it before the meeting starts. See also Customize who can access a recording or transcript (support article, not rechecked).

Don’t confuse it with Who can record and transcribe, the capture-side control. Both need Teams Premium or Copilot but are enforced in different places (Manage recording options for sensitive meetings):

Unconfirmed: enforcing access through a template. The original log said templates are the only way to enforce the access setting for a meeting type, because Microsoft’s matrix shows Template: Yes. However, the template option list in Create a custom meeting template doesn’t include this option (checked 2 November 2026). Check in the Teams admin centre that the option exists and can be locked before designing around it. Sensitivity labels can’t enforce it, and admin policy can’t set either control.

Baseline access without Premium or Copilot (pages 8–10):

Caveats for the customer:

• Channel meetings are the exception. Every channel member can view, edit and download (page 10). -ChannelRecordingDownload Block is an org-wide setting that makes channel recordings view-only for members while channel owners keep full access (Manage Teams recording policies). Channel recordings can’t be made organizer-only.
• Specific people is internal only; there is no external option.
• After the meeting, the owner can still change file permissions in OneDrive or Stream. Pair the meeting option with the download-blocking policy (SharePoint Advanced Management, org-wide, new files only) if view-only matters (Block the download of Teams meeting recording files).
• Restricting access also restricts Copilot. That is usually the intent for sensitive meetings, but tell users in advance.

Strongest access configuration found: Teams Premium or Copilot for meeting owners; a default or assigned template that locks who can record to organizers and co-organizers, and sets who has access to the same if the template supports it; a sensitivity label enforcing recording rights; and the download-blocking policy.

Supporting references

Q&A index · Full whitepaper

These are the references the answers rely on. A listing means the page was cited; it does not mean the whole page was converted. Pages marked “checked” were read on Microsoft Learn on 2 November 2026; the rest are carried over from the 29 September 2026 log.

Whitepaper

Teams recording, expiry and meeting options

Retention, deletion and recycle bins

Priority Cleanup and automation