A keyvault created with access policy using BICEP creates compound identity
I’m creating infrastructure in Azure using BICEP for our enterprise application. Our application uses key vaults to store and recall secrets using a service principal (application).