Downloads

CloudXplorer - fully functional 30-days evaluation

CloudXplorer (5.5 MB)

TableXplorer (14 MB)

Close all running instances of Microsoft Visual Studio.
Uninstall any previous version of AzureXplorer.
Run AzureXplorer installer, follow the instructions and complete the installation.
Open Microsoft Visual Studio and go to View » Other Windows » AzureXplorer or press Ctrl-W, V to open the AzureXplorer tool window.
Right-click on "Storage services" or "Subscriptions" to add a storage account or subscription.

April 4, 2018 - Update 4.9 adds support for Azure soft deleted blobs and IBM cloud object storage.
January 4, 2018 - Update 4.8 adds support for Box, Sharepoint Online, Azure blob tiers, master password and much more.
August 28, 2017 - Update 4.7 adds support for Oracle Cloud Storage, Rackspace Cloud Files, SoftLayer Object Storage and fixes an issue with Google OAuth2.
April 4, 2017 - Update 4.6 adds support for Azure Germany and OneDrive Business.
November 30, 2016 - Update 4.5 adds support for multiple Amazon Cloud Drive, Google Drive and OneDrive accounts and improves Azure DataLake store access.

November 4, 2015 - Release 2.2 introduces native OData query syntax and account signatures for Azure Tables.
August 31, 2015 - Release 2.1 makes mass data imports faster and more efficient and adds saved queries.
July 24, 2014 - Release 2.0 introduces a new UI and many new features.

March 5, 2013 - Release 1.3.8 adds table and queue shared access signatures.
October 25, 2012 - Maintenance release 1.3.7 fixes a critical bug with page blobs, adds native cross-account copy support for blobs and introduces search/report functionality for storage containers.
April 14, 2012 - Release 1.3 adds multithreading when downloading or uploading block blobs.
March 18, 2012 - Release 1.2 adds a hex-viewer for queue messages, preview for table entity values and fixes a certificate upload bug.
February 18, 2012 - Update 1.1.5 adds the ability to filter logs by the log level, e.g. critical, warning, information etc. Also the deployment process now uses a single container axdeploy for uploads.