I remember this issue from an old post where I left an answer. You can check it here !
Azure ML uses a service principal to interact with Azure resources so you need to verify that this principal has the necessary permissions on your Azure Storage Account:
- Go to your Azure Storage Account in the Azure portal.
- Go to Access control (IAM).
- Click on Add role assignment.
- Select Storage File Data Contributor.
- Assign this role to the Azure ML service principal.
If your Azure ML workspace or Storage Account is within a Virtual Network (VNet), so you need to check the network configurations and if your VNet allows outbound connections to ports 443 and 445 for the storage service tag.
If your Storage Account has a firewall enabled, confirm that it permits access from your Azure ML workspace:
- In the Azure portal, navigate to your Storage Account.
- Go to Firewalls and virtual networks.
- Ensure that access is allowed from your Azure ML workspace or the specific VNet.
If you are using private endpoints, verifythat DNS settings are correctly configured to resolve the Storage Account's private endpoint.
Misconfigured DNS can lead to mounting failures. For instance, a misconfigured DNS entry for a private endpoint can cause the compute to attempt mounting the storage at an incorrect FQDN/IP, resulting in timeouts.
Links to help you :
https://github.com/Azure-Samples/ai-studio-in-a-box/issues/7