Naming Considerations v1.1 Publish

Author: BernieEllis

.openpublishing.redirection.json

@@ -3780,6 +3780,11 @@
       "redirect_url": "/azure/azure-government/documentation-government-welcome",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/azure-government/documentation-government-k8.md",
+      "redirect_url": "/azure/azure-government",
+      "redirect_document_id": false
+    },
     {
       "source_path": "articles/azure-portal/resource-group-portal-linked-resources.md",
       "redirect_url": "/azure/azure-portal/azure-portal-dashboards",

articles/azure-government/documentation-government-concept-naming-resources.md

@@ -1,5 +1,5 @@
 ---
-title: Considerations for Naming Azure Resources | Microsoft Docs
+title: Considerations for naming Azure resources | Microsoft Docs
 description: This article contains guidance on how customers should consider naming their Azure resources to prevent attribution to business/mission sensitive workloads.
 services: Azure-government
 cloud: gov
@@ -15,9 +15,9 @@ ms.date: 4/6/2020
 ms.author: beellis
 
 ---
-# Considerations for Naming Azure Resources
+# Considerations for naming Azure resources
 Customers should not include sensitive or restricted information in Azure Resource Names because they may be stored or accessed outside the compliance boundary to facilitate support and troubleshooting.
-Azure Resource Names include information provided by you, or on your behalf, that is used to identify or configure Online Service resources, such as software, systems, or containers, but does **not** include customer-created content or metadata inside the resource (for example, database column/table names).  Azure Resource Names include the names a customer assigns to ARM-level objects and resources deployed in Azure.  Examples include the names of resources such as:
+Azure Resource Names include information provided by you, or on your behalf, that is used to identify or configure Online Service resources, such as software, systems, or containers, but does **not** include customer-created content or metadata inside the resource (for example, database column/table names).  Azure Resource Names include the names a customer assigns to Azure Resource Manager level objects and resources deployed in Azure.  Examples include the names of resources such as:
 *    VNets (Virtual Networks)
 *    Virtual Hard Disks (VHDs)
 *    Database Servers & Databases
@@ -29,7 +29,7 @@ Azure Resource Names include information provided by you, or on your behalf, tha
 >The above examples are but a subset of the types of resources customers can name. This list is not meant to be fully exhaustive and the types of resources could change in the future as new cloud services are added.
 >
 
-## Azure Resource Naming Convention
+## Naming convention
 The names of Azure resources are part of a larger resource ID as follows:
 
 `/subscriptions/<subscriptionID>/resourceGroups/<ResourceGroupName>/providers/<ResourceProvider>/<ResourceType>/<ResourceName>`
@@ -39,7 +39,7 @@ An example of a virtual machine resource ID is:
 `/subscriptions/<subscriptionID>/resourceGroups/<ResourceGroupName>/providers/Microsoft.Compute/virtualMachines/<virtualMachineName>`
 
 
-## Resource Naming Considerations
+## Naming considerations
 For all names that meet the criteria above, from the name of the larger resource group to the name of the end resources within it, customers should avoid names that are sensitive to business/mission functions.  Customers should also avoid names that indicate customer regulatory requirements (e.g., [ITAR](https://docs.microsoft.com/microsoft-365/compliance/offering-itar?view=o365-worldwide), [CJIS](https://docs.microsoft.com/microsoft-365/compliance/offering-cjis?view=o365-worldwide), etc.), as applicable.
 
 >[!NOTE]