HotDocs Advance Static Outbound IP Addresses

HotDocs Advance sends iManage integration calls and webhook deliveries from a small, fixed set of static outbound IP addresses. If your organization restricts incoming traffic using an IP allowlist, you can add these addresses to your firewall or API gateway rules instead of allowing a broader range of Azure addresses.

Static IP Addresses by Region

The following table lists the static outbound IP address for each region.

Region Static outbound IP address
Central US 9.234.81.43
North Europe 48.222.48.39

Limitations

  • These static outbound IP addresses apply to HotDocs Advance Cloud only. On-premise deployments use your own network egress and are not covered by these addresses.
  • The addresses cover outbound traffic for iManage integration calls and webhook deliveries only. They do not apply to any other Advance traffic, and they are source addresses: the addresses Advance sends from. Add them to the inbound allowlist on your firewall, API gateway or iManage environment; they are not destinations you connect to.
  • All addresses are IPv4.

Failover Behavior

HotDocs Advance runs in more than one Azure region. In normal operation, your outbound iManage and webhook traffic originates from the static IP address for the region that serves your organization. During a regional failover, planned maintenance or if your tenancy is re-homed, that traffic may instead originate from the other region's static IP address.

For this reason, whitelist both static outbound IP addresses, not just the one for your region. Both addresses belong to Advance, so allowing both keeps the integration working through a failover event without widening your allowlist beyond two known addresses. If you whitelist only your region's address, the integration may stop working during a failover until you add the other address.

IP Rotation

These static outbound IP addresses are stable and are not expected to change during normal operation. If a change becomes necessary, Advance will notify affected customers in advance.

iManage and Webhook Traffic

These IP addresses cover outbound traffic for:

  • Calls that Advance makes to your iManage instance.
  • Deliveries from Advance webhooks to your endpoint.