Merge pull request #238317 from MicrosoftDocs/fixes

Fixing missing escape characters

Author: v-regandowner

articles/azure-arc/resource-bridge/system-requirements.md

@@ -103,7 +103,7 @@ There are several different types of configuration files, based on the on-premis
 
 ### Appliance configuration files
 
-Three configuration files are created when the `createconfig` command completes (or the equivalent commands used by Azure Stack HCI and AKS hybrid): <resourcename>-resource.yaml, <resourcename>-appliance.yaml and <resourcename>-infra.yaml.
+Three configuration files are created when the `createconfig` command completes (or the equivalent commands used by Azure Stack HCI and AKS hybrid): \<resourcename\>-resource.yaml, \<resourcename\>-appliance.yaml and \<resourcename\>-infra.yaml.
 
 By default, these files are generated in the current CLI directory when `createconfig` completes. These files should be saved in a secure location on the management machine, because they're required for maintaining the appliance VM. Because the configuration files reference each other, all three files must be stored in the same location. If the files are moved from their original location at deployment, open the files to check that the reference paths to the configuration files are accurate.
 

articles/azure-monitor/containers/container-insights-manage-agent.md

@@ -91,7 +91,7 @@ To reenable discovery of the environmental variables, apply the same process you
 ```  
 ## Semantic version update of container insights agent version
 
-Container Insights has shifted the image version and naming convention to [semver format] (https://semver.org/). SemVer helps developers keep track of every change made to a software during its development phase and ensures that the software versioning is consistent and meaningful. The old version was in format of ciprod<timestamp>-<commitId> and win-ciprod<timestamp>-<commitId>, our first image versions using the Semver format are 3.1.4 for Linux and win-3.1.4 for Windows. 
+Container Insights has shifted the image version and naming convention to [semver format] (https://semver.org/). SemVer helps developers keep track of every change made to a software during its development phase and ensures that the software versioning is consistent and meaningful. The old version was in format of ciprod\<timestamp\>-\<commitId\> and win-ciprod\<timestamp\>-\<commitId\>, our first image versions using the Semver format are 3.1.4 for Linux and win-3.1.4 for Windows. 
 
 Semver is a universal software versioning schema which is defined in the format MAJOR.MINOR.PATCH, which follows the following constraints: 
 

articles/azure-monitor/essentials/prometheus-remote-write-azure-ad-pod-identity.md

@@ -12,7 +12,7 @@ ms.reviewer: rapadman
 
 
 > [!NOTE] 
-> The remote write sidecar should only be configured via the following steps only if the AKS cluster already has the Azure AD pod enabled. This approach is not recommended as AAD pod identity has been deprecated to be replace by [Azure Workload Identity]  (https://learn.microsoft.com/azure/active-directory/workload-identities/workload-identities-verview)
+> The remote write sidecar should only be configured via the following steps only if the AKS cluster already has the Azure AD pod enabled. This approach is not recommended as AAD pod identity has been deprecated to be replace by [Azure Workload Identity](/azure/active-directory/workload-identities/workload-identities-overview)
 
 
 To configure remote write for Azure Monitor managed service for Prometheus using Azure AD pod identity, follow the steps below.
@@ -26,7 +26,7 @@ To configure remote write for Azure Monitor managed service for Prometheus using
     az role assignment create --role "Virtual Machine Contributor" --assignee <managed identity clientID> --scope <Node ResourceGroup Id> 
     ```	 
 
-    The node resource group of the AKS cluster contains resources that you will require for other steps in this process. This resource group has the name MC_<AKS-RESOURCE-GROUP>_<AKS-CLUSTER-NAME>_<REGION>. You can locate it from the Resource groups menu in the Azure portal.
+    The node resource group of the AKS cluster contains resources that you will require for other steps in this process. This resource group has the name MC_\<AKS-RESOURCE-GROUP\>_\<AKS-CLUSTER-NAME\>_\<REGION\>. You can locate it from the Resource groups menu in the Azure portal.
 
 1. Grant user-assigned managed identity `Monitoring Metrics Publisher` roles.
 

articles/migrate/troubleshoot-changed-block-tracking-replication.md

@@ -114,7 +114,7 @@ The component trying to replicate data to Azure is either down or not responding
     > [!Note]
     > This is applicable only for the projects that are set up with public endpoint.<br/> A Service bus refers to the ServiceBusNamespace type resource in the resource group for a Migrate project. The name of the Service Bus is of the format *migratelsa(keyvaultsuffix)*. The Migrate key vault suffix is available in the gateway.json file on the appliance. <br/>
     > For example, if the gateway.json contains:  <br/>
