Issue with Whitelisting Azure IP Ranges for Bot Service

Question

Hello,
I am encountering an issue related to whitelisting Azure IP ranges. I work on a bot solution that utilizes the Azure Bot Service and Microsoft Bot Framework, which we deploy on-premises.

Most of our clients deploy the service behind a firewall. When an issue arises related to IP blocking, we typically refer to the "Azure IP Ranges and Service Tags – Public Cloud" document, available here.

Recently, we encountered a situation where the domain "login.botframework.com" resolved to an IP address, "20.105.232.11", which was not listed in the IP ranges. Upon further investigation, I found that this IP is located in the Netherlands and belongs to Azure.

Could you provide any insights into this issue? Is there a reason why this IP wasn't included in the standard IP range list? Any guidance on how to handle such discrepancies would be greatly appreciated.

Thank you for your help!

Answer 1

@Muhammed Abdulaziz I understand you are using this to whitelist IPs of Azure every week but unfortunately this is a risk that is captured in bot service documentation.

Bot Framework Services is hosted in Azure data centers world-wide and the list of Azure IPs is constantly changing. That means allow-listing certain IP addresses may work one day and break the next as the Azure IP Addresses change.

I feel in this case, the mentioned IP was missed in the JSON. I am not sure how this list gets updated but if this is a dependency for you, try raising a support case to confirm if there is an alternative way to whitelist the required domain or IPs.