Office 365 Connectors Private Channels Support Inquiry

Hi 성건희 (Lime)

Thank you for reaching out to the Microsoft Q&A forum.

I completely understand your concern and why this situation can be confusing, especially when you’re planning migrations around the retirement of Office 365 Connectors and are waiting for feature parity in Workflows.

Based on the latest updates, Microsoft has extended the Office 365 Connectors retirement deadline to April 30, 2026, and has indicated that additional details regarding private channel support will be shared in future updates.

However, there is currently no published confirmation that private channel support is available or generally released, and no exact availability date has been announced at this time.

In the meantime, the best approach is to continue monitoring official Microsoft communications such as the Microsoft 365 Developer Blog for the most up to date information.

Please understand that as a forum moderator, I do not have visibility into internal or unpublished timelines. I also do not have the ability to influence Microsoft’s product roadmap or provide any confirmed dates for upcoming features.

I understand this may not be the definitive timeline you were hoping for, and I truly appreciate your understanding.

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.

Support for Office 365/Microsoft 365 connectors, including webhook-based connectors such as Incoming Webhook, is being retired and new Microsoft 365 Connectors will soon be blocked. Existing webhook-based connectors must have their URLs updated to the new endpoint to continue working only until December 31, 2024, after which they will no longer post notifications into Teams.

Private channels do not support connectors at all, and this limitation remains in place. Private channels explicitly do not support connectors (along with certain tabs such as Stream, Planner, Tasks by Planner and To Do, and Forms). There is no date in the provided information indicating that connector support will be added to private channels in the future.

For new integrations, the recommended approach is to use the Workflows app/Power Automate with the When a Teams webhook request is received trigger, or to enhance a Teams app (for example, using bots with proactive messages) instead of relying on Office 365/Microsoft 365 connectors.

References:

• IT Admins - Private channels in Microsoft Teams
• Build webhooks and connectors
• Create connectors for Microsoft 365 Groups
• Manage Microsoft 365 connectors and custom connectors