-    > *"AzureKeyVaultArmId": "/subscriptions/<SubscriptionId>/resourceGroups/<ResourceGroupName>/providers/Microsoft.KeyVault/vaults/migratekv1329610309"*,<br/> the service bus namespace resource will be *migratelsa1329610309*. 
+    > *"AzureKeyVaultArmId": "/subscriptions/\<SubscriptionId\>/resourceGroups/\<ResourceGroupName\>/providers/Microsoft.KeyVault/vaults/migratekv1329610309"*,<br/> the service bus namespace resource will be *migratelsa1329610309*. 
 
     This test checks if the Azure Migrate appliance can communicate to the Azure Migrate Cloud Service backend. The appliance communicates to the service backend through Service Bus and Event Hubs message queues. To validate connectivity from the appliance to the Service Bus, [download](https://go.microsoft.com/fwlink/?linkid=2139104) the Service Bus Explorer, try to connect to the appliance Service Bus and perform the send message/receive message operations. If there's no issue, this should be successful.
 

articles/operator-nexus/howto-cluster-metrics-configuration-management.md

@@ -72,7 +72,7 @@ az networkcloud cluster metricsconfiguration create \
  --resource-group "<RESOURCE_GROUP>"
 ```
 
-Here, <path-to-yaml-or-json-file> can be ./enabled-metrics.json or ./enabled-metrics.yaml (place the file under current working directory) before performing the action.
+Here, \<path-to-yaml-or-json-file\> can be ./enabled-metrics.json or ./enabled-metrics.yaml (place the file under current working directory) before performing the action.
 
 To see all available parameters and their description run the command:
 ```azurecli

articles/sentinel/data-connectors/digital-shadows-searchlight-using-azure-function.md

@@ -113,7 +113,7 @@ Use this method for automated deployment of the 'Digital Shadows Searchlight' co
 (add any other settings required by the Function App)
 Set the `uri` value to: `<add uri value>` 
 >Note: If using Azure Key Vault secrets for any of the values above, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Azure Key Vault references documentation](/azure/app-service/app-service-key-vault-references) for further details.
- - Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: https://<CustomerId>.ods.opinsights.azure.us. 
+ - Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: `https://<CustomerId>.ods.opinsights.azure.us`. 
 4. Once all application settings have been entered, click **Save**.
 
 

articles/sentinel/data-connectors/rubrik-security-cloud-data-connector-using-azure-function.md

@@ -25,22 +25,19 @@ The Rubrik Security Cloud data connector enables security operations teams to in
 
 **Rubrik Anomaly Events - Anomaly Events for all severity types.**
    ```kusto
-Rubrik_Anomaly_Data_CL
- 
+   Rubrik_Anomaly_Data_CL
    | sort by TimeGenerated desc
    ```
 
 **Rubrik Ransomware Analysis Events - Ransomware Analysis Events for all severity types.**
    ```kusto
-Rubrik_Ransomware_Data_CL
- 
+   Rubrik_Ransomware_Data_CL
    | sort by TimeGenerated desc
    ```
 
 **Rubrik ThreatHunt Events - Threat Hunt Events for all severity types.**
    ```kusto
-Rubrik_ThreatHunt_Data_CL
- 
+   Rubrik_ThreatHunt_Data_CL
    | sort by TimeGenerated desc
    ```
 
@@ -132,7 +129,7 @@ If you're already signed in, go to the next step.
 		RansomwareAnalysis_table_name
 		ThreatHunts_table_name
 		logAnalyticsUri (optional)
- - Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: https://<CustomerId>.ods.opinsights.azure.us. 
+ - Use logAnalyticsUri to override the log analytics API endpoint for dedicated cloud. For example, for public cloud, leave the value empty; for Azure GovUS cloud environment, specify the value in the following format: `https://<CustomerId>.ods.opinsights.azure.us`. 
 4. Once all application settings have been entered, click **Save**.
 
 

articles/storage/common/storage-use-azcopy-blobs-copy.md

@@ -25,7 +25,7 @@ See the [Get started with AzCopy](storage-use-azcopy-v10.md) article to download
 > [!NOTE]
 > The examples in this article assume that you've provided authorization credentials by using Azure Active Directory (Azure AD) and that your Azure AD identity has the proper role assignments for both source and destination accounts. 
 >
-> Alternatively you can append a SAS token to either the source or destination URL in each AzCopy command. For example: `azcopy copy 'https://<source-storage-account-name>.blob.core.windows.net/<container-name>/<blob-path><SAS-token>' 'https://<destination-storage-account-name>.blob.core.windows.net/<container-name>/<blob-path><SAS-token>'`.<blob-path><SAS-token>'.
+> Alternatively you can append a SAS token to either the source or destination URL in each AzCopy command. For example: `azcopy copy 'https://<source-storage-account-name>.blob.core.windows.net/<container-name>/<blob-path><SAS-token>' 'https://<destination-storage-account-name>.blob.core.windows.net/<container-name>/<blob-path><SAS-token>'`.
 
 ## Guidelines