In Azure, you can often get access to a resource by getting its service key or connection string, which contains a token. While such an approach is super simple and saves time, it is really problematic when it comes to security management and granular access to the different features of a service.
At the time of writing this, a few months ago, Managed Identity (MI) was named Managed Service Identity (MSI). In some older publications, you can still see the old name but do not be confused – it is still the same feature.
Before we get started, I want to ensure that you understand all the pros and cons of MSI:
- Addresses the problem of revoking access to services, which has limited capabilities when it comes to security (such as Azure Storage or Azure Cosmos DB)
- Allows you to introduce identities to resources that did not have them previously
- Gives you the capability to declare access to different services using RBAC and custom roles
- Uses service...
