ARTIFACTORY: Transition to Static Inbound IPs for Azure Artifactory Customers

We are pleased to announce that Static Inbound (Ingress) IP addresses are now in full production for JFrog SaaS services hosted on Microsoft Azure.

This transition represents a significant upgrade to our infrastructure, designed to provide our customers with predictable connectivity and streamlined security validation. By moving to a static model, we are enabling organizations with strict firewall requirements to maintain stable connections without the risks associated with dynamic IP changes inherent in cloud-managed load balancers. As part of this infrastructure modernization, JFrog will be decommissioning the older, dynamic IP configurations.

The hard cut-over date is scheduled for August 16th, 2026.

WARNING: Customers who have hardcoded the old IPs in their firewall rules, local DNS overrides, or application configurations will permanently lose traffic connectivity once the dynamic IP configurations are replaced with the new static IPs. To ensure zero downtime for your R&D and DevOps operations, you should transition to the recommended FQDN method.


Required Actions for DevOps and R&D

To prepare for this transition and prevent service interruption, all Azure-based customers must complete the following items:

1. System Audit: Perform a comprehensive review of your network and application configurations. Ensure that no internal systems—including build agents, local proxies, or scripts—contain hardcoded references to the old IP addresses listed in the table below.

2. Update Allowlists: If your corporate security policy prohibits FQDN-based filtering and mandates IP-based rules, update your firewall configurations to include the new static CIDR blocks provided in the reference table.

3. Post-Migration Verification: After updating your firewall rules, verify connectivity to your instance. You can confirm the path is clear by running a simple health check command from within your network: curl https://<your-instance-name>.jfrog.io/artifactory/api/system/ping A 200 OK response confirms that your routing is correctly configured for the new infrastructure.

Technical Note on /29 CIDR Blocks: The new static IPs are provided as /29 CIDR blocks, which represent a range of 8 total IP addresses. This specific format is used solely for Inbound (Ingress) traffic into the JFrog platform; it does not apply to outbound traffic from JFrog (such as webhooks). Providing a block rather than a single IP allows JFrog to rotate addresses within a fixed, predictable range for maintenance and high availability without requiring you to update your firewall rules again.


IP Migration Reference Table

Identify your specific SaaS region in the table below and update your configurations accordingly.

Support and Conclusion

For the vast majority of customers who follow JFrog’s official documentation and use the recommended FQDN-based access, this transition will be completely seamless. We encourage all customers who use hardcoded IP addresses to use this transition to adopt FQDN-based access going forward. However, if your infrastructure relies on explicit IP address entry, you must utilize the current grace period to migrate to the appropriate static CIDR block as soon as possible. 

If you have questions regarding these changes or require technical assistance during this transition, please contact our support team at support@jfrog.com.