Microsoft Teams: Private channels increased limits and transition to group compliance

• https://techcommunity.microsoft.com/blog/microsoftteamsblog/unlocking-the-full-potential-of-private-channels-in-microsoft-teams/4438767

1. 7 Jul 2026

   UpdateUpdated July 7, 2026: We have heard the concern from customers to remediate channels without owners, in the timeline we provided. Hence we are proceeding with migrating these channels as-is and will retain them. To clarify, we will not be deleting these channels as of June 2, 2026 –previously communicated. We do continue to encourage all admins to remediate channels in this state as soon as possible. We have updatedwill complete the migration for these ownerless channels in the timeline. Thank you for your patience.  public cloud by 31st July 2026. Migration of channels is complete with a few pending channels for which …

2. 3 Jun 2026

   Update as of April 30th,June 2, 2026 – Admin action is needed and We have updated the content has been updated. timeline. Thank you for your patience.  Migration of channels is complete with a … here for admin remediation. Admins must take action within 30 days, by June 5th,end of July, 2026, to remediate specific private channel configurations that are currently not eligible … one in-tenant user as an owner to each affected private channel by June 5th,end of July, 2026. This ensures the channels have valid ownership and meet requirements. If no action is taken by June 5thend of July 2026, impacted channels will be soft deleted and remain recoverable for 30 …

3. 30 Apr 2026

   The text changed; it is too long to compare word by word here.

4. 8 Apr 2026

   Updated February 27,April 8, 2026: We haveThe migration of private channels continues with most migration now complete (95%). Organizations can check status including % complete in their tenants with the PowerShell cmdlet listed below. Migration is scheduled to complete by late April 2026, with some special cases that will require additional time: private channels with an empty membership list or guest-only membership are rare cases and will require additional steps, and this post will be updated the content. Thank youwith more details on those special cases. New limits for your patience.private channels will rollout starting late April 2026. Private channels not yet migrated would not receive new limits until their migration is complete. In response to customer feedback, we are introducing enhanced flexibility, greater scalability, … of private channels will begin in early October 2025 and continue through March 2026. late April 2026 (previously March). During this period, private channels will continue to operate normally. Admins and … begins. Changes to private channel limits and meeting scheduling will follow in late April through early April 2026.May 2026 (previously early April). As part of this change, newly created private channels will not be … migration early October 2025 (previously late September) and expect to complete by Marchlate April 2026 (previously February).March). Updated channel limits and meeting scheduling will complete in April 2026.early May 2026 (previously April). Restricted clouds rollout will begin in March 2026.April 2026 (previously March). Action required by compliance managers and admins Purview eDiscovery and Legal Hold …

5. 27 Feb 2026

   The text changed; it is too long to compare word by word here.

6. 27 Jan 2026

   … policies instead of the individual user level. The migration of private channels to the updated capabilities will begin in early October 2025 and continue through January 2026 (previously December 2025).  February 2026. During this period, private channels will continue to operate normally. Admins and compliance managers should complete any required policy changes by October 2025 (previosly September),  2025, before the migration begins. Changes to private channel limits and meeting scheduling will follow in Februaryearly March 2026. Migration can start or end at different times for each tenant during the rollout period. To track progress, a new PowerShell command will be available for tenants to check whether their migration has started or is completed. This post will be updated soon with details on the PowerShell command. As part of this change, newly created private channels will not be … happen: General Availability (Worldwide): We will begin rolling out private channel migration  early October 2025 (previously late September) and expect to complete by late January 2026 (previously mid-December 2025). February 2026. Updated channel limits and meeting scheduling will begin rollout complete in early February 2026 and we expect to complete by end of FebruaryMarch 2026. Action required by compliance managers and admins Purview eDiscovery and Legal …

7. 12 Jan 2026

   Updated December 8, 2025:January 12, 2026: We have updated the timeline.content. Thank you for your patience. In response to customer feedback, we are … This post will be updated soon with details on the PowerShell command. As part of this change, newly created private channels will not be created with a document library by default; the root folder is used as a default location for any new files. When this will happen: General Availability (Worldwide): We will begin rolling out …

