acrolinx and table

Author: JnHs

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

@@ -16,29 +16,31 @@ To use Azure Policy, select a built-in policy definition and create a policy ass
 
 Once the assignment is created, the Azure Policy engine identifies all Azure Arc-enabled Kubernetes clusters located within the scope and applies the GitOps configuration to each cluster.
 
-To enable separation of concerns, you can create multiple policy assignments, each with a different Flux v2 configuration pointing to a different source. For example, one Git repository may be used by cluster admins and other repositories may be used by application teams.
+To enable separation of concerns, you can create multiple policy assignments, each with a different Flux v2 configuration pointing to a different source. For example, one Git repository can be used by cluster admins while other repositories can be used by application teams.
 
 ## Built-in policy definitions
 
 The following [built-in policy definitions](policy-reference.md) provide support for these scenarios:
 
-* Flux extension install (required for all scenarios): `Configure installation of Flux extension on Kubernetes cluster`
-* Flux configuration using public Git repository (generally a test scenario): `Configure Kubernetes clusters with Flux v2 configuration using public Git repository`
-* Flux configuration using private Git repository with SSH auth: `Configure Kubernetes clusters with Flux v2 configuration using Git repository and SSH secrets`
-* Flux configuration using private Git repository with HTTPS auth: `Configure Kubernetes clusters with Flux v2 configuration using Git repository and HTTPS secrets`
-* Flux configuration using private Git repository with HTTPS CA cert auth: `Configure Kubernetes clusters with Flux v2 configuration using Git repository and HTTPS CA Certificate`
-* Flux configuration using private Git repository with local K8s secret: `Configure Kubernetes clusters with Flux v2 configuration using Git repository and local secrets`
-* Flux configuration using private Bucket source and KeyVault secrets: `Configure Kubernetes clusters with Flux v2 configuration using Bucket source and secrets in KeyVault`
-* Flux configuration using private Bucket source and local K8s secret: `Configure Kubernetes clusters with specified Flux v2 Bucket source using local secrets`
+|Description  |Policy  |
+|---------|---------|
+|Flux extension install (required for all scenarios)     |  `Configure installation of Flux extension on Kubernetes cluster`       |
+|Flux configuration using public Git repository (generally a test scenario)     | `Configure Kubernetes clusters with Flux v2 configuration using public Git repository`        |
+|Flux configuration using private Git repository with SSH auth     | `Configure Kubernetes clusters with Flux v2 configuration using Git repository and SSH secrets`        |
+|Flux configuration using private Git repository with HTTPS auth     | `Configure Kubernetes clusters with Flux v2 configuration using Git repository and HTTPS secrets`        |
+|Flux configuration using private Git repository with HTTPS CA cert auth     | `Configure Kubernetes clusters with Flux v2 configuration using Git repository and HTTPS CA Certificate`        |
+|Flux configuration using private Git repository with local K8s secret     |  `Configure Kubernetes clusters with Flux v2 configuration using Git repository and local secrets`       |
+|Flux configuration using private Bucket source and KeyVault secrets     | `Configure Kubernetes clusters with Flux v2 configuration using Bucket source and secrets in KeyVault`      |
+|Flux configuration using private Bucket source and local K8s secret     | `Configure Kubernetes clusters with specified Flux v2 Bucket source using local secrets`        |
 
-To find all of the Flux v2 policy definitions, search for **flux**.
+To find all of the Flux v2 policy definitions, search for **flux**. For more information, see [Azure policy built-in definitions for Azure Arc-enabled Kubernetes](policy-reference.md).
 
 ## Prerequisites
 
 * One or more Arc-enabled Kubernetes clusters and/or AKS clusters.
 * `Microsoft.Authorization/policyAssignments/write` permissions on the scope (subscription or resource group) where you'll create the policy assignments.
 
-## Create a policy assignment to install the Flux exension
+## Create a policy assignment to install the Flux extension
 
 In order for a policy to apply Flux v2 configurations to a cluster, the Flux extension must first be installed on the cluster. To ensure that the extension is installed to each of your clusters, assign the **Configure installation of Flux extension on Kubernetes cluster** policy definition to the desired scope.
 
