Sorry that you are still facing this issue. I had a discussion with the team about the problem you are facing and we have a couple of steps you could try to help narrow down the root cause of the issue.
Step 1: We suggest running a PowerShell script locally instead of the UI to test the authentication of your Azure credentials. You would need to install Azure PowerShell module using the command
Install-Module -Name Az -AllowClobber. (Here is Microsoft’s documentation on how to do this).
Next, please run the TestAzure.ps1 (731 Bytes). You will have to enter your
Secret in the script. If it works you should be able to see the Azure Resource Groups you have access to.
Your output should look something like this:
Step 2: If Step 1 works could you please RDP into your server running the Octopus instance and try running the script there? Please note that the script would have to be run on a PowerShell window with the same user permissions used by your Octopus server. By doing this we are eliminating the possibility that there is something blocking on Octopus Server or your Azure credentials.
Step 3: If that works we recommend trying to connect to Azure using a local instance of Octopus Server.
Step 4: If the above steps work, we recommend next logging the outgoing requests rejected by your firewall/proxy. We think there might be an endpoint used by the Azure authentication library that may be blocked.
Hope this helps!