Deploy an Azure Resource Manager template - MSAL doesn't respect Octopus Custom Proxy - 2023.2+

[FinnianDempsey]

Severity

Not Blocking, Workaround Exists

Version

2023.2.13239

Latest Version

I could reproduce the problem in the latest build

What happened?

When a proxy is configured as a Custom proxy in Octopus and the proxy in Internet Explorer is disabled, deployments that use MSAL such as Deploy an Azure Resource Manager template won't use the configured proxy.

Reproduction

1. Configure a custom proxy in Octopus
2. Make sure the proxy in windows is also disabled
3. Deploy an ARM template
4. Fail due to proxy not used

Error and Stacktrace

12:11:19 Error | A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (login.windows.net:443)

More Information

Internal - Slack
Internal - Slack RND
Internal - Zendesk

Workaround

Don't use the "Use a custom proxy server" in Octopus and configure the proxy in Windows instead

[octoreleasebot]

Release Note: Fixed an issue where some azure deployments did not respect proxy configured in Octopus

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2023.2	2023.2.13363
2023.3	2023.3.13091
2023.4	2023.4.5965
2024.1+	all releases