Merge pull request #223171 from MicrosoftDocs/repo_sync_working_branch

huypub · web-flow · commit 1788d15d670b · 2023-01-06T09:46:44.000-08:00
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
diff --git a/articles/automation/enable-managed-identity-for-automation.md b/articles/automation/enable-managed-identity-for-automation.md
@@ -308,7 +308,7 @@ Disable-AzContextAutosave -Scope Process
 # Connect to Azure with system-assigned managed identity
 $AzureContext = (Connect-AzAccount -Identity).context
 
-# set and store context
+# Set and store context
 $AzureContext = Set-AzContext -SubscriptionName $AzureContext.Subscription -DefaultProfile $AzureContext
 ```
 
@@ -435,4 +435,4 @@ Azure Automation provided authentication for managing Azure Resource Manager res
 
 - If you need to disable a managed identity, see [Disable your Azure Automation account managed identity](disable-managed-identity-for-automation.md).
 
-- For an overview of Azure Automation account security, see [Automation account authentication overview](automation-security-overview.md).
+- For an overview of Azure Automation account security, see [Automation account authentication overview](automation-security-overview.md).
diff --git a/articles/automation/troubleshoot/update-agent-issues-linux.md b/articles/automation/troubleshoot/update-agent-issues-linux.md
@@ -206,7 +206,7 @@ Curl on provided OMS endpoint
 
 ### Software repositories
 
-Fix this issue by allowing the prerequisite Repo URL. For RHEL, see [here](https://learn.microsoft.com/azure/virtual-machines/workloads/redhat/redhat-rhui#troubleshoot-connection-problems-to-azure-rhui).
+Fix this issue by allowing the prerequisite Repo URL. For RHEL, see [here](../../virtual-machines/workloads/redhat/redhat-rhui.md#troubleshoot-connection-problems-to-azure-rhui).
 
 Post making Network changes you can either rerun the Troubleshooter or
 
diff --git a/articles/azure-monitor/essentials/prometheus-remote-write-active-directory.md b/articles/azure-monitor/essentials/prometheus-remote-write-active-directory.md
@@ -208,7 +208,7 @@ This step is only required if you didn't enable Azure Key Vault Provider for Sec
     | Value | Description |
     |:---|:---|
     | `<CLUSTER-NAME>` | Name of your AKS cluster |
-    | `<CONTAINER-IMAGE-VERSION>` | `mcr.microsoft.com/azuremonitor/prometheus/promdev/prom-remotewrite:prom-remotewrite-20221102.1`<br>This is the remote write container image version.   |
+    | `<CONTAINER-IMAGE-VERSION>` | `mcr.microsoft.com/azuremonitor/prometheus/promdev/prom-remotewrite:prom-remotewrite-20221103.1`<br>This is the remote write container image version.   |
     | `<INGESTION-URL>` | **Metrics ingestion endpoint** from the **Overview** page for the Azure Monitor workspace |
     | `<APP-REGISTRATION -CLIENT-ID> ` | Client ID of your application |
     | `<TENANT-ID> ` | Tenant ID of the Azure Active Directory application |
diff --git a/articles/azure-monitor/essentials/prometheus-remote-write-managed-identity.md b/articles/azure-monitor/essentials/prometheus-remote-write-managed-identity.md
@@ -134,7 +134,7 @@ This step isn't required if you're using an AKS identity since it will already h
     | Value | Description |
     |:---|:---|
     | `<AKS-CLUSTER-NAME>` | Name of your AKS cluster |
-    | `<CONTAINER-IMAGE-VERSION>` | `mcr.microsoft.com/azuremonitor/prometheus/promdev/prom-remotewrite:prom-remotewrite-20221102.1`<br>This is the remote write container image version.   |
+    | `<CONTAINER-IMAGE-VERSION>` | `mcr.microsoft.com/azuremonitor/prometheus/promdev/prom-remotewrite:prom-remotewrite-20221103.1`<br>This is the remote write container image version.   |
     | `<INGESTION-URL>` | **Metrics ingestion endpoint** from the **Overview** page for the Azure Monitor workspace |
     | `<MANAGED-IDENTITY-CLIENT-ID>` | **Client ID** from the **Overview** page for the managed identity |
     | `<CLUSTER-NAME>` | Name of the cluster Prometheus is running on |
diff --git a/articles/machine-learning/how-to-use-pipeline-ui.md b/articles/machine-learning/how-to-use-pipeline-ui.md
@@ -263,7 +263,7 @@ Along with the profiling, you can also use the *Output + logs* (on the details p
   - In this view, you'll see more nodes than in critical path.
 - Compact view
   - You'll only see step jobs that are longer than 30 seconds.
-- Structured view.
+- Hierarchical view.
   - You'll see all jobs including pipeline component jobs and step jobs.
 
 ### Download the duration table
diff --git a/articles/sentinel/normalization.md b/articles/sentinel/normalization.md
@@ -91,7 +91,7 @@ On the other hand, while ASIM parsers are optimized, query time parsing can slow
 
 Currently, ASIM supports the following normalized tables as a destination for ingest time normalization:
 - [**ASimDnsActivityLogs**](/azure/azure-monitor/reference/tables/asimdnsactivitylogs) for the [DNS](normalization-schema-dns.md) schema.
-- [**ASimNetworkSessionLogs**](/azire/azure-monitor/reference/tables/asimnetworksessionlogs) for the [NetworkS Session](network-normalization-schema.md) schema 
+- [**ASimNetworkSessionLogs**](/azure/azure-monitor/reference/tables/asimnetworksessionlogs) for the [Network Session](network-normalization-schema.md) schema 
  
 For more information, see [Ingest Time Normalization](normalization-ingest-time.md).
 
diff --git a/articles/synapse-analytics/get-started-create-workspace.md b/articles/synapse-analytics/get-started-create-workspace.md
@@ -66,7 +66,7 @@ After your Azure Synapse workspace is created, you have two ways to open Synapse
 > To sign into your workspace, there are two **Account selection methods**. One is from **Azure subscription**, the other is from **Enter manually**. If you have the Synapse Azure role or higher level Azure roles, you can use both methods to log into the workspace. If you don't have the related Azure roles, and you were granted as the Synapse RBAC role, **Enter manually** is the only way to log into the workspace. To learn more about the Synapse RBAC, refer to [What is Synapse role-based access control (RBAC)](./security/synapse-workspace-synapse-rbac.md).
 
 ## Place sample data into the primary storage account
-We are going to use a small 100K row sample dataset of NYX Taxi Cab data for many examples in this getting started guide. We begin by placing it in the primary storage account you created for the workspace.
+We are going to use a small 100K row sample dataset of NYC Taxi Cab data for many examples in this getting started guide. We begin by placing it in the primary storage account you created for the workspace.
 
 * Download the [NYC Taxi - green trip dataset](../open-datasets/dataset-taxi-green.md?tabs=azureml-opendatasets#additional-information) to your computer. Navigate to the [original dataset location](https://www.nyc.gov/site/tlc/about/tlc-trip-record-data.page) from the above link, choose a specific year and download the Green taxi trip records in Parquet format.
 * Rename the downloaded file to *NYCTripSmall.parquet*.
