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.
Make azure data studio default application 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. 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.
0 kommentar(er)
