Register the Azure Pipelines Agent with Its Proxy Inputs

Supply proxy URL and account at agent configuration, then follow task, external-tool and container requests separately.

./config.sh --proxyurl http://proxy.example:8080 \
  --proxyusername PROXY_USER \
  --proxypassword PROXY_PASSWORD

Add these parameters to the installation's normal registration inputs. Use config.cmd on Windows and obtain real account values through the deployment's credential handling.

The recorded proxy covers Azure DevOps communication and built-in source/artifact operations. Tasks obtain exposed proxy information through the task library and must apply it to their own HTTP clients.

External curl, dotnet or Maven needs its own supported input. Container jobs also need a reachable endpoint from their network; the host agent's loopback means another location there. Earlier image pulls are a container-runtime request.

For a proxy accepting Basic fallback when setup gets 407, the documented --usebasicauthforproxy flag selects that path; it cannot add a mechanism the proxy does not support.

In a generated deployment-group script, add the inputs to its config.cmd invocation while preserving organization and group arguments. A parent PowerShell WebRequest.DefaultWebProxy change is not the child's agent configuration.

Artihkkalat mat laktásit