I've ran into a Cloud/SaaS use case where we'd really like to have this feature.Our customer needs to connect to an external API (using the HttpClient object) that uses allowlisting/whitelisting.Unfortunately Business Central Cloud/SaaS doesn't define a dedicated IP range where all HttpClient connections originate from. In short, in static allowlist scenarios one should add all AzureCloud. (westeurope in our case) ranges.Adding a complete Azure cloud region to the allowlist is unacceptable for the third party.So, we'll have to add some sort of proxy/middleware/API Management in between to let the IP connections originate from Business Central.As an added complicating factor, the connection to the third party needs to work with a client certificate. This is well supported in modern BC versions, so from a an On-Premise install (with allowlisted IP address(es)) this works flawlessly.If we were able to use a proxy on the HttpClient object we would be able to "just" use any explicit forward proxy and still let the encryption and client certificate handling be done by Business Central.Unfortunately, without proxy support in AL (or as Volker Krausse suggested: extension/tenant wide support in BC for a proxy for every HttpClient), we'll have to come up with a different solution where we're connecting to some middleware (With a static IP address) that creates another connection to the third party. This means the middleware will need to know about and use the client certificate. And this also means that now there is a different place where administration needs to happen to keep this interface up and running. We'd really like to see this become simpler in the future.So, yes, we would really like to allow setting a Proxy for the HttpClient in SaaS/Cloud scenarios.