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.
Read the complete articleWhen 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:
Read the complete articleWhen 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.
Read the complete articleWhen working with Azure DevOps pipelines you will often want your tasks to run PowerShell scripts. Since the execution of the upcoming tasks can be dependent to the result of the current task, your script will have to inform about success or error.
For this task you can use exit codes, which indicate the success or failure of a command or script. We are also going to learn how to use the $LASTEXITCODE variable to determine the outcome of your commands.