Azure File Explorer Download

-->

Overview

Microsoft Azure Storage Explorer is a standalone app from Microsoft that allows you to easily work with Azure Storage data on Windows, macOS and Linux. Files Show tools chocolateyInstall.ps1.
Storage Explorer will open a webpage for you to sign in. After you successfully sign in with an Azure account, the account and the Azure subscriptions associated with that account appear under ACCOUNT MANAGEMENT.Select the Azure subscriptions that you want to work with, and then select Apply. EXPLORER displays the storage accounts associated with the selected Azure subscriptions.

Microsoft Azure Storage Explorer is a standalone app that makes it easy to work with Azure Storage data on Windows, macOS, and Linux.

You need to enable JavaScript to run this app. Azure Data Explorer. You need to enable JavaScript to run this app. Microsoft is radically simplifying cloud dev and ops in first-of-its-kind Azure Preview portal at portal.azure.com.

In this article, you'll learn several ways of connecting to and managing your Azure storage accounts.

Prerequisites

The following versions of Windows support Storage Explorer:

Windows 10 (recommended)
Windows 8
Windows 7

For all versions of Windows, Storage Explorer requires .NET Framework 4.7.2 at a minimum.

The following versions of macOS support Storage Explorer:

macOS 10.12 Sierra and later versions

Storage Explorer is available in the Snap Store for most common distributions of Linux. We recommend Snap Store for this installation. The Storage Explorer snap installs all of its dependencies and updates when new versions are published to the Snap Store.

For supported distributions, see the snapd installation page.

Storage Explorer requires the use of a password manager. You might have to connect to a password manager manually. You can connect Storage Explorer to your system's password manager by running the following command:

Storage Explorer is also available as a .tar.gz download. If you use the .tar.gz, you must install dependencies manually. The following distributions of Linux support .tar.gz installation:

Ubuntu 20.04 x64
Ubuntu 18.04 x64
Ubuntu 16.04 x64

The .tar.gz installation might work on other distributions, but only these listed ones are officially supported.

For more help installing Storage Explorer on Linux, see Linux dependencies in the Azure Storage Explorer troubleshooting guide.

Download and install

To download and install Storage Explorer, see Azure Storage Explorer.

Connect to a storage account or service

Storage Explorer provides several ways to connect to Azure resources:

Sign in to Azure

Note

To fully access resources after you sign in, Storage Explorer requires both management (Azure Resource Manager) and data layer permissions. This means that you need Azure Active Directory (Azure AD) permissions to access your storage account, the containers in the account, and the data in the containers. If you have permissions only at the data layer, consider choosing the Sign in using Azure Active Directory (Azure AD) option when attaching to a resource. For more information about the specific permissions Storage Explorer requires, see the Azure Storage Explorer troubleshooting guide.

In Storage Explorer, select View > Account Management or select the Manage Accounts button.
ACCOUNT MANAGEMENT now displays all the Azure accounts you're signed in to. To connect to another account, select Add an account....
The Connect to Azure Storage dialog opens. In the Select Resource panel, select Subscription.
In the Select Azure Environment panel, select an Azure environment to sign in to. You can sign in to global Azure, a national cloud or an Azure Stack instance. Then select Next.
Tip
For more information about Azure Stack, see Connect Storage Explorer to an Azure Stack subscription or storage account.
Storage Explorer will open a webpage for you to sign in.
After you successfully sign in with an Azure account, the account and the Azure subscriptions associated with that account appear under ACCOUNT MANAGEMENT. Select the Azure subscriptions that you want to work with, and then select Apply.
EXPLORER displays the storage accounts associated with the selected Azure subscriptions.

Attach to an individual resource

Storage Explorer lets you connect to individual resources, such as an Azure Data Lake Storage Gen2 container, using various authentication methods. Some authentication methods are only supported for certain resource types.

