This article focuses on the steps on how to configure the Always Encrypted (AE) feature for SQL Databases using Azure Key Vault as the key store provider; which is still in preview at the time of this writing. In order to try out what I have explained here you should have January 2016 preview or […]
This post goes with the series of my posts under the Azure Key Vault. I assume that you know about Azure Key Vault and have used it, and continue this article. If you’re new to Azure Key Vault, please review the below links. You can read more about Azure Key Vault and how to use […]
Azure Key Vault is generally available. If you use Azure Key Vault in your projects, then there’s a high probability that you felt the need of a handy dev tool to manage your Vault. Here it is. http://keyvaultmanager.azurewebsites.net GitHub: https://github.com/thuru/AzureKeyVaultManager More about Azure Key Vault: https://thuruinhttp.wordpress.com/2015/05/30/azure-key-vault-setup-and-usage-scenarios/
Introduction At the time of this writing Azure Key Vault is in preview. Azure Key Vault is a secure store solution for storing string based confidential information. The reason I’ve mentioned that the string based confidential information is that you can store a key used for encrypting a file, but you cannot store the encrypted […]
Introduction Sometime back when it was in the preview, I posted an article on Azure Managed Service Identity (MSI) and how we can use it, to eliminate storing credentials in the code, whilst avoiding the bootstrap problem. Read the link for more details. This post is about Managed Identity, in short, Managed Identity is the new […]
Cloud has the proven promise of great opportunities for organizations & ISVs. Modern cloud platforms have low entry barriers and huge array service offerings beyond traditional enterprise application requirements. Cloud and the services provide intact environment to SaaS application providers with cutting edge innovation, agility and computational and storage scale for the global reach.
We keep the credentials and other secrets of the application in the source files. These secrets are visible to developers and being pushed to the source control. In order to avoid this, we can keep the secrets in centralized key management systems – but the credentials of the centralized key management system should be kept in the source files, resulting that at least one credential being placed in the source files.
Let’s see how to overcome this using Azure Managed Service Identity
Azure Web Apps is a component of Azure App Service. Developers love Web Apps as this is very simple web server as a service model. Often people ask the question, what is the difference between VMs Cloud Services and Web Apps. I think this post explains the difference in greater details. Accessing KUDU Azure Web […]