Skip to main content

Azure Tools - Azure SAS Generator

By
I decided to start a new series of articles about tools that can be used by Developers to improve their experience with Microsoft Azure. Each week I will publish a post related to a tool. The main focus is on tools that are free of charge, but sometimes I might include paid one.
Context: Having discussions with various technical people, especially from the development area, I realize that the tools that they are aware of are limited. There are so many tools that can improve our experience when we work with Microsoft Azure. Even so, many times we rely only on a few of them.

Highlights of Azure SAS Generator

Azure Services: Azure Storage (blobs, tables and queues)
Cost: free of use
How is delivered: Native Windows application
Top 3 features:
  • #1 SAS key generator
  • #2 Works offline
  • #3 Update the SAS key dynamically when you change an attribute

Pain points:
  • #1 Sometimes freeze and does not generate the keys
  • #2 Cannot add accounts using your Azure account
  • #3 Does not load the resources dynamically from the account storage

Download URL:  https://www.microsoft.com/en-us/p/azure-sas-generator/9wzdncrdlv09
Credits: Jeffrey M Richter (https://twitter.com/jeffrichter)

Today I will start with Azure SAS Generator, that enables us to generate Shared Access Signatures (SAS) for Azure Storage. Using this tool you can generate SAS for Containers, Blobs, Tables and Queues.

What I like about these tools is the way how the SAS is generated. Each time when you change an attribute to the key it automatically updates the generated key. Clean and easy to use, it is the kind of tool that I highly recommend when you want to learn how a SAS is generated, what does it contain and the attributes of the key. You have the ability to specify the version of SAS key you want to use. Even so in general, we use the latest one, but there might be situations when you want to use older versions.
The tool is not perfect, sometimes you might find out that the key is not generated. In these situations change the Resource Type from Blob to Tables and back to Blob. This actions should fix the problem. Adding new storage accounts can be done only using the account name and key. You might prefer to log in using your account credentials, but at least, in this case, you know all the time what account key it is used to generate the SAS key.

TIP: SAS keys are generated using the account key. When you regenerate the account key all the SAS keys generated using that account key will be invalidated.

The application can be used to generate SAS keys in offline mode, because generating this kind of access keys does not require to make a call to Azure Storage - they just required the account key to generate the signature of the SAS – “sig”
There is a strange name in the interface used for one of the properties of the SAS key - “Signature identifier”. It represents the SAS policy in the case when you want to use one. The app is not able to load the SAS policies that exist for a specific account, but you can specify it.

Comments

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

By
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...
Post a Comment
Read more

Can User Technical Profile Influence AI Architecture Decisions?

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