This chapter covers Microsoft Teams compliance features for recording and archiving, a critical topic for the MS-102 exam under objective 1.3 (Tenant Management). You will learn the technical mechanisms behind Teams meeting recording, retention policies, and eDiscovery holds, including how they interact with compliance boundaries such as communication compliance and legal hold. Expect 5-7% of exam questions to directly test this area, often through scenario-based questions that require you to distinguish between recording and archiving capabilities, and to apply the correct retention or hold policy to meet regulatory requirements.
Jump to a section
Imagine a high-stakes courtroom trial. Every word spoken must be recorded verbatim for the official record. The court stenographer sits in the room, typing every syllable on a specialized machine. However, the stenographer can only capture what happens inside the courtroom—not sidebar conversations in the hallway or private chats between lawyers. Once the trial ends, the stenographer hands over the transcript to the court clerk, who seals it in an evidence locker. The locker has strict access controls: only the judge, the prosecution, and the defense can view the transcript, and only after signing a log. Now, imagine a second, silent observer—an archivist—who sits in the back of the room, recording the entire proceeding on video. The archivist does not type; they capture the audio and video feeds directly from the courtroom microphones and cameras. After the trial, the archivist stores the video in a different vault, which has its own access rules. In Teams, the 'recording' feature is the stenographer: it captures meeting audio, video, and screen sharing, then saves the file to OneDrive or SharePoint. The 'archiving' feature is the silent archivist: it uses retention policies and eDiscovery holds to preserve the recording and associated chat messages for compliance, regardless of whether the original file is deleted. Just as the courtroom transcript and video are separate but complementary, Teams recording and archiving are distinct mechanisms that work together for compliance. The recording captures the meeting content; archiving ensures that content (and related data) is retained and discoverable for legal or regulatory purposes. Misunderstanding this separation leads to the common exam trap: assuming that simply enabling recording satisfies compliance requirements, when in fact you must also configure retention and eDiscovery holds.
What Teams Recording and Archiving Are and Why They Exist
Microsoft Teams provides two distinct compliance mechanisms for meeting content: recording and archiving. Recording captures audio, video, and screen sharing during a live meeting and saves it as an MP4 file. Archiving, on the other hand, refers to the retention and preservation of Teams communications—including chat messages, channel posts, and meeting recordings—for compliance purposes such as legal hold, regulatory retention, or eDiscovery. The two are often confused, but the exam tests your ability to differentiate them and to configure each correctly.
Teams recording is governed by the TeamsMeetingPolicy object, specifically the AllowCloudRecording parameter. Archiving is governed by retention policies (in the Microsoft 365 Compliance Center) and eDiscovery holds (Litigation Hold or eDiscovery case holds). Recording alone does not guarantee compliance; you must also configure retention and holds to prevent deletion and ensure discoverability.
How Recording Works Internally
When a user starts recording in a Teams meeting, the following occurs:
Initiation: The user clicks 'Start Recording' in the meeting controls. Teams sends a request to the Teams backend service, which verifies that the user has permission to record (based on the AllowCloudRecording setting in their assigned TeamsMeetingPolicy).
Stream Capture: The Teams client begins capturing local audio and video streams, plus any screen sharing. The streams are sent to the Teams Recording Service in Microsoft 365, which processes them in real-time. The service uses Azure Media Services to transcode and package the streams into a single MP4 file.
Transcription: If enabled, the recording service also generates a transcript using speech-to-text AI. The transcript is stored as a VTT file alongside the MP4.
Storage: Once the meeting ends, the recording is processed and stored in OneDrive for Business (for non-channel meetings) or SharePoint (for channel meetings). Specifically:
Non-channel meetings: The MP4 is saved in the Recordings folder in the organizer's OneDrive, under Documents/Recordings/. The file is named with the meeting title and date.
Channel meetings: The MP4 is saved in the Teams Chat Data folder in the SharePoint document library associated with the channel, under Documents/Recordings/.
Permissions: By default, the recording is shared with all meeting participants. The organizer can modify permissions after the fact.
Key technical details:
Recording is limited to 4 hours max (the meeting duration limit).
The MP4 file size depends on resolution and length; typical bitrate is around 1-2 Mbps.
Transcription is only available for English (US) initially, but expands to other languages.
Recording cannot be paused; stopping recording ends the capture.
How Archiving Works Internally
Archiving in Teams is not a single feature but a combination of retention policies and eDiscovery holds:
Retention Policies: These are configured in the Microsoft 365 Compliance Center under Data Lifecycle Management > Retention. They can be applied to Teams channel messages, private chats, and meeting recordings. When a retention policy is applied, Teams items are retained for a specified period (e.g., 7 years) after creation. After the retention period, they are either permanently deleted (if configured to delete) or remain (if configured to retain only). The retention policy works by placing items in a preservation vault (a hidden, secure location) until the retention period expires.
- eDiscovery Holds: These are used to preserve content for legal or investigative purposes. There are two types: - Litigation Hold: Placed on a user's mailbox (Exchange Online) to preserve all Teams chat messages (which are stored in the user's mailbox). This does NOT preserve meeting recordings stored in OneDrive/SharePoint. - eDiscovery Case Hold: Created in the Compliance Center under eDiscovery > Cases. A hold can be placed on Teams content by specifying a query (e.g., all messages containing a keyword) or by targeting specific users or locations. This hold preserves both chat messages and meeting recordings (if the recording is stored in SharePoint/OneDrive and the location is included in the hold).
Communication Compliance: This is a separate feature that uses machine learning to detect policy violations in Teams messages and recordings (via transcription). It can also trigger retention or alerts.
Key Components, Values, Defaults, and Timers
- TeamsMeetingPolicy parameters:
- AllowCloudRecording: Boolean (default False for most policies). Must be set to True to enable recording.
- AllowRecordingStorageOutsideRegion: Boolean (default False). Controls where recordings are stored geographically.
- RecordingStorageMode: Enum (StreamOnly, StreamAndRecord, RecordOnly). Default is StreamAndRecord.
Retention Policy defaults:
No default retention policy is applied to Teams content. You must create one.
Retention period can be from 1 day to 3650 days (10 years) or indefinite.
Retention action: Delete, Retain, or Retain and then Delete.
eDiscovery Hold:
Holds are indefinite until released.
A hold can be applied to up to 1,000 mailboxes or sites per hold.
Timers:
Recording processing: Typically completes within minutes after meeting end, but can take up to 24 hours for long meetings.
Retention policy application: Changes take effect within 1 day for new items, up to 7 days for existing items.
Configuration and Verification Commands
To configure recording policy via PowerShell:
# Connect to Teams PowerShell
Connect-MicrosoftTeams
# Create a new policy that allows recording
New-CsTeamsMeetingPolicy -Identity "RecordingAllowed" -AllowCloudRecording $true
# Grant the policy to a user
Grant-CsTeamsMeetingPolicy -Identity "user@contoso.com" -PolicyName "RecordingAllowed"To configure a retention policy via PowerShell:
# Connect to Security & Compliance Center PowerShell
Connect-IPPSSession
# Create a retention policy for Teams messages
New-RetentionCompliancePolicy -Name "TeamsRetention7Years" -ExchangeLocation All -SharePointLocation All -SkypeLocation All -ModernGroupLocation All -TeamsChannelLocation All -TeamsChatLocation All
# Add a retention rule to retain for 7 years then delete
New-RetentionComplianceRule -Name "TeamsRetention7YearsRule" -Policy "TeamsRetention7Years" -RetentionDuration 2555 -RetentionRetentionAction RetainThenDeleteTo place a Litigation Hold on a user:
# Connect to Exchange Online PowerShell
Connect-ExchangeOnline
# Enable Litigation Hold
Set-Mailbox -Identity "user@contoso.com" -LitigationHoldEnabled $true -LitigationHoldDuration 365Interaction with Related Technologies
Exchange Online: Teams chat messages are stored in Exchange Online mailboxes (in a hidden folder). Therefore, Litigation Hold on the mailbox preserves those messages. Meeting recordings are NOT stored in Exchange; they are in OneDrive/SharePoint.
OneDrive and SharePoint: Recordings are stored here. eDiscovery holds on SharePoint/OneDrive sites can preserve them.
Azure Information Protection: Sensitivity labels can be applied to recordings to enforce encryption or access restrictions.
Microsoft Purview Data Lifecycle Management: Retention policies are part of this suite.
Microsoft Purview eDiscovery: Used to search, hold, and export Teams content.
Common Exam Traps
Trap 1: Believing that enabling recording automatically archives the meeting. Reality: Recording only captures the meeting; retention policies or holds are needed to prevent deletion.
Trap 2: Thinking that Litigation Hold preserves recordings. Reality: Litigation Hold only preserves mailbox content (chats), not OneDrive/SharePoint files. To preserve recordings, use an eDiscovery case hold or a retention policy on SharePoint/OneDrive.
Trap 3: Assuming that retention policies apply retroactively. Reality: Retention policies apply to content created after the policy is created, unless you use a preservation hold (which is different).
Configure Teams Meeting Policy
First, ensure the Teams meeting policy assigned to users allows cloud recording. Use the Teams admin center or PowerShell to set `AllowCloudRecording` to True. This is a per-user policy; you can create a custom policy for compliance users. Without this, the 'Start Recording' button is grayed out. The default global policy has recording disabled, so you must explicitly enable it.
Start Recording in Meeting
During a meeting, a user with the recording policy clicks 'Start Recording'. The Teams client sends a request to the backend, which validates permissions. Once approved, the client begins streaming audio, video, and screen sharing to the recording service. The service uses Azure Media Services to create an MP4. If transcription is enabled, speech-to-text runs in parallel, generating a VTT file.
Storage in OneDrive/SharePoint
After the meeting ends, the recording is processed and stored. For non-channel meetings, the MP4 is placed in the organizer's OneDrive under `Documents/Recordings`. For channel meetings, it goes to the SharePoint document library of the channel. The file is automatically shared with meeting participants. The organizer can adjust permissions later.
Apply Retention Policy
To archive the recording (and associated chat messages), create a retention policy in the Compliance Center. Specify the locations: Teams channel messages, Teams chats, and SharePoint/OneDrive sites. Set the retention period (e.g., 7 years) and action (retain then delete). The policy places items in a preservation vault until the period expires. This ensures recordings are not deleted prematurely.
Place eDiscovery Hold
For legal or regulatory compliance, create an eDiscovery case hold. In the Compliance Center, go to eDiscovery > Cases, create a case, and add a hold. Specify the locations: include the SharePoint/OneDrive sites where recordings are stored, and the Exchange mailboxes of users for chat messages. This hold preserves content indefinitely, overriding any deletion policies. Use this for active investigations.
Enterprise Scenario 1: Financial Services Compliance
A large bank must retain all internal communications for 7 years per SEC regulations. They enable Teams recording for all meetings involving traders. They configure a retention policy that retains Teams chats and meeting recordings for 7 years, then deletes them. However, they also need to preserve recordings for an ongoing investigation. They create an eDiscovery case hold on the relevant users' OneDrive sites and mailboxes, ensuring those recordings are not deleted even after 7 years. A common issue: the retention policy deletes recordings after 7 years, but the hold prevents deletion, so the recordings remain. The bank uses PowerShell scripts to periodically verify that holds are active on the correct locations.
Enterprise Scenario 2: Healthcare Organization
A hospital uses Teams for telemedicine. They must comply with HIPAA, which requires recordings of patient consultations to be retained for 6 years. They enable recording and also apply a sensitivity label to automatically encrypt the recording file. They configure a retention policy with a 6-year retention period. However, they also need to ensure that recordings are not accessible to unauthorized staff. They use SharePoint permissions to restrict access to the recording folder. A pitfall: if the retention policy is not applied to the SharePoint site where recordings are stored, the recordings could be deleted after 30 days by default (OneDrive recycle bin policy). They learned this the hard way and now verify the retention policy includes the specific site.
Scenario 3: Legal Hold for Litigation
A company is sued and must preserve all Teams communications from the past year. The legal team places a Litigation Hold on the mailboxes of key employees to preserve chat messages. However, they forget to place an eDiscovery hold on the SharePoint/OneDrive sites where meeting recordings are stored. Later, when they need to produce a recording, it has been deleted because the retention policy (which deletes after 1 year) applied. The company had to explain the absence to the court. The lesson: always apply holds to both Exchange (chats) and SharePoint/OneDrive (recordings).
What MS-102 Tests on This Topic
Objective 1.3 (Tenant Management) includes configuring compliance features for Teams, specifically recording and archiving. The exam tests your ability to:
Enable cloud recording via TeamsMeetingPolicy.
Configure retention policies for Teams content.
Use eDiscovery holds (Litigation Hold vs. eDiscovery case hold) for preservation.
Understand where recordings are stored (OneDrive vs. SharePoint).
Identify the limitations of Litigation Hold (only mailbox content, not recordings).
Common Wrong Answers and Why Candidates Choose Them
'Recording automatically archives the meeting' – This is wrong because recording only captures the content; archiving requires explicit retention or hold. Candidates confuse the two terms.
'Litigation Hold preserves meeting recordings' – Wrong because Litigation Hold only applies to Exchange mailboxes. Recordings are in SharePoint/OneDrive. Candidates think 'hold' covers everything.
'Retention policies apply to all existing content immediately' – Wrong because retention policies apply to new content after creation; existing content is processed within 7 days but not retroactively before policy creation. Candidates assume immediate effect.
'You can pause a recording' – Wrong; there is no pause. You can only stop. Candidates may assume a pause feature exists.
Specific Numbers and Terms That Appear on the Exam
AllowCloudRecording parameter.
Retention period maximum: 3650 days or indefinite.
Recording storage locations: OneDrive for Business (non-channel) and SharePoint (channel).
Litigation Hold duration: can be set in days (default indefinite if not specified).
eDiscovery case hold can be placed on up to 1,000 locations.
Edge Cases and Exceptions
If a user leaves the organization, their OneDrive recordings may be deleted after 30 days (via OneDrive retention). Ensure retention policy covers OneDrive.
Channel meeting recordings are stored in SharePoint, which has its own retention settings. If a retention policy is not applied, SharePoint's default retention (30 days in recycle bin) may delete them.
External participants: recordings are still stored in the organizer's OneDrive/SharePoint, not the external user's tenant.
How to Eliminate Wrong Answers
If the question asks about preserving recordings for legal hold, eliminate any answer that mentions only Litigation Hold or only Exchange. Look for answers that include SharePoint/OneDrive or eDiscovery case hold.
If the question asks about enabling recording, look for the AllowCloudRecording parameter in PowerShell or the Teams admin center.
If the question asks about retention, ensure the answer specifies the location (Teams channel messages, chats, or recordings) and the action (retain, delete, or retain then delete).
Teams recording is enabled via AllowCloudRecording in TeamsMeetingPolicy.
Recording files are stored in OneDrive (non-channel) or SharePoint (channel).
Retention policies are required to automatically retain or delete recordings after a specified period.
Litigation Hold preserves only Exchange mailbox content (chats), not recordings.
eDiscovery case holds can preserve both chats and recordings by targeting Exchange and SharePoint/OneDrive locations.
Recording cannot be paused; it can only be stopped.
Retention policies apply to new content after creation; existing content is processed within 7 days.
Channel meeting recordings are stored in SharePoint, not OneDrive.
These come up on the exam all the time. Here's how to tell them apart.
Teams Recording
Captures audio, video, screen sharing during live meeting.
Stored as MP4 in OneDrive or SharePoint.
Controlled by TeamsMeetingPolicy (AllowCloudRecording).
No automatic retention; file can be deleted by owner.
Does not preserve chat messages or other content.
Teams Archiving (Retention & Holds)
Preserves content for compliance or legal reasons.
Uses retention policies and eDiscovery holds.
Configured in Microsoft 365 Compliance Center.
Prevents deletion of content within retention period.
Can preserve chat messages (via Exchange) and recordings (via SharePoint/OneDrive).
Mistake
Recording a meeting automatically archives it for compliance.
Correct
Recording only creates an MP4 file; it does not apply any retention or hold. Without a retention policy or eDiscovery hold, the file can be deleted by the owner or after the OneDrive/SharePoint recycle bin retention period (default 30 days).
Mistake
Litigation Hold preserves all Teams content, including recordings.
Correct
Litigation Hold only preserves mailbox content (chats). Recordings are stored in OneDrive/SharePoint and are not affected by Litigation Hold. To preserve recordings, use an eDiscovery case hold or a retention policy on the SharePoint/OneDrive site.
Mistake
Retention policies apply to existing content immediately.
Correct
Retention policies apply to content created after the policy is created. Existing content is processed within 7 days, but the policy does not retroactively preserve content that was already deleted.
Mistake
You can pause and resume a Teams recording.
Correct
Teams does not support pausing a recording. You can only stop recording (ending the capture) or start a new recording after stopping. This is a common exam detail.
Mistake
All meeting participants can start or stop recording.
Correct
Only the meeting organizer and presenters (by default) can start/stop recording, unless the policy allows attendees. Check the `AllowRecordingByDefault` parameter (not to be confused with `AllowCloudRecording`).
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Modify the global Teams meeting policy or create a new policy. In the Teams admin center, go to Meeting policies, select the policy, and set 'Allow cloud recording' to On. Or use PowerShell: `Set-CsTeamsMeetingPolicy -Identity Global -AllowCloudRecording $true`. Note that this does not enable recording for existing meetings; users must start recording during the meeting.
For non-channel meetings, recordings are stored in the organizer's OneDrive for Business under Documents/Recordings. For channel meetings, they are stored in the SharePoint document library of the channel under Documents/Recordings. This distinction is important for applying retention policies and eDiscovery holds.
No. Litigation Hold preserves mailbox content, which includes Teams chat messages (stored in Exchange Online), but not meeting recordings (stored in OneDrive/SharePoint). To preserve recordings, you need to apply an eDiscovery case hold on the SharePoint/OneDrive site or use a retention policy that includes those locations.
A retention policy automatically retains and optionally deletes content after a set period. It is used for lifecycle management. An eDiscovery hold preserves content indefinitely for legal or investigative purposes, overriding any deletion policies. Holds are typically used for active cases, while retention policies are for long-term compliance.
External participants (guests) can record only if the meeting policy allows it. By default, only the organizer and presenters can record. The `AllowRecordingByDefault` policy setting controls this. Additionally, the recording is stored in the organizer's tenant, not the external participant's.
Processing typically completes within minutes, but for long meetings (near 4 hours) or high traffic, it can take up to 24 hours. The recording appears in the meeting chat and in the storage location. If it doesn't appear, check the meeting chat or the OneDrive/SharePoint folder.
Retention policies apply to content created after the policy is created. Existing recordings will be processed within 7 days of the policy being applied, but they are not retroactively preserved if already deleted. To preserve existing recordings immediately, use an eDiscovery hold.
You've just covered Teams Compliance: Recording and Archiving — now see how well it sticks with free MS-102 practice questions. Full explanations included, no account needed.
Done with this chapter?