Overview of Azure Files Integration
Access Azure Files shares through the Azure API, without mapping a network drive. Handy on machines where SMB port 445 is blocked.
- Works over HTTPS, no SMB port needed
- Account key, SAS URL or connection string
- Copy between Azure Files and your local disks or other clouds
In-App Configuration Dialog
How to connect Azure Files in Ultra Explorer
-
Choose Azure Files
Select Azure Files in Network Protocols.
-
Enter account and key
Enter the name of the Storage Account and your access key.
-
Explore your files
Click 'Connect and verify'.
Configuration fields
Storage Name
Required
name= Azure FilesUnique identifier for this storage remote in Ultra Explorer (e.g. gdrive-perso, backup-s3).Default value: Azure Files
Account Name / ID
Optional
accountAccount identifier, Key ID, or storage account name required for authentication.
Application Key / Shared Key
Optional
keySecret application key, shared key, or access token paired with your account.
Azure File Share Name
Optional
share_nameOptional. Name of the Azure File Share to scope navigation.
Connection String
Optional
connection_stringOptional. Complete Azure Storage connection string copied from the Azure portal.
SAS URL (Shared Access Signature)
Optional
sas_urlOptional. Direct access URL with restricted SAS token for scoped access without account keys.
Frequently Asked Questions about Azure Files
-
Ultra Explorer communicates over Azure Files' secure HTTPS REST API, completely bypassing frequent carrier blocking of SMB port 445.
Ready to explore your Azure Files?
Available on Windows, macOS and Linux, or as a Docker container. The Free version needs no subscription.