Skip to main content

Azure Tools - Azure Cloud Explorer


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:
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

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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

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...