Forum Discussion
Petri-X
Aug 16, 2024Bronze Contributor
Creating Workflows is disabled in somewhere
Hi,
I was following this guide: Prerequisites to get the the predefined workflow (Post to a channel when a webhook request is received) done. In the next section in step seven instead of having positive sign, I do have a message "Looks like this workflow is disabled by your organization".
Anybody knows what other prerequisites the Workflow could have? What else I should have enabled? Somewhere I saw info that I should have "Entra ID \ Logic Apps" enabled, but that is not so clearly stated in anywhere. Something should be enabled (or not locked) in Power Apps site?
- bedo1976_Copper Contributor
I had also this issue
You can check Microsoft Teams / More Apps / Workflow that the workflow was created but set to inactive. If you activate the workflow you receive more details information, why it was blocked. Im my case "Admin data policy "xyz" restricts use of these apis
Check and modify the Power Platform admin center / policies / data policies:
https://admin.powerplatform.microsoft.com/dlp - Prasad_Das-MSFT
Microsoft
Petri-X - Thanks for raising your issue. We are also facing the same issue and have raised a bug for the same and engineering team is looking into it. We will inform you once we get any further update.
Thanks!
- Petri-XBronze Contributor
Do you see the same:
1. Go to microsoft365.com and Power Automate (or directly powerautomate.com)
2. Great the same workflow than on Teams. The steps are the same.
3. When you hit [create] I'm getting an error: "Admin data policy 'Data Policy XYZ' restricts use of these apis: TeamsWebhookRequestReceived."
I believe this is my issue:
Need to find way if that can be enabled.
- Prasad_Das-MSFT
Microsoft
Petri-X , we got update from engineering team stating that, this is expected when the tenant has a DLP policy that does not allow webhooks in their default environment.
Flows using that webhook are disabled.
- Petri-XBronze Contributor
Nice to hear that I'm not alone with this 🙂
But I'm not sure if this is really a bug, or more likely some security configuration in a tenant.