Minimum Retention Policies for Teams and Exchange Locations
You have a Microsoft 365 E5 subscription. You need to create static retention policies for the following locations: Teams chats Exchange email SharePoint sites Microsoft 365 Groups Teams channel messages What is the minimum number of retention policies required?
Community Insight
Tests the constraint that Teams chats and Teams channel messages are distinct retention locations that cannot be combined with Exchange, SharePoint, or M365 Groups in a single policy.
Determines the minimum number of static retention policies required to cover Teams chats, channel messages, Exchange email, SharePoint sites, and M365 Groups. Establishes that Teams content must be separated from other workloads.
Learners often choose 1 policy, assuming Microsoft 365 allows combining all supported locations into a single retention scope, ignoring the specific isolation rules for Teams messaging.
Community Discussion (14 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct answer is B (2). In Microsoft Purview, you can combine Exchange mailboxes, SharePoint sites, OneDrive accounts, and Microsoft 365 Group mailboxes/sites into a single retention policy. However, Teams content is treated differently: 'Teams chats' and 'Teams channel messages' are separate workload locations that cannot be included in the same policy as Exchange/SharePoint/M365 Groups. Therefore, you need one policy for the 'Teams chats' location and a second policy that covers 'Teams channel messages' along with the other three workloads (Exchange, SharePoint, M365 Groups). Wait, actually, let's re-verify the grouping.Correction: 'Teams chats' (private) and 'Teams channel messages' are indeed separate locations. Can they be in the same policy? No, historically they were separate. But can 'Teams channel messages' be grouped with Exchange/SharePoint? Yes. And 'Teams chats' must be alone? Or can 'Teams chats' be grouped with anything?
Let's look at the official documentation structure. Policy 1: Teams chats. Policy 2: Teams channel messages, Exchange mailboxes, SharePoint sites, M365 Groups. This totals 2 policies. Alternatively, if Teams chats and Teams channel messages cannot be mixed with others, but CAN they be mixed with each other? No, they are distinct locations. So Policy 1 = Teams Chats. Policy 2 = Teams Channel Messages + Exchange + SharePoint + M365 Groups. This is valid. So the minimum is 2.
Why the Other Options Are Wrong
Option A (1) is incorrect because you cannot create a single policy that includes both Teams chats/channel messages AND Exchange/SharePoint due to workload separation constraints. Option C (3) would be the count if Teams chats, Teams channel messages, and the rest were all forced into separate policies, but Teams channel messages can share a policy with Exchange/SharePoint/M365 Groups. Options D and E are unnecessarily high.Community Comment Notes
Several users correctly identified the answer as B, noting that Teams content must be managed separately from Exchange and SharePoint. As user DiegoWill noted, "Only 2 policies are needed because it is not possible to contain team chats and channels together with the other workloads." User JamesM9 confirmed via testing that "you cannot include Teams Channel messages in the same policy as SharePoint... So therefore, the answer here is B - 2 policies."Exam Strategy
Remember the 'Teams vs. Non-Teams' split. Any retention policy covering Teams chats or channel messages cannot also cover Exchange, SharePoint, or OneDrive. You must always account for this separation when counting minimum policies.
Frequently Asked Questions
Why can't I put all locations in one retention policy?
Microsoft Purview restricts mixing Teams messaging locations (chats/channels) with productivity locations (Exchange/SharePoint) in a single static retention policy.
Can Teams channel messages be combined with SharePoint sites?
Yes, Teams channel messages can be included in the same retention policy as Exchange mailboxes, SharePoint sites, and Microsoft 365 Groups.