AZURE DATA STUDIO DEBUG HOW TO
AZURE DATA STUDIO DEBUG CODE

One of the critical characteristics was that these APIs are able to read the credentials with which I had signed into Visual Studio.

Then I moved the connection string into Azure Key Vault and using the Azure.Identity SDK for accessing secrets (a combination of Azure.Identity and .Secrets NuGet packages) I told my application to look for the connection string in Azure Key Vault. I started out with a SQL Server LocalDB on my computer and its connection string tucked into appsettings.json. The ASP.NET Core Razor Pages application ( Figure 1) uses EF Core to interact with its data.įigure 1: The sample app as displayed when debugging locally The application I built in the previous article was to maintain a list of episodes of “The 425 Show,” a Twitch stream run by the Identity Developer Advocacy team. Here, I'll consider the rest of the details of the connection string important enough to keep it in the Key Vault and not embed it in the application code. I want to help my fellow “OMG please don't make me learn security stuff” developers adopt this new area of expertise as well.Įven as we remove the need for storing the secrets of the connection string, there are plenty of other secrets that you may want to continue storing in the Key Vault. I can no longer claim ignorance, which was, honestly, more a matter of fear of failure than anything else. However, walking pragmatically through the steps truly helped me understand what I was doing, why I was doing it, and eased me into having a much deeper comprehension of Azure Managed Identity than I originally thought I wanted to be bothered with. Interceptors are a great feature, but in this particular case, the new workflow is much simpler.Īs a non-security person, going directly to the new workflow continued to confuse me. I think this option is much easier than how we had to leverage Managed Identity authentication with EF Core prior to this new feature, which was by using EF Core Interceptors. In the end, it's simply a matter of a leveraging a new feature of the SQLClient API to use Managed Identity for authentication. In this article, I'll begin with the application as I left off in the earlier article, and walk you through deploying it and removing all secrets from the connection string.

AZURE DATA STUDIO DEBUG HOW TO

The services are all part of the same ecosystem and they know how to share among themselves. If you're using Azure SQL for your database and your application is running in Azure, it's possible (and easy) to have an Azure Managed Identity to authenticate and access your database. That's all well and good for debugging applications in your IDE, but when it's time to deploy your app, you can take this secret sharing even further. The clear evidence is that I was able to pull it off! The best part is that you don't have to be a security or SysOps guru to do this. NET Core to let your application access that while debugging locally in Visual Studio or Visual Studio Code.

AZURE DATA STUDIO DEBUG CODE

In the May/June 2021 issue of CODE Magazine, I wrote an article called “ Can You Keep a Secret? Azure Can!” showing you how to store a connection string with its secrets in Azure Key Vault and then use Azure Managed Identities with.

Azure data studio debug