Preserving Azure Key Vault access policies when recreating with Bicep
While RBAC roles are the preferred access control method for Key Vaults, there are still projects where you need to work with access policies, where a Managed Identity is given specific permissions to the Key Vault.
In the latter case, a common challenge arises when recreating a Key Vault with Bicep - you lose all existing access policies. This phenomenon is documented in this GitHub issue.
In this article, you will find a simple trick to preserve and reapply them during deployment.
How to reference a feature branch inside an Azure DevOps Pipeline
When working with Azure Pipelines, you may need to access a repository and reference its code from a specific feature branch instead of the default branch. I am dealing with this scenario almost everyday and the most common case is testing changes made on a feature branch, before they’re merged to the main branch.
Fix 403 Forbidden errors between Logic Apps and Azure Functions
When calling an Azure Function from a Logic App, you might encounter a 403 Forbidden error with the response header x-ms-forbidden-ip. This happens when the Function’s networking rules block the IP address or the subnet of the Logic App.
Fix the no user-assigned managed identity found error in Azure
When working with Managed Identities in Azure you might encounter the error No user assigned or delegated managed identity found for specified clientid/resourceid/principalid.
But first of all let us see what a Managed Identity is and does.
When working with Azure Bicep, you can safely reference an existing Azure resource using the existing keyword. This eliminates the risk of unintended modifications or deletions.
Here’s the syntax to retrieve an existing resource: