Standalone NICs not listed in Endpoint node

Open
#371 1 comment 0 reactions 1 assignee View on GitHub

@DCMattyG is already working on this.

Since Dec 2, 2025.

Assessment

This issue has not been assessed yet.

Description

bug

Describe the bug
When a standalone NIC (not attached to a resource) is deployed in Azure, the IPAM app identifies this and the number of assigned IPs for corresponding subnet in the subnet node is increased by 1. However, the NIC is not listed in the endpoint node. This leads to a mismatch between the number of assigned IPs in a subnet and the number of endpoints in that subnet.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy a standalone NIC in Azure
  2. In IPAM app, visit the subnet node and confirm that the number of assigned IPs had increased by 1.
  3. In IPAM app, visit the endpoint node and confirm that the deployed NIC does not appear in the list.

Expected behavior
Standalone NICs are included in the endpoint list

Screenshots
3 IPs assigned in subnet (x1 NIC + x2 VMs)
Image

2 IPs in endpoint list
Image

Dominant language
JavaScript
Stars
327
Forks
111
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/ipam

All issues in Azure/ipam

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.