This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 5%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHD%3C/text%3E%3C/svg%3E)
Dear Microsoft Azure Team,
We are facing challenges while allowing Azure DevOps (dev.azure.com) through our on-premises firewall.
Our Azure DevOps organization is located in the South India region. We have already allowed the domain dev.azure.com, but we are still encountering connectivity issues. From our firewall logs, we observed that requests are coming via Azure Front Door/CDN with dynamic IPs that change frequently (weekly updates).
Our concern is:
Do we have the possibility to whitelist a single domain or fixed IP range for South India DevOps traffic, instead of allowing multiple dynamic IP ranges for CDN/Front Door?
If not, what is the recommended best practice to securely allow DevOps traffic from South India region to our on-premises servers, while minimizing firewall changes?
We would appreciate your guidance on the most efficient way to configure firewall rules for Azure DevOps connectivity.
Regards,
Hamja D
ACG World
Hi Hamja,
Can you try with wildcard as it will cover all other dependant domain names and you should not face this issue again, can you share this with your FW / Network team?
The new Domain URL https://*.dev.azure.com
Hope this helps.
JS
==
Please Accept the answer if the information helped you. This will help us and others in the community as well.