diff --git a/cmd/netassert/cli/root.go b/cmd/netassert/cli/root.go
index 199af2b..3f2f2f2 100644
--- a/cmd/netassert/cli/root.go
+++ b/cmd/netassert/cli/root.go
@@ -19,11 +19,11 @@ var (
 var rootCmd = &cobra.Command{
 	Use:   "netassert",
 	Short: "NetAssert is a command line utility to test network connectivity between kubernetes objects",
-	Long: "NetAssert is a command line utility to test network connectivity between kubernetes objects. " +
-		"It currently supports Deployment, Pod, Statefulset and Daemonset. You can check the traffic flow between these objects or from these " +
-		"objects to a remote host or an IP address.",
+	Long: "NetAssert is a command line utility to test network connectivity between kubernetes objects.\n" +
+		"It currently supports Deployment, Pod, Statefulset and Daemonset.\nYou can check the traffic flow between these objects or from these " +
+		"objects to a remote host or an IP address.\n\nBuilt by ControlPlane https://control-plane.io",
 
-	Version: fmt.Sprintf("\nNetAssert by control-plane.io\n"+
+	Version: fmt.Sprintf("\nBuilt by ControlPlane https://control-plane.io\n"+
 		"Version: %s\nCommit Hash: %s\nBuild Date: %s\n",
 		version, gitHash, buildDate),
 }
diff --git a/e2e/README.md b/e2e/README.md
index db6dc22..906c31f 100644
--- a/e2e/README.md
+++ b/e2e/README.md
@@ -55,3 +55,17 @@ Run the tests using the following command:
 ```
 
 Tests can be configured by updating values in [end-to-end test helpers](./helpers/)
+
+## Azure AKS Integration
+
+Currently, end-to-end testing of NetAssert with Azure Kubernetes Service (AKS) is not scheduled. However, we do not foresee any architectural reasons that would prevent successful integration.
+
+### Network Policy Support
+There are [three primary approaches](https://learn.microsoft.com/en-us/azure/aks/use-network-policies) for supporting network policies in AKS.
+
+If the requirement is limited to **Linux nodes only** (excluding Windows), the recommended solution is [Azure CNI powered by Cilium](https://learn.microsoft.com/en-us/azure/aks/azure-cni-powered-by-cilium).
+
+### Deployment via Terraform
+For deploying a testing cluster, the Container Network Interface (CNI) configuration appears straightforward. It can likely be handled via a single parameter in the `azurerm` provider, specifically the [`network_policy` argument](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/kubernetes_cluster#network_policy-1). 
+
+*Note: This Terraform configuration has yet to be validated.*
\ No newline at end of file