Track Azure NIC MAC addresses as lifecycle-bound observations

Source facts

Azure assigns a NIC’s MAC address after attachment to a VM and the VM’s first start. Administrators cannot specify that assigned address.

Microsoft says the address remains assigned until the NIC is deleted or the private IP on the primary IP configuration of the primary NIC changes. The NIC Properties page has a blank MAC field when the NIC is not attached to a VM. Microsoft Learn.

Applicability

Identify the actual NIC resource, attachment, primary configuration and consumers of its observed address. Do not infer a defective deployment merely from an unpopulated pre-start inventory field.

DSE recommendation

DSE recommends keeping the cloud resource identity separate from the observed MAC value. Flag NIC replacement and primary-address changes for review by owners of any MAC-dependent inventory or application configuration. Avoid promising a predetermined address during provisioning. Capture the value only at an appropriate lifecycle stage, and retain enough context to explain a later difference.

Verification

For an approved test deployment, compare the unattached record with the attached, started VM’s NIC properties. Before a separately authorized replacement or address change, record the existing mapping and required downstream checks. Reconcile the observed after-state with those consumers without silently treating the new value as the same immutable identifier.

Official references

Microsoft Learn: Create, Change, or Delete Azure Network Interfaces. Source retrieved September 9, 2026.