NetAppFiles causes orphaned nic - OperationNotPermittedOnNicCreatedByDifferentOwner

Hank Beasley 0 Reputation points
2026-01-29T22:46:49.46+00:00

I delete my netapp files account but now I can delete the related nic or subnets. See error below.

az resource delete --ids /subscriptions/x/resourceGroups/testdeploy/providers/Microsoft.Network/networkInterfaces/anf-aadds-dev-vnet-nic-LFJ57D --verbose
(OperationNotPermittedOnNicCreatedByDifferentOwner) Network Interface /subscriptions/x/resourceGroups/testdeploy/providers/Microsoft.Network/networkInterfaces/anf-aadds-dev-vnet-nic-LFJ57D was created by Microsoft.Netapp and can be modified only by the creator.
Code: OperationNotPermittedOnNicCreatedByDifferentOwner
Message: Network Interface /subscriptions/x/resourceGroups/testdeploy/providers/Microsoft.Network/networkInterfaces/anf-aadds-dev-vnet-nic-LFJ57D was created by Microsoft.Netapp and can be modified only by the creator.
Some resources failed to be deleted (run with `--verbose` for more information):
/subscriptions/x/resourceGroups/testdeploy/providers/Microsoft.Network/networkInterfaces/anf-aadds-dev-vnet-nic-LFJ57D     
Command ran in 2.098 seconds (init: 0.242, invoke: 1.8
Azure NetApp Files
Azure NetApp Files

An Azure service that provides enterprise-grade file shares powered by NetApp.

0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-01-29T22:46:55.77+00:00

    The error you are encountering, OperationNotPermittedOnNicCreatedByDifferentOwner, indicates that the Network Interface (NIC) you are trying to delete was created by the Azure NetApp Files service and can only be modified or deleted by that service. This is a common restriction in Azure where certain resources are managed exclusively by their creator.

    To resolve this issue, you typically need to delete the Azure NetApp Files account first, which you mentioned you have already done. However, if the NIC is still present and cannot be deleted, you may need to check if there are any dependencies or associated resources that need to be removed first. If the NIC is orphaned and you cannot delete it through the Azure portal or CLI, you might need to contact Azure support for assistance, as they can help you with resources that are stuck due to ownership issues.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Thanmayi Godithi 11,825 Reputation points Microsoft External Staff Moderator
    2026-01-29T23:28:37.4566667+00:00

    Hi @Hank Beasley,

    Thank you for reaching out on Microsoft Q&A forum.

    After review, the networking team identified that the issue was related to the Azure NetApp Files service backend. The case was escalated to the Azure NetApp Files (ANF) team, who confirmed that a stale backend network interface (NIC) associated with the resource was present.

    The ANF team manually removed the orphaned NIC from the backend. Once this cleanup was completed, the issue was resolved and no further action was required from your side.

    At this point, the problem is considered mitigated. Please let us know if you observe any further anomalies or if the issue reoccurs.

    Thank you for your understanding.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.