<p>What are you trying to achieve?
If your goal is to run build agents to execute pipelines on premises, then you don't have to allow inbound access. Build agents will query Azure DevOps for any new jobs, so the connections are actually outbound.</p>

CC BY-SA 4.0
2020-12-26T10:22:43.587Z
2020-12-26T10:22:43.587Z
Piotr Gwiazda
<p>Do I need to allow Azure DevOps access to the On-Premises environment? According to the document at &quot;https://docs.microsoft.com/en-us/azure/devops/organizations/security/allow-list-ip-url? view = azure-devops, &quot; on &quot;Inbound connections&quot; connections are made from the 191.235.226.0/24 (Brazil South) network, but we are receiving connections to our IPs 40.65.126.175, 40.117.36.92 and 52.152.147.38.</p>
<p>And the IPs are changed with each access making it impossible to restrict access.</p>
<p>Know someone who can answer?</p>

<azure><firewall>
Azure Devops x On-Premises
likith sunny
# Azure Devops x On-Premises

(Asked by: username_0 on 2020-12-26)

Do I need to allow Azure DevOps access to the On-Premises environment? According to the document at "https://docs.microsoft.com/en-us/azure/devops/organizations/security/allow-list-ip-url? view = azure-devops, " on "Inbound connections" connections are made from the 191.235.226.0/24 (Brazil South) network, but we are receiving connections to our IPs 40.65.126.175, 40.117.36.92 and 52.152.147.38.

And the IPs are changed with each access making it impossible to restrict access.

Know someone who can answer?

**Tags:** azure, firewall


---

## 1 answers

### Answer by username_1 on 2020-12-26. Score: 1

What are you trying to achieve?
If your goal is to run build agents to execute pipelines on premises, then you don't have to allow inbound access. Build agents will query Azure DevOps for any new jobs, so the connections are actually outbound.


---

