My Blog

When working with Azure, you’ll encounter various types of IDs in the form of GUIDs (Globally Unique Identifiers). Understanding these IDs is crucial for managing resources, setting up authentication, and working with the Azure CLI.

When working with Azure Logic Apps (Standard) and you try to use a User-Assigned Managed Identity for accessing a storage account, you might encounter the following error:

Microsoft.Azure.Workflows.Data.Edge authentication credential type for the storage account isn't valid

In my case the error was because I was using the wrong ID as value of the AzureWebJobsStorage__managedIdentityResourceId app setting.

Imagine the following scenario on Azure: You have an App Registration A which should be able to administrate another App Registration B. For that, App Registration A should be made an owner of App Registration B. However, on the Azure Portal it is only possible to add a real user as an owner and not a Service Principal (in this case, an App Registration).

In this article, we’ll use an Azure CLI command to achieve our goal. But first, let’s clarify the difference between an App Registration and its associated Enterprise Application.

The file_header_template property in .editorconfig allows you to automatically add a license or custom header to every new C# file you create. This is especially useful for maintaining consistent file headers across your project.

Working with Azure resources often means dealing with complex FQDNs like myapp.azurewebsites.net or mystorageaccount.blob.core.windows.net. While these work perfectly fine, they’re not always the most user-friendly or company-branded names for your internal teams to remember and use. That’s where Azure Private DNS zones come to the rescue, allowing you to create custom, company-friendly aliases for your Azure resources.

In this article, I’ll show you how to set up a Private DNS zone to create a CNAME record that maps a company domain to your Azure App Service, making it accessible via a URL like app.mycompany.com.