Fix Teams Workflow App Cannot Run a Flow in a Shared Channel

When you create a workflow in the Teams Workflow app and try to run it from a shared channel, the flow may fail with an error or simply not trigger. This typically happens because shared channels use Azure AD B2B direct connect, which changes how permissions and licensing are evaluated. In this article, I will explain why the Teams Workflow app fails in shared channels and show you the exact steps to fix it.

You will learn how to check your workflow’s owner, verify the shared channel’s access settings, and re-create the workflow if needed. I will also cover common mistakes that cause the flow to stop working and how to avoid them.

Why the Teams Workflow App Cannot Run a Flow in a Shared Channel

Shared channels in Teams are designed for collaboration with people outside your organization. They rely on Azure AD B2B direct connect, which creates a trust relationship between your tenant and the external tenant. This trust allows external users to access the channel without being added as guests. However, this also means that the Teams Workflow app, which runs on Power Automate, must handle permissions and licenses across tenants.

The most common reason a flow fails in a shared channel is that the workflow owner is not a member of the channel. When you create a workflow from the Workflow app, the owner is the person who creates it. If that person is an external user or a guest, the flow may not have the necessary permissions to read the channel’s data or trigger actions. Another cause is that the shared channel inherits the host tenant’s policies, but the workflow app might not be enabled for external users.

How Shared Channels Differ from Standard and Private Channels

Standard channels are visible to all team members, and private channels restrict access to a specific set of members. Shared channels are the only channel type that allows external participants without making them guests of the tenant. This difference is critical because Power Automate flows use the identity of the workflow owner to access the channel. In a standard channel, the owner is always in the same tenant, so permissions work as expected. In a shared channel, the owner might be in a different tenant, and the flow may not be able to authenticate.

Steps to Diagnose and Fix the Workflow App in a Shared Channel

Follow these steps in order. Each step addresses a specific failure point.

1. Check the workflow owner
   Open the Teams Workflow app and select the workflow that fails. Look for the owner name under the workflow details. The owner must be a member of the shared channel. If the owner is an external user, ask the channel owner to run the workflow from their account. You can also add the external user as a guest in the host tenant, but that changes the collaboration model.
2. Verify the shared channel’s access settings
   Go to the shared channel and select the ellipsis (…) next to the channel name. Choose “Manage channel” and then “Members.” Confirm that the workflow owner is listed as a member. If not, add them. Also, check the “External access” tab to see if external users are allowed to run apps in this channel.
3. Check the Workflow app permissions in Teams admin center
   Sign in to the Teams admin center at admin.teams.microsoft.com. Go to Teams apps > Manage apps. Search for “Workflow” and select it. In the app’s permission settings, confirm that it is allowed for external users. If it is blocked, change the setting to “Allowed” and save.
4. Re-create the workflow from the shared channel
   If the above steps do not fix the issue, delete the workflow and create a new one directly from the shared channel. In the channel, select the Workflow app from the message extension or the “+” button. This ensures the workflow is scoped to the shared channel and uses the correct permissions.
5. Test the flow in Power Automate
   Open Power Automate at make.powerautomate.com. Find the flow under My flows. Select it and run a test with a sample message. If the test fails, check the error message. Common errors include “403 Forbidden” or “Connection not found.” These indicate that the flow’s connections are invalid for the shared channel tenant.
6. Update the flow’s connections
   In Power Automate, edit the flow and select each action. For each connection, click the “Change connection” button and choose a valid connection. For shared channels, use a connection that belongs to a user in the host tenant. If you are using the Teams connector, make sure the connection is not tied to an external account.

If the Workflow App Is Not in the Shared Channel

Sometimes the Workflow app does not appear in the shared channel’s message area. This happens when the app is not enabled for shared channels. To enable it, go to the Teams admin center and select Teams apps > Permission policies. Edit the global policy or create a new one, then add the Workflow app to the “Allowed apps” list. Assign the policy to the users who need to use the workflow.

If the Flow Still Fails After the Main Fix

Flow shows “Shared channel not supported” error

This error appears when the workflow’s trigger is not compatible with shared channels. For example, the “When a new message is added” trigger works only in standard channels. To fix this, use a trigger that supports shared channels, such as “When a new member is added” or “When a file is created.” Edit the flow in Power Automate and change the trigger.

Flow runs but does not post a message to the shared channel

If the flow runs but the output goes to the wrong channel, check the channel ID in the action. In Power Automate, select the action that posts to Teams and verify the “Team” and “Channel” fields. For shared channels, the channel ID might be different. You can copy the channel ID from the channel URL in Teams.

External users cannot see the workflow in the shared channel

External users in a shared channel may not see the Workflow app if the app is not available for external identities. In the Teams admin center, go to External access > Cross-tenant access settings. Create a policy for the external tenant and allow the Workflow app. Also, ensure that the external user’s tenant has the Workflow app available.

Teams Workflow App in Shared Channel vs Standard Channel

Item	Shared Channel	Standard Channel
External users	Allowed via B2B direct connect	Not allowed without guest access
Workflow owner	Must be a member of the shared channel	Any team member
Trigger compatibility	Limited to supported triggers	All standard triggers
Permission model	Cross-tenant authentication required	Single tenant authentication
Common failure	403 Forbidden or connection errors	Rare, usually due to policy

Now you can diagnose and fix the Teams Workflow app when it cannot run a flow in a shared channel. Start by checking the workflow owner and channel membership. Then verify the app permissions and re-create the workflow if necessary. Finally, test the flow in Power Automate and update connections. For advanced troubleshooting, use the Power Automate “Run history” to see detailed error logs for each run.