liveBook · Manning

Service tag

As explained in Azure Security

An Azure service tag is a managed identifier representing the IP address prefixes used by a category of Azure services.

A service tag identifies the IP address prefixes used by a category of Azure services. In Azure App Service access restrictions, it lets you allow or deny traffic from that service category instead of maintaining individual address ranges. section 4.5.2

Use service tags with these access-restriction controls:

  • Set an Allow or Deny action and assign a priority; the lowest priority takes precedence. section 4.5.2
  • Remember that access restrictions control inbound traffic and do not restrict traffic entering through a private endpoint. section 4.5.2

Allow Azure Front Door traffic

Run az webapp config access-restriction add for ContosoWebApp001 with --action Allow, --priority 200, --service-tag AzureFrontDoor.Backend, and the required x-azure-fdid header. The resulting rule records the service tag and header condition.

How Azure Security covers it

How deep it goes
Explains rule types, priority, limits, and CLI configuration, but stops short of service-tag maintenance internals.
Examples
Uses an Azure Front Door rule with AzureFrontDoor.Backend, priority 200, and an x-azure-fdid header.
What it assumes
Assumes an Azure App Service workload and access-restriction permissions; introduces service-tag rule configuration.
What you can do after
Apply it via Azure CLI to create and inspect a service tag–based App Service access restriction.
How it connects
Connects service tags with Azure App Service, access restrictions, Azure Front Door, HTTP headers, and private endpoints.

Also explained in

Compare how 2 books explain service tag →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Azure Security. The section links point to the parts of the book it draws on.