Issue: Unable to create Azure NetApp Files volume in centraluseuap — all attempts fail with FileSystemAllocationFailed

Hi @Balaji Kottaram ,

The FileSystemAllocationFailed error indicating "There are currently insufficient resources available to create a volume with Standard network features for the provided VNet in this region" typically points to a temporary resource capacity limitation in Azure NetApp Files for the selected VNet and region.

What this means

When Azure NetApp Files creates or resizes a volume, Azure must allocate both storage and networking resources. If sufficient capacity isn't available for Standard network features in the selected VNet, the operation may fail with this error.

Recommended Troubleshooting Steps

1. Retry the operation after some time
   • This issue can be transient.
     • Capacity may become available as resources are released within the cluster, availability zone, or region.
     1. Try using a different VNet
        • Create the volume in a new VNet and delegated subnet.
          • This can help avoid networking-related resource limitations associated with the current VNet.
          1. Review the network feature requirement
             • If Standard network features are not required for your scenario, consider using Basic network features where supported.
               • If Standard features are required, continue with the alternate VNet approach and retry.
               1. If the issue persists
                  • Open a Microsoft Support request and provide:

                    - Subscription ID
                    
                          - Region
                    
                                - VNet name
                    
                                      - Timestamp of the failed deployment
                    
                                            - Correlation ID (from Activity Log)
                    

Additional Information Requested

To better understand the issue, could you please confirm:

1. Are you intentionally selecting Standard network features? If so, which specific features are required?
2. Have you attempted the deployment using a different VNet?
3. Which Azure region is being used?
4. Is this a new volume creation or an existing volume resize operation?
5. How long after the initial failure did you retry the deployment?

Reference Documentation

• Azure NetApp Files - Troubleshoot Volume Allocation Errors https://learn.microsoft.com/azure/azure-netapp-files/troubleshoot-volumes#errors-for-volume-allocation
• Azure NetApp Files - Resource Provider Error Troubleshooting https://learn.microsoft.com/azure/azure-netapp-files/azure-netapp-files-troubleshoot-resource-provider-errors#common-azure-netapp-files-resource-provider-errors
• Azure NetApp Files - Configure Network Features https://learn.microsoft.com/azure/azure-netapp-files/configure-network-features