A few weeks ago, we endup encountering a forbidden issue while trying to deploy a couple of workflows to a brand new Logic App Standard:
Error 403 – Fordidden
In our case, we were using a brand new Logic App Standard with VNet integration.
📝 One-Minute Brief
When deploying Azure Logic Apps Standard workflows, you may encounter the error 403 – Forbidden, which blocks deployments even when permissions appear correct. This post explains why this issue usually occurs in Logic Apps Standard environments with VNET integration, how network restrictions can cause deployment failures, and what configuration change is required to unblock and complete the deployment successfully.
Cause
This issue typically occurs when you configure your Logic App Standard to use a VNET, and you may have misconfigured or non-existent network-required configurations.
To better troubleshoot whether there was a missing network configuration between the developer machine or user permission, we ended up manually creating on the Azure Portal a dummy workflow that receives an HTTP request and simply returns a response, and we were able to do that. So, it was not a user permission.
Next, we use this same POC workflow and try to trigger it from our developer machine using a form example, POSTMAN – in this case, we endup getting the same error: 403 Forbidden. That proved it was indeed a network issue on our developer machine and in the Logic App Standard.
Solution
In our case, we contacted the infra team, and it was a simple fix:
- They just need to add a firewall rule to allow the developer machine to be able to access.
I hope you find this helpful! If you liked the content or found it useful and want to help me write more, you can buy (or help me buy) my son a Star Wars Lego!