Resource type	Azure AD	Account Name and Key	Shared Access Signature (SAS)	Public (anonymous)
Storage accounts	Yes	Yes	Yes (connection string or URL)	No
Blob containers	Yes	No	Yes (URL)	Yes
Gen2 containers	Yes	No	Yes (URL)	Yes
Gen2 directories	Yes	No	Yes (URL)	Yes
File shares	No	No	Yes (URL)	No
Queues	Yes	No	Yes (URL)	No
Tables	No	No	Yes (URL)	No

Storage Explorer can also connect to a local storage emulator using the emulator's configured ports.

To connect to an individual resource, select the Connect button in the left-hand toolbar. Then follow the instructions for the resource type you want to connect to.

When a connection to a storage account is successfully added, a new tree node will appear under Local & Attached > Storage Accounts.

For other resource types, a new node is added under Local & Attached > Storage Accounts > (Attached Containers). The node will appear under a group node matching its type. For example, a new connection to an Azure Data Lake Storage Gen2 container will appear under Blob Containers.

If Storage Explorer couldn't add your connection, or if you can't access your data after successfully adding the connection, see the Azure Storage Explorer troubleshooting guide.

The following sections describe the different authentication methods you can use to connect to individual resources.

Azure AD

Storage Explorer can use your Azure account to connect to the following resource types:

Blob containers
Azure Data Lake Storage Gen2 containers
Azure Data Lake Storage Gen2 directories
Queues

Azure AD is the preferred option if you have data layer access to your resource but no management layer access.

Sign in to at least one Azure account using the steps described above.
In the Select Resource panel of the Connect to Azure Storage dialog, select Blob container, ADLS Gen2 container, or Queue.
Select Sign in using Azure Active Directory (Azure AD) and select Next.
Select an Azure account and tenant. The account and tenant must have access to the Storage resource you want to attach to. Select Next.
Enter a display name for your connection and the URL of the resource. Select Next.
Review your connection information in the Summary panel. If the connection information is correct, select Connect.

Account name and key

Storage Explorer can connect to a storage account using the storage account's name and key.

You can find your account keys in the Azure portal. Open your storage account page and select Settings > Access keys.

In the Select Resource panel of the Connect to Azure Storage dialog, select Storage account.
Select Account name and key and select Next.
Enter a display name for your connection, the name of the account, and one of the account keys. Select the appropriate Azure environment. Select Next.
Review your connection information in the Summary panel. If the connection information is correct, select Connect.

Shared access signature (SAS) connection string

Storage Explorer can connect to a storage account using a connection string with a Shared Access Signature (SAS). A SAS connection string looks like this:

In the Select Resource panel of the Connect to Azure Storage dialog, select Storage account.
Select Shared access signature (SAS) and select Next.
Enter a display name for your connection and the SAS connection string for the storage account. Select Next.
Review your connection information in the Summary panel. If the connection information is correct, select Connect.

Shared access signature (SAS) URL

Storage Explorer can connect to the following resource types using a SAS URI:

Blob container
Azure Data Lake Storage Gen2 container or directory
File share
Queue
Table

A SAS URI looks like this:

In the Select Resource panel of the Connect to Azure Storage dialog, select the resource you want to connect to.
Select Shared access signature (SAS) and select Next.
Enter a display name for your connection and the SAS URI for the resource. Select Next.
Review your connection information in the Summary panel. If the connection information is correct, select Connect.

Local storage emulator

Storage Explorer can connect to an Azure Storage emulator. Currently, there are two supported emulators:

Azure Storage Emulator (Windows only)
Azurite (Windows, macOS, or Linux)

If your emulator is listening on the default ports, you can use the Local & Attached > Storage Accounts > Emulator - Default Ports node to access your emulator.

If you want to use a different name for your connection, or if your emulator isn't running on the default ports:

Start your emulator.
Important
Storage Explorer doesn't automatically start your emulator. You must start it manually.
In the Select Resource panel of the Connect to Azure Storage dialog, select Local storage emulator.
Enter a display name for your connection and the port number for each emulated service you want to use. If you don't want to use to a service, leave the corresponding port blank. Select Next.
Review your connection information in the Summary panel. If the connection information is correct, select Connect.

Connect to Azure Cosmos DB

