Message ID: MC1197145 (Updated)
Updated July 8, 2026: We have updated the timeline and added documentation. This feature is now available. Thank you for your patience.
Introduction
We’re excited to announce that Microsoft Teams now supports apps in Private channels. This update enables richer collaboration scenarios across teams and organizations by allowing users to add and use apps—including bots, tabs, and message extensions—directly within Private channels. This change aligns with customer feedback requesting more consistent and flexible app experiences across collaboration spaces. Support for apps in Private Channels follows the same model as that for shared channels, ensuring a unified experience for users and developers.
For organizations using custom line-of-business (LOB) apps, developer updates are required to ensure private and shared channel compatibility.
This message is associated with Roadmap ID 518215 and applies to Teams for Windows desktop and Teams for Mac desktop.
When this will happen:
- Targeted release: Rollout begins mid-January 2026, and we expect to complete by late June 2026 (previously late January).
- General availability (Worldwide): This feature is now available.
How this affects your organization:
Who is affected:
- All Microsoft Teams users who participate in Private Channels
- Admins managing Teams app policies
- Developers maintaining Teams apps
What’s changing:
- Apps can now be added to Private Channels. Previously, only a limited set of tabs were supported.
- This feature is available by default.
- All apps marked to work in Private and Shared Channels will be available.
- Channel owners or members can add apps to a Private Channel, with new governance and consent controls.
- A new channel setting allows owners to control who can add apps.
- Apps must be explicitly added to each channel; installing at the team level will no longer apply to Shared or Private Channels.
Screenshot 1: Apps must be added per channel. Users are prompted for consent when interacting with an app that hasn’t been added. Apps are available through all standard discovery entry points.
Screenshot 2: Manage apps in your channels from the new Apps tab in Manage channel settings.
- Guest users can use supported apps depending on app and admin settings.
- Only apps updated by developers to support Private Channel functionality and allowed by admins will be available.
- Support for apps in Private Channels will follow the same model and require similar updates.
- Guidance is available now so organizations can work with custom LOB app developers to plan required updates.
What you can do to prepare:
Admins:
- Review custom LOB apps used in team and channel scenarios and coordinate with app developers to complete the required updates for private/shared channel compatibility.
- Update internal documentation.
- Update your app to meet documented requirements and validate supported scenarios.
- Detailed implementation guidance: Apps for shared and private channels
| Compliance Area | Explanation |
|---|---|
| Does the change store new customer data, if so, where, and is the data cached or permanently stored? | Apps added to Private Channels may store channel-specific data such as membership, settings, and user interactions. Storage location depends on the app’s architecture and may include Microsoft 365 or third-party services. |
| Does the change alter how existing customer data is processed, stored, or accessed? | Apps now operate at the channel level, not the team level. This changes how data access and permissions are scoped, requiring updates to app manifests and use of channel-specific APIs. |
| Does the change provide a new way of communicating between users, tenants, or subscriptions? | Apps (including bots and message extensions) within Private Channels enable new interaction paths among channel members, including guest users, depending on admin and app settings. |
| Does the change modify, interrupt, or disable any of the following capabilities (Purview)? | Apps must be explicitly added per channel, which may affect how DLP policies, audit logging, and eDiscovery apply. Admins should validate app behavior in Private Channels to ensure compliance. |
| Does the change alter how admins can monitor, report on, or demonstrate compliance activities? | Admins must review app usage and permissions at the channel level. Monitoring tools may need updates to reflect app activity in Private Channels. |
| Does the change modify how users can access, export, delete, or correct their personal data within Microsoft 365 services (GDPR Data Subject Rights)? | Apps in Private Channels may store user interactions and data that must be considered in GDPR-related requests. Admins and developers should ensure data handling aligns with privacy obligations. |
| Does the change include an admin control and, can it be controlled through Entra ID group membership? | Admins can manage app permissions and availability via Teams app policies and channel settings. Entra ID group membership may be used to scope access. |
| Does the change allow a user to enable and disable the feature themselves? | Channel owners can control who can add apps, and users can interact with apps once added, subject to consent prompts and admin policies. |
Source: Microsoft
<<< [MC1197145] Archive
Tooltip: View earlier revisions of this post
Latest Posts
- MC1197145: Microsoft Teams Adds Full App Support to Private Channels
- Amazon EC2 High Memory U7i instances now available in AWS Europe (Zurich) region
- MC1420635: Dynamics 365 Contact Center Gets Role-Based Access via Microsoft Entra ID
- MC1420564: Dynamics 365 Sales Adds AI-Powered Automatic Record Linking and Suggested Updates for Accounts, Contacts, and Leads
