401 Unauthorized HTTP Request Trigger in Logic App

Question

401 Unauthorized HTTP Request Trigger in Logic App

Clint Meade 0

I have an integration partner receiving a 401 UNAUTHORIZED when hitting my HTTP Request trigger to post JSON payload. Works for me from postman, are they doing something wrong?

Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-10-02T20:32:46.8166667+00:00
Hi Clint Meade,

Thank you for posting your question in the Microsoft Q&A forum

The 401 Unauthorized error your integration partner is receiving when hitting your HTTP Request trigger in Logic App is typically due to missing or incorrect authentication credentials.

Since it works for you in Postman but not for them, likely reasons are:

They are not sending the required authentication token or header that your Logic App expects.

The HTTP method or URL they are using may be incorrect.

They may not be using the SAS token or API key if your endpoint requires it.

The security settings on the Logic App may restrict access to certain callers or require specific permissions.

You can verify the following

Ensure they use the exact same HTTP method (POST/GET) and URL including any SAS tokens or query parameters.

Confirm authentication details like headers or tokens are correctly included.

Check if the Logic App has IP restrictions or additional authentication schemes enabled.

You can also review the Logic App run history and diagnostics to see why the request was rejected.

Enable Diagnostic Logs

Enable Diagnostic Logs for your Logic App to capture detailed information about incoming requests:

Navigate to your Logic App > Diagnostic Settings.

Send logs to Log Analytics, Storage Account

Reference

https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-create-api-app

https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-securing-a-logic-app?tabs=azure-portal

https://learn.microsoft.com/en-us/azure/logic-apps/view-workflow-status-run-history?tabs=consumption

Kindly let us know if the above helps or you need further assistance on this issue.

Please "Upvote" if the information helped you. This will help us and others in the community as well.

Thanks
Clint Meade 0 Reputation points

2025-10-02T20:41:22.39+00:00

Not helpful. I've reviewed all the basics multiple times and have used countless logic Apps. They too are successful using postman. There are no IP or other access restrictions. Gotta be something else or unique with how they are posting. Also, I've enabled logging via diagnostic settings and I can see the logs for successful posts but not the posts returning the below. Is there a way to check that ms-request-id below to see what's going on? I've attempted to replicate the 401 but everything I change still results in a successful post response with a 200.

They supplied the following response data:

"responseData":{"headers":{"Content-Length":["254"],"Content-Type":["application/json; charset=utf-8"],"Date":["Thu, 02 Oct 2025 15:48:22 GMT"],"Cache-Control":["no-cache"],"Expires":["-1"],"Pragma":["no-cache"],"Strict-Transport-Security":["max-age=31536000; includeSubDomains"],"x-ms-request-id":["northcentralus:ddf49562-52c8-4c23-b24c-9d7dd2064d98"]},"body":"","statusCode":"UNAUTHORIZED","statusCodeValue":401}}]
Rakesh Mishra 9,080 Reputation points Microsoft External Staff Moderator

2025-10-06T09:42:54.2066667+00:00

Hi Clint Meade, following up to see if you had a chance to check Pashikanti Kumar's previous response and if it was helpful. Please do let me know if you're still facing the issue and need any further assistance on this.
Anonymous

2025-10-08T17:44:13.5833333+00:00

Hi Clint Meade,
I hope you check previous response and if it was helpful. Please do let me know if you're still facing the issue and need any further assistance on this.
Thanks

1 answer

Your answer

Pashikanti Kumar 1,725 Reputation points Microsoft External Staff Moderator

2025-10-02T20:32:46.8166667+00:00

Hi Clint Meade,

Thank you for posting your question in the Microsoft Q&A forum

The 401 Unauthorized error your integration partner is receiving when hitting your HTTP Request trigger in Logic App is typically due to missing or incorrect authentication credentials.

Since it works for you in Postman but not for them, likely reasons are:

They are not sending the required authentication token or header that your Logic App expects.

The HTTP method or URL they are using may be incorrect.

They may not be using the SAS token or API key if your endpoint requires it.

The security settings on the Logic App may restrict access to certain callers or require specific permissions.

You can verify the following

Ensure they use the exact same HTTP method (POST/GET) and URL including any SAS tokens or query parameters.

Confirm authentication details like headers or tokens are correctly included.

Check if the Logic App has IP restrictions or additional authentication schemes enabled.

You can also review the Logic App run history and diagnostics to see why the request was rejected.

Enable Diagnostic Logs

Enable Diagnostic Logs for your Logic App to capture detailed information about incoming requests:

Navigate to your Logic App > Diagnostic Settings.

Send logs to Log Analytics, Storage Account

Reference

https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-create-api-app

https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-securing-a-logic-app?tabs=azure-portal

https://learn.microsoft.com/en-us/azure/logic-apps/view-workflow-status-run-history?tabs=consumption

Kindly let us know if the above helps or you need further assistance on this issue.

Please "Upvote" if the information helped you. This will help us and others in the community as well.

Thanks
Clint Meade 0 Reputation points

2025-10-02T20:41:22.39+00:00

Not helpful. I've reviewed all the basics multiple times and have used countless logic Apps. They too are successful using postman. There are no IP or other access restrictions. Gotta be something else or unique with how they are posting. Also, I've enabled logging via diagnostic settings and I can see the logs for successful posts but not the posts returning the below. Is there a way to check that ms-request-id below to see what's going on? I've attempted to replicate the 401 but everything I change still results in a successful post response with a 200.

They supplied the following response data:

"responseData":{"headers":{"Content-Length":["254"],"Content-Type":["application/json; charset=utf-8"],"Date":["Thu, 02 Oct 2025 15:48:22 GMT"],"Cache-Control":["no-cache"],"Expires":["-1"],"Pragma":["no-cache"],"Strict-Transport-Security":["max-age=31536000; includeSubDomains"],"x-ms-request-id":["northcentralus:ddf49562-52c8-4c23-b24c-9d7dd2064d98"]},"body":"","statusCode":"UNAUTHORIZED","statusCodeValue":401}}]
Rakesh Mishra 9,080 Reputation points Microsoft External Staff Moderator

2025-10-06T09:42:54.2066667+00:00

Hi Clint Meade, following up to see if you had a chance to check Pashikanti Kumar's previous response and if it was helpful. Please do let me know if you're still facing the issue and need any further assistance on this.
Anonymous

2025-10-08T17:44:13.5833333+00:00

Hi Clint Meade,
I hope you check previous response and if it was helpful. Please do let me know if you're still facing the issue and need any further assistance on this.
Thanks

Answer 1

Hi Clint Meade,

Verify Authentication Setup:

Confirm the Logic App HTTP trigger's authorization settings—does it use Function keys, Shared Access Signature (SAS), or OAuth?
If using function keys, ensure the partner includes the key in the URL query string or the Authorization header exactly.
For OAuth or API-authorized endpoints, verify the token is correctly obtained and presented.

Use Diagnostic Logs and x-ms-request-id:

With the provided x-ms-request-id, search Azure Monitor or Log Analytics for detailed failure context.
In the Azure portal’s "Monitor" > "Logs" section linked to your Logic App’s resource, run:

AzureDiagnostics | where requestId_s == "northcentralus:ddf49562-52c8-4c23-b24c-9d7dd2064d98"

This can expose why the request was rejected even if it does not appear in run history.

Recreate the Logic App Trigger or Connector:

· If nothing else helps, recreate the HTTP trigger or API connection in Logic App to reset any hidden config errors.

Reference

Check workflow status, view run history, and set up alerts - Azure Logic Apps | Microsoft Learn

Kindly let us know if the above helps or you need further assistance on this issue.

Please "Upvote" if the information helped you. This will help us and others in the community as well.

Thanks

Share via

401 Unauthorized HTTP Request Trigger in Logic App

1 answer

Your answer