8. 19 Dec 2025

   … February 2026 and we expect to complete by end of February 2026. Action required by compliance managers and admins Purview eDiscovery and Legal Hold With this change, private channel data will move from user mailboxes to the group mailbox, aligning with how shared channels data is stored. Previously, legal holds were applied to user mailboxes since private channel data resided in each member’s mailbox. Post-migration, the latest version of private channel message data from each user’s mailbox is moved to the private channel’s group mailbox. Message exceedsedits and deleted messages will not be copied into the group mailbox. Note: For users on hold, copies of message edits and deleted messages will remain in the user’s preserved library folder until the hold expires, while the latest version of private channel message data from each user’s mailbox is copied to the private channel’s group mailbox. Before migration If a legal hold exists for a private channel, admins must also apply the policy to the team’s group, in addition to the policy already applied to users’ mailboxes, in order for a hold to apply to new data generated and stored in the private channel’s mailbox. Note that policies applied to the team’s group can apply to all channels in the team. Screenshot 1: Setting up a new hold in Microsoft Purview compliance portal. After migration For existing holds admins will need to ensure that the hold is applied to the user mailbox as well as the new group mailbox, in order for a hold to apply to existing and new message data. Any new legal holds will need to be applied to the group. For complete eDiscovery, include both the private channel’s users’ mailboxes and the team’s group mailbox to retrieve pre-migration messages, message history, and post-migration new content. Screenshot 2: Configuring an eDiscovery search in Microsoft Purview compliance portal. Purview Data Loss Prevention (DLP) With this change, private channel messages will be included as a part of the DLP policy scoped to the private channel’s team’s group, as opposed to the user mailbox. Before migration Admins must modify the “Teams chat and channel messages” policy for private channels to add the team’s group containing the private channel, in addition to the user mailbox, in order to include new private channel messages in a policy. Note that policies applied to the team’s group can apply to all channels in the team. After migration Ensure that “Teams chat and channel messages” policy for private channels is scoped to the team’s group containing the private channel. Screenshot 3: Configuring a data loss prevention policy in Microsoft Purview compliance portal. Purview Retention Policy After this change, creation of new private channel-specific policies will not be possible in the Purview portal. Instead, “Teams channel messages” policies applied to the team’s group will now include private channels. Existing private channel policies will remain in effect and preserve all held message data in user mailboxes. Editing of existing policies will not be supported but policies can be removed. Before migration Apply current private channel retention policies (previously on user mailboxes) to Teams channel messages to include the team’s group, in order to include new private channel messages in a policy. In Microsoft Purview compliance portal, go to solutions > Data Lifecycle Management > Retention policies. Note that policies applied to the team’s group can apply to all channels in the team. After migration If the parent team’s group retention policy differs from the private channel’s policy, create a new or equivalent policy to ensure consistent retention. Screenshot 4: Configuring “Teams channel messages” for a retention policy in Microsoft Purview compliance portal. 4. Microsoft policies for Optical Character Recognition Before Migration: In Microsoft Purview compliance portal, go to Settings, -> Optical character limitrecognition (OCR), -> Select locations and scope to 1 all users and groups or 2 specific users and groups After Migration: Set the settings for “all users and groups” to cover private channels as specific users and groups are not supported. Frequently asked questions How can admins identify a user’s private channel memberships? Use Teams Admin Center under team settings, or run PowerShell: Get-TeamChannelUser to list members. When is compliance manager action required? If a policy (legal hold, eDiscovery, retention, DLP) applied to a user’s mailbox, in order to include private channel messages, differs from the team policies for the team hosting the private channel. Policies must be applied to the team’s group in order to include new private channel messages in a policy. Note that policies applied to the team’s group can apply to all channels in the team. During eDiscovery for users on hold or during migration, search both user mailbox and group mailbox for complete data on a private channel. What if no action is taken? User-level policies will not apply to a private channel’s new message data. Team-level policies will apply to private channels. Why isn’t Microsoft automatically applying policies from user mailboxes to a private channel’s team? Tenant admins and compliance managers must assess and apply policies as needed. Group policies apply to all channels in the Team. Some user mailbox policies are intended for all of a user’s messages, and some are intended for private channel messages. Each organization must review and decide on policies. Is there any impact to end users? During migration, users may see duplicate search results in Teams searches—both links will navigate to the same content in Microsoft Teams. 6. When will migration happen for my tenant and how long will it take? Migration can start or end at different times for each tenant during the request portal. Adding html belowrollout period and can take some weeks depending of the tenant. To track progress, a new PowerShell command will be available for tenants to check whether their migration has started or is completed. The command will be - Get-TenantPrivateChannelMigrationStatus -TenantId <tenantId>  Please refer to this blog post for more information: New enhancements in Private Channels in Microsoft Teams unlock their full potential  We appreciate your attention to this important update. Please refer to this blog post for reference: https://microsoft-my.sharepoint-df.com/:t:/p/brimcg/ERmYzK2UOKBBi9726qR52nEBGw-0sPPCEc1PfogoBOxb-A?e=mfTqqsmore information: New enhancements in Private Channels in Microsoft Teams unlock their full potential  We appreciate your attention to this important update.

9. 8 Dec 2025
   • Tags New feature, User impact, Admin impact → Updated message, New feature, User impact, Admin impact

   The text changed; it is too long to compare word by word here.

10. 18 Sep 2025

    The text changed; it is too long to compare word by word here.

11. 13 Aug 2025 · first version seen

• https://techcommunity.microsoft.com/blog/microsoftteamsblog/unlocking-the-full-potential-of-private-channels-in-microsoft-teams/4438767Not read yet

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

• Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
• 1 linked page has not been read yet.