An Azure service that provides enterprise-grade file shares powered by NetApp.
Hello @Uday Sagar T
The Snapshot policy option should normally be available for a standard Azure NetApp Files volume, so if it is completely missing from the volume's Edit blade, I would first check whether this is a portal/UI issue or a restriction on that particular volume.
Microsoft's documented workflow is:
NetApp account → Volumes → select the volume → Edit → Snapshot policy → select the policy → OK
The snapshot policy itself is created and managed at the NetApp account level under Snapshot policy.
A couple of things are worth checking.
First, verify that a snapshot policy actually exists for the NetApp account and is enabled. You can confirm this independently of the portal with Azure CLI:
az netappfiles snapshot policy list \
--resource-group <resource-group> \
--account-name <netapp-account> \
--output table
The CLI supports listing, showing, creating, and updating ANF snapshot policies, so it is also useful for determining whether the issue is limited to the portal experience.
Second, check whether this volume is a destination volume in a cross-region replication relationship. This matters because Microsoft explicitly states that you can't apply a snapshot policy to a destination volume in cross-region replication.
If it isn't a replication destination, I would also check the volume resource directly:
az netappfiles volume show \
--resource-group <resource-group> \
--account-name <netapp-account> \
--pool-name <capacity-pool> \
--name <volume>
Then compare that volume with another ANF volume that has a Snapshot policy field, if you have one.
Also note that Snapshots, Snapshot policy, and Backup policy are different features. The Snapshots blade is for on-demand snapshots, while Snapshot policies schedule automatic snapshots.
If the volume isn't a cross-region replication destination, an enabled snapshot policy exists, you have sufficient RBAC permissions, and the Snapshot policy field is still absent from Volume → Edit, then the behavior doesn't match Microsoft's currently documented portal workflow. At that point, I would capture the NetApp account, volume resource ID, region, volume protocol/service level, replication status, and a screenshot of the Edit blade, then open an Azure support request so the ANF team can determine whether this is a portal- or resource-specific issue.
I wouldn't recreate the volume just to restore the missing portal option.
Sharing these references with you:
Microsoft - Manage snapshot policies in Azure NetApp Files
Microsoft - Azure CLI ANF snapshot policy commands
Help make this community better for everyone: if this answer resolved your issue, please accept it or leave an upvote. If not, share more details in a comment so we can continue the discussion and find the right solution.