Network configuration
If your organization uses firewalls or other network security systems, these may block requests based on policies such as geolocation filtering or IP restrictions. In such cases, whitelisting is required to ensure uninterrupted connectivity. Lobyco APIs are exposed through Azure Front Door, Microsoft’s global edge network service. This setup allows us to provide you with high availability, low latency, and enhanced security. Azure Front Door doesn’t offer static or dedicated frontend anycast IPs at this time. To avoid blocked requests or failed API calls, please ensure that your firewall and network security systems are configured to whitelist the Azure Front Door IP ranges. These IPs are published underAzureFrontDoor.Frontend service tag in the official Azure IP Ranges and Service Tags dataset. This file is updated weekly. New ranges appearing in the file will not be used in Azure for at least one week. Please download the new json file every week and perform the necessary changes at your site to correctly identify services running in Azure.
Automate updates by running a script that fetches the latest IP ranges. As a best practice, this script should run daily to guarantee your configuration is always aligned with Microsoft’s updates. This way you never miss an update, even if Microsoft pushes an emergency change.
Recommendation: If you use firewalls inside Azure (such as Network Security Groups or Azure Firewall), consider using service tags (e.g. AzureFrontDoor.Frontend) instead of hardcoding IP addresses. This simplifies configuration and ensures you automatically stay aligned with Microsoft’s updates.
AzureFrontDoor.Frontend service tag must be whitelisted explicitly, since service tags cannot be used directly.