Fix Teams Workflow App Cannot Run a Flow after a Policy Update

After your organization updates Teams policies, the Workflow app may stop running flows. You see an error like “Flow failed to start” or “The workflow could not be triggered.” This typically happens because the policy update changed the permissions that the Workflow app uses to access Teams data. This article explains the exact causes and provides step-by-step fixes for both end users and administrators.

The Workflow app relies on Microsoft Power Automate to run flows inside Teams. When an admin changes Teams app permission policies, data policies, or connector sharing settings, existing flows can lose their required access. You will learn how to diagnose the failure, repair the flow’s connection, and adjust the correct policy settings to restore functionality.

Why Teams Workflow App Stops Running Flows After a Policy Update

The Workflow app in Teams runs on Power Automate. Each flow contains one or more connections to services like Teams, Outlook, or SharePoint. When an admin updates a policy, the change can revoke or alter the permissions attached to those connections. The flow then cannot authenticate, so the trigger fails.

Policy Types That Affect the Workflow App

Three main policy categories control the Workflow app:

• Teams app permission policies determine whether the Workflow app is visible and usable for a user. If the policy was changed to block the app, the flow cannot start from Teams.
• Data loss prevention policies in Power Automate can block the Teams connector entirely. Even if the app is allowed, the flow cannot use a blocked connector.
• Connector sharing policies control which users can share connections. A policy update can remove a user’s access to a shared connection, breaking the flow.

Steps to Diagnose and Fix the Workflow App Flow Failure

Follow these steps in order. Each step addresses a common cause. Stop when the flow works again.

Step 1: Check the Flow Run History

1. Open Power Automate
   Go to make.powerautomate.com and sign in with your work or school account. This is the web portal for managing all flows.
2. Select My flows
   In the left navigation, click My flows. Find the flow that failed. Look at the Run history column to see the most recent run status.
3. Open the failed run
   Click the failed run. On the run details page, expand each step. Look for a red error icon. The error message usually says “Connection not found” or “Access denied.” Write down the exact error text.

Step 2: Re-authenticate the Teams Connection

1. Open the flow editor
   In Power Automate, click the name of your flow to open the editor.
2. Find the connection
   Scroll through the flow steps. Each step that uses Teams or another service shows a connection name. Click the connection name. If the connection is invalid, you see a yellow warning icon.
3. Sign in again
   Click Sign in next to the connection. Enter your credentials when prompted. If you have multiple accounts, choose the same account that you use in Teams.
4. Save and test
   Click Save in the top right. Then click Test and choose Manually trigger to run the flow. If it succeeds, the issue was a stale connection.

Step 3: Verify the Workflow App Permission Policy

1. Open Teams admin center
   Go to admin.teams.microsoft.com and sign in as a Teams administrator.
2. Go to permission policies
   In the left menu, expand Teams apps, then click Permission policies. Click the policy that applies to the affected user.
3. Check the Workflow app
   In the policy settings, find Microsoft Apps. Confirm that Workflow is set to Allowed. If it is blocked, change it to Allowed and click Save.
4. Wait for propagation
   Policy changes can take up to 24 hours to propagate. Ask the user to sign out and sign back in to Teams to speed up the update.

Step 4: Check Data Loss Prevention Policies

1. Open Power Automate admin center
   Go to admin.powerplatform.microsoft.com and sign in as a Power Platform administrator.
2. Select Data policies
   In the left menu, click Data policies. You see a list of DLP policies.
3. Examine each policy
   Click each policy and look at the Connectors tab. Find the Teams connector. If it is in the Blocked group, the flow cannot use it. Move Teams to the Business or Non-business group, depending on your organization’s rules.
4. Save and test again
   Click Save. Then go back to the flow and run a manual test. If the flow works, the DLP policy was the cause.

Step 5: Recreate the Flow from the Workflow App

1. Open the Workflow app in Teams
   In Teams, go to Apps and search for Workflow. Open the app.
2. Find your flow
   The app shows a list of your flows. If the broken flow appears, click it. If not, the app is not loading it due to a permission issue.
3. Create a new flow
   Click Create and choose a template that matches your original flow. Reconfigure the steps and connections. This gives you a fresh flow with correct permissions.

If Teams Workflow App Still Cannot Run a Flow

Teams Workflow App Shows “You Don’t Have Access”

This error appears when the user is not assigned to a permission policy that allows the Workflow app. The fix is to update the user’s permission policy in the Teams admin center. Go to Users > Manage users, select the user, and click Policies. Assign a policy that allows the Workflow app.

Flow Runs but Fails at a Specific Step

If the flow starts but errors at the same step every time, the connection for that step is broken. Open the flow editor and re-authenticate the connection for that step. If the step uses a service like SharePoint or Outlook, check that the user still has access to that service.

Flow Disappeared from the Workflow App

The flow is likely hidden because the app permission policy was changed. After the policy update, the app may not display flows created under a different environment. Open Power Automate, go to Solutions, and check the environment. Move the flow to the default environment if needed.

Teams Workflow App vs Power Automate Portal: Key Differences

Item	Teams Workflow App	Power Automate Portal
Access point	Inside Teams under Apps	Web browser at make.powerautomate.com
Flow management	Simplified list and creation	Full editor with run history and advanced settings
Policy visibility	No admin policy settings	DLP and environment policies visible
Best for troubleshooting	Quick creation and testing	Detailed error diagnosis and connection repair

You now know how to fix a Workflow app flow that fails after a policy update. Start by re-authenticating the connection in Power Automate, then check the Teams permission policy and DLP policies. If the flow still fails, recreate it from the Workflow app. After the fix, test the flow with a manual trigger to confirm it works. For future changes, always check the run history first — it shows the exact error and saves you time.