Skip to main content

Azure Tools - Azure Cloud Explorer

By

Highlights of  Azure Cloud Explorer
Azure Services: Azure Blob Storage
Cost: Free of use
How it is delivered: Installer
Top 3 features:
     #1 Looks and feel like File Explorer
     #2 Drag and drop functionality
     #3 Integrated with local file storage
Pain points:
     #1 Lack of support for virtual directories (e.g. OneDrive)
     #2 Linux support
     #3 Hard to find download link using search engine
Download URL:
     https://monzacloud.com/azure-cloud-explorer/
Credits:
     Monza Cloud

First time when I discovered these tools was a few months ago. I was looking for a method for copying data from Azure Blob Storage to the local disk for non-technical people. Imagine that you need to share content with somebody from HR knows to use only Office and Windows. For them, a tool that looks like Windows File Explorer is perfect.
The first thing that impressed me at the tools what the similarities with File Explorer. The initial look and feel are almost the same. As you can see below the icons, the position of the content and the features are the same. I like that that copy&paste and drag and drop are working seamlessly. With the current UI, even my mother that has 70+ years old can use Azure Storage without a problem for sharing content.

You can use the local emulator storage or you can add any Azure Storage account using a SAS key, connection string or using the <storage account name, key> tuple. For each path (aka folder) or blob inside the Azure Storage, you can see properties (e.g. size, ETag, last modified date) or manage the SAS or permissions if needed.
You can add multiple storage accounts for which you are allowed to copy content between them or to the local storage. Even if you don’t see the virtual folders like OneDrive ones, you can bookmark it and access from there later on.
Until now, I didn’t have any issues with the tool or limitations. I even create a script that installs automatically Azure Cloud Explorer and configure the Azure Storage accounts. In this way, a non-technical use has the tool ready for use in just a few seconds.

Azure Cloud Explorer is one of that kind of tools that people don’t know about it, even if the tool is free and provide the same experience as you have with File Explorer when you upload/download content from Azure Blob Storage. It’s the perfect tool for non-IT people. You should give it a try.

Comments

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(...
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see...
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provi...
Post a Comment
Read more