Power Platform Community Forum Thread Details

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.

Categories:

Building flows

Yes,your diagnosis is very likely correct. This does not look like a payload/body or Teams channel configuration problem. It looks like an environment-routing/provisioning problem in the Power Automate webhook endpoint.
Microsoft confirms that “When a Teams webhook request is received” exposes a callback URL and accepts POST requests. If the POST never creates a flow run, the failure is occurring before the trigger execution itself.
1. Check the organization's Default Environment
Go to:
Power Platform admin center → Environments
Confirm:
The environment marked Default
Environment ID
Environment URL
Region
Status = Ready
No provisioning/copy/restore/upgrade operation currently running
The Teams Workflows experience is specifically tied to the organization's default environment; Microsoft states that flows created through the Teams Workflows app are created in the organization's default environment.
If the Default Environment is missing, disabled, stuck in provisioning, or otherwise unhealthy, that is the first thing to resolve.