Update AutoOps + ECK docs for removal of enterprise license requirement.

deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md

@@ -127,6 +127,42 @@ If any errors in the logs mention "authorization" or "unauthorized connection",
 :::{include} ../_snippets/autoops-allowlist-port-and-urls.md
 :::
 
+## Verify {{agent}} version meets license requirements
+
+```{applies_to}
+eck: ga 3.3.1
+```
+
+The minimum required {{agent}} version for the ECK installation method depends on your license type. If the agent version is below the minimum for your license, the `AutoOpsAgentPolicy` resource enters the `Invalid` phase.
+
+| License type | Minimum agent version |
+| --- | --- |
+| Basic | 9.2.4 |
+| Enterprise | 9.2.1 |
+
+:::::{stepper}
+
+::::{step} Check the policy status and version
+Run the following command.
+```shell
+kubectl get autoopsagentpolicy <policy_name> -o jsonpath='{.spec.version}{"\n"}{.status.phase}{"\n"}'
+```
+If the status is `Invalid` with a version-related message, {{agent}} does not meet the minimum version requirement for your license type.
+::::
+
+::::{step} Check your license type
+Run the following command to check your cluster's license type.
+```shell
+kubectl get configmap elastic-licensing -n <ECK_operator_namespace> -o jsonpath='{.data.eck_license_level}'
+```
+::::
+
+::::{step} Upgrade {{agent}}
+Based on your findings in the previous steps, upgrade {{agent}} to the appropriate version.
+::::
+
+:::::
+
 ## Check cluster health
 
 Ensure that the {{es}} clusters you are trying to connect to AutoOps are healthy. {{agent}} may fail to connect clusters in a Red state.

deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md

@@ -25,6 +25,7 @@
 * [My organization's firewall might be preventing {{agent}} from collecting and sending metrics.](#firewall)
 * [{{agent}} is failing to connect because it doesn't recognize my SSL certificate.](#custom-cert)
 * [I went through the wizard with {{ECK}} (ECK) as my installation method, but I can't view any connected clusters in my account.](#eck-no-clusters) {applies_to}`eck: ga 3.3`
+* [My `AutoOpsAgentPolicy` resource entered the `Invalid` phase after a license change.](#invalid-phase-license-change) {applies_to}`eck: ga 3.3`
 
 $$$single-cloud-org$$$**I’m trying to create a Cloud organization, but I’m already part of a different one.**
 :   :::{include} /deploy-manage/monitor/_snippets/single-cloud-org.md
@@ -52,6 +53,11 @@
 $$$eck-no-clusters$$$**I went through the wizard with {{ECK}} (ECK) as my installation method, but I can't view any connected clusters in my account.** {applies_to}`eck: ga 3.3`
 :   Refer to [](/deploy-manage/monitor/autoops/autoops-sm-troubleshoot-eck-no-clusters.md) to diagnose and resolve common issues.
 
+$$$invalid-phase-license-change$$$**My `AutoOpsAgentPolicy` resource entered the `Invalid` phase after a license change.** {applies_to}`eck: ga 3.3`
+:   The [minimum required {{agent}} version](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites) for the ECK installation method depends on your license type. Enterprise licenses require agent versions 9.2.1 and later, and Basic licenses require versions 9.2.4 or later. If your license is downgraded from Enterprise to Basic and your agent version is between 9.2.1 and 9.2.3, the policy will fail validation and enter the `Invalid` phase.
+
+    To resolve this issue, upgrade {{agent}}.
+
 ## Run the AutoOps Connectivity Check
 
 Run the [AutoOps Connectivity Check](../autoops/autoops-connectivity-check.md) to test your system and diagnose any issues that might prevent you from connecting your cluster to AutoOps.

deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md

@@ -30,6 +30,14 @@ Ensure your system meets the following requirements before proceeding:
 * Your cluster is on a [supported {{es}} version](https://www.elastic.co/support/eol) (7.17.x and above).
 * The agent you install for the connection is allowed to send metrics to {{ecloud}}.
 * {applies_to}`eck: ga 3.3` To install {{agent}} using ECK, your ECK operator is on version 3.3.0 and above.
+* {applies_to}`eck: ga 3.3.1` The instance of {{agent}} you install meets the version requirements for your license type:
+  * **Basic license**: 9.2.4 or later.
+  * **Enterprise license**: 9.2.1 or later.
+
+:::{important}
+:applies_to: { eck: ga 3.3.1 }
+If your ECK-managed cluster's license is downgraded, you must upgrade {{agent}} accordingly to avoid your `AutoOpsAgentPolicy` resource becoming invalid.
+:::
 
 ## Connect to AutoOps [connect-to-autoops]
 

deploy-manage/monitor/autoops/ec-autoops-faq.md

@@ -103,7 +103,7 @@ $$$deployment-types$$$ **Which deployment types can be connected to AutoOps thro
 :   You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment, both on-premise and in private cloud environments.
 
 $$$maintenance$$$ **Do I have to do any maintenance when using AutoOps for ECE, ECK, or self-managed clusters?**
-:   AutoOps is a cloud service, so you don't need to upgrade it yourself. However, we recommend keeping {{agent}} upgraded to the latest version so you can access new features and fixes. 
+:   AutoOps is a cloud service, so you don't need to upgrade it yourself. However, when using the ECK installation method, make sure your instance of {{agent}} meets the [version requirements](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md#prerequisites) for your license type. In general, we recommend keeping {{agent}} upgraded to the latest version so you can access new features and fixes.
 
 $$$support$$$ **What kind of support is available to me when using AutoOps for ECE, ECK, or self-managed clusters?**
 :   Support eligibility is determined by the license of your connected cluster: