How to enable shared channel support for a Teams app/bot

Question

How to enable shared channel support for a Teams app/bot

Weston Boone 20

Hello,

I see that teams should now support apps in shared channels ( https://mc.merill.net/message/MC1168294 ). The developer sections says:

Update your app manifest to include supportsChannelFeatures: tier1 as part of the latest manifest version

but latest manifest spec doesn't appear to note a property called supportsChannelFeatures : https://developer.microsoft.com/json-schemas/teams/v1.24/MicrosoftTeams.schema.json

Is there a working example anywhere of this being done? My searches through the sample code repos didn't find much using newer manifest versions

Answer accepted by question author

1 additional answer

Your answer

Answer 1

Teddie-D 9,680 Microsoft External Staff Moderator

Hi @Weston Boone

Thank you for posting your question in the Microsoft Q&A forum.

According to this documentation Teams connect shared and private channels - Teams | Microsoft Learn, you’ll only need to add the property supportsChannelFeatures: tier1 to your app manifest and then test your app across different channel types to confirm expected behavior.

Currently, the public schema hasn’t yet been updated to reflect this property, so please treat it as a permitted extension while the rollout is in progress. You should add:

supportedChannelTypes: ["sharedChannels","privateChannels"]
supportsChannelFeatures: "tier1"

to your app manifest and test your app across different channel types. It’s also important to continue following the per‑channel installation and membership guidance outlined in the documentation.

The rollout is scheduled to start in early November 2025 and should finish worldwide by late November 2025. Until then, using the configuration above will keep your app aligned with the upcoming changes and ready for full support once the rollout completes.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Weston Boone 20 Reputation points

2025-11-11T01:22:47.48+00:00

Thanks, not sure how i missed the linked documentation. I'll test out in the morning and then mark this as accepted once confirmed
Nivedipa-MSFT 3,946 Reputation points Microsoft External Staff Moderator

2025-11-11T05:22:19.1233333+00:00

@Weston Boone - Could you please confirm if your issue resolved with above information or are you still looking for additional information?
Weston Boone 20 Reputation points

2025-11-11T19:58:14.0966667+00:00
I can't upload the manifest zip because:

Manifest parsing error message unavailable.

The only change to the manifest.json was to add:

"supportedChannelTypes": ["sharedChannels","privateChannels"], "supportsChannelFeatures": "tier1",

as top level properties (just above "validDomains") and to bump the manifestVersion from 1.19 -> 1.24. My editor seems upset about the supportsChannelFeatures property so i assume that is also why it fails to upload... How do i get Teams to treat it as a permitted extension?
Teddie-D 9,680 Reputation points Microsoft External Staff Moderator

2025-11-12T11:10:27.6266667+00:00

Hi @Weston Boone
Microsoft’s documentation now references the manifest property supportsChannelFeatures: "tier1", but the Teams App Validation Service is still aligned with the published JSON schema (v1.24). Because this schema does not yet include that property, the validator treats it as invalid and returns the generic error Manifest parsing error message unavailable.
Apps in shared channel are currently in public developer preview. If your tenant is enrolled in Microsoft 365 Targeted Releases, developer preview is automatically enabled.

You can treat supportsChannelFeatures: "tier1" as a permitted extension, meaning it’s safe to include in your manifest in source control. However, public tenants may not accept it until your environment receives the updated schema. In practice, this lets you prepare your manifest ahead of time so validation will succeed once your tenant’s Teams service build recognizes the property.
Weston Boone 20 Reputation points

2025-11-12T21:21:51.77+00:00

I don't have access to enroll the tenant in the targeted releases, but since this should be rolling out so soon to the general release I'm just going to circle back in a few weeks. I'll optimistically mark the answer as excepted and try to remember to come back and update if things still don't work in December
Teddie-D 9,680 Reputation points Microsoft External Staff Moderator

2025-11-12T23:24:36.1233333+00:00

Hi @Weston Boone
Thank you for your response.
If you have any further updates on this issue, please feel free to post back. Thank you!
Weston Boone 20 Reputation points

2025-12-18T23:57:45.9566667+00:00

@Teddie-D welp it is mid December now and v1.24 still looks to be the latest manifest version and it still doesn't expect or allow supportsChannelFeatures

Any suggestions or anywhere i would be able to see what the updated timeline is?
Teddie-D 9,680 Reputation points Microsoft External Staff Moderator

2025-12-19T12:22:04.0233333+00:00

Hi @Weston Boone
Sorry for the late update!
Microsoft officially updated MC1168294 on November 14, 2025. The rollout for Shared Channel app manifest changes, which include acceptance of the supportsChannelFeatures property, is now scheduled to begin in mid‑January 2026 and finish in late January 2026.
Due to this delay, most tenants will still reject the supportsChannelFeatures property until the rollout completes.

You can read more at Message Center https://admin.cloud.microsoft/?ref=MessageCenter/:/messages/MC1168294.

It’s worth keeping an eye on the Microsoft 365 Roadmap as well: Roadmap ID 505791.
Weston Boone 20 Reputation points

2025-12-19T16:04:06.81+00:00

Thanks! I'll monitor those instead of pestering here

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

How to enable shared channel support for a Teams app/bot

1 additional answer

Your answer