Merge pull request #259494 from yossi-y/patch-14

Updated linked workspace section

Author: prmerger-automator[bot]

articles/azure-monitor/logs/logs-dedicated-clusters.md

@@ -201,32 +201,34 @@ The managed identity service generates the *principalId* GUID when you create th
 
 ---
 
-
 ## Link a workspace to a cluster
 
 When a Log Analytics workspace is linked to a dedicated cluster, the workspace billing plan in workspace is changed to cluster plan, new data ingested to the workspace is routed to your dedicated cluster, and existing data remains in Log Analytics cluster. Linking a workspace has no effect on data ingestion and query experiences. Log Analytics query engine stitches data from old and new clusters automatically, and the results of queries are complete and accurate. 
 
 When dedicated cluster is configured with customer-managed key (CMK), new ingested data is encrypted with your key, while older data remains encrypted with Microsoft-managed key (MMK). The key configuration is abstracted by Log Analytics and the query across old and new data encryptions is performed seamlessly.
 
-A cluster can be linked to up to 1,000 workspaces. Linked workspaces must be located in the same region as the cluster. A workspace can't be linked to a cluster more than twice a month, to prevent data fragmentation.
+A cluster can be linked to up to 1,000 workspaces located in the same region as the cluster. A workspace can't be linked to a cluster more than twice a month, to prevent data fragmentation.
+
+Other than the billing aspects that is governed by the cluster plan, all workspace configurations and query aspects remain unchanged after the link.
+
+The workspace and the cluster can be in different subscriptions. It's possible for the workspace and cluster to be in different tenants if Azure Lighthouse is used to map both of them to a single tenant.
 
 You need 'write' permissions to both the workspace and the cluster resource for workspace link operation:
 
 - In the workspace: *Microsoft.OperationalInsights/workspaces/write*
 - In the cluster resource: *Microsoft.OperationalInsights/clusters/write*
 
-Other than the billing aspects that is governed by the cluster plan, the linked workspace configuration remain.
-
-The workspace and the cluster can be in different subscriptions. It's possible for the workspace and cluster to be in different tenants if Azure Lighthouse is used to map both of them to a single tenant.
-
 > [!NOTE]
 > Linking a workspace can be performed only after the completion of the Log Analytics cluster provisioning.
 > Linking a workspace to a cluster involves syncing multiple backend components and cache hydration, which can take up to two hours.
 
-Use the following commands to link a workspace to a cluster:
+Use the following steps to link a workspace to a cluster. You can automated for linking multiple workspaces:
 
 #### [CLI](#tab/cli)
 
+> [!NOTE]
+> Use **cluster** value for linked-service ```name```.
+
 ```azurecli
 # Find cluster resource ID
 az account set --subscription "cluster-subscription-id"
@@ -243,6 +245,9 @@ az resource wait --deleted --ids $workspaceResourceId --include-response-body tr
 
 #### [PowerShell](#tab/powershell)
 
+> [!NOTE]
+> Use **cluster** value for ```LinkedServiceName```.
+
 ```powershell
 Select-AzSubscription "cluster-subscription-id"
 
@@ -258,7 +263,7 @@ Set-AzOperationalInsightsLinkedService -ResourceGroupName "resource-group-name"
 Get-Job -Command "Set-AzOperationalInsightsLinkedService" | Format-List -Property *
 ```
 
-#### [REST API](#tab/restapi)
+#### [REST API](#tab/restapi)
 
 Use the following REST call to link to a cluster:
 
@@ -282,6 +287,7 @@ Content-type: application/json
 
 ---
 
+
 ### Check workspace link status
 
 When a cluster is configured with customer-managed keys, data ingested to the workspaces after the link operation completion is stored encrypted with your managed key. The workspace link operation can take up to 90 minutes to complete and you can check the state by sending Get request to workspace and observe if *clusterResourceId* property is present in the response under *features*.