Home / Azure / Fix Azure File Share Mount Failed

Azure

Fix Azure File Share Mount Failed

Resolve Azure Files mount failures by checking SMB protocol, firewall rules, storage account keys, and network connectivity.

Published: Apr 2, 20266 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

Introduction

Azure Files provides fully managed file shares accessible via SMB protocol. When mount operations fail, applications can't access shared file storage, impacting workloads that depend on shared file systems.

Symptoms

Mount error on Linux:

```bash $ sudo mount -t cifs //storageaccount.file.core.windows.net/share /mnt/share -o vers=3.0,username=accountname,password=KEY

mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page ```

Windows mapping failure:

```cmd > net use Z: \\storageaccount.file.core.windows.net\share /u:AZURE\storageaccount KEY

System error 53 has occurred. The network path was not found. ```

Permission denied:

bash

mount error(13): Permission denied
Refer to the mount.cifs(8) manual page

Common Causes

1.Port 445 blocked - Firewall blocking SMB traffic
2.SMB version mismatch - Client doesn't support required SMB version
3.Storage account key incorrect - Wrong or expired access key
4.Storage account firewall - Network rules blocking access
5.DNS resolution failure - Can't resolve storage account name
6.Private endpoint issues - Incorrect private endpoint configuration
7.Share deleted - Target file share doesn't exist

Step-by-Step Fix

1.Check logs for specific error messages
2.Verify configuration settings
3.Test network connectivity
4.Review recent changes
5.Apply corrective action
6.Verify the fix

Step 1: Check Port 445 Connectivity

```bash # Test if port 445 is open telnet storageaccount.file.core.windows.net 445

# Or using PowerShell Test-NetConnection -ComputerName storageaccount.file.core.windows.net -Port 445

# If blocked, you may need to: # - Use VPN or ExpressRoute # - Enable public endpoint # - Use REST API instead of SMB ```

Step 2: Check Storage Account Firewall

```bash # Get storage account network rules az storage account show \ --name storageaccount \ --resource-group my-rg \ --query '{NetworkAcls:networkAcls}'

# If default action is Deny, add your IP az storage account network-rule add \ --account-name storageaccount \ --ip-address YOUR_PUBLIC_IP

# Or allow all Azure services az storage account update \ --name storageaccount \ --default-action Allow ```

Step 3: Verify SMB Version Support

```bash # Check SMB version on Linux sudo smbd --version

# Mount with specific version # SMB 3.0+ recommended for Azure Files sudo mount -t cifs //storageaccount.file.core.windows.net/share /mnt/share \ -o vers=3.0,username=storageaccount,password=STORAGE_KEY

# Try SMB 2.1 if 3.0 fails sudo mount -t cifs //storageaccount.file.core.windows.net/share /mnt/share \ -o vers=2.1,username=storageaccount,password=STORAGE_KEY ```

Step 4: Get Correct Storage Account Key

```bash # List storage account keys az storage account keys list \ --account-name storageaccount \ --resource-group my-rg \ --query '[].{KeyName:keyName,Value:value}'

# Regenerate key if needed az storage account keys renew \ --account-name storageaccount \ --key primary ```

```bash # List file shares az storage share list \ --account-name storageaccount \ --query '[].name'

# Create share if missing az storage share create \ --name myshare \ --account-name storageaccount ```

Step 6: Verify DNS Resolution

```bash # Check DNS resolves correctly nslookup storageaccount.file.core.windows.net

# Should return IP address # If fails, check DNS settings

# Flush DNS cache sudo resolvectl flush-caches # Linux systemd ipconfig /flushdns # Windows ```

Step 7: Check Private Endpoint Configuration

```bash # If using private endpoint az network private-endpoint show \ --name my-private-endpoint \ --resource-group my-rg \ --query '{PrivateLinkServiceConnections:privateLinkServiceConnections}'

# Check DNS zone az network private-dns zone show \ --name privatelink.file.core.windows.net \ --resource-group my-rg

# Verify A record points to private IP az network private-dns record-set a show \ --name storageaccount \ --zone-name privatelink.file.core.windows.net \ --resource-group my-rg ```

Step 8: Test with Storage Explorer

```bash # Install Azure Storage Explorer # Or use az storage commands

# List files in share az storage file list \ --account-name storageaccount \ --share-name myshare

# Download file az storage file download \ --account-name storageaccount \ --share-name myshare \ --path test.txt \ --dest ./test.txt ```

Step 9: Check for Encryption in Transit

```bash # Enable secure transfer az storage account update \ --name storageaccount \ --resource-group my-rg \ --https-only true

# Mount with encryption sudo mount -t cifs //storageaccount.file.core.windows.net/share /mnt/share \ -o vers=3.0,username=storageaccount,password=KEY,seal,sec=ntlmssp ```

Step 10: Review Activity Logs

bash

# Check for failed mount attempts
az monitor activity-log list \
  --resource-group my-rg \
  --caller $(az ad signed-in-user show --query userPrincipalName -o tsv) \
  --query "[?contains(operationName.value, 'storage')].{Time:eventTimestamp,Operation:operationName,Status:status.value}"

Azure Files Mount Commands Reference

OS	Command
Linux	`mount -t cifs //account.file.core.windows.net/share /mnt -o vers=3.0`
Windows	`net use Z: \\account.file.core.windows.net\share`
macOS	`mount_smbfs //account:KEY@account.file.core.windows.net/share /mnt`

Verification

```bash # After fixing, test mount sudo mount -t cifs //storageaccount.file.core.windows.net/share /mnt/share \ -o vers=3.0,username=storageaccount,password=KEY

# Verify mount df -h | grep cifs

# Create test file echo "test" | sudo tee /mnt/share/test.txt

# Check file in Azure Portal # Or list files az storage file list --account-name storageaccount --share-name myshare ```

[Fix Azure Storage Account Inaccessible](/articles/fix-azure-storage-account-inaccessible)
[Fix Azure Blob Upload 403 Forbidden](/articles/fix-azure-blob-upload-403-forbidden)
[Fix Azure Private Endpoint Connection](/articles/fix-azure-private-endpoint-connection)

[Technical troubleshooting: Fix Azure Aks Pod Crashloopbackoff Issue in Azure](azure-aks-pod-crashloopbackoff)
[Technical troubleshooting: Fix Azure Api Management Policy Expression Runtime](azure-api-management-policy-expression-runtime-error)
[Technical troubleshooting: Fix Azure App Configuration Feature Flag Not Refre](azure-app-configuration-feature-flag-not-refreshing)
[Technical troubleshooting: Fix Azure App Service 503 Always On Disabled Issue](azure-app-service-503-always-on-disabled)
[Technical troubleshooting: Fix Azure Application Gateway Err SSL Unrecognized](azure-application-gateway-err-ssl-unrecognized-name-alert)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

Azure File Share Mount Failed Azure File Share Mount Failed Azure Azure File Share Mount Failed troubleshooting Azure File Share Mount Failed fix Resolve Azure Files mount failures by checking SMB protocol, firewall rules, storage account keys, and network connectivity Azure Resolve Azure Files mount failures by checking SMB protocol, firewall rules, storage account keys, and network connectivity

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

Azure Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this azure-errors troubleshooting guide applies to my situation?

This guide is designed for azure-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these azure-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of azure-errors issue?

Most azure-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this azure-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for azure-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Apr 2, 2026

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation