Merge pull request #313770 from msmbaldwin/security-placeholders

Standardize placeholders in security docset

Author: prmerger-automator[bot]

articles/security/develop/threat-modeling-tool-authentication.md

@@ -6,7 +6,7 @@ author: jegeib
 ms.service: azure-information-protection
 ms.subservice: azure-information-protection-policy
 ms.topic: article
-ms.date: 02/07/2017
+ms.date: 03/26/2026
 ms.author: jegeib
 ms.custom: devx-track-csharp
 ---
@@ -483,7 +483,7 @@ await deviceClient.SendEventAsync(message);
     ```javascript
     var clientFromConnectionString = require('azure-iot-device-amqp').clientFromConnectionString;
     var Message = require('azure-iot-device').Message;
-    var connectionString = 'HostName=<HostName>DeviceId=<DeviceId>SharedAccessKey=<SharedAccessKey>';
+    var connectionString = 'HostName=<host-name>DeviceId=<device-id>SharedAccessKey=<shared-access-key>';
     var client = clientFromConnectionString(connectionString);
     ```
   #### SAS Token
@@ -492,7 +492,7 @@ await deviceClient.SendEventAsync(message);
 * Create a sas token :
     ```javascript
     resourceUri = encodeURIComponent(resourceUri.toLowerCase()).toLowerCase();
-    var deviceName = "<deviceName >";
+    var deviceName = "<device-name>";
     var expires = (Date.now() / 1000) + expiresInMins * 60;
     var toSign = resourceUri + '\n' + expires;
     // using crypto
@@ -515,13 +515,13 @@ await deviceClient.SendEventAsync(message);
 * Generate a self signed X509 certificate using any tool such as OpenSSL to generate a .cert and .key files to store the certificate and the key respectively
 * Provision a device that accepts secured connection using certificates.
     ```javascript
-    var connectionString = '<connectionString>';
+    var connectionString = '<connection-string>';
     var registry = iothub.Registry.fromConnectionString(connectionString);
-    var deviceJSON = {deviceId:"<deviceId>",
+    var deviceJSON = {deviceId:"<device-id>",
     authentication: {
         x509Thumbprint: {
-        primaryThumbprint: "<PrimaryThumbprint>",
-        secondaryThumbprint: "<SecondaryThumbprint>"
+        primaryThumbprint: "<primary-thumbprint>",
+        secondaryThumbprint: "<secondary-thumbprint>"
         }
     }}
     var device = deviceJSON;
@@ -531,7 +531,7 @@ await deviceClient.SendEventAsync(message);
     ```javascript
     var Protocol = require('azure-iot-device-http').Http;
     var Client = require('azure-iot-device').Client;
-    var connectionString = 'HostName=<HostName>DeviceId=<DeviceId>x509=true';
+    var connectionString = 'HostName=<host-name>DeviceId=<device-id>x509=true';
     var client = Client.fromConnectionString(connectionString, Protocol);
     var options = {
         key: fs.readFileSync('./key.pem', 'utf8'),

articles/security/fundamentals/trusted-hardware-identity-management.md

@@ -6,7 +6,7 @@ ms.service: security
 ms.subservice: security-fundamentals
 ms.topic: article
 ms.author: mbaldwin
-ms.date: 04/16/2025
+ms.date: 03/26/2026
 ---
 
 # Trusted Hardware Identity Management
@@ -184,25 +184,25 @@ Follow these steps to request AMD collateral in a confidential container:
        1. Create a resource group in one of the CVM supported regions:
 
           ```bash
-          az group create --resource-group <RG_NAME> --location <LOCATION> 
+          az group create --resource-group <resource-group> --location <location> 
           ```
 
        2. Create an AKS cluster with one CVM node in the resource group:
 
           ```bash
-          az aks create --name <CLUSTER_NAME> --resource-group <RG_NAME> -l <LOCATION> --node-vm-size Standard_DC4as_v5 --nodepool-name <POOL_NAME> --node-count 1
+          az aks create --name <aks-cluster-name> --resource-group <resource-group> -l <location> --node-vm-size Standard_DC4as_v5 --nodepool-name <pool-name> --node-count 1
           ```
 
        3. Configure kubectl to connect to the cluster:
 
           ```bash
-          az aks get-credentials --resource-group <RG_NAME> --name <CLUSTER_NAME> 
+          az aks get-credentials --resource-group <resource-group> --name <aks-cluster-name> 
           ```
 
     - Add a CVM node pool to an existing AKS cluster:
 
       ```bash
-      az aks nodepool add --cluster-name <CLUSTER_NAME> --resource-group <RG_NAME> --name <POOL_NAME > --node-vm-size Standard_DC4as_v5 --node-count 1 
+      az aks nodepool add --cluster-name <aks-cluster-name> --resource-group <resource-group> --name <pool-name> --node-vm-size Standard_DC4as_v5 --node-count 1 
       ```
 
 2. Verify the connection to your cluster by using the `kubectl get` command. This command returns a list of the cluster nodes.