Resizing the volume is failing with error stating insufficient resources available

Hello Uday Sagar T

I understand that you are trying Resizing the volume fails with error insufficient resources available.

The issue caused due to the ANF volume can’t expand because the underlying storage system has reached its capacity limit.

Because of system constraints, the capacity limit can’t be increased, so you’ll need to migrate the data to new volumes.

Hope the above answer helps! Please let us know do you have any further queries.

Please do consider to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Hi Uday,

That message usually indicates an Azure NetApp Files regional allocation problem while the service is trying to extend the volume. It is different from the normal “volume/pool is full” condition.

I would check these items first:

1. Capacity-pool headroom — confirm that the pool can accommodate the new volume quota. The sum of provisioned volume quotas cannot exceed the pool capacity. If this is a replication source, also check headroom in the destination pool; resizing the source can resize the destination too.
2. Regional ANF quota — in Subscriptions > Usage + quotas, verify the Azure NetApp Files regional capacity quota has sufficient remaining capacity for the pool growth. Request a quota increase if needed.
3. Exact Activity Log failure — open the failed ScaleUp operation and retain the timestamp, correlation ID, target size, region, pool name, and volume resource ID. This is what Support will need if the allocation cannot be retried successfully.
4. Retry after a short interval — Microsoft documents this specific error as a temporary shortage of storage or networking resources in the region/cluster. A retry can succeed after capacity is freed. If you use Standard network features, a new VNet can also avoid a networking-resource constraint, where that is feasible.

If it continues to fail, please open an Azure support request and include the Activity Log correlation ID and the information above; this normally needs the ANF service team to check regional allocation capacity.

References:

• Troubleshoot Azure NetApp Files volume errors
• Resize a capacity pool or volume
• Azure NetApp Files resource limits

If you can share the exact error text from the screenshot, the region, and whether the volume is replicated, I can help narrow down which path applies.