What this check looks at
Checks that Teams live events are not set to be recorded every time.
Teams live events are broadcast-style meetings for large audiences. The live events policy (TeamsMeetingBroadcastPolicy) has a "Record an event" setting, BroadcastRecordingMode: Always record (AlwaysEnabled), Never record (AlwaysDisabled) or Organiser can record (UserOverride). Microsoft is replacing live events with town halls, but the live events policies stay in the tenant and are what this check reads.
The check reads every live events policy, Global and custom, and fails when any is set to Always record, naming them. It warns when a policy came back without the setting.
With Always record, every live event, including internal briefings on sensitive matters, produces a recording that attendees and producers can watch and download afterwards, whether anyone wanted one or not. Because nobody decides to keep the content, nobody decides how long to keep it or who may see it.
Why it matters
A live event recorded every time keeps a copy of every broadcast, whatever was said in it. The organiser should decide whether an event is recorded.
A typical case: an all-staff live event announces a restructuring, with some names and figures on the slides. The policy records it automatically and the recording link is posted on the intranet. Months later, people who have since left still have the link, and the recording shows information that was only ever meant to be heard once.
UK GDPR’s data minimisation and storage limitation principles ask organisations to keep only what they need for as long as they need it. A recording made by default for every event works against both, and adds to what has to be searched for every subject access request.
CISA SCuBA MS.TEAMS.1.7v2 asks that events are not set to always record. The organiser can still record any event they need to, and attendees see no change.
How to fix it
Where: Teams admin centre → Meetings → Live events policies
Before you start
- Check whether any live event is required to be recorded, and tell its organiser to choose recording when scheduling it.
Step by step
- List the live events policies. Install the Teams PowerShell module if it is not already there (Install-Module MicrosoftTeams), then run Connect-MicrosoftTeams and sign in as a Teams Administrator. Run Get-CsTeamsMeetingBroadcastPolicy | Select-Object Identity, BroadcastRecordingMode and note every policy showing AlwaysEnabled.
- Check whether any event must always be recorded. Ask the people who run live events whether any is required to be recorded (for example a regulated briefing). Tell them that from now on they choose recording when they schedule the event.
- Change the Global live events policy. In the Teams admin centre, go to Meetings > Live events policies and select Global (Org-wide default). Set "Record an event" to "Organiser can record" (or "Never record") and select Save. If your tenant no longer shows Live events policies, make the change in PowerShell instead.
- Change every other policy in PowerShell. Run Set-CsTeamsMeetingBroadcastPolicy -Identity Global -BroadcastRecordingMode UserOverride, then for each custom policy from the first step, Set-CsTeamsMeetingBroadcastPolicy -Identity "<policy name>" -BroadcastRecordingMode UserOverride.
- Confirm the change. Run Get-CsTeamsMeetingBroadcastPolicy | Select-Object Identity, BroadcastRecordingMode again: every policy should show UserOverride or AlwaysDisabled.
With PowerShell
Connect-MicrosoftTeams Set-CsTeamsMeetingBroadcastPolicy -Identity Global -BroadcastRecordingMode UserOverride
What users will notice
Organisers choose whether each live event is recorded; nothing changes for attendees.
How to confirm it worked
Get-CsTeamsMeetingBroadcastPolicy | Select-Object Identity, BroadcastRecordingMode shows UserOverride or AlwaysDisabled.
Frameworks and controls
This check maps to controls in 7 frameworks. Passing it is evidence that the setting is in place, not a certification against any of them.
| Framework | Control |
|---|---|
| NCSC CAF | B3.c Stored data |
| Zero Trust | Data |
| SOC 2 | C1.1 Identifying and maintaining confidential information |
| ISO 27001:2022 | A.5.33 Protection of records |
| CISA SCuBA | MS.TEAMS.1.7v2 Events not set to always record |
| NIST CSF 2.0 | PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected |
| NCSC 10 Steps | Data security |
The framework mappings were last checked against the published standards in October 2026.
Microsoft’s documentation
- Set-CsTeamsMeetingBroadcastPolicy (Microsoft Learn)