Azure service-tag requirements and limitations
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/azure-docs · commit b56e6e5 · +0 −10 lines · also on GitHub
⋯ 159 unchanged lines
160160
>
161161
> - If you implement a [virtual network service endpoint](virtual-network-service-endpoints-overview.md) for a service, such as Azure Storage or Azure SQL Database, Azure adds a [route](virtual-networks-udr-overview.md#optional-default-routes) to a virtual network subnet for the service. The address prefixes in the route are the same address prefixes, or CIDR ranges, as those of the corresponding service tag.
162162
163
−### Tags supported in the classic deployment model
164
−
165
−The classic deployment model (before Azure Resource Manager) supports a small subset of the tags listed in the previous table. The tags in the classic deployment model are spelled differently, as shown in the following table:
166
−
167
−| Resource Manager tag | Corresponding tag in classic deployment model |
168
−|---|---|
169
−| **AzureLoadBalancer** | AZURE_LOADBALANCER |
170
−| **Internet** | INTERNET |
171
−| **VirtualNetwork** | VIRTUAL_NETWORK |
172
−
173163
### Tags unsupported for user defined routes (UDR)
174164
175165
The following list of tags is currently unsupported for use with user defined routes (UDR).
⋯ 66 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/azure-docs, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 9 Oct 23:37 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.