Azure Public IP Not Associated
A static public IP is billed while it is reserved, and one attached to nothing is holding an address out of the pool for no traffic.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Delete unattached public IP address. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
In one click, ZopNight deletes the resource, then checks the change took. When someone other than an admin starts a pause or a delete, an admin approves it first.
- Applies to
- Public IP on Azure
- The fix, by hand
- Open Portal → Public IP addresses → the resource, confirm Associated to is empty.
- Note the IP value. Grep customer config, Application Gateway listeners, and DNS zones for that literal IP.
- If anything references it: re-associate the IP to that resource instead of deleting.
- If genuinely orphan: Delete from the IP's Overview page. Confirm by name.
ZopNight does this for you in one click.
- Category
- Orphaned resources. Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1363- Full reference
Related checks
See the orphaned resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.