Logic Apps never cease to surprise us with new features and different behaviors between the Consumption and Standard tiers. Did you know that when you do an HTTP call inside Logic App Consumption by default, a few internal default HTTP headers are added to your HTTP request? And some of those headers contain sensitive information that shouldn’t be transmitted to external systems? Like our Azure Subscription ID and our Resource Group name.
It turns out it’s also a bit different for Consumption vs. Standard tiers:
- Consumption has more headers, and that contains more sensitive information.
- But the Standard request, luckily for us, doesn’t include those headers. That is a nice improvement made by the LA team, which will make our processes/solutions safer.
Let’s see this in more detail.
To emulate these behaviors, let’s create two Logic Apps Consumptions:
- A simple Logic App with request-response actions like the picture below.

- And another Logic App that calls through the HTTP connector is the first Logic App.

- Now, let’s replicate those two Logic Apps in the Standard tier by creating two stateful workflows with the same logic.
If we test the Logic App Consumption and check the raw outputs of the When an HTTP request is received trigger,

we will see that several headers start with x-ms-workflow-*, and some contain information we shouldn’t share with external systems, the most critical being the subscription ID (x-ms-workflow-subscription-Id). But we share the subscription id, so we can also consider the following ones sensitive:
- x-ms-workflow-id
- x-ms-workflow-system-id
- x-ms-workflow-resourcegroup-name
- x-ms-execution-location
- x-ms-workflow-run-id

Doing the same exercise with the Logic App Standard, we will notice that neither the Subscription ID nor the resource grouped are shared by default. So, there is nothing critical or sensitive shared on those calls:

Thanks, Calle Anderson, for pointing out this behavior.
To lazy to read? We’ve got you covered! Check out our video version of this content!
If you liked the content or found it helpful and want to help me write more content, you can buy (or help buy) my son a Star Wars Lego!