Thank you for asking this question on the **Microsoft Q&A Platform. **
Usually, this happens when the SAS token expires.
Also from your PC do the following test
$resourceGroupName = "<your-resource-group-name>" $storageAccountName = "<your-storage-account-name>" # This command requires you to be logged into your Azure account and set the subscription your storage account is under, run: # Connect-AzAccount -SubscriptionId ‘xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx’ # if you haven't already logged in. $storageAccount = Get-AzStorageAccount -ResourceGroupName $resourceGroupName -Name $storageAccountName # The ComputerName, or host, is <storage-account>.file.core.windows.net for Azure Public Regions. # $storageAccount.Context.FileEndpoint is used because non-Public Azure regions, such as sovereign clouds # or Azure Stack deployments, will have different hosts for Azure file shares (and other storage resources). Test-NetConnection -ComputerName ([System.Uri]::new($storageAccount.Context.FileEndPoint).Host) -Port 445
If the connection was successful, you should see the following output:
ComputerName : <your-storage-account-name> RemoteAddress : <storage-account-ip-address> RemotePort : 445 InterfaceAlias : <your-network-interface> SourceAddress : <your-ip-address> TcpTestSucceeded : True
If it is not successful, then you have a communication issue.
Please review the documentation for Troubleshoot Azure Files problems in Windows (SMB)
Let me know how it goes.
Hope this helps!
Accept Answer and Upvote, if any of the above helped, this thread can help others in the community looking for remediation for similar issues.
NOTE: To answer you as quickly as possible, please mention me in your reply.