Integrations
Connect tenants without write access.
Spot IPAM uses a collector model: one read-only service principal with Reader role per Entra tenant. Collectors never hold Owner or Contributor rights. Spot IPAM syncs VNets, peerings, subnets, and address spaces on a schedule — your subscriptions stay read-only.
-
Azure tenant discovery
One read-only service principal per Entra tenant. Collectors sync VNets, peerings, subnets, and address spaces on a schedule.
-
Live VNet utilisation
Plan CIDR allocations against synced subnet data — see used prefixes and free blocks before you assign a /22 or smaller.
-
Cross-tenant conflict checks
Detect overlaps across Entra tenants, VNet peerings, and on-prem ranges imported from CSV.
-
Azure Private DNS
Reconcile address-space records against Private DNS zones in each connected subscription.
-
Cloudflare DNS
Compare allocated prefixes with Cloudflare DNS records to catch drift between IPAM and public or split-horizon zones.
-
CSV exports
Export the address-space register for handoffs, audits, and ISO 27001 control A.8.20 evidence.
-
IaC webhooks
Allocation events push to Terraform, Bicep, or Pulumi pipelines with tenant and prefix metadata in the payload.
-
REST API
Query inventory, submit allocation requests, and pull audit entries from your automation stack.
Connect a tenant.
-
Create an app registration
In the target Entra tenant, register an application and grant it Reader role on the subscriptions you want inventoried.
-
Add the collector in Spot IPAM
Paste the tenant ID, client ID, and client secret. Spot IPAM validates Reader access and starts the first sync.
-
Review imported address space
VNets, peerings, and subnets appear in the register. Import on-prem ranges from CSV and run a conflict check.