Merge pull request #116058 from shashankbarsin/master

Address broken links and add role requirements for onboarding

Author: GitHubber17

articles/azure-arc/kubernetes/connect-cluster.md

@@ -21,7 +21,7 @@ Verify you have the following requirements ready:
 
 * A Kubernetes cluster that is up and running
 * You'll need access with kubeconfig, and cluster-admin access. 
-* The user or service principal used with `az login` and `az connectedk8s connect` commands must have the 'Read' and 'Write' permissions on the 'Microsoft.Kubernetes/connectedclusters' resource type.
+* The user or service principal used with `az login` and `az connectedk8s connect` commands must have the 'Read' and 'Write' permissions on the 'Microsoft.Kubernetes/connectedclusters' resource type. The "Azure Arc for Kubernetes Onboarding" role having these permissions can be used for role assignments on the user or service principal used with Azure CLI for onboarding.
 * Latest version of the *connectedk8s* and *k8sconfiguration* extensions
 
 ## Supported regions

articles/azure-arc/kubernetes/toc.yml

@@ -14,12 +14,12 @@
       href: use-gitops-connected-cluster.md
     - name: Use GitOps with Helm
       href: use-gitops-with-helm.md
+    - name: Use Azure Policy
+      href: use-azure-policy.md
     - name: Azure Monitor for containers
       href: deploy-azure-monitor-for-containers.md
     - name: Install Azure Policy add-on
       href: ../../governance/policy/concepts/policy-for-kubernetes.md?toc=/azure/azure-arc/kubernetes/toc.json
-    - name: Use Azure Policy
-      href: use-azure-policy.md
     - name: Deploy IoT workloads
       href: deploy-azure-iot-edge-workloads.md
     - name: Onboarding service principal

articles/azure-arc/kubernetes/use-azure-policy.md

@@ -60,4 +60,4 @@ After the policy assignment is created, for any new `connectedCluster` resource
 
 ## Next steps
 
-* [Use Azure Policy to govern cluster configuration](./use-azure-policy.md)
+* [Set up Azure Monitor for Containers with Arc enabled Kubernetes clusters](./deploy-azure-monitor-for-containers.md)

articles/azure-arc/kubernetes/use-gitops-connected-cluster.md

@@ -36,7 +36,7 @@ The example repository is structured around the persona of a cluster operator wh
 **ConfigMap:** `team-a/endpoints`
 
 The `config-agent` polls Azure for new or updated `sourceControlConfiguration` every 30 seconds.  This is the maximum time it will take for the `config-agent` to pick up a new or updated configuration.
-If you are associating a private repository, assure that you also complete the steps in [Apply configuration from a private git repository](https://github.com/Azure/azure-arc-kubernetes-preview/blob/master/docs/use-gitops-in-connected-cluster.md#apply-configuration-from-a-private-git-repository)
+If you are associating a private repository, assure that you also complete the steps in [Apply configuration from a private git repository](#apply-configuration-from-a-private-git-repository)
 
 ### Using Azure CLI
 
@@ -141,9 +141,9 @@ Options supported in  --operator-params
 
 * If enableHelmOperator is true, then operatorInstanceName + operatorNamespace strings cannot exceed 47 characters combined.  If you fail to adhere to this limit then you will get this error:
 
-```console
-{"OperatorMessage":"Error: {failed to install chart from path [helm-operator] for release [<operatorInstanceName>-helm-<operatorNamespace>]: err [release name \"<operatorInstanceName>-helm-<operatorNamespace>\" exceeds max length of 53]} occurred while doing the operation : {Installing the operator} on the config","ClusterState":"Installing the operator"}
-```
+   ```console
+   {"OperatorMessage":"Error: {failed to install chart from path [helm-operator] for release [<operatorInstanceName>-helm-<operatorNamespace>]: err [release name \"<operatorInstanceName>-helm-<operatorNamespace>\" exceeds max length of 53]} occurred while doing the operation : {Installing the operator} on the config","ClusterState":"Installing the operator"}
+   ```
 
 For more info see [Flux documentation](https://aka.ms/FluxcdReadme).