Thank you for the update.
Since you've confirmed that the Azure Function and the Storage Account are in the same VNet and the connection strings are correctly configured, the issue might be related to the VNet integration settings of the Function App.
To address this, please add the following application settings in your Function App (under Configuration > Application settings):
vnetRouteAllEnabled = 1
vnetContentShareEnabled = 1
These settings ensure that all outbound traffic, including traffic to Azure services like Blob Storage, is correctly routed through the integrated VNet.
After adding these settings, please restart your Function App and check if the issue persists.