Skip to content
LogScale Self-Hosted
This is an archived version of the documentation downloaded from LogScale Documentation Archives. Up to date documentation, and documentation for later versions, is available on LogScale Documentation

## `INGEST_FEED_AZURE_USE_PROXY`

Option | `INGEST_FEED_AZURE_USE_PROXY`
Description | Controls whether the system routes Azure service connections through a proxy server during data ingestion. When set to `true`, instructs LogScale to use configured proxy settings for Azure connections.
Default | `true`

When set to `true`, LogScale will route all Azure Event Hub connections through the configured HTTP proxy. This utilizes the general proxy settings defined in the LogScale configuration.

When set to `false`, LogScale will connect directly to Azure services without going through the proxy. This might be necessary in environments where Azure services are directly accessible, or when using specialized network configurations.

For this setting to work, you must configure the general HTTP proxy settings in LogScale: `HTTP_PROXY_HOST`, `HTTP_PROXY_PORT`, `HTTP_PROXY_NAME` (optional), and `HTTP_PROXY_PASSWORD` (optional).

Note that this parameter is only controlling proxy use for ingestion. To control proxy use for Azure export operations, see `AZURE_EXPORT_USE_HTTP_PROXY`. To control proxy use for Azure storage operations, see `AZURE_STORAGE_USE_HTTP_PROXY`.

#### Enter search term