My Blog

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.

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.

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:

When working with Azure Pipelines, the checkout keyword is typically used to reference a Git repository with a fixed name. For example in your Azure Pipeline you will add the following line:

- checkout: git://MyProject/MyRepository

While this works well for static scenarios, what if you’re working with multiple repositories? For instance, when automating tasks that iterate over a list of repositories, hardcoding each repository name becomes inefficient and error-prone.