@@ -57,26 +59,24 @@ In order for a policy to apply Flux v2 configurations to a cluster, the Flux ext
 Next, return to the **Definitions** list (in the **Authoring** section of **Policy**) to apply the configuration policy definition to the same scope.
 
 1. In the "Kubernetes" category, select the **Configure Kubernetes clusters with Flux v2 configuration using public Git repository**
-built-in policy definition, or another policy definition from the list above.
+built-in policy definition, or one of the other policy definitions to apply Flux configurations.
 1. Select **Assign**.
 1. Set the **Scope** to the same scope that you selected when assigning the first policy, including any exclusions.
 1. Give the policy assignment an easily identifiable **Assignment name** and **Description**.
 1. Ensure **Policy enforcement** is set to **Enabled**.
 1. Select **Next**, then select **Next** again to open the **Parameters** tab.
 1. Set the parameter values to be used.
     * For more information about parameters, see the [tutorial on deploying Flux v2 configurations](./tutorial-use-gitops-flux2.md).
-    * When creating Flux configurations you must provide a value for one (and only one) of these parameters: `repositoryRefBranch`, `repositoryRefTag`, `repositoryRefSemver`, `repositoryRefCommit`.
+    * When creating Flux configurations, you must provide a value for one (and only one) of these parameters: `repositoryRefBranch`, `repositoryRefTag`, `repositoryRefSemver`, `repositoryRefCommit`.
 1. Select **Next** to open the **Remediation** task.
 1. Enable **Create a remediation task**.
-1. Verify that **Create a Managed Identity** is checked, and that the identity will have **Contributor** permissions.
-
-    For more information, see [Quickstart: Create a policy assignment to identify non-compliant resources](../../governance/policy/assign-policy-portal.md) and [Remediate non-compliant resources with Azure Policy](../../governance/policy/how-to/remediate-resources.md).
+1. Verify that **Create a Managed Identity** is checked, and that the identity has **Contributor** permissions. For more information, see [Quickstart: Create a policy assignment to identify non-compliant resources](../../governance/policy/assign-policy-portal.md) and [Remediate non-compliant resources with Azure Policy](../../governance/policy/how-to/remediate-resources.md).
 
 1. Select **Review + create**, then select **Create**.
 
-After creating the policy assignments, the configuration is applied to new Azure Arc-enabled Kubernetes or AKS clusters created within the scope of policy assignment.
+The configuration is then applied to new Azure Arc-enabled Kubernetes or AKS clusters created within the scope of policy assignment.
 
-For existing clusters, you may need to manually run a remediation task. This task typically takes 10 to 20 minutes for the policy assignment to take effect.
+For existing clusters, you might need to manually run a remediation task. This task typically takes 10 to 20 minutes for the policy assignment to take effect.
 
 ## Verify the policy assignment
 
@@ -91,7 +91,7 @@ For existing clusters, you may need to manually run a remediation task. This tas
 
 ## Customize a policy
 
-The built-in policies cover the main scenarios for using GitOps with Flux v2 in your Kubernetes clusters. However, due to limitations on the number of parameters allowed in Azure Policy assignments (max of 20), not all parameters are present in the built-in policies. Also, to fit within the 20-parameter limit, only a single Kustomization can be created with the built-in policies.  
+The built-in policies cover the main scenarios for using GitOps with Flux v2 in your Kubernetes clusters. However, due to limitations on the number of parameters allowed in Azure Policy assignments (max of 20), not all parameters are present in the built-in policies. Also, to fit within the 20-parameter limit, only a single kustomization can be created with the built-in policies.  
 
 If you have a scenario that differs from the built-in policies, you can overcome the limitations by creating [custom policies](../../governance/policy/tutorials/create-custom-policy-definition.md) using the built-in policies as templates. You can create custom policies that contain only the parameters you need, and hard-code the rest, therefore working around the 20-parameter limit.