How to Use the Azure Resource ID Parser

Paste an Azure resource ID — from the Azure Portal's "Properties" blade, an ARM/Bicep template, or
az
CLI output — into the box.
Click Parse. The tool splits it into its labeled parts instantly in your browser.
Read the breakdown: subscription ID, resource group, provider namespace, resource type, and resource name — with any nested child-resource segments called out separately.
Nothing you paste is uploaded anywhere — this is pure string parsing running as JavaScript in your browser tab.

The Azure Resource ID Grammar

Every Azure Resource Manager (ARM) resource has a canonical ID with a fixed, hierarchical structure:

/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/{resourceProviderNamespace}/{resourceType}/{resourceName}

{subscriptionId}
— the GUID identifying the Azure subscription.
{resourceGroupName}
— the resource group the resource lives in.
{resourceProviderNamespace}
— the Azure resource provider, e.g.
Microsoft.Storage
,
Microsoft.Compute
,
Microsoft.Network
. Every Azure resource type belongs to exactly one provider namespace.
{resourceType}
/
{resourceName}
— the specific type within that provider (e.g.
storageAccounts
) and the resource's own name.

Worked Example

/subscriptions/12345678-1234-1234-1234-123456789012/resourceGroups/myResourceGroup/providers/Microsoft.Storage/storageAccounts/mystorageaccount

decodes as: subscription

12345678-...

, resource group

myResourceGroup

, provider

Microsoft.Storage

, resource type

Microsoft.Storage/storageAccounts

, resource name

mystorageaccount

Nested (Child) Resources

Some Azure resources live inside another resource, and their ID reflects that by repeating

{type}/{name}

pairs after the parent's own type/name. A subnet, for example, exists inside a virtual network:

/subscriptions/.../resourceGroups/net-rg/providers/Microsoft.Network/virtualNetworks/myVnet/subnets/mySubnet

This parser correctly walks every

{type}/{name}

pair in the chain rather than stopping at the first one, so a nested resource like the subnet above is reported with its full type chain (

virtualNetworks/myVnet → subnets/mySubnet

) and its combined resource type

Microsoft.Network/virtualNetworks/subnets

, not truncated at the parent.

Two Shorter, Also-Valid Forms

Not every real Azure resource ID has all the segments above:

Resource-group-only ID (no provider):
/subscriptions/{id}/resourceGroups/{rg}
— this is the resource group itself as a manageable object, not a resource inside it.
Subscription-level resource (no resource group):
/subscriptions/{id}/providers/{namespace}/{type}/{name}
— some resource types (like policy definitions) are scoped to the subscription directly, skipping the resource-group level entirely.

Both are recognized and correctly labeled by this tool rather than being rejected as malformed.

What's Out of Scope: Management-Group and Tenant-Scoped IDs

Azure also has resource IDs scoped above the subscription level entirely — management-group-scoped IDs (

/providers/Microsoft.Management/managementGroups/{id}

) and tenant-scoped IDs. These follow a genuinely different structure from the subscription-scoped form this tool implements, and rather than force them through the wrong parser and produce a mis-labeled result, this tool reports them as out of scope.

What This Tool Does NOT Do

This is a structure-only parser. It does not call the Azure Resource Manager API, and it cannot confirm the subscription, resource group, or resource actually exists, or that you have permission to access it. An ID that parses cleanly here is grammatically well-formed — it is not proof the resource is real.

Frequently Asked Questions

Are Azure resource ID segment names case-sensitive? The path segment keywords themselves (

subscriptions

resourceGroups

providers

) are matched case-insensitively by this tool, matching how Azure's own APIs generally treat them — but the actual values (subscription ID, resource group name, resource name) are shown exactly as typed.

Why does my storage account's ID have

Microsoft.Storage

twice, sort of? It doesn't —

Microsoft.Storage

(the provider namespace) appears once, immediately followed by

storageAccounts

(the resource type within that provider) and then the actual account name. The "resource type" this tool reports (

Microsoft.Storage/storageAccounts

) is the namespace and type combined, which is how Azure documentation itself refers to a resource type.

Is my resource ID uploaded or stored anywhere? No. The parsing runs entirely as JavaScript inside your browser tab — nothing is sent to a server, logged, or stored.

Is this tool free? Yes, completely free, no login, no limit.