Teams channel incoming webhook fails

Selva Saravanakumar 0 Reputation points
2026-08-16T07:32:09.1+00:00

Hi Team,

We’re configuring Microsoft Teams channel alerts using a Power Automate workflow with the “When a Teams webhook request is received” trigger.

Every POST request returns HTTP 404. The response says that the Default Power Platform environment does not exist and shows the environment name with an unexpected CU00 suffix appended to it. It also states that a CustomerManagedKeyJob or SelfHostProvisionJob may be in progress or may have failed.

We tested the callback URL both with and without the scale-unit path, but both formats return the same 404 error with the CU00 suffix. No run appears in the workflow’s run history, suggesting that the request fails in the Power Automate proxy or environment-routing layer before reaching the trigger.

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sayali-MSFT 6,396 Reputation points Microsoft External Staff Moderator
    2026-08-17T09:18:37.23+00:00

    Hello Selva Saravanakumar,
    This does not appear to be a Teams webhook payload or URL formatting issue. Since no run is created in Power Automate, the request is failing before it reaches the trigger. The 404 response mentioning the Default environment, unexpected CU00 suffix, and CustomerManagedKeyJob / SelfHostProvisionJob points to a Power Platform environment provisioning or routing issue.
    Please check the environment health in Power Platform Admin Center, recreate the trigger to regenerate the callback URL, and test in another environment.

    Was this answer helpful?

    0 comments
  2. Jayden-P 1,840 Reputation points Independent Advisor
    2026-08-16T07:39:39.91+00:00

    Hi @Selva Saravanakumar

    Since this question is primarily related to Power Automate / Power Platform, I'd recommend posting it in the Microsoft Power Automate Community. 

    User's image

    That community is dedicated to Power Automate topics and is actively followed by engineers, MVPs, and experienced Power Platform users. They'll be able to provide more targeted troubleshooting about the issue you are facing.

    I hope this redirection helps save you some time and leads you to the most relevant support resources.  

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.