Storage Explorer also supports connecting to Azure Cosmos DB resources.

Connect to an Azure Cosmos DB account by using a connection string

Instead of managing Azure Cosmos DB accounts through an Azure subscription, you can connect to Azure Cosmos DB by using a connection string. To connect, follow these steps:

Under EXPLORER, expand Local & Attached, right-click Cosmos DB Accounts, and select Connect to Azure Cosmos DB.
Select the Azure Cosmos DB API, enter your Connection String data, and then select OK to connect the Azure Cosmos DB account. For information about how to retrieve the connection string, see Manage an Azure Cosmos account.

Connect to Azure Data Lake Store by URI

You can access a resource that's not in your subscription. You need someone who has access to that resource to give you the resource URI. After you sign in, connect to Data Lake Store by using the URI. To connect, follow these steps:

Under EXPLORER, expand Local & Attached.
Right-click Data Lake Storage Gen1, and select Connect to Data Lake Storage Gen1.
Enter the URI, and then select OK. Your Data Lake Store appears under Data Lake Storage.

This example uses Data Lake Storage Gen1. Azure Data Lake Storage Gen2 is now available. For more information, see What is Azure Data Lake Storage Gen1.

Generate a shared access signature in Storage Explorer

Account level shared access signature

Right-click the storage account you want share, and then select Get Shared Access Signature.
In Shared Access Signature, specify the time frame and permissions you want for the account, and then select Create.
Copy either the Connection string or the raw Query string to your clipboard.

Service level shared access signature

You can get a shared access signature at the service level. For more information, see Get the SAS for a blob container.

Search for storage accounts

To find a storage resource, you can search in the EXPLORER pane.

As you enter text in the search box, Storage Explorer displays all resources that match the search value you've entered up to that point. This example shows a search for endpoints:

Note

To speed up your search, use Account Management to deselect any subscriptions that don't contain the item you're searching for. You can also right-click a node and select Search From Here to start searching from a specific node.

Next steps

Some time ago, Redgate created the free Microsoft Azure storage tool, Azure Explorer. It’s a neat solution that lets users manage all of their Azure blobs in one place, reliably upload and download them through its responsive UI, transfer them between storage accounts, and easily search and filter blobs.

While it sat outside Redgate’s portfolio of database development and management solutions, in a kind of niche of its own, it was a popular download. Without a development team behind it to take it further, however, it was languishing and we didn’t feel good about that.

Step in Monza Cloud

Monza Cloud are the people behind AzStudio, a tool that speeds up the development of Microsoft Azure applications and typically reduces development time by 40-60%. They have deep experience in delivering solutions around cloud-centric application development and addressing the unique needs of cloud-centric DevOps challenges. The kind of experience that a tool like Azure Explorer requires in order for it to be developed further.

So to ensure the future of the tool, they’ve taken over the upkeep and updates of Azure Explorer, which can now be freely downloaded from MonzaCloud.com/Azure-Cloud-Explorer/.

It’s good news for everyone. Users can still rely on it to easily browse and manipulate their Azure blob storage. We’re happy at Redgate that a tool we developed will continue to help people. And the team at Monza Cloud have plans to expand the scope of Azure Explorer with new features and integrations with the rich suite of options that AzStudio provides.

So, if you’d like an easier way to handle the scale demands of production-sized cloud datasets, download Azure Explorer from the Monza Cloud website.

Tools in this post

Azure Explorer

A free storage tool for Microsoft Azure.

Also in Blog

What’s Redgate’s plan for PASS?

My blog post from February 1 explains that Redgate took the opportunity to purchase the assets of PASS with the main goal of supporting the community.

The PASS association ran for 21 years bringing...

Azure File Sync

Also in Software development

Azure File Explorer Download Free

Healthcare IT responds to pandemic with increased focus on database monitoring and the cloud

Azure File Explorer Download Mac

Every year, Redgate’s State of Database Monitoring Report reveals how businesses and organizations are monitoring their database estates. Are they using in-house or third-party monitoring tools? Who...