Skip to content

Commit 12e7a37

Browse files
Update tag-support.md
Removed: "> For Azure Front Door Service, you can apply tags when creating the resource, but updating or adding tags is not currently supported. Front Door doesn't support the use of # or : in the tag name." Tested this in my lab and this appears to be false on all 3 SKUs: Classic, Standard, Premium. I can show to the Contributor in case there is doubt. Also tested the Traffic Manager / DNS Zone claim and that appears to be correct.
1 parent 0ad2a07 commit 12e7a37

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

articles/azure-resource-manager/management/tag-support.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2367,8 +2367,6 @@ To get the same data as a file of comma-separated values, download [tag-support.
23672367
<a id="network-limitations"></a>
23682368

23692369
> [!NOTE]
2370-
> For Azure Front Door Service, you can apply tags when creating the resource, but updating or adding tags is not currently supported. Front Door doesn't support the use of # or : in the tag name.
2371-
>
23722370
> Azure DNS zones and Traffic Manager doesn't support the use of spaces in the tag or a tag that starts with a number. Azure DNS and Traffic Manager tag names do not support special and unicode characters. The value can contain all characters.
23732371
>
23742372
> Azure IP Groups and Azure Firewall Policies don't support PATCH operations, which means they don't support updating tags through the portal. Instead, use the update commands for those resources. For example, you can update tags for an IP group with the [az network ip-group update](/cli/azure/network/ip-group#az-network-ip-group-update) command.

0 commit comments

Comments
 (0)