Power Platform Community Forum Thread Details

Receiving this error while using 'Post to a channel when a webhook request is received'.

Error message : Admin data policy 'Connectors' restricts use of these apis: TeamsWebhookRequestReceived.

Categories:

The error "Admin data policy 'Connectors' restricts use of these APIs: TeamsWebhookRequestReceived" occurs because your Power Platform DLP (Data Loss Prevention) policy is blocking the Teams Webhook connector from being used in your environment.

Why Is This Happening?

DLP policies are set by admins to prevent certain connectors from being used together in a flow.
The Teams Webhook is categorized as a Business, Non-Business, or Blocked connector based on how your organization's policies are configured.
If it's blocked or in a different policy group than other connectors in your flow, Power Automate will not allow the webhook to be used.

How to Fix It?

1. Check Your Environment's DLP Policies

Go to Power Platform Admin Center:
https://admin.powerplatform.microsoft.com/
Navigate to Data Policies under Environments.
Look for a policy that restricts Teams Webhooks.

2. Adjust the DLP Policy (If You Have Admin Access)

If you are an admin, modify the policy to:
- Move the Teams Webhook connector to the same category (Business/Non-Business) as other connectors in your flow.
- Ensure it's not blocked.

3. Contact Your Power Platform Admin

If you don’t have admin access, reach out to your Power Platform or Microsoft 365 admin and request the Teams Webhook connector to be allowed in your environment.

4. Workaround: Use Power Automate's Built-in Teams Actions

If modifying the DLP policy isn't an option, consider using Power Automate’s built-in "Post a message in a channel" action instead of the webhook.

Summary

🔹 Your organization's DLP policy is blocking the Teams Webhook connector.
🔹 You need admin access to check and modify the policy.
🔹 If you’re not an admin, contact your IT team to adjust the policy.
🔹 Alternative: Use Power Automate's standard Teams actions instead of a webhook.