Using managed identities
When deploying services to Azure, you can utilize a variety of different resources that will eventually interact with each other. You can have a virtual machine hosting an application connecting to a database, data orchestrators interacting with storage services, and many, many other possibilities. When designing such solutions, one often thinks about authentication and authorization mechanisms that will be used to determine what one service can and cannot do when connecting to another one. Most of the time, this can be solved by using concepts such as connection strings, access policies, or an in-built RBAC mechanism. This, however, is not always an ideal way of handling that challenge. In this section, we’ll talk more about using managed identities when connecting with Azure Storage to see how they make the whole setup simple.
Definition of managed identity
A managed identity in Azure is a concept for assigning an identity to a service that normally...
