Microsoft Teams: Apps now supported in Shared Channels [MC1168294]

Message ID: MC1168294

Introduction

We’re excited to announce that Microsoft Teams now supports apps in Shared 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 Shared Channels. This change aligns with customer feedback requesting more consistent and flexible app experiences across collaboration spaces. Support for apps in Private Channels will follow the same model, ensuring a unified experience for users and developers.

This message is associated with Roadmap ID 505791 and applies to Teams for Windows desktop, Teams for Mac desktop, Teams for the web, and Teams for iOS/Android.

When this will happen:

• Targeted Release: Rollout begins in mid-October 2025 and is expected to complete in late October 2025
• General availability (Worldwide): Rollout begins in early November 2025 and is expected to complete in late November 2025.

How this affects your organization:

Who is affected:

• All Microsoft Teams users who participate in Shared Channels
• Admins managing Teams app policies
• Developers maintaining Teams apps

What’s changing:

• Apps can now be added to Shared Channels. Previously, only a limited set of tabs were supported.
• This feature is available by default.
• All apps marked to work in Shared Channels will be available.
• Channel owners or members can add apps to a Shared 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.

  

• External users (via Teams Connect) can use supported apps depending on app and admin settings.
• Only apps updated by developers to support Shared Channel functionality and allowed by admins will be available.
• Support for apps in Private Channels will follow the same model and require similar updates.

What you can do to prepare:

Admins:

• Review your Teams app policies and ensure required apps are updated for Shared Channel support.
• Communicate this change to helpdesk staff.
• Update internal documentation if you detail this feature.
• Confirm that apps used in Shared Channels are permitted by your organization’s app governance policies.

• Update your app manifest to include supportsChannelFeatures: tier1 as part of the latest manifest version.
• Use channel-specific APIs for membership, storage, and permissions. Do not assume team membership equals channel membership.
• Review and update Resource-Specific Consent (RSC) permissions if required.
• Test your app in Shared Channels and with different user roles (internal, guest, external) to validate functionality.
• For apps with advanced scenarios (e.g., file access, cross-channel data, custom permissions), review the full developer guidance for targeted updates.

Before rollout, we will update this post with new documentation.

Compliance Area	Explanation
New communication method between users/tenants	Apps in Shared Channels allow external users to interact via apps, expanding cross-tenant collaboration.
Admin control available	Admins can manage app availability via policies and channel-level settings. Apps installed to team are not added by default in shared and private channels. Channel member/owner needs to explicitly add the app to channel.
User control	Channel owners can control who can add apps to Shared Channels.

Source: Microsoft

Latest Posts