Create a new API Connection and Access Policy for connecting Your Azure Logic App to Blob Storage in Bicep
When building workflows with Azure Logic Apps (Standard), a common requirement is to connect securely to Azure resources such as Blob Storage. In this article, we’ll show how to automate the creation of API Connections and Access Policies using Bicep, enabling your Logic Apps to access Blob Storage securely. We’ll cover both authentication methods: Shared Key and Managed Identity.
How to Fix "The connection to the Cosmos DB database could not be made due to missing authorizations" in Azure AI Search
When integrating Azure AI Search with Cosmos DB, you might encounter the following error:
The connection to the Cosmos DB database '<the-name-of-the-database>' could not be made due to missing authorizations
This error typically means that the Managed Identity used by your Azure AI Search service does not have the necessary data plane permissions on the Cosmos DB account.
The correct syntax when using capturing groups in PowerShell
When working with regular expressions in PowerShell, capturing groups allow you to extract specific parts of a matched pattern. However, there are two important syntax considerations when referencing these groups in your code.
But first, let us understand what a capturing group is.
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.