Logic app work flow with Request trigger url with redirect url

Question

Logic app work flow with Request trigger url with redirect url

Betty Xu (Yun) (202) 86

I created a work flow with request trigger in Standard logic app. Request method is "POST" and message in Json.

I can trigger the work flow using the request original url from Postman without a problem.

We want to use F5 redirects the call with better url (more meaningful), every time I use the redirect url to trigger the workflow, I received error - "Microsoft Azure Web App - Error 404".

Can you tell if we want to use F5 for redirect what we need to do?

Thanks!

Praveen Kumar Gudipudi 2,290 Reputation points Microsoft External Staff Moderator

2025-09-15T14:44:00.41+00:00

Betty Xu (Yun) (202),

Thanks for reaching out.

Could you please share the steps you're taking so I can validate them on my end?
Betty Xu (Yun) (202) 86 Reputation points

2025-09-15T15:26:12.9333333+00:00

Working one with my work flow original url:

The redirect url behind our F5:

The original url I got from

I don't know whether you can reproduce the problem as there is firewall block. I just want to know in general processes to share with my network folks.
Praveen Kumar Gudipudi 2,290 Reputation points Microsoft External Staff Moderator

2025-09-15T15:46:09.3633333+00:00
Betty Xu (Yun) (202),

When a HTTP request is received trigger will automatically generate the URL, and it cannot be changed manually.

This URL includes query parameters that specify a Shared Access Signature (SAS) key, which is used for authentication.

I haven't thought of a way to completely customize the URL to https://MyDnsName.com/Path/Action, but there are two ways to make it look more meaningful.

1. Function App Proxy

After you create an Azure Function App, you can create an proxy.

After you create Azure Function App proxy, your URL is in this format:

https://<function-name>.azurewebsites.net/xxx

2. API management

After creating an Azure API Management service instance, you can customize the URL suffix.

After you create a API management, your URL is in this form:

https://<API management-name>.azure-api.net/xxx

Please try above suggested steps to customize URI of http trigger.
Anonymous

2025-09-16T06:50:24.0433333+00:00

@Anonymous Just checking to see if you have a chance to check previous response shared by @Praveen Kumar Gudipudi and helped, do let us know if you have any further questions on this.
Anurag Rohikar 3,190 Reputation points Microsoft External Staff Moderator

2025-09-17T09:52:17.1433333+00:00

Hello Betty Xu (Yun) (202), following up to see if you have a chance to check the previous response by Praveen Kumar Gudipudi and helped, do let me know if you have any further questions on this. Thank you!
Betty Xu (Yun) (202) 86 Reputation points

2025-09-19T18:14:00.01+00:00

Yes, after I removed ":443" then it works! Thanks for the helps!
Betty Xu (Yun) (202) 86 Reputation points

2025-09-19T18:20:00.5833333+00:00

We are doing a different way - not using API management for proxy, instead system wants to use "F5" to redirect. Thanks you for the idea you provided and it sounds a better approach.

1 answer

Your answer

Praveen Kumar Gudipudi 2,290 Reputation points Microsoft External Staff Moderator

2025-09-15T14:44:00.41+00:00

Betty Xu (Yun) (202),

Thanks for reaching out.

Could you please share the steps you're taking so I can validate them on my end?
Betty Xu (Yun) (202) 86 Reputation points

2025-09-15T15:26:12.9333333+00:00

Working one with my work flow original url:

The redirect url behind our F5:

The original url I got from

I don't know whether you can reproduce the problem as there is firewall block. I just want to know in general processes to share with my network folks.
Praveen Kumar Gudipudi 2,290 Reputation points Microsoft External Staff Moderator

2025-09-15T15:46:09.3633333+00:00

Betty Xu (Yun) (202),

When a HTTP request is received trigger will automatically generate the URL, and it cannot be changed manually.

This URL includes query parameters that specify a Shared Access Signature (SAS) key, which is used for authentication.

I haven't thought of a way to completely customize the URL to https://MyDnsName.com/Path/Action, but there are two ways to make it look more meaningful.

1. Function App Proxy

After you create an Azure Function App, you can create an proxy.

After you create Azure Function App proxy, your URL is in this format:

https://<function-name>.azurewebsites.net/xxx

2. API management

After creating an Azure API Management service instance, you can customize the URL suffix.

After you create a API management, your URL is in this form:

https://<API management-name>.azure-api.net/xxx

Please try above suggested steps to customize URI of http trigger.
Anonymous

2025-09-16T06:50:24.0433333+00:00

@Anonymous Just checking to see if you have a chance to check previous response shared by @Praveen Kumar Gudipudi and helped, do let us know if you have any further questions on this.
Anurag Rohikar 3,190 Reputation points Microsoft External Staff Moderator

2025-09-17T09:52:17.1433333+00:00

Hello Betty Xu (Yun) (202), following up to see if you have a chance to check the previous response by Praveen Kumar Gudipudi and helped, do let me know if you have any further questions on this. Thank you!
Betty Xu (Yun) (202) 86 Reputation points

2025-09-19T18:14:00.01+00:00

Yes, after I removed ":443" then it works! Thanks for the helps!
Betty Xu (Yun) (202) 86 Reputation points

2025-09-19T18:20:00.5833333+00:00

We are doing a different way - not using API management for proxy, instead system wants to use "F5" to redirect. Thanks you for the idea you provided and it sounds a better approach.

Answer 1

Betty Xu (Yun) (202) 86

The problem was fixed. The answers above provided several ways to tackle the problem. Thanks!

Anurag Rohikar 3,190 Reputation points Microsoft External Staff Moderator

2025-09-22T13:28:33.4033333+00:00

Hello Betty Xu (Yun) (202), Glad to hear it worked out! Appreciate you circling back to let us know.

Share via

Logic app work flow with Request trigger url with redirect url

1 answer

Your answer