Azure Function dotnet-isolated servicebus trigger proxy

Question

Jinalkumar Patel 21

This is mainly related to proxy settings for Azure Function with ServiceBusTrigger or output binding.

dotnet-isolated (dotnet 5)
dotnet-isolated (dotnet 6) ( I am sure this settings is not there for inprocess)

Now normally when I upload function to Azure env, it works fine. There is always issue with working locally in restricted env.

My scenario

For localdevelopment entire team working behind proxy and servicebus trigger is not working and output binding too.
For binding we solve using ServiceBusClient as it provide configuration for proxy but same is not there for "ServiceBusTrigger" and it is not trigger at all.

As I am working on complex system , calling servicebustrigger function with http endpoint is also a problem.

Two things.

Why there is no proxy setting ? ( Because that available for WebJob and console application).

MughundhanRaveendran-MSFT 12,511 Reputation points

2021-11-26T06:22:46.063+00:00

@Jinalkumar Patel ,

I didnt understand your question/ask properly.

Are you trying to use Azure functions as a proxy? or the function app is behind a proxy as a backend url/api?

I am not sure how you are triggering a servicebus function using http endpoint, we dont have any documentations on this.

In your question :Why there is no proxy setting ? Which proxy settings are you referring to? Could you please point out some articles/Microsoft documentation?

I will be able to provide a proper answer once I have some clarity
Jinalkumar Patel 21 Reputation points

2021-11-27T06:15:05.627+00:00

Let me try to clarify.

I am not using Azure Function as a proxy.

I am using Azure Function App behind proxy. So proxy is blocking 5672 and 5671 port.

Also if I use servicebusclient to send message and if I configure WebProxy and TransportMode = websocket then it is working for sending and it is working for receive too.

For ServiceBusTrigger for Azure function there is no configuration for proxy so it is not working and also for trigger I can not change transport mode.
MughundhanRaveendran-MSFT 12,511 Reputation points

2022-01-13T07:19:16.213+00:00

Could you please try to set the transport mode to websocket in connection string and see if that helps?

Your answer

MughundhanRaveendran-MSFT 12,511 Reputation points

2021-11-26T06:22:46.063+00:00

@Jinalkumar Patel ,

I didnt understand your question/ask properly.

Are you trying to use Azure functions as a proxy? or the function app is behind a proxy as a backend url/api?

I am not sure how you are triggering a servicebus function using http endpoint, we dont have any documentations on this.

In your question :Why there is no proxy setting ? Which proxy settings are you referring to? Could you please point out some articles/Microsoft documentation?

I will be able to provide a proper answer once I have some clarity
Jinalkumar Patel 21 Reputation points

2021-11-27T06:15:05.627+00:00

Let me try to clarify.

I am not using Azure Function as a proxy.

I am using Azure Function App behind proxy. So proxy is blocking 5672 and 5671 port.

Also if I use servicebusclient to send message and if I configure WebProxy and TransportMode = websocket then it is working for sending and it is working for receive too.

For ServiceBusTrigger for Azure function there is no configuration for proxy so it is not working and also for trigger I can not change transport mode.
MughundhanRaveendran-MSFT 12,511 Reputation points

2022-01-13T07:19:16.213+00:00

Could you please try to set the transport mode to websocket in connection string and see if that helps?