1. Azure Storage Explorer Silent Install
2. Microsoft Azure Storage Explorer Version 1.12.0 Download
3. Microsoft Azure Storage Explorer App
4. Microsoft Azure Storage Explorer Download
5. Microsoft Azure Storage Explorer Version 1.6.2 Download
6. Download Microsoft Azure Explorer

Azure Storage Explorer Silent Install

Microsoft Azure Storage Explorer is a user-friendly application designed to help you manage your Azure cloud storage resources and assets in a clean graphical environment. It’s 100% freeware and works with all Windows editions that support Microsoft Azure.

The Microsoft Azure storage services support multiple versions. To make a request against the storage services, you must specify the version that you want to use for that operation, unless the request is anonymous.

• NOTE: As of version 9.4.0, this library has been split into multiple parts and replaced: See Microsoft.Azure.Storage.Blob, Microsoft.Azure.Storage.File, Microsoft.Azure.Storage.Queue, and Microsoft.Azure.Storage.Common. For table support, see Microsoft.Azure.CosmosDB.Table. This client library enables working with the Microsoft Azure storage.
• Active blobs and blobs without current version. In this view, Storage Explorer displays: Active non-version blobs; Current versions; Latest active previous versions. For blobs that don't have a current version but have an active previous version, Storage Explorer displays their latest active previous version as a representation of that blob.
• Install latest/stable of Microsoft Azure Storage Explorer. Ubuntu 16.04 or later? View in Desktop store Make sure snap support is enabled in your Desktop store.

Available Versions

The current version of the Azure storage services is 2020-06-12, and using that version is recommended where possible. For information about the latest version, see Versioning for the Azure Storage Services.

Additional supported versions include:

Requests authorized via a Shared Access Signature (SAS)

A request made via a SAS is processed according to which service version was used to generate the SAS. Versions 2013-08-15 and 2012-02-12 include a versioning parameter (SignedVersion, or sv), which specifies which version to use to authorize and execute the SAS request.

Version 2012-02-12 and later

Requests with Shared Access Signatures (SAS) generated using version 2012-02-12 or later require the SignedVersion (sv) parameter. SignedVersion indicates the service version used for authorization and authorization and for calling the API operation. If the x-ms-version header is passed on the request, it is ignored; only the SignedVersion (sv) parameter determines the service version to use to process the request made via the SAS.

Note

For version 2013-08-15 and earlier, code that prepares and distributes shared access signature URLs (*that is, SAS providers or generators) should specify versions that are understood by client software (*that is, SAS consumers) that makes storage service requests.

The following table indicates which services are supported for which version for a request made via a SAS:

Example

Microsoft Azure Storage Explorer Version 1.12.0 Download

The following example shows a SAS that calls List Blobs using sv=2013-08-15.

Microsoft Azure Storage Explorer App

https://myaccount.blob.core.windows.net/mycontainer?restype=container&comp=list&sv=2013-08-15&si=readpolicy&sig=a39 %2BYozJhGp6miujGymjRpN8tsrQfLo9Z3i8IRyIpnQ%3d

In this example, the service will authorize and execute the request using version 2013-08-15. The response will not include the Url element under the Blob element, as it was removed in 2013-08-15 version.

If a client application using a version of the Storage Client Library based on version 2012-02-12 makes a request using this SAS, the client would expect the Uri element and so would fail with a NullReferenceException.

Versions Prior to 2012-02-12 (Blob Service Only)

The Blob service introduced shared access signatures in version 2009-07-17, while the Table and Queue services introduced shared access signatures in version 2012-02-12, so SAS behavior prior to version 2012-02-12 applies only to the Blob service. Version 2012-02-12 also introduced the SignedVersion (sv) parameter, which enables the SAS generator to specify the version to use to process the request. A SAS generated with a version prior to 2012-02-12 cannot specify the version to use to process the request and so relies on the following rules.

In versions prior to 2012-02-12, the following rules are used to process the SAS request for authorization, authorization, and API execution:

Microsoft Azure Storage Explorer Download

1. If the SAS request against the Blob service has a valid x-ms-version header, the earliest valid version (2009-07-17) is used to interpret the SAS parameters, and the version specified by x-ms-version is used to perform the Blob service storage operation.

2. If the SAS request against the Blob service does not have an x-ms-version header and the owner has set the default version for this storage service type using Set Blob Service Properties, version 2009-07-17 is used to interpret the SAS parameters and the owner-specified default version is used to perform the Blob service storage operation.

3. If the SAS request against the Blob service does not have an x-ms-version header and the owner has not set a default version, the Blob service uses the earliest valid version (2009-07-17) to interpret the SAS parameters. If the container is public and its access restrictions were set with a Set Container ACL operation that used version 2009-09-19 or newer, version 2009-09-19 is used to perform the Blob service operation. Apple magic keyboard stand.

4. If the SAS request against the Blob service does not have an x-ms-version header and the owner has not set a default version, the Blob service uses the earliest valid version (2009-07-17) to interpret the SAS parameters. If the container access restrictions were not set with a Set Container ACL operation that used version 2009-09-19 or newer, the Blob service operation is performed using the earliest version of the service.

The following table applies these rules to various scenarios, and assumes the SignedVersion parameter is not included.

Microsoft Azure Storage Explorer Version 1.6.2 Download

Note

Microsoft recommends using version 2011-08-18 or later for scenarios that require quoted ETag values or valid Accept-Ranges response headers, because browsers and other streaming clients require these headers for efficient download and retries.

Download Microsoft Azure Explorer

See Also