Updated Tagging Nodes Documentation page (#436)

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Freshness Pass

* Update 8-1-0.md

* Update 8-1-0.md

* Update 8-1-0.md

* Update 8-4-0.md

* Update tag-nodes.md

Added note about the restricted characters when tagging nodes and added an example.

* Update tag-nodes.md

* Update tag-nodes.md

Removed moniker tag

Author: bgtheswe

articles/cyclecloud/how-to/tag-nodes.md

@@ -2,7 +2,7 @@
 title: Tagging Nodes
 description: Learn about tagging nodes in Azure CycleCloud. CycleCloud automatically adds Azure tags to resources created from nodes.
 author: adriankjohnson
-ms.date: 03/20/2020
+ms.date: 2/7/2025
 ms.author: adjohnso
 ---
 
@@ -16,9 +16,9 @@ Azure CycleCloud will automatically create and add three tags to each node: a na
 | Name                 | Name of the node (for head node resources only)                                        |
 | CycleOwner           | The user that started the node                                                         |
 | LaunchTime           | The time that this resource was created                                                |
-| ClusterId            | A identifier for the cluster (deprecated as of 8.2)                                    |
-| CycleCloudCluster    | A globally unique name for the cluster (as of 8.2)                                     |
-| CycleCloudNodeArray  | A globally unique name for the nodearray, if it comes from a nodearray (as of 8.2)     |
+| ClusterId            | A identifier for the cluster (Available on CycleCloud v8.2 or earlier)                                    |
+| CycleCloudCluster    | A globally unique name for the cluster (Available from CycleCloud v8.2 onwards)        |
+| CycleCloudNodeArray  | A globally unique name for the nodearray, if it comes from a nodearray (Available from CycleCloud v8.2 onwards)     |
 
 The formats for the encoded tags are as follows:
 - `CycleCloudCluster`: /sites/[site_id]/clusters/[cluster_name]
@@ -47,11 +47,11 @@ Nodes in the "Compute" nodearray would get an additional tag:
 CycleCloudNodeArray => "/sites/92xy4vgh/clusters/Demo/nodearrays/Compute"
 ```
 
-::: moniker range=">=cyclecloud-8"
+#::: moniker range=">=cyclecloud-8"
 > [!NOTE]
 > The CycleCloudCluster and CycleCloudNodeArray tags were added in 8.2 to make it easier to get costs from Azure Cost Management, using a standard format also used for 
 > the subject of [events sent to Event Grid](~/events.md#subject). The value for ClusterId is not constant over time, since the site name and owner can be changed.
-::: moniker-end
+#::: moniker-end
 
 
 Within a resource that supports [Resource Manager Operations](/azure/azure-resource-manager/resource-group-using-tags) you can create additional tags to assign to the instance by specifying them with a node definition inside your template:
@@ -74,13 +74,20 @@ CustomText => "Hello world"
 
 ## Restrictions
 
-There are limits on the number and format of tags applied to each Virtual Machine. Please review the [Tagging Azure Resources documentation](/azure/azure-resource-manager/resource-group-using-tags) for full details.
+There are limits on the number and format of tags applied to each Virtual Machine. Please review the [Limitations on tagging Azure Resources documentation](/azure/azure-resource-manager/management/tag-resources#limitations) for full details.
 
 Do not include quotation marks or periods in your tag names.
 
 > [!NOTE]
-> Tag names in CycleCloud cannot contain the following characters:<br>
->  `.` `"` `:` `=`
+> Tag names in CycleCloud cannot contain the following characters: `.` `"` `:` `=`
+> If a tag needs to include a period ('.'), use the notation Tag == ['tag.subtag'=value]. For instance, if you want to create a tag named compute.node, you should use Tag == ['compute.node'=value].
+> 
+> Also, following are some alternatives to the notation Tag == ['tag.subtag'=value] for defining tags with periods:
+> - **Underscores**: Use underscores instead of periods, e.g., Tag == ['compute_node'=value].
+> - **CamelCase**: Combine the main tag and subtag without separators, e.g., Tag == ['computeNode'=value].
+> - **Nested Tags**: Represent the hierarchical structure, e.g., Tag == ['compute'={'node'=value}].
+> - **Colon Separator**: Use a colon instead of a period, e.g., Tag == ['compute:node'=value].
+
 
 ## Further Reading