Logic App Standard deploy issue: Error 403 – Forbidden

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.

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 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 form example, POSTMAN – in this case, we endup getting the same error: 403 Forbidden. That proved that it was indeed a network issue from our developer machine and the Logic App Standard.

Solution

In our case, we contact 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! 

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published. Required fields are marked *

turbo360

Back to Top