When working with Azure, you will encounter various types of IDs in the form of GUIDs (Globally Unique Identifiers). Understanding these IDs is crucial for managing resources, configuring access, and using the Azure CLI (az) effectively.
We’ll explore these IDs (terms in backticks match the Azure portal labels):
Tenant ID — identifies your Microsoft Entra ID directory; used for authentication and identity management.
Subscription ID — identifies a subscription; used for billing and scoping resource operations.
Resource GUID — an internal GUID assigned to a resource instance; helpful for cross-referencing resources.
Resource ID — the full ARM path showing where a resource lives; used in ARM templates and API calls.
Application (Client) ID — the client identifier (appId) for a registered application; used in OAuth flows.
Object ID — a tenant-scoped identifier for directory objects like users and service principals.
How to Solve the "authentication credential type for the storage account isn't valid" Error in Azure Logic Apps
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.
Add an Enterprise Application aka. Service Principal as owner of an App Registration
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.
Add a file header to your C# files with the help of .editorconfig
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.
Creating Private DNS Zones for company-friendly aliases (CNAME) in Azure
Ever struggled with cryptic Azure resource URLs like myapp123.westeurope.cloudapp.azure.com 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.