We have in our orgsanisation guidelines that prevent the creation of Azure ressources from a public ip address. So if we try to use the azure plugiin we get an error
Azure Error: RequestDisallowedByPolicy Message: Resource 'digitalaistorage' was disallowed by policy
We can and have set the proxy in the azure.cloud Object but the Deploy tries to do everything through this proxy connection and because of the policy settings it is not possible to create ressources.
If we connect to azure manually we set a proxy and add the azure network to a no_proxy variable.
Is it possible to modify the azure plugin to work with this kind of restriction.
Regards
by: Claus-Peter D. | 7 months ago | Integrations
Comments
We are planning to investigate our Azure network setup policies during May 2025 and will follow up on this thread with our findings and next steps.
---
We've identified a similar or duplicate idea: https://ideas.digital.ai/devops/Idea/Detail/4557. We're linking it here and will be closing it as a duplicate.
This change is planned for 25.3 release.
Following the working session for https://ideas.digital.ai/devops/Idea/Detail/4388 and the changes that were agreed upon, please confirm whether this idea is still relevant.
The customer who originally requested this enhancement resolved the issue by configuring the no-proxy setting at the system level (on the host machine where the proxy is configured).
The Azure plugin supports selecting a configured proxy; however, no_proxy handling should be managed at the system or JVM level.
Implementing no_proxy configuration within the plugin would duplicate existing functionality and increase maintenance complexity.