Azure Functions Service Bus Trigger Proxy Settings in host.json

Use Service Bus extension 5.x host.json webProxy with amqpWebSockets, rather than configuring another ServiceBusClient in function code.

{
  "version": "2.0",
  "extensions": {
    "serviceBus": {
      "transportType": "amqpWebSockets",
      "webProxy": "http://proxy.example:8080"
    }
  }
}

Merge this into the existing Functions host configuration. The binding extension creates the trigger's client; a separately constructed client in function code does not replace it.

Extension 5.x supports webProxy with amqpWebSockets, not amqpTcp. Keep namespace/authentication in the existing Service Bus connection setting. For a public Service Bus namespace where public intermediaries are permitted, the HTTP proxy list provides candidates for the no-account webProxy URL.

The application-setting equivalents are:

AzureFunctionsJobHost__extensions__serviceBus__transportType=amqpWebSockets
AzureFunctionsJobHost__extensions__serviceBus__webProxy=http://proxy.example:8080

Use that double-underscore hierarchy in environment settings, or entries under local development local.settings.json's Values. They are host settings, not connection-string fields.

Match the installed extension generation. An isolated worker's independent HTTP or Service Bus client still needs its own route.

Artihkkalat mat laktásit