When trying to operationalize a solution in Azure, the question of keys, logins, passwords and other rather important bits tend to come up. The challenge is to figure out where to store these secrets - they shouldn't be in the code for obvious reasons, and putting them in source control is just as bad. The proper solution is the Azure Key Vault, but that requires an AD identity - i.e a user to access it.
What if there was a way to assign an identity to an Azure resource? There is a way, and that way is through a managed identity.
This session will look at what a managed identity is and how it works inside of Azure Active Directory, how to create and maintain managed identities and finally how to use managed identities in Azure Synapse Analytics.